How to track cricket net sessions (bowlers): a simple repeatable system

If it is not repeatable, it is not tracking - it is storytelling

Net sessions are messy: multiple bowlers, time pressure, bad light, and coaches who are also human. A tracking system has to be **lightweight** or it will not survive Saturday morning.

Before the session (2 minutes)

• Decide **what you are measuring** this week: peak, average, dispersion, or workload
• Pick **camera or radar placement** and mark it (tape on floor, phone tripod spot)
• Align on **spell length** and rest rules for the group

During the session

• Start capture **after** warm-up when bowling is representative
• Log **deliveries continuously** rather than cherry-picking highlights
• Note **conditions** in one line (indoor/outdoor, ball type) if your app does not store it

After the session (5 minutes)

• Review **session average vs peak** and whether late-spell drift appeared
• Pick **one** adjustment for next week
• If you coach multiple athletes, snapshot each player's trend line

For academies: standardize one workflow

Programs win when every coach uses the **same capture SOP**. If each lane does something different, your database becomes noise.

Share a one-page SOP: device position, who starts/stop recording, and how debriefs run.

Software that fits nets

Look for guided setup, delivery segmentation, and confidence cues. Crickmatic targets exactly that environment - see For coaches and request access for organizations.