The Empty Column Is Also a Record: The Injury Ledger Indian Athletics Never Files

There were nine columns. The first was meant to hold a name — it stayed empty. The second, an event — empty. Mark, competition, date, injury history, coach, tier, risk: eight columns stalled on the same entry, insufficient information.

This was not a theoretical exercise. It is the nine-dimension audit frame built for athletics — performance assessment, athlete condition, qualification mechanics, event landscape, rules and anti-doping, training system, risk matrix, public narrative, and the industry transmission chain. It was run against a record, and the record held nothing worth testing. The frame came back with a single line: there is no material to examine. When the source carries no facts, the most honest finding is also blank — and that blank is itself reportable, provided someone is willing to report it.

What happened here is not merely a technical glitch. It is a small sample of the everyday condition of the beat I have worked for nineteen years. Performance in Indian athletics is recorded like heavy rainfall — every heat time, every round's start list, every meet's results sheet. In the same sport, the body's record is a dry well. Nobody's central register says how many days a hamstring took, who was scanned for what, who was entered as DNS at which meet and why. The Athletics Federation of India publishes no injury surveillance. The physio notes written inside SAI centres and at NIS Patiala stay inside. Only two things come out: the start list, and the disappearance of a name from it.

My first job was on the night desk of a Bangalore digital sports operation in 2026, as a results assistant, aged twenty-six. The work was direct: AFI wires and domestic results. Eleven domestic meets — Federation Cup, National Inter-State, National Open, Indian Grand Prix legs — and three road races. Across them I logged 214 withdrawals, DNS and DNF entries. An economics training had given me one habit: treat these as a sample, not as anecdotes. So I built a fixed template — event, round, age, personal best, days since last race, sports-quota employer, and whatever public rehab note existed. The template never changed afterwards, even when louder stories walked past the desk.

The clearest output of that log: 38 per cent of 400m and relay withdrawals involved a hamstring or groin. That number says nothing about any individual athlete. It says something about the event — one in which the body is asked for the same thing repeatedly, and in which rest is not a calendar item.

April 2026 was the Gold Coast Commonwealth Games; July 2026 was the World U20 Championships at Tampere. I covered both from the Bangalore desk. Hima Das's 51.32 seconds for 400m gold at Tampere was the clean story — time, round, medal, done. The dirty story was nowhere on the results sheet: within nine weeks, five Indian 400m runners reported hamstring or groin strains, three of them from the women's relay pool. I counted 34 race starts, travel legs, camp moves between Patiala and the competition base, and days between rounds. The pattern was not one bad workout. It was calendar compression. A cluster is not a coincidence. Three hamstrings in one squad is a schedule problem, not a character problem.

That is where my method changed. I adopted cluster language, built calendar-load tables, and stopped blaming a single session. I began keeping a precedent file of nine-week windows, which made my injury pieces slower to publish and much harder to dismiss.

In 2026 that paid off and cost me at once. The pandemic emptied stadiums and froze the AFI calendar. Between March and August I wrote fourteen rehab explainers with no live results to lean on. For a 27-year-old 800m runner with a grade-2 hamstring strain, I projected six weeks. The actual return was eleven. I audited nine comparable cases from my log — mean error 3.8 weeks, worst error five weeks. The fault was not in the model but in the thinking: I was reading rehab as a fixture list. The scan said six weeks. I have learned to add the hidden weeks. I rebuilt the model around milestones instead of dates — pain-free jogging, seventy per cent sprint, full stride.

Back to the empty spreadsheet. If an audit that returns N/A across nine columns reaches a reader without a warning label, he will read it as: no risk found. That is the single largest hazard in this whole exercise. "Not assessed" and "assessed as safe" are different sentences, and the distance between them is often exactly one injury long. I have a rule in my own work: no rehab timeline until there are three comparable cases and one named public source. Where that condition fails, the correct word is unknown, not an estimate.

The second lesson is more concrete and it comes from the calendar. A return date is never purely medical. It depends on whether the athlete sits inside a SAI centre or NIS Patiala with a physio on staff, or holds a Railways sports-quota post and trains alone between inter-departmental meets. Same grade-2 strain, two support systems, two different returns. Put the announced weeks against the base rate for that injury, that event and that support level, and the delta is the story. That delta never reaches a report, because no federation puts its own support inequality into a column.

An honest boundary belongs here too. From a distance I cannot tell you how badly a runner's hamstring tore or how long a stress line runs through a bone. The scan report does not arrive at my desk; a camp's "niggle" arrives as a word, and a word is not a diagnosis. What I can do is count — who vanished when, who came back when, whose absence was never explained. I kept a withdrawal log at 3 a.m. for eleven months. It taught me what absence looks like. It looks like a column with no name in it, only a date.

This is where the temptation to fill the blank begins, and I am writing against it. Three easy routes.

One: the fourth-place inheritance. Milkha at Rome 2026, Usha at Los Angeles 2026, 0.01 seconds off bronze. It is the readymade emotional grammar of this beat and it flatters the writer as a custodian of memory. But it belongs to genuine near-misses. A season's best that loses is not a national heartbreak. Tokyo 2026 broke that spell; forcing it back now is mere laziness.

Two: reading every absence as concealment. The federation's communication is genuinely poor, so an unstated reason feels like a proven one. "No stated reason" and "a reason was suppressed" are not the same sentence. Most often the actual cause is calendar chaos, an informal fitness test, and the absence of any medical-reporting infrastructure. Saying so is the stronger finding, because it can be fixed. An insinuation of conspiracy leaves nothing to fix.

Three: doping inference by default. The 2026 CAS-confirmed bans on six women athletes, including members of the 2026 gold-medal relay squads, stand right behind the era I cover. So a sudden withdrawal invites the inference automatically. Write that era with the asterisk, not the insinuation: cite the confirmed bans, apply base rates to the individual case, and never let a schedule gap stand in for a positive test.

All three routes do the same work — they fill the empty space comfortably and remove the need for evidence. That is the most common error on this beat, because a filled paragraph gets read more than an empty spreadsheet.

So what should be done with the empty column? Publish it, the way times are published. The best injury reporting is boring: dates, mechanisms, and the same question asked twice. Before I believe a comeback, I look for the minutes nobody talks about — the first race that lives in a training note rather than a results sheet; the first round where an athlete ran two seconds off her personal best and nobody asked why. And I got six weeks wrong once. Now I check who benefits from the early return date: a sponsor, a selection-trial calendar, or a quota employer whose meet lands squarely in the middle of a camp.

The demand I would take out of this whole exercise is small and not difficult: the AFI should publish a DNS column alongside every domestic meet's start list, with name, event, round and stated reason — and where there is no reason, say plainly that there is none. This is not injury surveillance. It is merely something anyone can count. In a sport that records to the hundredth of a second, asking for it is not much.

The scan said six weeks. What the seventh week looked like has never appeared in any report. The next time an athlete disappears from a start list, ask which column recorded the name — or whether the column was ever built.