The Empty Spreadsheet: What Indian Fast Bowling's Injury Ledger Refuses to Count

The Empty Spreadsheet: What Indian Fast Bowling's Injury Ledger Refuses to Count

Hook

Last month a file landed on my desk with eight columns, all eight blank. The headers read "Match details," "Bowler," "Format," "Injury type," "Return date," "Source." Every cell said N/A. This was not a technical glitch. It was an honest answer: the analysis pipeline that produced the file had nothing to send. I looked at it twice and closed it.

Twelve years ago, in 2026 in Ahmedabad, I started with a blank sheet very much like it — except I built the columns myself. Gujarat seamer Chintan Gaja had bowled 47.2 overs across three Ranji innings in 19 days that season. I logged seam position and release height on 126 deliveries, wrote down spell lengths, counted the days between spells. Two weeks later he left the field with a side strain. The post drew 18,000 reads and two Saurashtra coaches asked me for the spreadsheet.

That is my entire method, and it is also today's problem: what you do not record comes back as an injury — and when it does, you have no basis on which to say why.

The blank file was no joke. It was an accurate portrait of the system in which we discuss Indian fast bowlers' injuries — a system where exposure (how many balls, how many days, in which spell) is recorded nowhere, and only the outcome (who went down, for how many weeks) reaches the headlines.

Context

In Indian cricket, injury talk almost always revolves around a person. Who is hurt, when will he return, will he make the World Cup. That is natural — the reader knows the player, not the calendar. But in my trade, injury decoding, the question is inverted: who got hurt is the outcome; what changed seven days earlier is the question.

For several years I have kept a public workload log of Indian fast bowling — starting with Gujarat's seamers, using whatever I can get from newspapers, scorecards and my own film-room notes. The purpose is not to pass judgement on anyone's fitness. The purpose is that my claims can be checked. If I say there is risk in the next three weeks, the reader should be able to see what I counted.

And that is where the trouble starts. Exposure data in Indian domestic cricket simply is not public. Ranji scorecards tell you how many overs a bowler sent down. They do not tell you how those overs were split into spells, how much rest sat between spells, when the bowler's previous match was, or how many balls (match plus practice plus nets) he bowled that week. Not one of those numbers is officially published.

Which does not mean the data does not exist. The NCA in Bengaluru and franchise support staff have it — GPS units, RPE sheets, spell logs, screening records. The problem is that it is institutional, not public. As a journalist I have access to some people, and I am stating plainly that I have access — because the day I start hiding it, my reporting stops being worth anything.

So when an analysis pipeline hands me a blank sheet, I do not treat it as a technical fault. I treat it as a mirror. The biggest gap in Indian fast-bowling injury reporting is not data, it is data discipline — and its clearest evidence is the column that stays empty in every report: exposure.

Core Analysis: Every injury has a denominator, and the interesting part is who chose not to count it

1. Incidence rate versus raw count

In epidemiology you never count injuries alone. You count them as a fraction: per 1,000 bowling overs, per 1,000 player-days, per 100 match-days. Without a denominator the numerator means nothing. If eight fast bowlers were injured in a season, the question is: eight out of what? Out of a pool of 40 who bowled 22,000 overs between them? Or out of a pool of 12 who bowled 6,000?

The first number is unremarkable. The second is an epidemic. And in Indian cricket's public conversation, that denominator almost never appears.

I made exactly this mistake in my 2026 notebook — the first version counted overs, not spells. When I added spells, the picture changed. 47.2 overs split into six spells of eight is one thing. The same 47.2 overs split into three spells of 18, 16 and 13 is a completely different thing, even though the total is identical. In fast bowling, total workload is nearly meaningless; spell architecture is the real variable.

It is so obvious that I am embarrassed to write it, and yet it goes missing from every injury report. "He bowled 400 overs this season" — fine, who didn't? Compared to whom? In what format? In what weather? At what interval?

2. The calendar is the selector

If you asked me for the single strongest predictor of injury incidence in Indian fast bowling, it is not pace, not technique, not age. It is the calendar.

The IPL window, the WTC cycle, the Ranji fixture list, and since 2026 the compressed WPL calendar — these three put pressure on different cohorts simultaneously, and the administrators who build them never have to bowl the fourth spell.

Here is one concrete, public example. Jasprit Bumrah was out for a long stretch from 2026 with a back stress fracture and returned in a T20I against Ireland in August 2026. That is public record, not a leak. The question is not whether he got hurt — it is how much gap sat between his three formats in the twelve months before he did, and who signed off on that gap. That answer is not in any public document to this day.

That is my real complaint. I am not saying administrators are negligent — I am saying the system contains no single person whose job is to look at a bowler's last 28 days of load, object to the next 14 days of fixtures, and leave a written record of the objection. Physios look, coaches look, selectors look — but in separate files, and no file is public.

I sit between the doctor and the coach, and my job is to make both of them precise. I ask the doctor: "Is this injury acute or cumulative?" I ask the coach: "Who decided the length of that spell?" The two answers live on different pieces of paper, and the paper does not talk to itself.

3. Translation is the actual work

My generation grew up on Australian state beats, where in the 1990s the vocabulary of load monitoring came from football. Acute:chronic ratios, high-speed running, sprint load, total distance. That language is my mother tongue. And it breaks the moment you apply it to cricket.

Why? Because football's speed is built from distance — 11 kilometres, 900 metres high-speed, 30 sprints. Fast bowling's speed is not built from distance. A fast bowler who sends down 20 overs in a day may not walk four kilometres. The GPS will say: light day. His body will say: I absorbed roughly 120 impacts near 140 kilonewtons.

