Zero Information Points: When the Scorebook Columns Were Ruled but Empty

At 6:41 in the evening, in my room in Ahmedabad, I opened the file. It had eight sections. Under every section were tables, the columns ruled, the headers set in bold, and inside every cell the same sentence repeated — “N/A, insufficient information, cannot assess.” Thirty-five pages. Title: N/A. Source: N/A. One-sentence summary: blank. Information points: zero. Only one thing had survived, a label hanging in the corner of the document — cricket_asia.

I read it twice. The first time hoping a number, a date, a name had merely slipped through. The second time hoping I was reading it wrong. Both times the result was the same. The paper was complete; the cargo was empty.

At Motera, in the 2026-94 Ranji season, an almost identical page reached me. Rain had washed out the first day and the elderly scorer at the desk had ruled the over columns, drawn the run columns, and left the inside untouched. I asked why he had not written zero. He said: “Zero is a result of play. This was not played.” That day I learned the most basic rule of record-keeping, and it took me thirty years to learn how large its jurisdiction is: a blank cell does not tell you that zero happened. It does not even tell you that nothing happened. It tells you only that nobody filled it.

This is not a match report. I have no match to report. It is an audit of a document — one sent out to be analysed across eight dimensions of cricket, and containing not a single cricketing fact.

In my trade such a file is not new. What is new is that these files are now born in pipelines rather than scorebooks, and there is no elderly caretaker there to say, son, nothing has been written inside.

Context: layers of record, layers of silence

My entire career rests on one habit — treating the official record as the primary text and the broadcast narrative as a disputed secondary source. On the print desk this was necessity: there was nothing else. What the scorer wrote appeared next morning, and if he put a no-ball in his pocket, that no-ball never happened. That was not conspiracy. It was the natural weakness of a system with one source and no second source to check it against.

Across nine Gujarat home matches in 2026-94 I charted 1,412 overs, drew a wagon wheel for every innings, and logged every leg-before appeal with the bowler's release point, the batter's stride length and the umpire's initials. Nobody ever asked to read the file. I kept it anyway, because I did not yet understand what I was building. I understand now: I was building a record that could be compared against the official one. Without a second source, the first source can never be proven wrong.

Satellite replay supplied the second source. Suddenly the scorebook said one thing and the tape another. Ball-tracking made the gap measurable. That is where my work changed. I used to write that a decision was wrong. Now I write which protocol applied, who applied it, on which frame it was applied, and on which frame it stopped being applied. The scorebook says one thing; the tape says another.

In April 2026 Hansie Cronje's confession broke; that December Mohammad Azharuddin received a life ban. In those eight months I stopped writing opinion and started re-watching tape — sixty hours of 2026-2026 one-day internationals, logging 214 no-balls and 41 abnormally slow scoring overs. The sheet was never published. It taught me that a pattern is an argument and a single clip an anecdote.

In February 2026 that sheet put me on a broadcaster's third-umpire review desk for the India-Australia series. At Eden Gardens I was not watching V.V.S. Laxman's 281. I was watching its replays.

March 2026, M. Chinnaswamy Stadium. Steve Smith glanced toward the Australian dressing room over a DRS call, umpire Nigel Llong sent him back, India won by 75 runs, and Virat Kohli said he would not call opponents cheats. The papers argued morality for a fortnight. I spent nine days building a 41-minute video on the review protocol, the fifteen-second clock and the umpire's-call band. First-month views: 11,400. I answered roughly 300 comments personally, and not one of them asked about morality; they all asked where the fifteen seconds begin. That settled my method: protocol first, controversy second. In Bengaluru, the decision took longer than the replay.

Nobody covers this governance layer — match referee reports, code-of-conduct hearings, pitch inspections, NRR arithmetic, review protocols, NOC conditions, anti-corruption monitoring. None of it appears beyond the boundary; all of it can decide an outcome. My working belief follows: procedure is the true causal agent. Not who wanted it more, but which protocol was applied, by whom, and at what point it stopped being applied.

Core: eight dimensions and the hollow inside them

The field-by-field audit matters because it is the same method I apply to an over log. When a bowler's card shows zero wickets, the first question is not how badly he bowled; it is how many catches went down. If that number is also missing, the correct conclusion is not that the statistic is faulty. It is that we cannot yet say anything.

The most important line in the whole file is the one reading zero information points. An information point is the atomic unit every conclusion attaches to — a date, a number, a name, an event. Zero does not mean the article contained nothing. It means nothing could be extracted from it. Between those two sentences lies the same distance as between “no appeal was made” and “the appeal was not logged.”

