The Empty Load Notebook: The Number Nobody Counts in Indian Fast-Bowling Injury Reporting

The Empty Load Notebook

The folder was called load_notes. Eleven subfolders. Ten of them held not a single row. The eleventh held a 2026 spreadsheet — 126 deliveries, and against each delivery a release point, a seam position, a run-up length, and the day's overs total. The same sheet I pulled together seven years ago from Ahmedabad, when a Gujarat seamer bowled 47.2 overs across three Ranji innings in nineteen days, and I wrote up a side-strain risk two weeks before he left the field. Not by reading the post-match press conference. By reading the mechanics.

The other ten folders were empty. Zero bytes. No title, no source, no publication date, no format — Test, ODI, T20, The Hundred — and no player's name. One file still carried the template instruction, "identify from the information points above," while the information points were nowhere to be found.

Has a physio ever handed you a blank sheet? One has handed me one. The answer is always the same: "He's fine." That is the most dangerous sentence in journalism, because it closes the inquiry. And a closed inquiry does not lie — it simply goes quiet. Faced with that empty file, I had the usual options: invent a name, a scoreline, a scene; or write down that the sheet is blank. The second option is read less. I am taking it, and it is the most interesting part of the whole business.

Context: Why the notebook existed

In 2026, at 43, when I started this injury vertical out of Ahmedabad, I had fifteen years on the cricket beat and one plain stubbornness: no fitness story files without three load indicators. The stubbornness came from method rather than from the profession. Covering Australian domestic cricket in the 1990s, I had watched bowling being costed like work — spell length, rest between spells, season overs. In India at that time, injury was written as fate and comebacks as courage.

Two Saurashtra coaches asked for that 2026 sheet. Eighteen thousand people read the post. But a year later I understood that the sheet's value was never in its conclusion; it was in its method. Russia 2026 was running — 64 matches, 736 players, 14 June to 15 July 2026 — and a digital desk asked why 23-man squads were breaking. I compared those 64 matches and 736 players against the Indian Premier League 2026's 60 matches (7 April to 27 May 2026), built a load-spike table from fourteen medical papers, and missed the deadline by ninety minutes. The piece drew 46,000 reads. Since that day every injury piece carries a tournament-density box, and my phone carries a shared calendar of 21-day and 28-day turnarounds.

Here I have to disclose access, because this piece rests on it. The NCA and several franchise staff are colleagues to me, not subjects. What I have seen has sometimes arrived off the record; what I have been given has always arrived with conditions. What I have counted myself is the only thing I can write without conditions.

And now this file, which came back empty. Not one information point. No format, no player, no team, no league, no date. That does not mean nothing happened in cricket. It means that anything I presented as a cricket fact would be my invention. An injury decoder's entire trade rests on being able to show the notes. When there are no notes, there is one honest route — make the blank sheet itself the story.

Core: Four indicators, and a translation that breaks

Injury incidence in Indian fast bowling is manufactured mainly by the calendar, not by character — and the calendar is drawn by people who never have to bowl the fourth spell. I wrote that sentence in 2026 and every season since has sharpened it. The IPL window, the World Test Championship cycle and the Ranji fixture list are built on three different logics, and all three land on the same bowler's ankle. When someone says a bowler is "fragile," my first question is: how many overs in the last 28 days, split across how many spells, with how many days between them.

So four things are mandatory on my sheet. First, overs in the last 7, 14, 21 and 28 days, separately. Second, the number and length distribution of spells; "he bowled 22 overs" is a sentence, "he bowled three spells of 9, 4 and 9" is a risk profile. Third, the days between competitive bowling bouts — and here the Indian domestic calendar is the most culpable, because a Ranji match can end and the next begin four days later. Fourth, delivery-level intensity markers, or a plain admission that they do not exist. The fourth indicator is the hardest to obtain and the one that matters most.

This is where the real problem of translation begins. Fatigue does not read the fixture list, so I translate it from football into cricket — and the translation does not always survive. Football's monitoring vocabulary — acute:chronic ratios, high-speed running, sprint load, GPS-derived total distance — comes from a low-impact, high-distance sport. Bowling is the inverse: wrapped in three kilometres of jogging, but containing 120 high-impact landings, each carrying several times body weight, each adding an extension-rotation load to the spine. GPS will tell you he ran eight kilometres. It will not tell you he braked 132 times. A metric that measures distance cannot see the thing that is not distance.

