The Empty File: When Injury News Arrives, and When Cricket Stays Silent

I begin with an empty file. Last week a document landed on my desk with fourteen fields. Title: N/A. Source: N/A. Date: N/A. Summary: blank. List of facts: blank. Exactly one of the fourteen was populated, and it read: cricket. So the sport was known. The player was not, the format was not, the season was not, the ground was not. The document passed every schema check, because an empty document does not look broken. An empty document looks tidy.

I have been keeping a ledger of injury reporting for eight years, and that document did not surprise me. The Indian cricket medical bulletin arrives in precisely this shape — formal, polite, and empty of dates. "Bumrah has been rested." "Shami's progress is satisfactory." "His return is being monitored." No grade, no scan date, no named protocol, no name of the person who signed the file. Fourteen fields, thirteen of them blank.

This article is an accounting of that blankness. I am not going to write whether a particular player is fit or not — I have no evidence for that. I am going to write about what gets filled into that silence, and who pays for the filling.

The footage was clean until the 61st minute. Then the step changed. In my trade, the "61st minute" is the sixth over of a spell — the point where the run-up cadence breaks, where the next stride lands half a foot short, where the seam position collapses. After that frame there are usually two routes: a bulletin, or a net clip. And for the last few years, the net clip has won every time.

The date is the thing the bulletin never contains

Injury information in Indian cricket leaves through three doors. The first is the formal board release — usually carrying the name of the injury, an approximate duration, and the line "will report to the NCA." The second is the captain's or coach's press conference, where "he's fine" is treated as a complete medical sentence. The third is the trainer running onto the field, which is the most honest document of the three, because nobody edits it.

All three doors share one property: the absence of a date. Only occasionally does a board write down when the scan was done, who read it, and when the next review falls. Because of that, the reader is left with exactly one piece of information — he is out — and builds an entire story out of that single sentence. The biggest crisis in cricket injury reporting is not that teams lie. It is that they state only the portion of the truth that nobody can challenge.

I understood that distinction in 2026, when I was handed the "injury watch" box on a World Cup night desk — the section nobody wanted to touch. Mohamed Salah arrived from the 26 May 2026 Champions League final in Kyiv carrying a shoulder injury. My note at the time said he would be a penalty-box finisher, not a runner. Through the group stage, that note held. That box gave me a rule I have never broken since: no fitness story without a named medical source and a precedent case.

Let me be explicit, because everything below rests on it. What is happening inside a player's body can be established from three things only: a statement from a named doctor or physio, a scan report, and dated return-to-play checkpoints on a calendar. If none of the three exists, what remains is not analysis. It is weather.

The calendar is the diagnosis

I read injuries backwards. The first question is not where the injury happened. The first question is who got that body to that week.

The IPL 2026 schedule is still saved on my machine: 19 September to 10 November 2026, sixty matches in the United Arab Emirates. Through that season I logged every soft-tissue injury into a spreadsheet and counted the rest days between them. Twenty-three hamstring, calf and groin strains, with fast bowlers forming the bulk of it. That figure is not a board report — it is my own count, and I present it the way an auditor presents a worksheet.

The clearest thing in that sheet was not the heat. It was that turnaround days and strain counts were moving in the same direction. A bowler with fewer than three days between appearances had another column filled against his name. When I wrote that the fault lay in the calendar and not the weather, forty thousand people read it.

IPL 2026 is an even cleaner case, because that season contained a gap that has no business existing in any workload ledger. The season was suspended on 4 May 2026 and resumed on 19 September 2026 in the UAE. Four and a half months between two halves of one tournament. A bowler who played four games in the first half and then walked straight into death overs in the second half was asking his body to behave like two different seasons — and none of it was recorded anywhere.

Workload is not an opinion. It is a queue of dates. And when there is a hole in the queue, the injury is not suffered — it is invited.

Whenever an injury story breaks, I pull the player's previous twenty-one days: domestic matches, franchise matches, travel legs, NCA reporting windows. The picture that emerges from those four columns is usually different from the picture in the bulletin. The bulletin says the injury happened. The calendar says the injury was scheduled, and only the date was pending.

The frame before the diagnosis

I am routinely accused of reading too much into a single frame. The accusation is half fair, which is why I have imposed a rule on myself: one frame is never enough. I require a sequence across three overs.

Take the ankle injury Mohammed Shami suffered on 2 November 2026 in Mumbai, during the World Cup match against Sri Lanka. The important question after that day was not how severe the injury was. The important question was that he kept playing through the tournament. I went back and watched three overs: the over before, the over of the injury, and the first over of his next match. In the first, the front leg was bracing straight. By the third, that same leg was falling away after release. That difference is what no bulletin records and no scorecard displays.

The most reliable document of an injury is not the scan report. It is the over in which a bowler's front foot shifts half a foot from where it has always landed.

Jasprit Bumrah's case is the other side of the same rule. After a stress fracture in his lower back in 2026 he was out for a long stretch, returning in January 2026 for the ODI against Australia in Bengaluru. More than four months away, and a comeback in a match that demanded a full ten overs. That is what I call a clean file — because in the middle there was a calendar, a named protocol, and a return date that could be written down before the match.

Compare that with the common pattern: a bulletin, then three weeks later a net clip showing the bowler at full tilt, then a match the following week. Nobody says which checkpoints were cleared in between, who signed off at each one, and what failure at each one would have looked like. Rehab is a calendar, not a comeback. And where the calendar carries no dates, a comeback story gets written instead.

