Every Field N/A: Athletics' Empty Ledger and the Story It Actually Told

It was afternoon in Chicago when I opened the file. Nine dimensions. Forty-seven fields. Beside every field sat the same two characters — N/A. Performance assessment: N/A. Wind reading: N/A. Qualifying standard: N/A. Season's best against personal best: N/A. Coach's name: N/A. Testing history: N/A. Phase of the public narrative: N/A. Transmission path: N/A.

The framework was fully assembled. The table was laid, the chairs arranged, the column headers polished. The guest did not arrive.

I am a data journalist. My job is not to write about athletes; it is to audit the machine that writes about athletes. Since I was seventeen, the record book has been an untrusted source to me — something I will not accept until I have rebuilt it from primary results. This time the machine said nothing. That was the story.

I went looking for a trend and found a hole. There is no data here. That is the finding.

What the framework was built to do

In 2026 I joined a Chicago digital sports desk as its second data hire. In five months I built an automated match-report engine across 1,020 matches of the 2026-17 European season, encoding xG, PPDA and field tilt into templates that filed 1,100 recaps before an editor touched them. My first pitch argued that a 2-1 win was really a 0.4-2.3 xG defeat. The desk editor spiked it. I rewrote it with the shot map as the lede and it cleared. The lesson held: the number is the story, not the footnote.

In 2026 the live data stopped. Furloughed to three days a week, I started a javelin release-parameter project from broadcast footage. That was when I understood that Indian athletics does not suffer from a shortage of data. It suffers from a shortage of published data. I wrote a scraper against AFI and state-meet result PDFs — 1,400 documents covering 2026 to 2026. The output: published 400m split data for exactly three Indian meets in a decade. The black box became the beat.

So when I build an analytical frame, it stands on nine dimensions. One: performance assessment — the mark against the world record, against the qualifying standard, against contemporaneous rivals, with the mandatory wind, altitude, track and shoe corrections. Two: athlete condition — PB progression, injury history, peaking. Three: competition structure — the dual channel of qualifying standard and world ranking, the architecture of national selection. Four: event landscape — the season's top ten, group depth, the pipeline. Five: rules and anti-doping — ABP, whereabouts, equipment compliance. Six: the training system. Seven: the risk matrix. Eight: public narrative and the expectation gap. Nine: industry transmission.

The framework can hold an athlete's entire career. This time it held nothing.

Finding one: the null is itself a diagnostic signal

Let me show you the receipts before I show you the conclusion. The file that reached me had no title, no source, no article type, no core viewpoint, no information points. The field meant to list athletes, coaches and competitions was empty too. This is not an article without a name — such an article does not get published. Any athletics item that survives editorial review contains at least one of four things: an athlete, an event, a mark, a venue. All four vanishing together is not statistically impossible. It is implausible.

So the first conclusion is blunt: the failure is not in athletics. It is in the ingestion. The break point is identifiable — the title and source layer, upstream of entity extraction. Had entity extraction run and found nothing, the title would still be populated. An empty title means the source document was never read.

This is a story about a pipeline, not an athlete. Pipelines get fewer readers. They still need writing.

Finding two: the null is not an accident, it is the baseline

Here the real audit begins. An empty file can be dismissed as a bug. But my scraper's 1,400 PDFs arrived at the same verdict this file did — N/A everywhere. Three meets in a decade. That is not coincidence; that is architecture.

In Indian athletics, missing split data is not a technical gap. It is a priority decision. A meet that is not televised does not get a photo-finish camera. Where there is no photo-finish, hundredths are not recorded. Where hundredths are not recorded, no split narrative exists. And where no narrative exists, a fourth place from that race never enters the record at all.

The spreadsheet was clean. The story was not.

This is where my oldest stubbornness returns — the fourth-place audit. Milkha Singh finished fourth in Rome 2026, fractions from bronze. P. T. Usha finished fourth in the 400m hurdles at Los Angeles 2026, missing bronze by 0.01 seconds. We remember both as national grief-narratives. Ask the ledger how many athletes in that field were electronically timed, how deep the field actually was, and which comparable performances from the same year disappeared from the record, and the answers are thin. We mourn a margin whose denominator was never published.

