The Notice Before the Injury: Cricket's Injury Surveillance Is an Accounting Problem

Eleven days into the 2026 Tamil Nadu Premier League, seven bowlers had already crossed 120 deliveries inside a fourteen-day window. I know because I sat in the scorer's box at Chepauk and wrote down every spell by hand — rest intervals, stoppages, the whole ledger. Two of those seven later withdrew from local cricket with shoulder and ankle complaints.

What bothered me was never the injuries. It was the paperwork. The first written notice did not carry the date on which the bowler stopped bowling. It arrived three weeks later, with the date field left blank. The scorebook does not explain the injury. It only tells you where to start looking.

Inside a tournament cycle, that blank field becomes the most expensive object in the sport. Ranji Trophy, the IPL and bilateral white-ball cricket stack on top of each other with no off-ramp between them. Australia's load-management tradition rests on a genuine off-season; India does not have that floor. The BCCI's refusal to release contracted players to overseas T20 leagues closes the valve through which overs normally escape. The load stays where it is — it is merely accounted for somewhere else, and usually under someone else's name.

In 2026 cricket stopped and I was a junior writer on a Chennai desk. With no live matches to cover, I did the thing nobody else was doing: I transcribed fourteen injury and illness notices and eight Ranji Trophy scorecards into a single table. Five soft-tissue absences had landed within eleven days of three-day turnarounds. Instead of writing speculation, I built an internal availability table. When cricket returned to empty stadiums, that table became the basis for explaining return-to-play risk. Empty stadiums did not reduce the injuries. They only removed the noise around them.

The following year the IPL was suspended on 4 May 2026, after sixty matches had been played in India. I coded the spells of twenty-nine frontline fast bowlers across those sixty games. Twelve had bowled more than twenty-four overs in the India leg. After the UAE restart, seven soft-tissue absences came out of that same group. The simple line — congestion causes injury — was available and easy. I published a match-by-match workload table instead, because a clean pattern across thirty-two entries is a hypothesis, not a mechanism.

Those exercises produced the claim that now anchors everything I write: cricket's injury ledger is format-blind. The overs column on a scorecard adds T20 death overs, ODI middle overs and long Test spells into one figure. The physical price of a single over is not the same in each: yorkers and slower balls at the death, the sustained rhythm of the eighth over of a Test spell, two new balls in a fifty-over innings. Add up the overs and the spike you find may be an artefact of the calendar rather than of bowling. Without format tagging, no load conclusion survives contact with scrutiny.

The second failure is informational. A standard injury notice carries two or three hard facts — a name, an affected joint, a likely absence. Many carry less. No format, no date, no source. Building analysis on that is as meaningless as adding a Test average to a T20 strike rate and calling it a number. The real problem is not that injuries go unrecorded. It is that they go uncoded. A notice that was never filed is not evidence that no injury existed. The bowler who plays through pain is data too, and just as solid as the one who sits out with a statement.

The third failure is reporting lag. There are three documents — the physio's note, the team sheet and the press-conference line — and all three carry different dates. I trust the minute log more than the press conference, and the minute log has never lied to me. Until someone puts those three documents side by side, every analysis is built on whichever date is most convenient. Fourteen absence notices had already arrived before anyone thought to build a table.

The fourth failure is borrowed. Australian load thresholds were derived in cool schedules, with a real off-season and fewer formats. They do not travel unchanged into Indian heat, travel days and three-format congestion. Years of watching matches taught me that importing a threshold is easy and admitting it is imported is hard. When I use one, I now write down that it is borrowed.

The counter-intuitive part is that cricket does not urgently need faster diagnosis. It needs better counting. The broadcast vocabulary — fragile, glass, injury-prone — is an answer that should have been a question. When a tournament is live, return-to-play dates are often set by the calendar's needs rather than the body's repair schedule. Jasprit Bumrah went out with a back injury in September 2026 and returned in August 2026; Mohammed Shami had ankle surgery after the 2026 World Cup and was gone for a long stretch. Both show the same shape — a long wait, then a clean re-entry. That is a pattern, not proof, and treating a pattern as a mechanism is exactly the mistake I try to avoid.

The 2026 Impact Player rule is the test case for that caution. I waited thirty-eight matches before judging, then coded all seventy-four games. The rule was used 128 times, and only nineteen of those uses were injury-related. Batting totals rose; bowling workload did not fall. A rule billed as a tactical revolution failed at the job most expected of it — lightening the bowlers' load. My desk called the piece conservative. The later numbers called it late but correct.

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

The next tournament cycle will deliver another stack of notices. Somewhere a physio will write down a date; somewhere a team sheet will conceal it. The question is not when the next injury lands. The question is who builds the table — and whether they build it before the injury gets a name, or after.