Fourteen Notices, One Empty Column: Why Indian Fast-Bowling Injuries Never Add Up

That night there were fourteen rows on the spreadsheet in front of me, and nine of them had the last column blank. The column's name was plain enough — "balls bowled in the previous seven days". Everything else was there: the bowler's name, the date of the notice, the match it referred to, the part of the body, when the team bulletin was issued, when the player returned. What was missing was precisely the thing without which no cause of an injury can hold together.

I was building that file after coming back from the scorer's box in Chennai, and by then one thing had become clear to me: the biggest gap in this country's handling of fast-bowling injuries is not clinical. It is an accounting gap. Not the hospital's record, not the board's record — just that one column, which nobody saw any benefit in filling.

Context: The calendar is the injury

Indian cricket's domestic and international architecture leaves a fast bowler no space to breathe. The Ranji Trophy season, the IPL immediately after it, bilateral white-ball series after that, and an Asia Cup or a World Cup somewhere in between — the sequence does not end within a season, it runs through the year. In Australia, where I learned the load-management framework I still think in, there is a genuine off-season in the middle of the cycle, cooler weather, and fewer formats running simultaneously. That framework cannot simply be dropped into Indian conditions and expected to hold.

The concrete consequence is that an Indian player has no release valve for overs. Fast bowlers from England, Australia, South Africa and the West Indies can, after their domestic season, go and bowl low-pressure overs in an overseas T20 league — lower international intensity, a different climate, a different selection pressure. For BCCI centrally contracted players, that route is effectively closed. The load an Australian bowler discharges elsewhere simply keeps accumulating inside an Indian bowler's body.

The reporting structure is part of the same imbalance. The team bulletins that follow Ranji matches tend to be one or two lines — "the player has an injury to his left shoulder and will miss the next match". That sentence contains a date, a body part, and an absence. What it does not contain is: how long that shoulder had been troubling him, how many balls he had bowled before it, how many days of travel he had logged, and which stage of rehab he had reached. The first half of the information exists. The second half — the half that actually explains — is recorded nowhere.

From a reporter's point of view this is the most irritating part. You can publish the news of an injury, but you cannot audit it, because the data required to audit it does not exist in any public document. Fourteen absence notices arrived on my desk and I had to build a table first, before a single conclusion could be drawn.

Core: The column that gets filled is the column that tells the story

The scorebook does not explain the injury. It only tells you where to start looking. I have repeated that sentence for seven years, because every time I forgot it, I had to correct my own article later.

The first ledger is from 2026. I was twenty, studying statistics in Chennai, sitting voluntarily in the scorer's box at Chepauk and counting through all thirty-two matches of the Tamil Nadu Premier League. I logged every bowler's every spell, the rest interval between spells, and every injury stoppage in my notebook. I wrote down all thirty-two of them by hand, and the pattern only showed up in the last column. That column was "total balls in fourteen days". Seven bowlers emerged who had delivered more than 120 balls inside a fourteen-day window. Two of them later withdrew from local cricket — one with a shoulder complaint, one with an ankle.

That is where I had to put a brake on my own conclusion. Thirty-two matches, one stadium, one season, one state league — that is a hypothesis, not a mechanism. Two withdrawals out of seven is a signal, not proof. Even today, when someone quotes that number, I insist on writing n=32 and naming the window alongside it.

The second ledger is from 2026, when the grounds were empty and there was no live cricket. As a junior writer on a Chennai sports desk I had no obvious assignment, so I collected fourteen injury and illness notices and hand-coded eight Ranji Trophy scorecards from 2026-20. The finding was that five soft-tissue absences fell within eleven days of a three-day turnaround. Fourteen absence notices had already arrived before anyone thought to build a table.

That was the first time I saw the thing that later became the spine of my work: reporting lag. The gap between the date of the notice and the date of return to the field often says more about how serious an injury was than the words in the bulletin. When a notice says "niggle" and it lasts eleven days, the word is not lying — the word is incomplete.

