The Scorebook Came Back Blank: The Day Cricket's Data Chain Wrote 'N/A' in Every Column

The document arrived at the desk fully dressed. Eight sections, tables in every section, rows in every table, a status column against every row. From the outside it was the same Stage-2 analysis we commission before every major tour — same skeleton, same headline style, same written courage of "Confidence: High". I turned to page one. Title: N/A. Source: N/A. Article Type: Unclassified. Information Points: zero. Entities Involved: "identify from the information points above".

That last line was worth stopping for. The document was telling me to identify the entities from the information points listed above, when nothing was listed above. It was the same circular answer an umpire once gave me when I asked which frame the third umpire had based his decision on — "the frames he looked at decided it". Yes, but which frames.

A referee's eye is not a verdict; it is a delayed pattern. And here the pattern was plain. The failure was not cricket's. It was the record's. A document with eight sections and not one fact is itself a story — provided somebody has the nerve to call it blank. That afternoon three people on the desk wanted it closed as a "formatting issue". I counted the pages. Fourteen.

This report is about those fourteen pages.

Context: From the Teleprinter to the Pipeline

In 2026, when I sat down on the sports desk of The Times of India, a cricket report was made of three things — the scorebook, a quotation, and the one sentence the reporter had seen with his own eyes at the ground. All three could be checked. The carbon copy of the scorebook sat with the scorer, the quotation sat on the manager's tape recorder, and the thing I had seen had me as its witness. Newspapers then possessed something today's desk has lost: an errata column. Errors got printed, and the next day the correction got printed too, in its own place, in the same font.

By 2026 the picture had changed. Cricket coverage no longer began with a scorebook; it began with a database. The scorecard on the website, the numbers feed, the ICC rankings table — the reporter was now less a witness to an event and more a translator of figures. That shift improved one thing: the availability of facts. It ruined another: the habit of checking them. When the number is already on the screen, who feels the need to walk back to the document behind it.

In 2026 the supply chain of sports journalism runs on three floors. Retrieval on the ground floor: find the source article and bring it in. Deconstruction on the first floor, what we call Stage-1: break the article down and extract its title, source, information points and entities. Analysis on the second floor, Stage-2: build the argument on those points. All three floors rest on one another, and all three share a single condition — what the lower floor holds must physically reach the floor above.

The document I am describing has its upper floor fully built and its ground floor empty. Eight sections, eight frameworks, eight tables — and in every table the status reads "insufficient information". This is not a careless document. This is a document that found its foundation missing and refused to climb.

That is why this is not a cricket story but a story about cricket's information system. And I have one qualification for writing it: I am the man who, in March 2026 at the M. Chinnaswamy Stadium, watched Steve Smith glance toward the Australian dressing room mid-review, and refused that night to write outrage — pulling out the ICC Code of Conduct instead, laying Level 1 offences against Level 2, and explaining why match referee Ranjan Madugalle had no charge available to him for that incident. Afterwards I built a spreadsheet of every match referee ruling I could source back to 2026, and by December it had 1,140 rows.

I opened the ledger again, and the brain fade had a receipt. The lesson was singular: a claim that does not attach to a document must not attach to a paragraph either. Today that lesson is being applied in a new place — to the machine that builds the document.

Core: Five Columns That Came Back Empty

Column One — Title: N/A

The title is the first evidentiary object of any report. It is not merely a hook for the reader; it is the archive's key. Without a title you cannot find that article again in any record, cannot place it in a quotation, cannot fix its date in any dispute. In the old architecture, headline and dateline were written in the same breath because they did the same job — they made the document identifiable.

Here the title is N/A. That does not mean the article was bad. It means the article does not exist in the record. What has no name has no date, what has no date has no witness, and what has no witness appears neither in court nor at the desk. I have seen this only once before, in a Ranji Trophy scorebook from the 1980s: the page was there, the bowling figures were there, but nobody had filled in the box where the match's identity belonged. The page spoke. The introduction did not.

Column Two — Source: N/A, and a Circular Reply

What stung more was the source-quality column. It read: "judge from the source fields of the information points". That is the sentence an investigating officer writes when he has nothing to investigate. We are to assess the quality of a source that has not been supplied.