Usha's 0.01 was real. It was electronic. There is no doubt about the gap. The question is not whether the margin was true; it is that the coverage built around it was one-sided — we measured that race from a single athlete's angle and declined to measure the rest of the field. That is nostalgia without a denominator, and it is the cultural form of the same N/A that appeared forty-seven times in my file.

Finding three: a podium count is not a pipeline

The file noted that no depth assessment was possible because the season's top-ten list was unavailable. That is the root of my second stubbornness — the depth ledger behind the medal.

I remember the morning of 7 August 2026 clearly. Tokyo. Neeraj Chopra threw 87.58m for India's first Olympic athletics gold. I had the model ready — 63 javelin throws coded for release angle, block-leg extension, approach velocity — and filed ninety minutes after the final: his winning throw was his fourth-best of the season by release speed and his best by angle. An Indian outlet syndicated it, and editors started calling me for javelin numbers instead of vibes.

The following July, in Eugene, my first credentialed World Championships. Neeraj took silver at 88.13m and I coded forty throws in the mixed zone with a laptop balanced on a cooler. One question ran in the background: what does the row beneath the headline name actually look like?

Budapest 2026 answered part of it — Neeraj gold, Kishore Jena fifth. Two Indians in one Worlds final. That is a data point, not a production line. A production line is not measured in medals. It is measured in the number of Indians clearing 80m inside a qualifying window, in the conversion rate from junior to senior, and in the number of domestic meets where senior-level competition actually exists. All three of those are N/A in exactly the way my file was N/A.

The 90m obsession covers that hollowness. The record is 92.97m and it belongs to someone else. That is a finding, not an insult. Since Tokyo, this beat has learned to treat 89.45m silver as failure, and expectation inflation works the way empty fields work: the more blank space, the more room for invention.

Finding four: the dangerous move is reading N/A as clean

One line in the file stung most. Under anti-doping it read: no testing history, ABP status or whereabouts record supplied. And beside it, the warning: absence of evidence here must not be read as evidence of compliance.

That is the most honest sentence in the document and the one most likely to be deleted. Hand this file to a product team and the slide will say "no red flags." Within a week, "no red flags" becomes "clean record." That is the actual corruption route in data journalism — not inventing numbers, inventing completeness.

I think of 2026. The Russia World Cup live desk: 64 matches, twelve analysts, a three-shift rotation I designed in 48 hours after the opening match broke us. On 27 June 2026, Germany lost 0-2 to South Korea in Kazan. Forty minutes later we published the pressing-collapse chart: German PPDA had drifted from 8.1 at Brazil 2026 to 13.6 across the 2026 group stage. Our most-read piece of the year, most of it written before the final whistle. Somewhere in the third hour of the live desk, the numbers stopped lying — and that day I also learned I had built that rotation without asking anyone, which two analysts told me plainly.

Empty fields demand the same discipline. N/A means "nothing was found," not "nothing exists." The distance between those two readings decides whether a report is an audit or a guess.

The contrarian angle: the courage is in refusing to fill the blanks

There is a convenient route here. I could write that Indian athletics has a data crisis, that the administration is guilty, that this is a scandal. It would read fast and travel well. It would also be the same sin in a different costume — filling blank space with my own story.

The inverted truth is that this file contains no failed athlete, no failed administration, no failed narrative. It contains a failed reading layer. And if that layer is repaired, perhaps six of the nine dimensions will stay empty anyway — because where splits are not published, no PB progression curve can be built; where coaching information is not public, the training system cannot be assessed. Fixing the pipeline will not end the data crisis. It will only make it visible.

That is the real finding: we do not have a shortage of stories. We have a shortage of measurement. And mistaking the second for the first is the easiest error available.

What to watch next

The next step is obvious and boring. Re-ingest the source document. See whether a title and at least one information point come back. If they do, the whole frame above populates without rework. If they do not, the item is unverifiable and belongs in no dataset.

The thing I will be watching next month is not a mark. It is this question: when the next file arrives with forty-seven empty fields, will we publish it — or will we invent a name to fill it, because the reader wants a name and the editor wants a slot?