The Empty Ledger: Why Indian Cricket Doesn't Count Its Own Injuries

There is a file on my laptop — load_notes_2024.csv. The columns are already built: date, bowler, overs, number of spells, release height, seam position, next-morning stiffness. The rows are zero.

Last week a digital desk emailed: "Write an analysis of injuries based on this data." I opened the file. There was a header. Below it, nothing. I refreshed twice, the way you refresh an old scorecard. The file stayed the same — clean, elegant, empty.

This article is about that empty file. Not about cricket's injuries, but about the thing that should have existed before the injury and didn't: the counting.

Context: the notebook I built myself

I have been doing this work since 2026. Sitting in Ahmedabad, at 43, after fifteen years on the cricket beat, I started a separate injury-analysis vertical. Back then I had exactly one habit — looking at the mechanics before the press conference.

That year, Gujarat seamer Chintan Gaja bowled 47.2 overs across three Ranji innings in 19 days. I logged seam position and release height on 126 deliveries. Two weeks later he left the field with a side strain. My post drew 18,000 reads; two Saurashtra coaches came asking for the spreadsheet. I followed the mechanics, not the press conference.

The next year, during the 2026 Russia World Cup, a desk asked me why 23-man squads were cramping. I compared 64 matches and 736 players with IPL 2026's 60 matches and 1,024 player appearances, and built a load-spike table from 14 medical papers. I missed the deadline by 90 minutes; the piece drew 46,000 reads.

Since that day I attach a tournament-density box to every injury piece, and I keep a shared calendar of 21-day and 28-day turnarounds. When a desk asks for a quick quote, I send a two-column load table. My public injury log exists so readers can check my calls — and so that when I am wrong, that is on the record too.

I mention all this because when the empty file arrived, I knew exactly what it was evidence of.

Core: the calendar is the selector

Injury incidence in Indian fast bowling is not a product of effort. It is a product of scheduling. The IPL window, the WTC calendar and the Ranji fixture list are selection decisions made by administrators who never have to bowl the fourth spell.

I was on the Australian state beat in the 1990s, where load management was everyday language. There it was ordinary to say that a fast bowler's total overs matter less than his spell count. Coming to India, I found the order reversed — people count overs, not spells. But the damage happens in the spell: in the fourth spell, release height drops, the seam angle shifts, and the body starts compensating.

Across three seasons of my load notes, the pattern was embarrassingly simple. A bowler who does four-spell work three times in 19 days does not have his risk set by his average; he has it set by his turnaround. A turnaround under 21 days, plus the same bowler repeatedly bowling four spells — that pairing recurred more than anything else in my log.

So my first question in any injury piece is: what changed seven days before? I stopped asking who got hurt and started asking what changed seven days earlier. It is a small rephrasing, but it turns the whole direction of the reporting — you move from the player to the system.

Translation is the actual work

Fatigue does not read the fixture list, so I translate it from football into cricket.

Football's monitoring vocabulary — acute:chronic ratios, high-speed running, sprint load — does not survive the crossing intact. It is my native language, which is why I use it with deliberate suspicion. A fast bowler runs maybe two or three kilometres a day; that number is close to useless. The real event is different — landing on one leg twenty to twenty-five times a day, at eight to ten times body weight.

GPS does not measure that. It measures distance, not impact. When a franchise shows me that "look, this bowler ran the least this week," I ask how many landings he absorbed, and in which overs. The answer is often empty — exactly like my file.

And this is where the counter-intuitive finding emerges, the payoff for doing the unglamorous arithmetic: the bowler who looks freshest on the sheet is often the one already compensating. When a bowler lets his release height fall, he is usually applying less force — and less force looks like less load on the sheet. A falling metric and a rising risk, simultaneously. That is the price of the translation, and it is why I name it explicitly every time: this mapping is the claim under test, not the tool.

Chintan Gaja's case was clean precisely because I counted impact, not distance. 19 days, three innings, 47.2 overs — but alongside that, spell size, the trend in release height, the drift in seam position. When release height fell across three consecutive spells, the side strain became a forecast rather than a surprise. Two weeks later, it happened.

I will not say I predicted it. I will say I did the counting, and the counting did the rest.

The cohort with no baseline at all

Now the part that worries me most, and about which the least data exists.

Look at the women's calendar after 2026. The WPL began, bilateral series expanded, and a group of athletes suddenly started carrying a professional workload with no historical baseline. In men's cricket we have decades of experience data, however messy. In women's fast bowling that data does not exist — not injury history, not turnaround, not spell size.

This does not mean the players are fragile. It means the system is modelling a workload nobody has ever modelled. When you have no baseline, you cannot even apply the 21-day rule, because you do not know what normal is.

This is where the empty file stops being a metaphor and becomes a policy problem. Every injury has a denominator, and the interesting part is who chose not to count it.

The checklist as an act of care

During lockdown I turned a room at home into a film room — three seasons of footage, two screens, and a checklist taped to the wall. In the lockdown film room I learned that a checklist can be an act of care.

Screening, pre-habilitation, the boring bureaucracy nobody watches — durability lives there. Indian cricket still romanticises the "he'll tough it out" culture, and that culture is the injury factory it pretends to despise.

The cleanest correlation in my log is this: the bowler more fastidious about his routine stayed more available. Fastidiousness is not fragility; it correlates with availability. The player who reports every small stiffness is often the one who misses the fewest matches.

Contrarian angle: empty data is a finding, not an excuse

Here is what unsettles me most.

When the empty file arrived, my first thought was not that the data had broken. My first thought was that the data had never been collected. And those two things are worlds apart.

A technical fault can be fixed. A system that never started counting cannot. In Indian domestic cricket we have no public, continuous, player-level load record for fast bowlers. When a bowler breaks down, we cannot pull his spell load from the previous three series, because it was never written down anywhere. We guess, and then we call the guess analysis.

I sit between the doctor and the coach, and my job is to make both of them precise. When both are holding the same empty sheet, precision is impossible. The coach will say the lad looks fit; the doctor will say the scan is clean; and nobody in the middle will ask how many fourth spells he bowled in the last 19 days.

There is one more thing I write openly, because without it the whole argument is incomplete. In thirty years I have had access to boards, franchises and physios. That access is my comparative advantage, and it is also my trap. Where the relationship becomes worth more than the paragraph, the finding softens. So I state plainly what I observed and what I was granted. And I keep a separate file — of the findings I would publish on the day I no longer have these phone numbers.

In that file there is currently one line: an injury that is never recorded can never be prevented.

Takeaway

I am not ending this piece hoping someone will send me data. I am ending it with a question: the next time a fast bowler goes down with a hamstring, will we ask how many spells he bowled in the last 21 days — or will we praise his "strong mentality" again?

I have an empty file. Its columns are ready. Whoever writes the first row will be doing the most important work in this game — and it will never be shown at a trophy ceremony.