In journalistic practice a source does two jobs. It carries the weight of the claim, and it tells the reader how much weight to assume. "The ICC playing conditions" and "a board official" can sit in the same sentence; their weight cannot. A report without a source has zero weight on every claim it makes, however elegantly the claim is written.

Column Three — Type: Unclassified

This is the most neglected column and perhaps the most important. "Unclassified" means we do not even know what kind of article we are reading — a match report, an auction story, minutes of a board meeting, or a contract dispute. Every kind requires a different framework. Match reports are read for form and phases. Auction stories are read for price and the age curve. Board stories are read for constitutional amendments and vote counts.

Analysing an unclassified article is like listing a case in court without anyone remembering the section. The hearing can proceed. The judgment cannot arrive.

Column Four — Information Points: Zero

Here the load-bearing wall of the document falls. The other four columns are this column's children. An information point is the unit on which the whole Stage-2 building stands — a date, a number, a name, an event. Zero information points means the analysis has no ground to sit on.

One distinction matters here, because the entire report rests on it. Ignorance and low risk are not the same thing. When an inquiry finds nothing, the report does not say "no problem found"; it says "status unknown". There is an ocean between those two sentences. The first gives the accused a clean chit. The second keeps the inquiry open. Few people in sport understand this difference, which is precisely why spot-fixing inquiries stay open for decades.

Column Five — Entities: A Sentence That Is Itself an Instruction

The clearest evidence sits here. The entity column contains no player, team, board or league. It says: "identify from the information points above". That is an instruction, not a finding. No machine filled this column — it told us how it was meant to be filled, and left.

For me this was the Kazan moment. June 2026, Kazan Arena, France versus Australia, the first VAR-awarded penalty in World Cup history, awarded after Andrés Cunha's on-field review, converted by Antoine Griezmann. I had not gone there to write a preview; I went on a twelve-day research trip and sat in the tribune watching how referee instructors debrief each intervention. The most striking feature of that debrief was that every intervention had a log — who saw it, which camera, which second, on what basis, and why the decision was not overturned.

Kazan taught me to listen for the fourth official. The fourth official does not decide the match; he ensures the route to a decision stays clean. Substitutions, added time, the technical area — administrative work, and the most overlooked work there is. A report with an empty information-points column is a report with the fourth official's chair vacant.

Format: The Gate That Stayed Shut

The most honest line in the Stage-2 document was that no cricket analysis can begin without the format. Let me sharpen that.

Cricket is played in four distinct codes — Test, ODI, T20 and The Hundred. Each has a different ball count, different fielding restrictions and, more importantly, a different measure of success. A Test batting average and a T20 strike rate cannot be weighed on the same scale, because they answer two different questions from two different games. A Test bowling average tells you how long a bowler takes to buy a wicket; a T20 economy rate tells you how cheaply he leaks. Swap one for the other and your conclusion does not become wrong. It becomes meaningless.

Format, therefore, is not a detail. It is a gate. Until it is settled whether we are discussing Test or T20 cricket, no phase-wise performance discussion can begin. In T20 the powerplay (overs one to six), middle overs (seven to fifteen) and death overs (sixteen to twenty) are three separate strategies. In Test cricket the same division follows the new ball, the second session and the old ball. Pitch character, dew, rain and the Duckworth-Lewis-Stern method all sit behind that same gate.

The document wrote all this down, and then wrote down that not one piece of it was available. That is the moment an honest report stops being a report and becomes an alert.

Architecture: Retrieval Failure or Extraction Failure?

Now the question every editor should have asked and nobody on the desk did. Where did it break?

Two possibilities. One: the source article was never found. Two: the source article was found, but the machine that deconstructs it extracted nothing. The evidence in the document points to the second, and the pointer is typographical rather than argumentative.

The reasoning is plain. If the article had never been found, the domain label would have come back empty too. Here the domain label arrived — "cricket_world". The system knew this concerned the world of cricket; it simply failed to break it down. The second clue is the placeholder sentences themselves — "identify from the information points above", "judge from the source fields of the information points". These are template instructions that stayed printed and were never replaced. No machine filled these boxes; it abandoned the task and returned the template untouched.

