Fast Bowling Workload | The Cricket Physio

Written by: Thihan Chandramohan, physiotherapist
Category: Fast bowling
Last reviewed: 18 September 2026

The claim worth being careful about

"Bowling workload causes injury" is repeated so often that it has stopped being examined. It is too simple to be useful.

Bowling load is one input among several, and it interacts with the others. The same twenty overs land differently on a bowler who slept badly for a week, travelled on Friday, is coming back from a hamstring injury, or is sixteen and growing. Treating overs as the whole story produces the sort of management that restricts a fit bowler and clears a tired one.

What load monitoring does well is narrower and still valuable: it tells you what has happened, which is the part everyone is otherwise guessing at.

Three things that matter more than the total

1. Change, not volume

A bowler comfortable at twenty overs a week is not in danger at twenty overs a week. The same bowler going from five to twenty is in a different position. Risk sits in the rate of change more than in the absolute number.

2. Distribution

Twenty overs spread across three sessions is not twenty overs bowled in two days. Cricket schedules produce the second pattern often: a long gap, then a tournament.

3. What is not counted

Net overs, warm-up bowling, throwdowns, extra spells at training. Most systems record matches. Most bowling happens outside them.

What to record

The best system is the one people keep filling in. For most squads that is four columns:

Date
Balls or overs bowled, matches and nets both
Intensity, a simple one to ten for how hard it was
Soreness the next morning, one to ten

Four columns, filled in honestly for a season, beats a performance platform used for six weeks. Start there and add only what you find yourself wanting.

The Bowling Workload Tool

A mobile-first tool for logging bowling exposure, planning sessions and noticing patterns in load and soreness over a season. It does not predict injury and does not claim to. It shows you what you have bowled.

Basic ball-count logging and workload trends are free. Memberships add soreness monitoring, alerts, dashboards, return-to-bowling tracking and, depending on the level, a clinician reading it.

Start tracking your bowling

Fast bowling
Return to bowling
Getting from cleared to a full match spell, one variable at a time.Reviewed 18 Sep 2026

For coaches

The most useful thing a coach does with workload data is not a restriction. It is a conversation earlier. Bowlers under-report. If the numbers give you a reason to ask on Tuesday rather than finding out on Saturday, the system has paid for itself.

Common questions

What is a safe number of overs?

There is no single number that transfers between bowlers. Guidelines for junior cricket give useful ceilings by age, and they are worth following. Beyond that, the question worth asking is not how many overs but how the number compares to what this bowler has been doing recently.

Is the acute to chronic workload ratio still useful?

As a way of thinking, yes: what you did this week against what you have been doing for the past month. As a precise number with a threshold that predicts injury, the method has been criticised on statistical grounds and should be treated with caution. Use it to notice change, not to make decisions on its own.

Do net overs count?

Yes, and leaving them out is the most common gap in cricket monitoring. A bowler who bowls six overs in a match and twelve in nets has bowled eighteen.

What about intensity?

Overs on their own miss it. Six overs bowled flat out is not six bowled off a short run in a warm-up. Recording a simple intensity rating alongside volume gets you most of the way.

Is low workload safe?

No. Long gaps reduce tolerance, so the load that was previously fine is no longer fine on return. Both ends of the range carry risk, which is why a return after a break needs building up rather than resuming.

Bowling workload