The Column That Was Never Filled: Cricket's Injury Surveillance Is an Accounting Problem First

The file lay open on my desk and every field in it was blank. Title: unavailable. Source: unavailable. Information points: not a single one. The eight analytical sections that should hold up any cricket report each carried the same sentence — insufficient information, assessment not possible. For thirteen years my job has not been filling blanks; it has been saying where the blank is, how wide it is, and why it stays there. In the scorer's box at Chepauk in the summer of 2026 I learned that the most important column on a scorecard is the one nobody thought to fill. That afternoon there was no injury in front of me, no bowler, no scorecard. There was one record telling me, through its empty fields, that it had never been written. In this trade an empty record is still a document, and everything below is an examination of that document.

In Indian cricket a public injury fact travels through three documents: the physio's note, the team bulletin, and the match-day team sheet. The days between them I call the reporting lag. That lag never appears in a broadcast graphic, is never raised at a press conference, and therefore never becomes part of an analysis. Yet it is the actual question — when was the note written, and when did the sheet change.

In 2026, when the grounds were empty and there was no live cricket, I tried to count that lag. I pulled fourteen Tamil Nadu injury and illness notices, pulled eight scorecards from the 2026-20 Ranji Trophy, and built an internal availability table. Five soft-tissue absences clustered within eleven days of a three-day turnaround. Fourteen absence notices had arrived before anyone thought to build a table. Empty stadiums did not reduce the injuries; they only removed the noise around them. Our desk began using that table in previews, and my injury lines stopped being vague — I write 'unavailable' only after the bulletin exists, and 'how many days' only when a date is on file.

We are now inside a major tournament cycle. A tournament compresses emotion — flag, story, hero, elegy, all in one week. Readers get swept up in it and that is natural; I get swept up myself. But when a bowler's name disappears from a team sheet, the first task is to establish which documents we have and which we do not. The file that opened this piece had no title, no source, no player, no date. It had eight analytical columns and one entry in all of them — insufficient information. In this profession that is not a disgrace. The disgrace would be filling the blank with a familiar story, because familiar stories are always available.

I have one rule and it has not changed in thirteen years: state the n, name the window, mark the confidence. Where there is no sample, there is no sample — the discomfort of writing that sentence is the professional honesty itself. The eight-section frame every cricket report passes through — format and match, player and technique, team landscape, league economics, rules and governance, risk, public narrative, industry transmission — returns empty in every box, and only one conclusion emerges: analysis is not possible. But that is also a conclusion. An empty box tells us where the information system breaks. In injury surveillance that break is accounting, not clinical.

The 2026 Chepauk ledger. I hand-coded thirty-two TNPL matches. Every bowler's spell, rest interval and injury stoppage sat in a column. Seven bowlers emerged who delivered more than 120 balls in fourteen days; two later withdrew from local cricket with shoulder or ankle complaints. I wrote down all thirty-two by hand, and the pattern only showed up in the last column. Seven is a hypothesis, not a mechanism — one season, one city, one coaching staff, and no independent medical examination of any complaint. The number I hold is about overs; the question I hold is about tissue, and the two never share a document.

The half season of 2026. The India leg of the 2026 IPL ended when the season was suspended on 4 May 2026, and it restarted in the UAE on 19 September 2026. Across those sixty matches I coded the spells of twenty-nine frontline fast bowlers. Twelve bowled more than twenty-four overs in the India leg; after the UAE restart that same group produced seven soft-tissue absences. Sixty matches into a suspended season, the audit stopped being about pace and started being about load. Three caveats belong here: a four-and-a-half-month break, quarantine travel, and Gulf heat and humidity. Seven out of twelve versus the other five says nothing more than where to look next. Anyone who calls it proof that congestion causes injury has read half of my ledger and skipped the rest.

The 2026 rule audit. The IPL introduced the Impact Player rule in 2026, and several television panels declared a tactical revolution inside a week. I waited thirty-eight matches, then coded all seventy-four and separated tactical substitutions from injury replacements. There were 128 Impact Player uses, only 19 of them injury-related; batting totals rose, bowling workload did not fall. The sample was stable enough to question the hype, not stable enough to crown a new meta. That same discipline now has me sitting in front of an empty file, saying what I said then: do not let a number become a verdict until it has survived a full season.