This is not a retrieval failure but an extraction failure — and that distinction is the most useful technical clue in the entire affair. If the article had been missing, the remedy would be obvious: go and find the source. Extraction failure demands something else: repair the machine that is reading but not recognising.

Add one more detail. The domain label came back as "cricket_world" rather than "Cricket" — a trivial drift in taxonomy that has outsized downstream effects. If routing was meant to land on a specific sub-domain and missed, the next article of this kind will go into the wrong folder, receive the wrong framework and yield the wrong conclusion. In sports journalism this is equivalent to granting a match first-class status when it was a List A game. The numbers will exist. They will simply have come through the wrong door.

Cross-Code: Kazan, VAR and DRS — Three Questions, Two Different Answers

Here I have to rein in a habit, because football's VAR and cricket's DRS sound alike and my first instinct is to collapse them into one story. Before doing that, three structural differences have to be named.

First, the review count. In cricket a player has a limited number of reviews, and a failed review burns one. In football VAR checking is unlimited; it applies to goals, penalties, red cards and mistaken identity, with no quota system. This difference rewrites strategy. In cricket a review is a resource to be spent deliberately; in football it is standing surveillance.

Second, umpire's call. Cricket's DRS carries a formal error margin inside which the on-field decision stands. Football's "clear and obvious error" threshold is not numerical in that way; the referee's decision can be changed at the monitor, but there is no formal technical margin granting it shelter. This is why cricket's controversies tend to end on margin and football's on interpretation.

Third, who owns the decision. In cricket the player requests the review, the third umpire examines it, and the outcome either overturns or preserves the on-field call. In football final authority stays with the referee; VAR can summon him, advise him, but the referee writes the decision. That difference decides whom the public will blame. Cricket's anger goes to the third umpire; football's goes to the man in the middle.

Add a fourth difference, the one that stings most and the one Kazan taught me — the existence of a debrief. Football tournaments keep a written log of every VAR intervention, and referee instructors open it the next morning. Cricket keeps no such public debrief of third-umpire decisions. What has no log has no correction.

Now apply that back to our document. A document whose every column says "insufficient information" does contain a debrief — it is simply the debrief of a failure. And that is its value. The replay shows the foul; the ledger shows who pays.

Fail-Closed: Umpire's Call Translated into Journalism

Here I reach the conclusion that struck me as newest in the whole document, and which may surprise the reader too.

In the world of DRS there is one rule: when evidence is insufficient, the on-field decision stands. Technically it is called umpire's call, and it is routinely treated as the most irritating rule in the sport. It is in fact a design principle known in engineering as fail-closed — when input is missing, the system returns "no conclusion" rather than a guess.

Cricket carries this principle in two places. One is DRS umpire's call; the other is DLS. In a rain-affected match the Duckworth-Lewis-Stern method produces a revised target, and even inside it there are cases where the calculation is explicit rather than estimated. In both places the philosophy is identical — uncertainty is not concealed but given a place inside the law.

Now look at the document that landed on my desk that afternoon. It did exactly this. Every section kept its framework, every framework kept its table, and every row in every table read "insufficient information". In cricket's language, this report took umpire's call — evidence was thin, so the on-field decision stood, and the on-field decision was that there would be no conclusion.

The cost of that is real and I know it. Editors return such documents marked "did not work". Readers finish such a report and say there is nothing in it. Both are correct: this document contains no cricket finding, no team, no player, no number. What it contains is a refusal.

A refusal is also a document, provided it is written down. I remember a voice on the Kolkata desk in 2026 saying a spreadsheet does not make a story. I said a spreadsheet does not make a story, but a story built without one is a lie. The same applies here.

Transmission: If a Hollow Report Reaches the Table

Now the question the document raised loudest and could not answer itself: what happens if this report travels onward without a warning label?

Sport has a straight information channel — desk to broadcaster, broadcaster to viewer, viewer to market. In cricket there are three junctions where a hollow report does the most damage.

First, the auction table. The IPL auction carries instruments such as the Right to Match, which lets a player's previous franchise match the top bid. Decisions at that table rest on numbers, and if a numbers report omits which format the numbers came from, the bid can land on the wrong player. The risk of paying heavily for a young player is already a live debate; there is no need to add another layer of uncertainty to it.

