Empty Input, Full Template: The Chain of Custody in Cricket Analysis

An analysis file opened on the Delhi desk on Wednesday afternoon. The cover read: Stage-2 Cricket Analysis. Inside were eight dimensions, a table for each, columns for each table, and in every cell the same sentence: "N/A — insufficient information." The document was complete. The information was empty. In the final row of the risk matrix, one entry was filled: "Analytical-process risk: High — Confirmed (occurred)."

The danger in that zero was small. The danger was that the file looked like a verdict. Headings, sub-headings, tables, confidence tags, a disclaimer — the whole skeleton was present. A junior writer could have picked it up and assumed a position on cricket had been formed. I have carried that fear since 2026, when I first saw an empty ledger — one I had built myself.

The 2026 Champions Trophy. Nineteen years old, knee operated on, playing career over, and a spiral notebook in Delhi University's library. I logged every DRS review from fifteen matches — 18 in total: nine upheld, six overturned, three umpire's call. Each entry carried the over, the ball, the batter and the third umpire's name. The tournament ended at The Oval, India losing to Pakistan by 180 runs, and I wrote a 900-word piece. There was no byline. But a habit had formed: process first, verdict second.

The next year I took 14 VAR reviews from the World Cup group stage and laid them beside 11 DRS reviews from 2026 in a single table. FIFA's "clear and obvious error" and the ICC's "umpire's call" were two answers to one question: how large must an error be before intervention? That 1,200-word piece became my first byline at twenty. That table taught me a word that now returns in every report — "indeterminate." It is not "low risk." It is a separate category.

The same word now applies to this file, and this is where the audit begins. I opened the old DRS ledger to see which decision had aged badly — and this time the decision under review belongs not to a match but to a pipeline.

The hardest piece of evidence in this document is one populated field. In the Stage-1 output, exactly one field carried content — the domain tag cricket_world. Everything else was empty: no title, no source, type unclassified, the information-points list empty, the entity list empty. That combination is itself a fingerprint. The classification layer worked — it knew the subject was cricket. The body-extraction layer failed. The fault sits in article-body extraction, not in the classifier. That fixes the direction of the investigation, and it is the most valuable line in the file.

Three routes for filling the blanks lie open here, and all three are wrong. Treat a heading as a finding: "Rules & Governance Analysis" is printed, so the reader assumes governance has been reviewed, when in fact the table beneath it has N/A in all five rows. Aggregate N/A cells into a section score: eight dimensions at zero, an average of zero, and out comes "low risk" — a category error, because an absence of evidence is not evidence of compliance. Fill blanks from domain priors: it is cricket, so write about the IPL, about T20, about a rights deal. That is decoration, not analysis. All three have one cure: every conclusion must carry its evidence pointer. No pointer, no conclusion.

The next entry is the quarrel I have carried across my whole beat — chain of custody. What the third umpire sees and what the director chooses to air are two different things. The replay package is the cut the broadcaster selects; the screen's own record is not. This file holds two things too. What Stage-1 extracted: nothing. What Stage-2 printed: a full template. The template presented here is the director's cut. That a reader mistook it for the match record is the effect of that cut.

The habit of treating audio as a document also applies. During the empty-stadium IPL of 2026 in the UAE I built a stump-mic log across sixty matches: 27 audible appeals, 14 on-field exchanges, three code-of-conduct charges. The empty stadium taught me to listen for the referee in the stump mic. Every clip was cross-checked against the IPL Code of Conduct and match referee reports, including the Royal Challengers Bangalore versus Mumbai Indians match of 28 September 2026. One rule emerged: write the clip timestamp and the clause number, or do not write. The same rule applies here. There is no timestamp, no clause; the only pointer is a domain tag.

Then vocabulary before analysis. I covered the 2026 mega auction as a rulebook story: 600 shortlisted, 204 sold, 10 teams, a 90 crore rupee purse, four retentions. "Sold" is not "signed"; "retained" is not "available." In the same way, "indeterminate" is not "low risk." A ruling is only as strong as the paper trail behind it. This file's paper trail says: the rules ran; the data did not arrive.

And the repair? Sitting empty-handed is not reporting. One clean re-run. If the second attempt also fails, the matter is not a transient fetch failure but a parser defect — and it goes to engineering. That distinction decides the next step: retry or escalate.

Now the part of this beat that troubles me most. A newsroom wants a full report — 1,033 words, tables, tags, conclusions. Blank cells are a career risk. So the default is to fill them. Here I will say the opposite: this null report is the protocol succeeding, not the analyst failing. The real failure would be a smooth, flowing, confident story with not one source behind it. The replay shows the angle; the ledger shows what it cost.

But I have to look at my own side too. Forty-five pages of "insufficient information" is not courage; it is a stall. Proceduralism can become its own vanity — the safest byline in the building. The answer is that null handling must come with a repair, an owner and a deadline. "There is no data" is a finding, not an alibi. My notebook's rule is plain: no receipt, no transfer story. The extension is this: no evidence pointer, no conclusion.

The way forward is not hard, only clear. Before this document reaches any downstream reader, there must be a gate — is the information-points list empty? If it is, stamp the file VOID. After that, the first task is to establish the subject: which format — Test, ODI, T20, The Hundred. Second, at least one name on the list — team, player, coach, event. Third, the provenance of the source — outlet, author, date. Without those three, every remaining table stays empty, and that is correct.

In cricket we measure the age of a ruling by its ledger. A verdict with an empty ledger does not survive court. The question is not how many headings this report carried. The question is: a document that cannot produce its own evidence — on whose trust was it written?

— Root: Referee