The News Before the Diagnosis: Inside Indian Cricket's Incomplete Medical File

In the last week of February 2026, the Board of Control for Cricket in India issued a medical release. Six lines. Mohammed Shami had undergone surgery on his right ankle in London. Rehabilitation had begun. He would miss IPL 2026. For roughly four weeks before that, the news desk had run a queue of "sources say" — every bulletin swinging between "fear" and "hope," and not one of them carrying a date.

My complaint is not that the board was late. My complaint is that what arrived was the thinnest slice of the file. Ankle surgery — which surgery. The date of the scan. The name of the surgeon. How many checkpoints had been fixed for the next nine months, and what a setback at each of them would mean. Not one of those questions was in the release. That is the difference between news and a record.

I have been on the microphone since I was 19, and before that I sat in stands counting a fast bowler's run-up. Do this long enough and a habit forms: before the story lands, you open the footage to check it. In Indian cricket, the injury story always arrives before the diagnosis — and that is not coincidence, it is the system's output.

I keep a file, and its middle column is blank

I maintain a ledger of injuries. Every entry has three columns: the name of the injury, the first public statement, and the date of return. The frightening thing about a file with hundreds of entries is that the third column is the fullest and the middle one the emptiest.

Jasprit Bumrah — lower-back stress fracture. Last match September 2026, return in August 2026 on the Ireland tour. About eleven months. On record: the name of the injury. Not on record: which bone, what grade, in which month the board set the first rehab target, and when that target was revised.

Mohammed Shami — surgery February 2026, return in November 2026 through a Ranji Trophy match for Bengal. About nine months. Mayank Yadav — 155 kph-plus in IPL 2026, a side strain in the same season, a T20I debut in October 2026, then a long back-injury break. Deepak Chahar — hamstring and quad, again and again across four years. Prasidh Krishna — knees and quads, an extended sequence.

In the women's game the same file is emptier still. The WPL began in March 2026, and across three seasons there was never a publicly declared workload cap for fast bowlers like Renuka Singh and Pooja Vastrakar. The home ODI World Cup of September–November 2026 arrived without anyone ever stating what a bowler's annual over-quota was. Where the infrastructure arrives late, injury information arrives last.

The calendar is the diagnosis

The IPL 2026 final was played on 26 May 2026. On 5 June 2026 India played their opening T20 World Cup match in New York. Ten days between the two: a domestic flight, a long-haul one, an eight-to-nine-hour time-zone shift, and a pitch this attack had never bowled on.

Inside that ten-day window, the only job left for a fast bowler's body is recovery — the one item no franchise schedule has a slot for, because it doesn't score runs.

I will not turn this into an argument against the IPL. That is the easiest applause line in Indian cricket writing and the most useless. The question is not the tournament, it is the dates. And every date has an owner:

• The board — sets the international calendar and the NCA reporting windows.
• The franchise — divides the spells across eight weeks.
• The player — reports his own fatigue, and that reporting is never published.
• The selector — grants the rest, and never records why.

Not one of those four decisions reaches the public with a date attached. So when the breakdown comes, the debate stops at whose fault it was and never arrives at how much load was carried.

The frame before the diagnosis

I was made in 2026. The IPL was played in empty stadiums in the UAE and the stump mic was clean. With no crowd noise, sounds that usually get buried were recorded — the grunt at release, the call for the trainer, the captain's small question asked away from the cameras. That season I built a sheet of all 60 matches, logging every soft-tissue injury alongside the rest days that preceded it. Most of them were fast bowlers.

That sheet taught me a method I still use as my first filter. An injury is never confirmed by a frame; it is confirmed by a sequence.

I tore my own knee at Navrangpura — March 2026, a BCCI one-dayer, turning for a second run, grade 3 ACL, nobody near me, no contact. Since that day I know what a bad step looks like in slow motion, and I also know how easily one bad step gets renamed into something else.

So I ask for three overs minimum. In the first, the length and cadence of the run-up; in the second, the bracing of the front leg at the crease; in the third, the length of the follow-through and the position of the seam. The footage was clean until the 14th over. Then the step changed. That is the primary document — not the grimace, but the over after which the rhythm broke.

A protocol for silence

If I could fill the middle column of my file, it would hold four things. First, the name of the injury alongside the date of the scan that named it — not "back," but the specific investigation. Second, the clinician who made the diagnosis and the institution that wrote the rehab protocol. Third, the return window in weeks, not months. Fourth, and most important, the dates of rehab: first gym session, first bowl, first full run-up, first match-intensity spell — and at each stage, what a setback would look like.

None of that breaches medical confidentiality. It is the same information every public employer gives to explain an absence. Cricket hides it under the phrase "the player's privacy," when in fact it is institutional convenience — because a delay attached to an undisclosed grade cannot be booked against anyone's account.

I watch what fills the vacuum instead. Net-session video fills it. The "bowling at full tilt" caption fills it, showing twelve deliveries and never showing the rest between them. Then the warrior frame fills it, the grit, the comeback. Heroic framing is the easiest story available, which is exactly why it hides the most load. A return is not an emotion; it is a set of dated checkpoints. A report without dates is not selling a comeback, it is selling hope.

The counter-intuitive question: transparency is also a load

Now the part I argue with myself about. The easy position is that the board should publish everything, the file would fill, the debate would correct itself. I don't think that is entirely right.

Every public checkpoint becomes a fresh deadline the player has to answer to. Announce that the first full run-up comes in the first week of June, and by the second week of June someone will ask whether it happened — and if it didn't, nobody will ask whether the body was behind schedule or the rhythm was. Setbacks in rehab are normal, part of the protocol. A public checkpoint converts that normality into a headline against a player's name.

So my proposal is not less transparency, it is structured transparency. Not a full medical feed — three declared dates a year: the date of diagnosis or surgery, the date of first bowling, and the expected return window. Three dates, three accountabilities, no more. And the owner of those three should be whoever sets the workload — not the franchise, but the board's medical team.

Forward

Asking for three dates today sounds unreasonable because the habit does not exist. But habits have histories. In 2026 I was 17 and writing a rehab diary that logged one physio session and a measured range of motion every week, because I had nothing else — only the discipline of keeping my own body as a ledger. That diary is my template now.

The next time a fast bowler pulls up mid-run-up, three questions should already be settled: which over the rhythm broke in, what the date of the scan was, and who writes down the date of the first ball bowled. The day those three answers exist outside the dressing room, the injury story will stop arriving before the diagnosis. The only question is whose file that day gets recorded in.