The column no table contains. Before any public injury announcement, a physio writes a note, a trainer sends a message, a selector gets a call, and only then does the team bulletin appear. That gap runs to two days sometimes, eleven days other times. Until it is recorded, injury surveillance in Indian cricket remains an accounting problem, and the debate about rushing a bowler back versus scientific rehab remains the second debate. The reporting lag has another effect that gets underrated: it gives a team room to justify its decision after the fact. When the announcement is late, the entire rehab calendar slides backwards and the public narrative turns it into a sudden injury that had in fact been logged weeks earlier.

What a good notice looks like. It has five fields: date of onset, mechanism, investigation result, expected return, and overs bowled in the previous fourteen days. The first four are medical; the fifth is cricket-specific. Public bulletins usually carry the first four and almost never the fifth. In the notices I have read, most of the argument comes from that fifth field being left blank — because it is the field that decides whether the injury arrived suddenly or was invited. The patient's record is complete; the player's is not. The entire argument rests on that incompleteness.

The protocol for an empty file. When the source is gone, the protocol is this: record what you have, state plainly what you do not, and keep inference in a separate column. In this file one concrete thing survived — the tag: cricket, Asia. A tag yields no conclusion, but it does tell you which direction to look. I looked, and what I found is that an empty file is not an accident. It is the last link in the same habit that logs absences rather than injuries.

Absence-notice bias. The documents I can obtain are the ones somebody filed — formal rest, formal withdrawal. The bowler who played through pain and quietly finished the season filed nothing, so he is not in my dataset. A missing notice does not prove a missing injury. This is the largest blind spot in my work and I repeat it in every piece, because the day I forget it, my count becomes testimony against a player. The same blind spot breeds another habit — labels like fragile, glass, injury-prone. Those labels stick to the bowler whose calendar was worst, not the body that was weakest. Whenever a quick is called fragile, my first question is: what were his overs against the team median, how many days separated his matches, and how much travel sat inside them? The answer usually breaks the label. The label is the weapon of a desk that did not count.

The imported threshold. My formative framework came from Australian load management, a system with a real off-season, cooler schedules and fewer formats. Those numbers travel in my head even when they should not. India brings heat, travel days, three-format congestion and, above all, no release valve — centrally contracted players are not permitted to offload overs in overseas T20 leagues. Other systems burn part of the annual load in another league; here that door is shut. So my arithmetic has to be about debt rather than the calendar — how much load was taken on and where it was repaid. With no release valve, every extra over goes straight onto the tissue account, and the interest compounds. The injury you cannot see this season shows up on the first tour of the next one.

The scorebook's limits. One last warning I give myself every week: the scorebook does not explain the injury. It only tells you where to start looking. Every time I named a cause from overs alone, I had to withdraw the claim once travel logs, rehab notes and reporting lag were added. Counting overs always produces a pattern, and a visible pattern does not make a cause. A number that pressures you to prove your point is not a number; it is a lawyer.

The public argument always starts late and in the wrong place. When a fast bowler goes down, the question is whether he was rushed back or handled with scientific rehab. That argument matters, but it is the second argument. The first is when the notice was filed, when the team sheet changed, and how many days sat between the two. Until that interval is public, the whole rush-back-versus-rehab fight is a hearing with no witness — both sides will tell their story and neither will be able to show what it actually did.

The second failure belongs to my own tribe. We become purists of the sample and then never decide anything. The empty file is that disease in its purest form: so much caution that eight analytical sections were produced and not one conclusion. Caution and silence are not the same thing. A small sample cannot be an excuse for a large one — it should be published with its limits attached, not locked in a drawer. The desk that called me negative later printed my workload table; and the desk that printed my table later said I had taken too long. Both were true, and the path between them is this: write down exactly what you counted, and leave what you did not count visibly blank.

I will not bang a drum about what should happen next. A public availability table would be enough, with three mandatory columns: the absolute date, the reporting lag, and the overs bowled in that window. On the day those three columns become part of an official bulletin, the phrase injury-prone will quietly turn from a diagnosis into an argument. The next time a fast bowler vanishes from a team sheet, the question should not be how fragile he is. The question should be: when did the note arrive, and when did we start counting?