The Empty Column: Why Indian Cricket's Injury Register Has Never Been Filled

On 11 April, at 9:40 pm, a three-line bulletin arrived in a state association's media group. The first line carried a fast bowler's name. The second said "unavailable". The third said "reason not specified". No body part, no date of onset, no return window, and no tag saying which format the diagnosis applied to. I opened the spreadsheet, added a row, and left column seventeen — expected return — empty again. That night I had sixty-eight such bulletins. Not one of them said which format the injury belonged to.

Where the counting began

Thirty-two matches. Chennai, 2026. I was a statistics student volunteering in the scorer's box of the Tamil Nadu Premier League, logging every bowler's spell, rest interval and injury stoppage by hand. Seven bowlers had delivered more than 120 balls in fourteen days. Two later withdrew from local cricket with shoulder and ankle complaints. A Chennai digital editor used the sheet for a 900-word pace-load explainer — my first paid cricket piece. That season the press box held two women. I learned that the answer to bias is a count, not a speech.

In 2026, with no live cricket, I collected fourteen Tamil Nadu injury and illness notices and matched them against eight Ranji Trophy scorecards. Five soft-tissue absences fell within eleven days of three-day turnarounds. Empty stadiums did not reduce the injuries. They only removed the noise around them. In 2026 I coded twenty-nine frontline fast bowlers across all sixty IPL matches. Twelve had bowled more than 24 overs in the India leg; that group produced seven soft-tissue absences after the UAE restart on 19 September. I published the workload table, not the alarm.

A document that exists but carries nothing

For this audit I hand-coded sixty-eight public team bulletins between 1 January 2026 and 31 March 2026 — forty-one first-class team sheets and twenty-seven IPL match-day squad updates — against seventeen fields. Thirty-seven named no body part. Fifty-one gave no date of onset. Five gave a return window. The format tag numbered zero out of sixty-eight. I recoded that column three times, assuming my definition was wrong. It returned zero each time. Nineteen entries used "niggle" or "workload management", which are administrative words, not clinical ones. Six entries were the single word "unavailable" — an empty row that parsed as valid because no field raised an error.

This is not a low-information article. It is an absent document. A structurally valid null record is more dangerous than silence, because it licenses every downstream conclusion while supplying no basis for any of them. A bulletin without a format tag is the domestic version of the same failure: the diagnosis arrives, the context does not.

Format is the first question, not the last

Metrics do not travel across formats. A Test offers two new balls, session-by-session attrition and five days of mental cost. A T20 separates powerplay from death overs, where every ball demands maximum effort. Ranji's three-day turnaround exists nowhere else. Without a format tag, "overs per week" is a number without a unit. So when a panel says a bowler is out under "workload management", I read a blank field, not a finding. The label is the question.

The calendar is the injury

The Indian domestic structure runs four-day gaps in the Ranji group stage with a travel day inside them, then the Syed Mushtaq Ali and Vijay Hazare blocks, the Irani Cup, and a two-month IPL window. A fast bowler's year splits across three formats, two climates and a great deal of rail travel. Compare a system with a genuine off-season and an open door to overseas T20 leagues for offloading overs. India's board does not issue full-season no-objection certificates to contracted players. In a system with no release valve, every injury will look sudden.

Jasprit Bumrah was out from September 2026 to August 2026 with a back stress fracture and left the Sydney Test in January 2026 with back spasms. Mohammed Shami finished the 2026 World Cup with an ankle problem, had surgery in February 2026, and missed both IPL 2026 and the T20 World Cup. Prasidh Krishna's comebacks slipped more than once. I name them not because their bodies are weak but because the same question sits in front of all of them: in the fourteen days before the breakdown, how many overs, in how many spells, in which format, with how many travel days? The scorebook does not explain the injury. It only tells you where to start looking.

Three years of the Impact Player

I waited thirty-eight matches before coding all seventy-four games of the 2026 season. Of 128 Impact Player uses, only 19 were injury-related. Batting totals rose; bowling workload did not fall. The rule changed the shape of the game, not the load on the bowler.

The contrarian turn

The easy conclusion is that India needs a central injury register and the problem is solved. I agree with half of it. A register is an administrative fix before it is a clinical one, and the bottleneck is administrative. The NCA and team physios hold the data; it never reaches a public form, so outside analysts always start from the absence notice — and the absence notice carries a bias. I can only count what someone wrote down. The bowler who played through pain and never withdrew is invisible in my dataset.

The second uncomfortable point: more data is not automatically better. A register without dates, format tags and return windows produces confident nulls. And the thresholds I inherited — 200 overs a season, four-day gaps, a clean off-season — are Australian artefacts. Applying them to Chennai humidity and Ranji rail travel is a category error, and the day I borrow a threshold I should say out loud that it is borrowed.

What a one-page bulletin would look like

Player. Format. Body part. Date of onset. Overs and spells in the previous fourteen days. Expected return window, even if estimated. Source, named. Seven lines, every week. Then the next time a fast bowler breaks, we will have two questions — what shape was his body in, and what shape was his calendar. Right now we have no instrument for the second, which is why every argument collapses into the first. Availability is a statistic. It has simply never been printed in the same font as goals.