The Empty Column: Indian Cricket's Injury Problem Is an Accounting Problem

I opened the file and the first field was empty.

No title. No source. Not a single line in the information-point list. The document I was supposed to use for an article on a fast bowler's injury had been delivered to me as a shell — nothing inside it. The editor's message sat alongside: "Needed by Monday evening."

I left the file open for two days. Wrote nothing. It would have been easy to write that a particular bowler's body is fragile, that another's mechanics have collapsed, that a third was 'rested under workload management.' Television panels do this every night. But I did not have one verifiable line, and in thirteen years I have learned that the most dangerous thing on the day you have no data is your own understanding.

On the third day I realised that the failure I was treating as mine was actually the story.

India's fast-bowling injury debate repeats every season and stalls in the same place every season. The cricketer's body becomes the subject of the argument; the cricketer's record never does. The team bulletin says 'rested.' The newspaper says 'injured.' The commentary box says 'his body isn't holding up.' These are not three descriptions of one event. They are three different evidentiary statuses, and calling them by one name is the mistake we make every time.

'Rested' and 'unavailable' are not the same thing, and that is the root of the whole argument.

Injury information in cricket travels on three channels at three different speeds. First, the board or team's official bulletin — slowest and shortest. Second, the coach's or captain's answer at a press conference — fastest and least reliable. Third, the player's actual record: how many days he spent off the field, how many overs he bowled, which format he returned in. My method is direct: read the third channel first, and use the first two only to confirm it — never the reverse.

I trust the minute log more than the press conference, and the minute log has never lied to me.

When you start counting appearances instead of statements, the picture changes. A bowler 'rested' for three weeks under workload management is, in the record, a three-week gap — and the reason for the gap is nowhere in the bulletin. If the reason is not recorded, you cannot know whether that rest was treatment, precaution, or an administrative arrangement to stay out of domestic cricket. And if you cannot know that, then whatever you say about his next injury is a guess.

This is the real crisis in Indian domestic injury surveillance: it looks medical and it is administrative. The National Cricket Academy sits in Bengaluru; the rehab facilities exist; the sports-science staff exist. What does not exist is a public, standardised availability register with four distinct columns per player: unavailable (injury), rested (scheduled), managed (capped load), and fit-but-not-selected. Four columns. That is all. If those four columns were published, half of the last decade's cricket journalism would have to be rewritten.

I still have a ledger from thirty-two matches.

In 2026, while studying statistics in Chennai, I volunteered in the scorer's box at Chepauk for the Tamil Nadu Premier League and hand-logged all thirty-two matches — every bowler's spell, rest interval, and injury stoppage. I had no software. One register, two pencils, a calculator. I kept the commentary muted, because commentary tells you what happened; the register tells you how often.

Seven names in that register had bowled more than 120 balls in a fourteen-day window. Seven, out of a population of thirty-two matches. Two of them withdrew from local cricket a few months later, one with a shoulder complaint, one with an ankle. No official bulletin came. No medical report was published. What came was a notice that they were not playing.

I wrote down all thirty-two of them by hand, and the pattern only showed up in the last column.

The last column said 'days of rest.' It taught me the thing that has held up for a decade: overs do not cause injury; the collapse of the gap between them does. Five of my seven had less than four days between consecutive spells. The count was high and the gap was lower still — and the gap is the thing that never appears on a scorecard.

There were two women in that scorer's box that season. I was one of them. Nobody asked my opinion, so I let the numbers answer. The habit never left.

Three years later, in 2026, the grounds were empty and there was no cricket.

I was a junior writer on a Chennai sports desk. I collected fourteen Tamil Nadu team notices — injury and illness unavailability — and pulled eight Ranji Trophy scorecards from 2026-20. Twenty-three documents in total. There was no spreadsheet, so I built one.

Five soft-tissue absences clustered within eleven days of matches that had three-day turnarounds. Five out of twenty-three. The n is small, and I am saying so now, because fourteen notices and eight scorecards point to a pattern, not to a mechanism. What matters more is what I did not write that year: I published no speculative piece. I built an internal availability table and used it when cricket returned to empty stadiums.

Empty stadiums did not reduce the injuries. They only removed the noise around them.

I repeat this because many people drew the opposite conclusion in 2026. Empty stands, no crowds, no pressure — therefore fewer injuries. They did not fall. Crowds do not create injuries. Calendars do. And the calendar was the same in 2026, and in 2026 it took its revenge.

Fourteen absence notices arrived before anyone thought to build a table.

The lesson of the sixty-match IPL is that you must count the bowler's denominator before you count his overs.

In 2026 I was on a national sports desk. The IPL's India leg, the suspension on 4 May 2026, the resumption in the UAE on 19 September 2026. More than four months in between.

After the suspension I reviewed all sixty matches and coded the spells of twenty-nine frontline fast bowlers. Twenty-nine was my population. I logged the start and end of every spell, the breaks inside spells, and — most importantly — every bowler's total overs in the India leg.

Twelve bowlers had delivered more than twenty-four overs in the India leg. After the UAE restart, that group produced seven soft-tissue absences.