Fast bowling is high-impact, low-distance work — and GPS metrics measure almost none of it. This is not a translation error, it is the impossibility of translation. Forcing football's model onto cricket is like reviewing a book by its thickness.

So what do I measure? I measure what is not on the scorecard but can be counted:

• Spell length (in overs, and the pace difference between the first and last ball of that spell)
• Gap between spells (in minutes, including the innings break)
• Days between matches (and the estimated net balls inside those days)
• Release height and seam position (fatigue shows here first — the release point drops, the seam straightens)
• Change in run-up length (a tired bowler often shortens the run-up — the clearest signal of compensation)

This produces a counter-intuitive finding I like best and that is most often misread: the bowler who looks freshest on the sheet is often the one already compensating. Shorter run-up, shorter spell, steady pace — that is not fitness, it is management. The body has reduced the work so the pain reduces. On the sheet it reads as smart workload management; in the film room it is a warning.

4. WPL and a new cohort carrying an unmodelled load

The WPL began in 2026. It is a huge step for Indian women's cricket and I am not arguing against it. But there is a medical fact that gets under-discussed: a population with no historical load baseline cannot have a risk model built for it.

In men's cricket we have decades of domestic and international data — incomplete, but present. In women's cricket, especially in India, both the domestic structure and the international calendar have shifted rapidly in recent years. When a fast bowler who has bowled a limited number of overs domestically suddenly enters a tournament with eight matches in 20 days, on what basis do you compute her acute:chronic ratio? She has no chronic baseline.

I ran a version of this exercise in 2026 — comparing Russia World Cup's 64 matches and 736 players with IPL 2026's 60 matches and 1,024 player appearances, and building a load-spike table from 14 medical papers. The piece drew 46,000 reads, but I missed the deadline by 90 minutes because I ignored the difficulty of execution. The lesson: tournament density (matches per day) should be a box in every injury report, or you cannot compare anything. Since then 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 instead.

5. The checklist as an act of care

This is my least fashionable argument and I will keep repeating it. In the lockdown film room I learned that a checklist can be an act of care.

Screening rituals, 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.

One data-backed point from my log: the bowlers who make the most fuss about screening and pre-hab tend to be the most available. Fastidiousness correlates with availability, not fragility. It sounds backwards because we grew up on stories of the hard and the delicate. But the player who complains honestly about his body is often the one who plays the whole season — because his small problem gets caught before it becomes a big one.

Contrarian Angle: My own framework is my biggest trap

Now the part that stings most when I write it.

I have just told you to count exposure, count spells, watch the calendar. All true. But if I am honest, I must also say that this same framework can take me to the wrong place.

Three seasons of load notes will always yield a pattern. n=12 plus hindsight will always manufacture a tidy culprit. My own signature sentence is my own trap: the pattern that looked "embarrassingly simple" may simply have been the one that fit.

In 2026 I flagged Chintan Gaja's risk two weeks early. I published it. It felt good. But the truth is that I tracked four other seamers that season and issued no such warning on any of them — and two of them were later injured. I did not write about those two. I added them to my log afterwards, but not to the public post. That is bias, and hiding it is the death of journalism.

So I have three rules, and they are rules against myself:

One: pre-register the hypothesis before the next dataset. At the start of every season I now write down what I think — which three bowlers are at risk and why. At the end of the season I update it in the same post, even if it embarrasses me.

Two: publish the sample size and the misses. "I looked at three seasons" is not enough. How many bowlers? How many injuries? How many predictions were wrong? If I do not write that, my analysis is just a guess with a good memory.

Three: write the piece the data refused to support. This is the hardest. When the data gives no clean story, you do not want to write. But that is where the real reporting is. I keep a file called "unwritten" — every analysis I did not publish because the numbers would not carry it. That file is my most honest work.

And a second contradiction: the uncritical import of football frameworks. Acute:chronic ratio is my native language and it sounds authoritative to a cricket audience. But have we audited it for cricket? ACR was built for distance-based sports where load is continuous and measurable. Bowling load arrives in stops and starts — five days of Test, three days off, a T20, then travel. What is the chronic baseline here? 28 days? 21 days? On what basis?

I name the translation every time, state what the metric cannot see in cricket, and treat the mapping as a claim under test rather than a tool. It is exhausting. But what is the alternative — drawing baseless conclusions from baseless numbers?

A third contradiction, the most uncomfortable: the insider's curse. Thirty years of access built my relationships. NCA and franchise staff are colleagues, not subjects. And when a paragraph costs a relationship, the paragraph often goes soft. So I made a rule: disclose access in every piece, separate what was observed from what was granted, and keep a running file of findings I would publish if I lost the phone numbers.

And one last thing I have to apply to myself: pain is data, not character. Any sentence that praises a player for bowling through a tear — "he dragged himself to the crease" — inverts my entire premise. I will never write it. If someone bowled on a broken body, that is a medical failure, not heroism. Documenting that failure is my job; celebrating it is not.

Takeaway

So what do we do with the blank spreadsheet?

My answer: do not throw it away. Make it page one. The most important document in the cricket we are watching is the one not yet written — an exposure log for every fast bowler, public, verifiable, and as available as his average.

Over the next five years the biggest question in Indian fast bowling will not be who is quickest. It will be which board has the nerve to publish its bowlers' load data — because a board that does so is also accepting accountability for every injury it presides over.

Until that day, I will sit with my blank sheet. It is not my failure. It is my evidence.