The third ledger was the largest. In 2026 I was on a national cricket desk and the IPL stretched from India to the UAE. The season was suspended on 4 May. I went back through all sixty matches and coded the spells of twenty-nine frontline fast bowlers. Twelve pacers had bowled more than 24 overs in the India leg. After the UAE restart, that group produced seven soft-tissue absences.

That number tempted me more than any other, and frightened me more too. It tempted me because the pattern was clean. It frightened me because the same window contained quarantine travel, the mental weight of a bio-bubble, and adaptation to two different climates. Counting overs tells you where the load sat; it does not tell you why the body gave way. When I published that table, it carried match-by-match workload and no diagnosis. Editors noticed the caution, and I think that was the right response.

The fourth ledger arrived with the Impact Player rule in 2026. When the rule came in, panels declared it a tactical revolution. I waited thirty-eight matches, then coded all seventy-four games and separated tactical substitutions from injury replacements. There were 128 Impact Player uses in total, of which only 19 were injury-related. Batting totals rose, but fast-bowling workload did not fall — the rule handed batting an extra slot and gave bowling no relief. I wrote a sceptical piece about it. Some television panels called it "negative". My desk called it reliable.

Put those four counts side by side and the picture that forms is not about injury. It is about record-keeping. Every single time, one piece of information was missing — the piece that measures the load on a bowler's body rather than the name of the injury.

A usable absence notice needs six things, and Indian domestic records typically carry three or four of them: first, the date and match identifier; second, the body part and type of injury; third, balls bowled and spell counts across the previous seven and fourteen days; fourth, the reporting lag between the event and the bulletin; fifth, the rehab stage and expected return date; sixth, balls bowled in the first match after return. The first two are almost always present. The third and the sixth almost never are.

This is why the "injury-prone" tag is so easy to apply. Once you do not have a record of a bowler's overs, the only thing left to blame is his body. The label is what a lazy desk uses when it hasn't counted.

Contrarian: An empty register is not a clean bill of health

There is a trap here, and I have fallen into it twice. Absence notices are the documents I can actually obtain, so the dataset quietly drifts into "players who were formally rested or ruled out". That is wrong. A bowler who never filed a notice is not a bowler who was never injured — he is a bowler who chose to play through pain, or who was never given a platform to speak.

Non-appearance is data too. The player sitting out of selection, the player removed from a squad under the word "rest", and the player who is on the field but shortening his spell — all three belong to this ledger. Indian domestic cricket has no public register for any of the three. A register that does not exist cannot be called clean.

The second contrarian point is about thresholds. The "24 overs" and "120 balls" lines I wrote above come from Australian load-management literature — different season, different temperatures, different travel days. Two hundred overs bowled across three weeks in Chennai humidity and two hundred overs bowled in a Melbourne winter are not the same thing. A threshold can be borrowed. A body cannot. Whenever I write a number, I have to write alongside it whether that number was derived here or imported from somewhere else.

The third point concerns rushed rehab. Speed of return is often treated as bravery in cricket — "he came back through the pain". Medically, that is the most expensive kind of bravery. In a soft-tissue injury, tissue healing is one thing; that tissue absorbing a full workload is another. When a bowler is sent straight into a four-over spell after four weeks of rehab, the rehab has not finished — the report has merely stopped. Of the seven absences in my 2026 group, at least three involved a full quota bowled in the very first match back. That data is in my column. That conclusion is not, because a sample of seven stays a sample of seven.

The fourth, and least comfortable: the reporting failure precedes the medical one. Until a team develops the habit of recording who bowled how much in which week, the physio can be as good as he likes and will still be working in the dark. And until the board publishes it, I and others like me will keep counting in the dark too.

Takeaway

I have two options and both are incomplete. The first: a mandatory injury register published at the end of every season — segregated by format, with player names, carrying at least four of those six columns. The second: the selection committee and the physio team sitting at the same table, rather than working from two separate files.

Until that happens, every new injury story will circle back to the same question — and that question will not be asked of the bowler's body, but of the file nobody filled in. The next time a fast bowler walks off after sixteen overs, do not ask whether his body was weak. Ask who was keeping the count of his last seven days. If no answer comes, understand that the injury did not happen that day — that was only the day it became visible.