Here I have to stop, because this is where the easiest lie gets told. Seven out of twelve. Not seven out of seven. And twelve out of twenty-nine. When someone says 'congestion causes injury,' they collapse three rows of a table into one sentence, and the error is in the collapse. The direction of the correlation is not clean — did the extra overs cause the injuries, or were the bowlers who bowled the extra overs the same ones whose teams depended on them most? That is a selection effect, and I refuse to hide it.

I published a match-by-match workload table that season rather than the simple congestion line. Editors noticed the caution. Readers did not. Readers want a simple cause and they are entitled to one — but a simple cause is a lie until you have counted its denominator.

Here is the thing I did not write then and should have. Every injury number published about Indian fast bowlers is published without a denominator.

That sentence is the spine of the whole subject. An injury is a numerator. A numerator means nothing without its denominator. 'Seven fast bowlers were injured this season' is a meaningless sentence, because you do not know how many bowlers played, how many overs were bowled in total, or what the rest intervals were. Seven injured in ten thousand overs is one thing. Seven in two thousand is another. Indian cricket can produce both numbers. It has never produced the second.

Another case. In 2026 the IPL introduced the Impact Player rule and the media immediately declared a tactical revolution. I waited thirty-eight matches. Then I coded seventy-four games and separated tactical substitutions from injury substitutions.

The picture was plain. There were 128 Impact Player uses, and only 19 were injury-related. Batting totals rose, but the rule did not reduce bowling workload. The rule was meant to change the XI; the outcome was the same old question — twenty-nine bowlers, twenty overs, a four-over quota, and an extra batsman who does not bowl.

I wrote a sceptical piece. Some TV panels called it 'negative.' My desk called it reliable. The sample was stable enough to question the hype and not enough to crown a new meta. That is the point at which most cricket analysis does not stop.

Out of all of it I built a rule-change audit template — sample size, injury-substitution share, workload effect, precedent — before writing on any new tactic. It made my writing slower. It made it harder to dismiss.

To count a fast bowler's injuries, you first have to count his calendar — and India's calendar has no release valve.

I have to be honest about my own formation. I grew up inside the Australian load-management school. The numbers that live in my head — overs per week, balls per spell, days between matches — were built there: one season, one summer, a real off-season, fewer formats, a long cool break.

Importing those numbers into India is an incomplete calculation. Here the Ranji Trophy, the Syed Mushtaq Ali Trophy, the Vijay Hazare Trophy, the IPL and the bilateral white-ball series all stack without a buffer. Here the heat changes the pace of rehab. Here travel days are spent differently — trains and flights and buses, with a domestic cricketer's body sitting in a vehicle for half a day.

And the largest structural point, almost never said: every other cricket economy has a release valve called the overseas T20 league. England's players go to the Big Bash, West Indies' to the PSL and CPL, Australia's to the IPL. The workload still exists, but part of it is spent elsewhere, under different conditions and different pressure.

An Indian centrally contracted player does not have that valve. The BCCI does not permit contracted players to appear in overseas T20 leagues; No Objection Certificates go largely to retired or uncontracted players. The result is that the entire load of overs and energy accumulates inside the Indian calendar. The overs have not gone down. Their destinations have stopped changing.

This is where I have to abandon my Australian frame. In Australia you can say: this bowler has bowled twenty-four overs in six matches in three weeks, he has crossed a red line. In India, twenty-four overs means something else, because those twenty-four overs include four thousand kilometres of travel and the mental switching between three formats.

So I calibrate every threshold locally, and when I borrow one I say out loud that it is borrowed. A reader is entitled to know that the number in my head came from my country's calendar, not this one.

'Injury-prone' is an accusation, not a finding — and Indian cricket files it weekly without evidence.

When someone calls a fast bowler 'glass,' they are creating a category they have never once measured. I sort the same player a different way: overs per seven days, spells per session, seam position under fatigue, days of travel between fixtures. Those four things can be measured. A 'fragile body' cannot.

And when you start measuring those four, some labels change themselves. I have seen bowlers called injury-prone whose actual record shows their overs ran fifty per cent above their team's median for four straight years. Their body is not weak. Their deployment is out of ratio. That is a management error, not a medical one, and writing it in medical language is the kind of dishonesty the Indian cricket media has grown used to.

I also want to avoid the opposite error: counting only what gets reported. My only document of national-team injury surveillance is the notice that became public. That does not mean what stayed private did not happen. There are hundreds of domestic bowlers playing through pain who never file a notice, because filing a notice means losing a place. They are 'fit' in the data and injured in fact. My ledger cannot count them, and that is the ledger's limit, which I state every time.

A bowler who never filed a notice is not a bowler who was never injured.

The most dangerous match is not the comeback match. It is the third match back — and that sounds backwards because we built the story backwards.

Media injury narratives almost always follow one shape: the bowler got hurt, rehab began, he came back too soon, the injury returned. It is a clean, dramatic, three-act story with an obvious villain. It has one problem: in most cases it is false, and I have a way to check it.