The list nobody wants to be on

I keep a list no player wants to appear on. It is the load history of Indian fast bowlers — overs bowled per season, days between tournaments, and what followed. When a new injury arrives, I price it against that list.

The list does not predict. It prices. When a fast bowler's ankle or hamstring goes, the loss is not confined to that match. The cost is paid in three places: the Test series, the central contract tier, and the next ICC event window. Those three together decide whether an injury costs a season or a career.

One technical point belongs here, because without it the entire argument runs in the wrong direction. The ICC maintains three separate ranking tables — Test, ODI and T20I. Workload data built in one format cannot be borrowed by another. Forty overs in a T20 month and forty overs in a Test month are the same number and not the same load. Analysis that discusses injury without fixing the format is not analysis. It is noise.

When a report does not even record the format, whatever gets added to it is not analysis — it is inference.

Format changes the arithmetic

Look at another picture inside international cricket. The IPL door and the board door run two separate calendars, and the player stands between them. The NOC system exists precisely because of this double calendar. When a centrally contracted player asks permission to play an overseas league, the real question is not the permission. It is the turnaround that follows it.

I want to be clear that my target is not the IPL. The IPL is the most visible load, which makes it the easiest applause line in Indian cricket writing. The real question is who decided on which date. There are four owners in every injury — the board, the franchise, the player, the selector. The board owns the reporting window, the franchise owns the playoff race, the player owns his place in the side, the selector owns the name of the next series. In every injury, one of those four owns the date, and no bulletin records the ownership.

I learned this in 2026, when I landed on that list myself. March 2026, the Sardar Vallabhbhai Patel Stadium in Navrangpura, a BCCI one-dayer for Gujarat Under-19. I was a left-arm spinner and I turned for a second run. Nobody was near me. No contact, no collision, and my ACL tore, grade 3. Surgery in April, nine months of rehab. I never turned that injury into a story; I turned it into a log. Thirty-eight weeks of entries, one physio session and one measured range of motion per week, published as "Rehab Diaries." That log taught me something no press conference ever did: the most honest document of a return is the date nobody bothers to announce.

That same year I deleted the word "hopeful" from my copy permanently. "It is hoped he will return for the next series" is not a medical sentence. It is entertainment. A medical sentence reads like this: running in week five, bowling group in week seven, full spell in week nine, match in week ten. And at each stage it states what a failure at that stage would mean.

Women's cricket: contracts first, structure later

This is where my larger concern begins, because this front is still open. The first Women's Premier League season was played in March 2026. In 2026 India hosted the Women's World Cup. Money, contracts, cameras and audiences arrived first. Workload structure, rotation habits and reporting formats are arriving afterwards.

Men's cricket already ran this experiment between 2026 and 2026, and we paid for it in fast bowlers' knees and backs. Women's cricket had the option of not repeating it, and from what is publicly on record so far, no ready-made structure was built in advance. The number of overs a WPL seamer bowls across three weeks can equal her entire domestic season. That number does not exist in any public report.

I am not saying any player is injured, or about to be — I have no evidence for that. I am saying that a league without a public workload ledger will make every injury story sound like rumour the first time and arrive late the second time. Three games in eight days is not a stress test with a result to follow. It is the result.

An empty bulletin is not a low-risk verdict

Here is where I have to disagree with a good number of my readers.

When no news arrives about a player, the cricket audience draws one of two conclusions: nothing serious, or the team is hiding something. Both conclusions come from the same error — treating absence of information as information. The most basic rule of my trade is that what is not on the record cannot support a conclusion. An empty file does not mean low risk. An empty file means: not yet known.

This is why comeback mythology irritates me so much. The warrior's return, the pain conquered, the tears to the field — all of it does the same job: it hides the load. Once a return is framed as a struggle, nobody asks how many overs that man bowled in the last eleven months, how many nights he spent in hotels and how many in aircraft. The story ends the question.

There is also the reader who sees a conspiracy in every injury — the franchise hid it, the board suppressed it, the selector knowingly picked him. I am not claiming that never happens. I am claiming that saying so requires exactly the same three things as refuting it: a name, a date, a document. Without those, both sides of the argument are two faces of one coin, and in both, the body has disappeared.

Eight years of watching matches has taught me that the least-read document in cricket is not the scorecard. It is the medical release — because at least a scorecard carries a date.

There is another angle that no board pays attention to. An empty bulletin does not only mislead the reader; it misleads the player. When a bowler does not know when his next review falls, he starts setting his own return date — and that date tends to land immediately before the next major tournament. That is not carelessness. It is a vacuum, and a vacuum always finds someone willing to fill it.

What is missing

I will not end this by writing that more information should be shared. Everyone has written that sentence and nothing has changed.

I will write down what should be recorded, because a list can be built. An acceptable injury bulletin should carry five things. One, the player's name and the format, because a Test load is not a T20 load. Two, the date of the injury and the date of the scan, separately. Three, the grade and the name of the protocol. Four, the name of the medical professional who did the assessment. Five, the dates of the next three checkpoints and what failure at each checkpoint would mean.

If even one of those five is missing, what remains is not journalism. It is the thing that landed on my desk last week — fourteen fields, thirteen of them blank. The document was tidy. The document passed every check. And the document contained no cricket.

The question is not which of the board, the franchise, the player or the selector is lying. The question is which of the four will own their date — and when those signatures get made. The day those signatures exist, injury news will not stop. That day it will simply have a document, and I will not have to fill it from guesswork at a four o'clock deadline.