My relationship with the acute:chronic ratio is tense for exactly this reason. It is my native analytical language, absorbed on the Australian state beat, and it sounds authoritative to a cricket audience. But the ratio has its own mathematical weaknesses: numerator and denominator are coupled, the relationship is not linear, and the "above 1.5 is danger" threshold is as validated in cricket as it is in a football squad — which is to say, not validated. I name it every time, because the metric I import as a tool is actually a claim still under test.

My way out of that translation crisis is cheap and unglamorous: I stopped asking who got hurt and started asking what changed seven days earlier. It sounds minor; it redirects the entire analysis. "Who got hurt" has a name for an answer, and behind every name there is a story already written. "What changed seven days earlier" has a comparison for an answer — how his spells were split in this match, what differed from the last one, whether the run-up length moved, whether the release point dropped.

From my own watching, I have seen this most often at the ground in Ahmedabad — the half-foot drop in release point in the third spell, recorded nowhere on the scorecard. No bowler becomes quick suddenly and none becomes slow suddenly; he negotiates with his body gradually, and every negotiation produces a small compensation. That is my least credible and most reliable finding: the bowler who looks freshest on the sheet is often the one already compensating. Because he has been pulled from a spell, because he is hiding it, because the sheet counts overs and not effort.

I went back through three seasons of load notes, and the pattern was embarrassingly simple. Which is precisely where I have to distrust myself. Three seasons of notes over twelve subjects will always yield a pattern, and hindsight will always manufacture a tidy culprit. The pattern that looked embarrassingly simple may simply have been the one that fit. So I keep a rule: write the hypothesis before the next dataset, publish the sample size, and publish the misses.

And then the thing all this arithmetic points at. Every injury has a denominator, and the interesting part is who chose not to count it. An injury count on its own is meaningless; it means something only when you can say how many bowlers, over how many overs, across what window took that risk. In Indian cricket the denominator is almost never public. We are told two bowlers broke down; we are not told how many fast bowlers bowled how many overs that season. Without a denominator, every injury story becomes an anecdote — and anecdotes never become data.

In the women's game the problem is newer and sharper. The Women's Premier League began in March 2026. Before it, this cohort had no long, continuous record of domestic and international bowling loads. Now a group with no historical baseline is being asked to absorb a workload nobody has modelled. I do not have the benchmark, and I say so — where a cohort has no history, the very definition of "normal load" is absent. This is my least fashionable point and I think the most necessary: the estimates we argue about in the men's game at least come from old data. Here even that is missing.

The contrarian angle: the empty file is a design, not a scandal

This is where I have to drop my easiest story. The first reaction to an empty file is that someone is hiding something — a board, a franchise, a system. I do not dismiss that reaction entirely, but it is too cheap. The absence of public load data is not a conspiracy; it is an incentive structure: injury information is competitive information. A franchise that knows its fast bowler will not return for four weeks does not tell the team that will bid for him at next year's auction. That secrecy is rational. The problem is that public analysis pays the bill.

And the real contrarian point is that the demand is ours. Media sells the comeback story, not the durability story. "He dragged himself to the crease" is a line that sells; "he bowled 214 overs this season and never exceeded nine in a spell" does not. When readers ask for the romance of the return, the system manages its data accordingly. We are the customers of the blank sheet, and then we are offended that it is blank.

One more thing becomes visible here, the oldest habit of my trade: the word "freak." The moment someone says it was a freak injury, the inquiry is over. I have never seen an injury without an antecedent — a raised run-up, a changed action, a block of three matches in four days, a new pair of shoes, a weight-management cycle. "Freak" is not a description of an injury. It is a refusal to describe one.

Where this goes: the checklist as an act of care

In that lockdown film room, with grounds shut and only archive running, I learned that a checklist can be an act of care. Screening rituals, pre-habilitation, boring repetition — durability lives there, not in the sentiment of a press conference. Indian cricket still romanticises the culture that says "he'll tough it out," and that culture is the injury factory it pretends to despise. Bowlers who are fastidious are not fragile. They are available.

Three things go into my own account for the road ahead. First, the hypothesis gets written before the next dataset, and the data that refuses it gets the same space as the data that supports it. Second, the public injury log for Gujarat's seamers continues, so my calls can be checked — some of what I have written has already been wrong, and that stays up too. Third, three load indicators remain mandatory for any fitness story; if they cannot be found, I will write that they could not be found.

The file is still empty. The question is not what was in it. The question is whether the next time a bowler begins his run-up for a fourth spell, the number for that day is already written on his sheet — or whether we file another paragraph praising his courage and close the empty folder again.