Second, the selection meeting. Selectors have little time and much paper. The report that looks tidy is the report that gets read. If every column of it says "insufficient information" and the warning banner is missing from the top, the reader will convert "insufficient" into "normal". That is the largest risk here, and it is not a sporting risk. It is an information risk.

Third, integrity work. The ICC Anti-Corruption Unit and the boards' own units do not depend on these reports, but media coverage is the public face of their work. Where an inquiry found nothing, writing "nothing was found" and writing "everything is clean" are worlds apart. Integrity status is "unknown", not "clear". That single sentence is the spine of the trade and belongs framed on every desk.

Whether the dispute concerns a No Objection Certificate or a league-versus-country squeeze, the question is identical — who holds authority, under which clause, and what is the appeal path. Those are the three questions I have applied to every controversy since Kazan, and applied here they give the answer: authority rested with the machine, the clause was fail-closed, and the appeal path is to re-run Stage-1.

Archive: The Lost Errata Column

What I regretted most in this whole affair was the absence of something nobody mourned — the corrections column.

Newspapers once carried a "Corrections and Clarifications" column. It was the most honest thing in the paper, because it admitted the paper could be wrong. In the digital era that column shrank and has now all but vanished. In its place comes the word "updated", which does not say what changed, why it changed, or who changed it.

In automated reporting the problem is ten times larger. When a machine files a report and the report is wrong, where does the correction get printed? In which font? Under which date? No mechanism exists. And where there is no mechanism for correction, there is no accountability for error either.

My suggestion is simple and, in keeping with my habits, paper-based: every automated report should carry a provenance block — which source, which date, which stage, which field came back empty, and why. That block is not for the reader. It is for the record. Fifty years from now, a researcher looking at cricket reporting in 2026 should be able to tell which story stood on numbers and which stood on blank paper.

Old Ranji Trophy scorebooks are valuable for exactly this reason. Every correction in them is handwritten, dated, in the margin. That correction can still be read today because it was on paper. A correction written on a screen disappears in two years.

Contrarian: The Fault Is Not the Machine's but the Desk's Appetite

Now the part where I have to point a finger at myself.

The easiest route through this whole argument is to blame the machine — the pipeline is broken, the engineers should fix it, re-run Stage-1. All of that is true and all of it should happen. It is not the real fault.

The real fault is that our desk has grown accustomed to a document that looks complete on the outside regardless of whether it is empty inside. We have begun pricing a report by its format rather than its facts. A report with eight sections is judged "good"; a report with two sections and truth in both is called "incomplete". That inverted value system is what produced the blank template in the first place.

A blank page is honest. A blank page printed in beautiful typography is a lie. And on the afternoon this document arrived, the desk first mistook it for a lie — because its format was complete. Fourteen pages. Nobody asked why there was not a single name in those fourteen pages.

On the other side, my own habit is also in the dock. My principle has been that a day's delay with the document in hand beats writing in a hurry without it. That principle holds right up to the point where it becomes permanent deferral. It could have become that here. Had I sat back saying I would write once Stage-1 was re-run, this report would never have existed. The news cycle would have closed, and a significant information failure would have passed unrecorded.

So I set a publication cut-off at the outset: what the ledger supports today gets published today; what it does not support is declared an open question rather than converted into an estimate. This piece is written inside that cut-off. What is blank in the document is left blank here. I have not filled in a single player's name, a single figure, a single scoreline — because filling them in would mean spreading, with my own hand, the very disease I am describing.

Takeaway: Who Is the Fourth Official of the Record?

Cricket has spent two decades strengthening its technical chain — DRS, the third umpire, stump mic, ball-tracking, Hawk-Eye. Every technology brought a protocol, every protocol an appeal path, every appeal path a written decision. On the field, the sport's information system is far better today than it was in 2026.

But the part of that information system that lives off the field — reporting, analysis, the archive — has no fourth official. There is no post whose job is to confirm that the route to a decision was clean. No debrief, no errata, no provenance block.

The question is whether cricket needs a fourth official for its own record — a post whose only duty is to check that what was printed had a source behind it, and that what was omitted was omitted deliberately. Or whether we will go on assuming that a report with eight sections must be telling the truth.