The Empty Column: In Cricket's Archive, Zero Does Not Mean All Clear

An October afternoon in 2026, in the scoring room at Pune's Nehru Stadium. The ceiling fan swung to one side only, and its shadow moved across the paper. Maharashtra were 148 all out before tea. The scorer was sharpening his pencil down to a stub — so far that the wood poked out past his thumb. I stood behind his shoulder: a twenty-three-year-old trainee who had been told to write a match report and to count the words.

He turned the page and showed me a column headed Extras. There was nothing in it. No zero, no figure. Just space. I asked, "Zero?" He put the pencil down and said, "No. Empty. You write zero when you have counted. Here we did not count."

That day I filed a report about a groundsman who had watered a pitch he had been told not to water, and a nineteen-year-old No. 9 who blocked seventy-one balls without scoring a run. My editor cut six hundred words down to two hundred and eighty, but kept the groundsman's name in the second paragraph. I did not understand then what the cut was punishing. I do now: an empty column and a zero column look alike on the page, but one says 'nothing happened' and the other says 'we watched, and nothing happened'. Cricket's entire record-keeping apparatus sits on the distance between those two sentences, a distance no scorebook measures.

Eight Tables Came Back, Every One Marked N/A

Last week a report landed on my desk that took me straight back to that scoring room. A Stage-2 deep analysis from the cricket domain. It had eight chapters: format and match analysis, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, risk-side analysis, public narrative and expectations, industry transmission. On paper, a complete, prepared, diligent framework.

Every table carried the same word: N/A.

No title. No source. Article type unclassified. Core viewpoints — the one-sentence summary, the author's stance, the stated purpose — all blank. The information points list entirely empty. Entities — teams, players, boards, venues — unresolved. Time sensitivity never assessed. Source quality never graded. What survived were field labels: names printed above empty boxes.

The report offered two plausible causes. One, the article body never reached the Stage-1 extractor at all — a pipeline or ingestion fault. Two, the source was unavailable at crawl time — paywalled, blank, or failed. And then the single most useful sentence in it: labels intact, values empty is more consistent with a hand-off fault than with an article genuinely containing no cricket information, because a real cricket article almost always yields at least a team name or a format.

So the analyst left all eight chapters blank. Deliberately, explicitly, on the record. He did not write that "something like this might have happened in an Asia Cup bilateral." He did not invent a batsman. He gave one star each to sporting value, industry value, timeliness value and reference value — four zeros. And closed with the least-read, most necessary sentence in any cricket report: this is not 'no risk found'; this is 'no risk could be tested.'

The Habit of Reading Zero as a Clean Chit

There is a habit here worth naming, and it belongs to the information industry rather than to sports journalism. A report in which every field says N/A reads like a report in which nothing was found wrong. Neither carries a red flag. Both look calm. And that calm is the most expensive illusion available: data systems fail silently, not loudly.

I learned this in the winter of 2026, when the desk put me on the fixing beat. I was bad at it — stakeouts bored me, and I kept drifting to the Deccan Gymkhana bar where retired Ranji players drank. What came out of that aimlessness was a former wicketkeeper's account of the exact silence in a dressing room when a teammate was asked to underperform in a 2026 one-dayer. I wrote four thousand words and called it "The Long Room." It contained no table. It described what a fix does to a friendship.

The beat left me two things. One, the desk never sent me on a sting again, which I minded less than I should have. Two, and this matters more — a claim you cannot source is not a weak claim; it is an invalid one. A weak claim can be strengthened. An invalid claim can only be removed.

The report passed that test. It said it did not know what it did not know. That is not radical in cricket. It is basic. Basic things are the first to be forgotten.

Three Things That Never Reach the Scorecard

After that 2026 afternoon I started a small pad I call the silence notebook. One rule: at every match, write three things that will never reach a scorecard. The sound of a bat handle being taped. What a bowler at fine leg says to himself. The tea tray arriving in the middle of a collapse.

Twenty-nine years later, almost every documentary script I write opens on a line lifted from that pad. But the pad's real use was not what I thought. Its real use was that it was a manual null-handling system: name the absence instead of filling it. Once an absence has a name, you cannot fill it with inference. That is a more useful habit today than any dashboard.

At one point the report noted that player-level assessment requires a named individual, because age-curve and injury history — the two fastest-moving risk variables — cannot run without one. Correct. But something else in that line deserves to be said plainly: who is the first-class cricketer whose nine thousand runs are not recorded in any dashboard the way a single IPL season's two hundred and eighty runs are recorded? He appears in no squad file. He has no expected-runs model. He has no "impact." And the day he retires, nothing is subtracted from the data — because his presence was never counted.

This is where the data-quality argument joins the oldest argument in Indian cricket. The IPL did not kill Test cricket; India remains the one country where Tests still sell out. What the IPL made invisible is the Ranji pyramid: thin coverage outside the knockout rounds, zonal selectors replaced by franchise scouts, a first-class season nobody watches until the final. Cut the reporting count and you cut the data count; cut the data count and absence slowly becomes non-existence. That is not a complaint about neglect. It is a description of structure, and structure is fixed with footage counts, not with tears.

