The Empty Column Is Also a Document: Asian Cricket's Unpaid Injury-Reporting Ledger

The scorer's box at Chepauk, Tamil Nadu Premier League, 2026. Thirty-two matches, and in front of me a hand-ruled sheet with four columns per bowler — overs, spells, the gap between spells, and a last column headed 'stoppage'. The first three filled themselves. The fourth stayed blank in almost every match. A bowler would pull up, the physio would jog out, water, spray, and two overs later the same bowler would finish his spell. Nothing went on the sheet, because there was no rule that said it should. At the end of the season I counted the three columns that had been filled. Seven bowlers had delivered more than one hundred and twenty balls in fourteen days. But the pattern did not show up in any of the completed columns. It showed up in the two names that left local cricket the following season — one with a shoulder complaint, one with an ankle. I wrote down all thirty-two of them by hand, and the pattern only showed up in the last column. That column was empty. It has been the first line of every injury piece I have written since: an empty column is also a document, we simply never built the habit of reading it. Three years later, in 2026, on a Chennai sports desk, I collected fourteen team notices and eight Ranji Trophy scorecards. Nobody had asked, before building the table, why the dates on those notices did not line up. The table got built, and it produced five soft-tissue absences clustering within eleven days of three-day turnarounds. Empty stadiums did not reduce the injuries. They only removed the noise around them. This week another file reached my desk. It carried a label — Asian cricket — and nothing else. No headline, no player, no date, no match, no format. This is not a rare failure. It is the ordinary condition of this beat. Fourteen absence notices had arrived before anyone thought to build a table; here, one notice arrived and expired before it could be read. Injury surveillance in Asian cricket is an accounting problem before it is a clinical one. No board maintains a central register showing which bowler sent down how many overs in a given week, across how many spells, with how many travel days between fixtures. What does exist is scattered across team bulletins, press releases, tweets and physio notes that never become public. Which means 'he got injured' is routinely not the same story as 'the injury was recorded'. And the documents that reach a reporter quietly become the dataset. My trouble starts there. I was raised inside Australian load-management orthodoxy — a real off-season, cooler schedules, fewer formats, and a bowler's count kept in a weekly overs log rather than inferred from body language. Transplant that framework into the Indian calendar — Ranji, IPL, bilateral white-ball series, no off-ramp — and it breaks. Worse, centrally contracted Indian players are not released to overseas T20 leagues, so the release valve every other system has is closed. When I borrow an Australian threshold, I say so in print. Heat, travel days, three-format congestion and the absence of a league release all change the price of every borrowed number. That is why my ledger opens with four columns and lives or dies by a fifth. Overs per seven days. Spells per session. Travel days between fixtures. Rest days between matches. And reporting lag — the distance between the date on the physio's note and the date the name appears on the team sheet. The fifth column should not matter. In practice it is the loudest one. A bowler whose injury is reported twelve days late starts rehab twelve days late. The delay is not in the news. It is in the treatment. I drew no conclusion from the thirty-two-match, seven-bowler table, and I do not draw one now. The n is 32, the window is a single season, and two names dropped out later. That is a hypothesis, not a mechanism. All it licenses is this: the scorebook does not explain the injury. It only tells you where to start looking. In 2026, when the IPL was suspended on 4 May and resumed in the UAE, I coded every spell across sixty matches — twenty-nine frontline fast bowlers. Twelve pacers had bowled more than twenty-four overs in the India leg. After the UAE restart, that group produced seven soft-tissue absences. The easy sentence was that congestion causes injury. I did not write it, because the table carried another column: quarantine and travel days. A bowler who sent down twenty-four overs in India and then spent two months in a hotel room was not in the same physical state as one who bowled the same overs continuously at home grounds. Two variables moved together. So I published the match-by-match workload table and named no cause. In 2026 the Impact Player rule arrived and most panels declared a tactical revolution inside a month. I waited thirty-eight matches, then coded all seventy-four, separating tactical substitutions from injury replacements. There were one hundred and twenty-eight Impact Player uses; only nineteen were injury-related. Batting totals rose. Bowling workload did not fall. Some television panels called the piece negative. My desk called it reliable. The difference was that I wrote what the table held, and where the table held nothing I wrote 'nothing' rather than 'probably'. This is where the real architecture of the debate shows. Arguing about a rushed comeback is easy — blame the captain, the selector, the physio. But at the level of the record, a player can only be shown to have been rushed back if we know when the note was written and when the sheet was updated. If that date does not exist, the argument does not resolve; it merely becomes two opinions. In my experience the largest cause of injury in cricket journalism is not bad rehab. It is a missing record. And that is administrative before it is clinical. There is a counter-intuitive corollary. I am not arguing for fewer overs. I am arguing that a bowler whose overs are counted can be managed, and a bowler whose overs are only narrated cannot. In Indian domestic cricket a fast bowler's overs are logged in three separate places — franchise, state association, board monitoring — in three different formats, and nobody has ever produced the sum. Until that sum exists, 'workload management' remains a phrase with no arithmetic behind it. There is a trap here too: absence-notice bias. Notices are the documents I can obtain, so the dataset quietly becomes a list of players formally rested or ruled out. 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. Playing through pain is data. Not appearing is data. Any system that counts only bulletins is ignoring more than half the actual load. My position on labels is fixed and repeats in every report. 'Injury-prone', 'fragile', 'workload casualty', 'niggle' — these are not explanations, they are the thing under examination. I will not call a bowler fragile until his overs have been compared with his team's median. If his seven-day overs sit two below the median and he still breaks, the problem is not workload; it is action, seam position under fatigue, or surface. And if his overs sit twenty per cent above the median, calling him fragile is an accusation I cannot yet support. The label is what a lazy desk uses when it has not counted. So when a file arrives carrying a label and nothing else, it is not empty to me. It is a specimen of the exact failure I have been describing for six years: a system that classified and did not record. Injury news in Asian cricket frequently arrives this way — a statement that a player is 'out', with no start date, no basis, no expected return. It becomes a headline. It never becomes a table. And here is the proportion almost nobody notices. We will spend hours on the surgical detail — scan, grade, injection, rehab stage — and five minutes on the record that should have said how many nights this man had spent in a hotel in the previous month. I remember building that 2026 table and finding the most startling row was not a row with an injury in it. It was a row showing twenty travel days across three legs and no injury at all. The system can work. It has to be asked to count. I will not close this by declaring who was rushed and who was not. I do not have that evidence, and the day I write without it, every other table I have built comes under suspicion too. The question runs forward: when will Asian cricket publish availability with the seriousness it reserves for the points table? Until availability is a statistic printed in the same font as runs, every 'fit' and every 'unfit' remains an estimate. Availability is a statistic. It has simply never been printed in the same font as runs.