An Empty Column Is Still a Result: Why I Won't File a Cricket Report Without Evidence

Ten past nine, the morning of 10 September 2026. The Old Trafford press box was half full and the fifth Test accreditation was in my hand. On the laptop sat a blank scorecard template; beneath it, the spiral notebook with every Indian seamer's spell logged by hand across the four Tests already played — length, rest interval, previous-day volume. A few hours before the toss, a positive Covid-19 test surfaced in the Indian camp and the match was gone. Not one ball was bowled.

The record still carries a result from that day. The same Test was played at Edgbaston in July 2026 and India won by seven wickets. A Test that never starts still leaves a result in the record.

Last week another blank sheet arrived. A title field, a source field, a domain reading cricket, and an information-point list that was empty. Zero facts, zero names, zero dates. Complete skeleton, missing body.

The habit goes back to 2026, when I was a volunteer with Lancashire's medical and conditioning staff at Old Trafford and the whole job was to log every delivery by hand. Three columns: overs, rest interval, previous-day volume. That August I applied the same method to India's tour of England — five Tests, more than a thousand deliveries, and a separate sheet for Jasprit Bumrah. The first clue was not the injury; it was the delivery ledger.

Bumrah, returning from a thumb fracture, took 5/85 at Trent Bridge. The papers wrote the comeback. My notebook recorded something narrower: the length of the first spell, the gap to the second, and the three consecutive days that followed. A hand-kept ledger does not lie; it only waits to be read. It does not name a cause, it dates the risk window. That is the distance between data and drama.

Empty stands taught me in July 2026 what a crowd never lets you hear — the sound of ball on seam. Across the bio-secure fixtures I stopped counting overs and started timing the gap between spells. What showed up was simple: the compressed calendar had stripped roughly a day of recovery from each fast bowler's cycle. Nobody was publishing that number, so I wrote it into a free newsletter with eleven subscribers. Since then the schedule comes before the scorecard.

After 10 September 2026 I set a rule I still keep: no injury claim reaches print without two independent confirmations and a look at the player's previous six weeks of spells. It made me slower than the news cycle and, in time, more trusted than it. The medical file is the first scouting report, and it rarely flatters.

This time the file contained no file. Zero information points, no resolvable entities, time sensitivity not assessed, article type unclassified, and a domain label of cricket_world instead of cricket. Three causes present themselves immediately — a scraping block, a paywall, or a JavaScript-rendered page the parser could not read. All three share one feature: the failure happened in extraction, not in the content.

A complete skeleton does not manufacture facts — and a fully structured report built on empty evidence is more dangerous than silence. Silence keeps a reader alert. An eight-section, confidently headed report puts them to sleep. Cricket carries that risk more heavily than most sports, because a plausible fact here is unusually cheap to invent. A score, an over count, a venue — all familiar enough that readers accept them without checking.

That is hallucination contamination. An empty source fed into a summarising system gets its gaps filled by inference, and the next layer cites that inference as a source. Two steps downstream, nobody can separate the fact from the filler. I have watched this chain run in cricket journalism many times, though usually not on paper — in bulletins, where a line beginning understood to be turns into a fact by the next morning.

The industry's incentives run the other way. Filling the gap is rewarded; admitting the gap is penalised. Editors want the sentence that runs, and sources say is the cheapest glue available. Which produces the least comfortable finding in this whole audit: the most valuable sentence in a cricket report is often we do not know yet. It does not mislead the reader, and it leaves room for the correct story tomorrow.

One caution is essential, because the principle that absence is evidence is slippery ground. Absence has a sound, and it usually arrives before the diagnosis — but only when the absence is documented. A name dropped from a team sheet, a press conference evaded, a net session quietly skipped: those are recorded events and they can be read. A blank page is different. A blank page does not say the player is missing. It says your instrument failed.

When a column sat empty in my notebook, I never treated it as zero. I treated it as a day I was not in the stand. In the record, that distinction changes everything: zero and unread are not the same number. The silence of a calibrated instrument is data; silence without calibration is only noise.

So I did not fill the eight sections this time. I wrote what could be written: the evidence is nil, and finding out why the nil exists is the next job. The report that looks unfinished is often more complete than the one with every box filled and not a single brick beneath it.

The next time an empty file lands, build the check into the pipeline rather than quietly padding it — an extraction-count assertion, a minimum of three information points, mandatory columns for outlet, date and byline. That work is dull and will never make a highlight reel. But if cricket journalism wants to be trusted through the next decade, it has to decide what an empty column means: a fact, a failure, or an opening.