Without a Format Tag, No Number Is a Number

One more element of that report stung, because it held up a mirror to my own trade. The domain label read cricket_asia. That is not a format. It is not a governance category either. It is a market hint, useless for any technical judgment.

Here is why. Test, ODI, T20 and The Hundred are four distinct competition structures, and their metrics are not transferable. A T20 economy under seven is excellent; a Test economy in isolation proves nothing. Put a T20 finisher's 180-plus strike rate on the same scale as a Test opener's average of forty-five and you have not analysed anything — you have committed a category error. Applying one format's numbers to another is the most common mistake in cricket analysis and the slowest to be punished.

Without a format tag, every other branch closes. Duckworth-Lewis-Stern? That governs rain-revised limited-overs targets and means nothing in a Test. DRS and umpire's call? That debate depends on the review regulations in force for that series. World Test Championship points and final qualification? A Test-only branch. Right to Match and auction premiums? A league mechanism, not an international fixture. NOC and central-contract disputes? Board governance.

The report asserted none of these. It listed them only as the reference set it would draw on if the input had contained a governance issue. That was its most disciplined move: it did not say what it knew, and it did not say what it did not know.

I see far less of that discipline in Stage-1 copy. The format is often omitted because the writer assumes the reader knows. The reader does not. And what the reader does not know must be told first, or everything after it is wasted.

The Biggest Risk Is Not to a Player. It Is to the Record.

One plain sentence in the report stopped me: "Source quality was not graded." It reads like a technical footnote. It is the widest open door in the document.

If the source is ungraded, no claim has a reliability ceiling. And where there is no ceiling, traffic-chasing accounts and unverified social posts eventually arrive at the same place as verified reporting — in the reader's eye. Twenty years ago the remedy was simple: two sources. The remedy has not changed. The habit has.

Here cricket's most worn subject attaches, and I would rather not leave it worn. One line in the report's betting analysis was serious: with no historical market data supplied, that lens stays closed. That restraint is admirable, because betting talk is loudest exactly where data is thinnest. It recalls the disease I met on arrival in this profession — the 2026 scandal, Mohammad Azharuddin's life ban, Hansie Cronje's confession. That era left at least one good habit behind: a reporter trained on documents distrusts any scandal claim he cannot source.

Apply that standard to something simpler. Every row of the risk matrix read N/A — sporting, personnel, commercial, rules and integrity, public opinion, systemic. The whole assessment returned zero, and that was its clearest warning: risk could not be graded because no subject existed to carry it. A risk-free match report and a data failure dressed as a risk-free match report share the same expression. A reader cannot tell them apart. The writer must, because he holds exactly one tool for the distinction: he knows whether he checked.

The Archive Is Never Silent

The story the industry tells about itself is that more data means more understanding. Expected runs, strike rotation, phase-wise economy, field-placement matrices — all trending up. A dead game, a living picture.

I accept the first half and not the second. More data does not guarantee that missing data will be caught. That is the whole thesis of this report, and the least discussed thing in the business. We have built sophisticated machinery for adding information. We have built no protocol for information going missing.

A broadcast van explains it best. The floor manager counts to a hard-out, second by second. If the audio drops out of the line, a dropped audio does not show up — silence shows up. And silence is exactly what sounds beautiful in cricket and exactly what sounds broken. A dead mic does not make you weep; it makes you check the mic. But the system only checks when someone complains that the mic is not delivering. Complaints about noise arrive. Nobody complains about silence.

Set that beside something twenty-five years of watching has taught me: cricket's public memory keeps events and discards process. Memory does not record what the scorer had to do next morning. Memory does not hold what happened behind the curtain-raiser. The report did inside the sport exactly what my silence notebook does: it recorded process failure, not outcome. That is its actual news.

And its most useful sentence is a warning rather than an analysis: if this recurs, treat it as a systemic defect, not a one-off. One case is tolerable. Two cases are a pattern. The industry's habit of counting cases is as weak as its habit of spotting empty columns.

Three Fields and One Man

The report closed with a list — the minimum input required to make all eight chapters executable. Six items: title, format tag, match nature, named entities, event date, three to eight discrete information points.

Three of those should become mandatory named fields in the next pipeline revision, because without them nothing else survives: format, entities, date. These are the three slots where an input can vanish entirely and nobody notices — an empty column in the scorebook that the next reader takes for a zero.

And a fourth thing no list will carry: one man at a desk willing to stamp the record not analysed rather than pass it onward as no issues found. In this whole episode that stamp was the bravest object in the file.

The archive is never silent; it just waits for a microphone. Sometimes the microphone is off, and on that day the truest available sentence is that nothing can be said yet. A game that taught me the pitch remembers what the scoreboard forgets also asks its record-keepers to sit in the room after the last whistle and decide what to write on a blank page — and often the right answer is to leave it blank, but to write the date and the name underneath.

I count the words because someone counted the hours. Today the hours belonged to the man behind the curtain who refused to fill eight empty tables. Next time a dashboard shows you a clean, green, unblemished screen, ask one question — who counted, and did they count, or did they just leave the space?