Record auditing needs a typology of silence, and I have used the same one for years: the silence of absence (the event never happened — a washed-out match), the silence of the instrument (it happened but was not captured — the camera angle was wrong), the silence of transcription (captured but lost in transfer — a no-ball that never reached the card), and the silence of decision (captured, known, deliberately not written). Each has a different remedy. The file before me carries instrumental and transcriptive silence. Reading it as absence would produce the sentence “nothing happened in this period,” when the truth is “something happened and we did not capture it.” The first is news. The second is the absence of news, and the absence of news is more dangerous because nobody prints it.

The surviving cricket_asia label is the key to the whole affair. Classification ran and succeeded; extraction ran and failed. The tell is inside the document itself, in the entities field: “identify from the information points above” — an instruction pointing at a list that does not exist. That is a template artefact, not analysis. It is the signature of a form printed, ruled and left blank.

The sequence runs: source → extraction → classification → analysis. The failure is in frame two; the damage shows in frame four. When a match summary compresses a review into “review lost,” three words bury the entire procedure. This document does the same thing to itself.

Here the cross-sport comparison earns its place. Tennis has Hawk-Eye with a published margin and a written rule that if the system fails the original call stands. Rugby's TMO has the referee refer a defined question, and if no conclusive angle exists the original decision stands. Football's VAR has an undefined “clear and obvious” threshold. Cricket's DRS has the umpire's-call band, a deference protocol, and if ball-tracking fails the on-field call stands. Every one of these sports has written a rule for instrument failure. None has written a rule for record failure. That is the information gain here: cricket has null-handling for measurement and none for documentation.

The cascade is where the real damage sits. A file that says “extraction failed” gets fixed. A file that says “no material for analysis” is logged as no signal and passes downstream, where it becomes a silent false negative — far more dangerous than a visible error. Cricket produces these daily. An over-rate rule unenforced does not leave a record reading “the rule was not applied”; it leaves a record reading “the match finished.” A later analyst will never know an enforcement failure occurred there.

The old record's silences are structural, not accidental. The untelevised Ranji overs, the women's matches with no full scorecard before the late 2010s, the pre-2026 franchise-less career paths — nobody hid anything; the frame had no room. And having no room in the frame is, in history, equivalent to hiding. Today's data desks reproduce a narrower version of the same fault.

Contrarian: the empty report is more honest than a full one, and that is the danger

Had an intelligent system filled this file from memory, we would have a handsome report — title, summary, a team's strengths, three paragraphs on a player's technique — and almost every sentence would be wrong, because it came from a memory store rather than a match. But it would read correctly. Reading correctly is the great hazard of this trade.

I do not celebrate the emptiness. This honesty is accidental, not virtuous. The system is quiet because it filled nothing, not because it refused to fill. And the same evidentiary bar I apply to others must apply to my own suspicion: nothing in this document establishes that anyone concealed anything. The record establishes a gap, not a cause. Attaching cause to a gap is the same error as reading intent into a sledge.

The deeper turn is less comfortable. This is not anyone's dishonesty; it is a protocol with no defined null state. A system without a zero-state handles zero in one of two silent ways — as news, or as the absence of news. Both are wrong. The third path is to name zero, code it, and alarm on it.

And the sharpest cut: on the day an over vanishes from the card, nobody shouts, because nobody knows. On the day ball-tracking fails, the whole stadium shouts. We have made our instruments' failures visible and our records' failures invisible. That is an inverted priority, and it will be fixed by habit, not technology.

Takeaway

I will not close on a verdict, because I do not have one. I have a gap, a template, and a surviving label. Four things should happen before the next run: hard-gate any analysis on at least one information point and one named entity; separate PARSE_FAILURE from NO_SIGNAL as distinct status codes; strip or mark unverified any regional label on a degenerate payload; and recover provenance — URL, outlet, author, publication timestamp — before re-running.

Beyond that the question is larger and I have no answer. If our generation's task is to accumulate the data of every match, we must also decide which part of it is quietly blank. When a researcher reads this decade of cricket from these archives in 2047, will they find a complete map, or a map with white spaces and no note explaining why they are white? My guess is the second. My further guess is that they will read those spaces as “nothing was there.”

Which may be the question every record-keeper should ask of himself, whether he sat at the Motera scoring desk in 2026 or on a server in 2026: when your paper is empty, do you write empty, or do you leave it? There is a thousand years of difference between the two, and it will show not in any scorebook but in how the next generation reads.