Eleven Fields, Eleven Blanks: When the Cricket Data Never Reached the Room

At six in the morning the first tea arrives in the Kolkata press box, and ten minutes later the first feed. That morning the analysis report that came with the feed carried a warning box at the very top. It said one thing: the article meant to be analysed never arrived. Eleven fields were expected — title, source, format, player, team, ranking, time-sensitivity, stakes. Beside all eleven: N/A. One under the other, eleven times, like a scorecard misprinted with no batsmen's names and no runs. The line that stung most sat inside: "Information Points: zero." In cricket a zero is a score, an event, sometimes a humiliation. Here the zero was an empty room, and that room smelled like my old press box, where the phone would cut and we would file the absence of news as news itself.

The document was a two-stage cricket-domain analysis. Stage one breaks an article into atomic "information points" — hard, citable facts. Stage two builds eight dimensions on those points: format and match nature, player technique and data, team landscape and rankings, league and commercial structure, rules and governance, risk, public narrative, and industry transmission. The framework's rule is strict: every conclusion must cite at least one information point, and the three formats must never be mixed. That morning the array was empty. Zero. The foundation on which all eight dimensions stand simply was not there. The page the article came from had either failed to open, or opened and returned blank.

Format is the heaviest beam in this framework, and it fell first. Test, ODI and T20 benchmarks are not interchangeable — the same strike rate is middling in one format and extraordinary in another. The ICC itself keeps three separate ranking tables; a side can sit top in Tests and outside the top five in T20Is. So the first question in cricket analysis is always: which format? When the answer is N/A, every number after it becomes a guess. Run rate, economy, average, endurance — the whole arithmetic hangs on that one unanswered question.

The player dimension hurt more. Not one cricketer was named in the document — no batter, no bowler, no coach. This was not thin data; this was a situation where player-level analysis was impossible in principle. I have to explain that distinction constantly, because on an editorial desk the two look identical. Low data means the conclusion will be weak. Zero data means there will be no conclusion at all. That day it was zero.

An old habit helped here. In the months after the 2026 fixing inquiry we were taught a lesson that appeared in no press note: read the silence, but do not mistake silence for conspiracy. "No comment" and "no story" come from the same dictionary and mean different things. That morning's lesson was exactly this. The report did not say the board hid anything; it said the document did not arrive, the date was unrecorded, the source was absent, and the file we were waiting for was stuck somewhere in the pipeline. To turn silence into evidence you must at least record that much.

Now the part that matters most. When the entire document is null — every field, no exception — the likeliest cause is not an empty article but a broken pipeline. Total-null and partial-null are two different illnesses with two different cures. Partial-null tells you something: if the article carried no numbers, it was a colour piece or a comment piece, and that is information. Total-null tells you nothing except that the fetch failed, the page sat behind a paywall, the page was JavaScript-rendered, or the source was a live-blog stub or a photo caption with no body text at all. All four are technical problems, not editorial ones.

And here sits the biggest danger — the pressure to fill an empty template. Whether a human or a machine sits before those blank boxes, the temptation is identical: make the structure look complete. Cricket commentary offers three easy routes, and all three were entirely absent from this document — the ageing-core fatigue argument, the old DLS complaint, and IPL economics. All three are real subjects, all three can host a good debate, and all three would have been lies here. A plausible-looking fact dropped into an empty slot is still a lie, because it has no context.

N/A does not mean "clean." N/A means "not examined." That single sentence is the most valuable thing in the whole document. Every cell of the risk matrix read "cannot be assessed," and the report said plainly that this is not the same as "low risk." The governance checklist behaved identically. A hurried desk will read it as "no governance controversy" and put it on a front page that night. That is the real problem — a record existing is not the same as content existing, and too many feeds still treat the two as one.

The document also wrote its own fix, and it is cheap: install a hard gate in the pipeline. Information points must number at least one, the title must not be null, and the entity list must not be empty — stage two should not begin until all three checks pass. Records failing these tests go to quarantine, and the same source gets a retry with fetch logging switched on. If a second run also returns zero, the question is not about the analyst; it is about whether the source is reachable at all.

Now the counter-intuitive question that troubles me most. In recent years cricket media's great fear has become "hallucination" — a machine will invent a cricketer's average and we will not catch it. That fear is legitimate, but it lives in the noise. What this document revealed is more dangerous and far more common: an immaculate empty scaffold. Eight dimensions, clean tables, professional language, and zero evidence underneath. A wrong number can be challenged — a source demanded, a correction printed. A blank cell is challenged by nobody, because even empty it looks professional. The triage desk sees a record and passes it along. Worst of all, N/A slowly turns into "fine," because nobody ever proved it wrong.

I have only one cure, and it is old: write the name of what did not arrive. Write the date. Write the name of the person who did not pick up. This column was born from that habit. The press box taught me that no final is ever only ninety minutes — and no analysis is ever only its headline. I chase the score after the score, the story beneath the scoreline. This time there was nothing beneath the scoreline, and writing that down was the honest thing.

What comes next. The next time such a report lands on the desk, the first question should not be "what is the story" — it should be "did the file arrive." That small habit can protect cricket journalism from the thing eroding it fastest: its faith in itself. At eleven at night the press box light goes off and those eleven fields remain on the screen. This time I did not fill them. I filed the news that they were empty — and it is not the first time in cricket that the truest line was the one absent from the scorecard.