Overs Written in the Notebook: The Invisible Workload Ledger of Ranji Trophy's Fast Bowlers

I begin with a verified number: 47.3 overs in nine days.

It was the final session of day three at the Vidarbha Cricket Association Stadium in Nagpur. The stands were close to empty — six or seven spectators in the western block, none on the north side. Which is why the sound carried. The crackle of dry grass under spikes, then the thud as the front instep landed at the crease. That bowler was his team's only fully fit quick. Going into his nineteenth over of the innings, he stopped, pressed a hand to his knee, and stood there for three or four seconds. The ball boy took his time bringing the ball back because it had gone past fine leg, where a grass-cutter was parked. None of that delay appears on a scorecard. It appears in my notebook.

Here is why the number matters. Nine days earlier he had played in another state, followed by a fourteen-hour train, followed by a first-class match. Across the two games, 47.3 overs. Eleven of those came in one unbroken spell from the same end, in 21-degree heat, on a slow outfield. Nobody was counting any of it, because the Ranji Trophy scorecard tells you who took wickets and who made runs. It does not tell you who paid.

I started counting overs because overs are the only currency a domestic bowler spends every single day, and nobody asks for a receipt.

The calendar itself manufactures the load

The Ranji Trophy now has 38 teams: 32 in the Elite groups, six in the Plate. The season opens in September-October with the Duleep Trophy and the Irani Cup. The Duleep Trophy uses four squads — India A, B, C and D — so it is only three or four matches, but they fall at the very start of the season, when last year's fatigue has not fully cleared. Then the marathon begins: back-to-back group games, four and five days each, with gaps of three to five days.

That gap is the deception. It reads as rest. In practice it contains a train or a flight, a hotel change, a preparation session, a physio slot, and a day on which the quick is asked for four overs in the nets. I have twice in ten years watched a side field three fast bowlers of whom none was fully fit, and all three played, because there was no alternative.

Vidarbha and Kerala are useful examples. Domestic success comes from continuity, and continuity means loading the same seven or eight bowlers into every fixture. Vidarbha won the 2026-25 Ranji Trophy; Kerala reached their first final. Both leaned heavily on spin — bowlers of the Harsh Dubey, Aditya Sarwate and Jalaj Saxena mould bowled long spells right through the season. Spinners bowl more overs, but the physical cost is a different shape, and that is not recorded either.

The problem is still sharpest with the quicks. A spinner can bowl 25 overs on the trot. A fast bowler cannot. Physiology does not negotiate.

First innings, second innings: one bowler, two energy budgets

The most useful split in my notebook is simple: overs by innings, plus a session count. In a first-class match, a seamer bowls roughly 14 to 18 overs in the first innings. In the second, usually six more. In between sit the fielding days — jogging in from slip or third man, chasing to the boundary, standing for entire sessions with knees flexed, tracking the batsman's line. Those fielding minutes never enter a ledger, yet they decide where his stump-to-stump line sits in the second innings.

There is a direct tactical consequence that typically goes unadded: the follow-on. When a captain enforces it, he is asking his lead quick for another 18 overs in the second innings after 17 in the first. Plausible on paper, not on a body. I have watched many matches where a follow-on was enforced and the side's premier fast bowler either missed the next fixture or turned up at half pace.

Pitch behaviour shifts the arithmetic too. In October the soil is soft, the ball comes on slowly, bounce is low, and the seamer has to hit the deck repeatedly — more physical cost. By December and January the surface dries, seam diminishes, but reverse swing demands an older ball, which stretches spells. January in Nagpur is not November in Rajkot, so a season-long 'average overs' figure misleads.

Before I write a report I read four documents: the scorecard, the medical note, the travel itinerary, and the wicketkeeper's count of catches taken standing up. If the four do not agree, I do not publish the number.

That habit is old. In 2026, while still at school in Mumbai, I volunteered as a data logger for the Mumbai City FC under-18 side and attended 42 training sessions, recording RPE, sprint counts and sleep hours for 23 players. The coach ignored my first report. So I re-watched every session tape and rebuilt it as a one-page table — because a number placed correctly changes a decision, while a story does not. In cricket the rule is stricter, since the resource is the human body, and nobody wants to be the one who puts a body on a spreadsheet.

Travel: the least acknowledged column in Ranji

Bengal to Gujarat, Gujarat to Kerala, Kerala to Vidarbha. Across a Ranji season a side will use eight to ten hotels during the group phase alone. These teams are not flying charters; they are on buses and trains. Six consecutive hours seated on a bus means stiffness pooling around a capsule. That is why many experienced domestic bowlers do not bowl in the pre-match net at all, and only run. Watched from outside, it looks lazy. It is not laziness.

I began logging this because nobody else was. In 2026, during the shutdown, I worked as a remote data intern with Mumbai City FC across the Indian Super League season in Goa, logging all 20 matches — 11 clean sheets, 24 goals, 62 per cent average possession. The stadiums were empty, so attention went to bench communication, ball-boy delays and the sound of boots on wet turf. That habit transferred to empty Ranji grounds. The stadium was empty, so the notebook got loud — you hear which bowler shakes his head, which slip fielder shifts his feet, and the moment a captain refuses to hand the last over before tea to anyone but his strike bowler.

The outside reading points at the wrong target

The consensus since November 2026 runs roughly like this: franchise T20 workload is the root cause of Indian fast-bowling injuries. My notebook disagrees. In a T20 league a quick bowls eight to twelve matches a month at four overs each — 40 to 48 overs, delivered in four-over chunks, two days apart, on good pitches, with air-conditioned dressing rooms and full-time physios. In a month of Ranji he bowls 65 to 80 overs across four or five first-class games, in six-to-eight-over spells, on a surface that crumbles on day four, with a physio who is also looking after twenty-seven other players.

The issue is different: T20 is the visible part, the part people can count. The real cost is invisible — delayed flights, pitch wear, three spells in one innings, and a captain asking a single question each morning: who bowls today? The side with one fit quick will overuse him. That decision gets made in an empty stadium, never in front of a broadcast camera.

One explanation I accept, and it is certainly incomplete: domestic cricket's paper trail is fragmented. The BCCI's NCA tracks a handful of contracted players, state associations track their own way, franchises track separately. The three records do not reconcile.

Against the County Championship: more matches, more rest, better records

An English county plays fourteen first-class matches, four days each, roughly one a week — but with three or four days between fixtures, short domestic travel, and a permanent strength-and-conditioning staff at nearly every club. In India, Ranji offers fewer matches but far more travel and often shared S&C personnel. A county seamer bowls 400-plus overs in a season; the Indian average is much lower. Indian fast bowlers still break more often.

Which means the problem is not volume. It is management. In county cricket there is a protocol for putting a bowler back together after four days, there is space, there is rest leave. In Ranji that discipline depends on individual conscience and a state association's budget. This is not a difference of comfort. It is a difference of data.

The next internal signal

I will not let this piece land on a verdict, because the sample is small and a large share of my data lives inside one notebook. But three things are worth watching over the next six months. First, whether anyone imposes an over cap on the international bowlers returning in the Irani Cup and Duleep Trophy. Second, whether the BCCI's pre-IPL workload bulletin starts reflecting domestic overs — so far it lists matches, not overs. Third, whether the states still leaning on a single fit quick are building a second-spell alternative.

Last week I sat in another empty stadium. In the first session the ball changed the bowler six times — a stump-to-stump plan that no scorecard will ever carry. It went into the notebook. Whether anyone reads it, I still do not know.

The rhythm broke before the scoreline did. That is the truest sentence about a domestic season, and the least written.