When you count the overs after a return, the picture changes. Match one is almost always controlled — a cap, short spells, off after the fourth over. Rehab teams watch this closely and it is the one place the Indian system is genuinely good. Match two is usually capped too.

In match three the caps come off, because the bowler has been declared fit, because the team needs a win, because the captain does not remember this is the same man who was in rehab four weeks ago. In match three he bowls his full quota, under full pressure. Tissue that tore four weeks ago is now being stretched at full intensity for the third time. Injury risk here is not measured in days; it is measured in overs per week — and the week the cap is removed is the week the overs-per-week number jumps highest.

So the real risk is not 'coming back too early.' The real risk is the administrative moment when the word 'managed' is deleted. Nobody records that moment. No bulletin announces: from today this bowler has no limit. So we never catch the moment, and we catch the story instead.

I do not hold this with the confidence of a TV panel. I have four small datasets — thirty-two, twenty-three, sixty, seventy-four. There is a pattern. A pattern is not proof. What I can say is that the data required to falsify this pattern is not published anywhere in India — and that is itself a statement.

A register that does not exist is not evidence.

People ask me often why fast-bowling injuries are rising in India. My honest answer is that I do not know that they are rising. I know their reporting has risen. Those are different things, and conflating them is the mistake we have made throughout.

When surveillance improves, old injuries surface that were never recorded before. The number goes up; the body stays the same. Reading that as a fitness crisis is the error of mistaking a new thermometer reading for a new fever.

My hope for the next step is a public availability register — four columns, every series, every player, week by week. Rest and unavailability would be visibly separate. Every numerator would carry its denominator: how many overs, at what interval. This is not performative transparency to me; it is the first thing that would move injury out of medical language and into administrative language. And administrative language is where the fix lives.

In February 2026 the board announced separate fast-bowling contracts for five bowlers — Akash Deep, Yash Dayal, Vidwath Kaverappa, Umran Malik and Navdeep Saini. It was the first time the system publicly conceded that fast bowling is a distinct profession requiring distinct accounting. I read the announcement twice and both times something jarred: it contained a number of years and a number of rupees, but not a number of overs. Same old habit — the body gets a contract, not a ledger.

Jasprit Bumrah could not bowl in the second innings of the Sydney Test in January 2026, and was then ruled out of the Champions Trophy. Mohammed Shami missed an entire year after ankle surgery in February 2026. Rishabh Pant returned in March 2026 from a road accident in December 2026. Shreyas Iyer's back pushed him toward surgery in 2026. Four names, four different injuries, four different rehab timelines, four different returns — and, in all four cases, the same incomplete public record.

I am not diagnosing any of them. I am saying that what the public record contains is not what an analyst needs. We know when they went out. We do not know how many overs they bowled in the six weeks before, how many days they spent travelling, or on what date the notice was filed. The first date gets printed. The second and third never do.

The scorebook does not explain the injury. It only tells you where to start looking.

One thing separates me from most people who talk about this. I never diagnose from body language. A bowler's face in the nineteenth over, a slow-motion grimace, a drop in pace — none of that lets me say he is injured. It is a scene, not a diagnosis. People who do this give viewers the illusion that injury is visible. Most injuries are not. A stress fracture does not show on a face. Cartilage wear does not show in an action until it is far too late. Before it shows, it was there for five weeks — and there is no record of those five weeks.

As a sports-science writer I am also asked whether India should adopt Australia's workload model. My answer: adopt the habit, not the model — the habit of stating before every series who is available, for how many days, and on what evidence. The magic of the Australian system is not its structure. It is its transparency. They have injuries too. But they have shared numbers to argue with. We have shared stories.

And stories always run in one direction — toward the player. 'His body isn't holding up' is the sentence that saves the system. If the body is at fault, the calendar is innocent. If the body is at fault, nobody has to ask why Ranji runs straight into the IPL, why the IPL runs straight into an England tour, and why there is not one week in between when the bowler's overs actually fall.

My complaint about fast-bowling injuries in India is not that they happen. They will happen; this is a physical sport and fast bowling is the most violent repeated action any athlete performs. My complaint is that we are not counting them, that without counting they cannot be understood, and that without understanding they cannot be prevented.

Availability is a statistic. It has simply never been printed in the same font as goals.

Next season, when a fast bowler drops out and the bulletin says 'rested,' I will do what I have done for eight years. I will open his register. I will count his overs across the previous six weeks. I will count the days between his last spell and the one before it. I will compute his team's median. And if he sits far above that median, I will write 'misallocated' instead of 'fragile.'

And if he does not sit far above it — if his load was normal and he broke anyway — I will write the thing nobody writes today: that I do not know, and that whoever does know should publish it.

One question I want to ask every time and never quite do: if the availability register were made public tomorrow, who would be most uncomfortable first — the player, the medical staff, or the desk that needs a fresh injury story every Monday?

The file is still on my desk. Its title field is still empty. I have added one thing to it — a line at the top, in pencil: "What is not recorded did not happen — the biggest lie in Indian fast bowling."

Under that line there are now forty-seven names. Fourteen of them say only 'rested,' and not one gives a reason.