The Empty Screen in the Review Room: Why 'N/A' Is the Fastest Evidence in Cricket Reporting

There is a screen in the review room that is never supposed to go blank. Last week a report landed in front of me with eight analytical slots and one word in seven of them — N/A. The eighth slot was alive: cricket_asia. No score, no format, no player, no date, no venue. Just a routing tag, stamped on before anyone had read the content. In January 2026, when I sat in the TV umpire's chair at Indore — the Ranji Trophy final, Gujarat's maiden title under Parthiv Patel, a five-wicket win over Mumbai, my 41st first-class match on the BCCI panel — that was the first thing I was taught. If the feed doesn't arrive, don't guess. Press the mic and say: no signal. A guess carries no timestamp, and a decision without a timestamp isn't a review, it's an opinion. It's worth being precise about what that report was meant to do. Eight dimensions: format and match nature, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, risk, public narrative, and industry transmission. Each has its own evidentiary standard. But one gate sits in front of all of them, and until it is passed the other seven are worthless — format. A strike rate of 145 is aggressive in T20 death overs, decent in ODI middle overs, and a number with no meaning at all in Test cricket. So when the format field is null, no metric can be benchmarked, except by saying that it cannot be benchmarked. That rigidity came from Indore. Six months after that final I resigned the panel and joined a digital cricket desk in Ahmedabad, pitching a weekly column on the ICC playing conditions that broke DRS reviews down frame by frame. Since then every piece opens with the clause, the camera angle and the reviews remaining. My economics degree supplied the frame: a review is not luck, it is resource allocation inside a two-per-innings budget. And the report's first failure was exactly a failure of budget thinking — the system spent its tag before it read the content and came back empty-handed. That is not an analysis failure. It is an ingestion failure. The distinction matters. Analysis fails when the evidence exists and the reasoning is wrong. Ingestion fails when the evidence never arrived. — Root: Experience 1, the Indore TV umpire. Now the replay, in the order the official sees it. Frame one: the format gate. The report itself concedes this field should have been non-nullable and wasn't. It's the same class of error cricket spent years arguing about under the soft signal, which was scrapped in 2026-21. Plenty of commentary still presents that removal as the system overturning decisions. It was a protocol clean-up: removing guesswork from the machinery. The report's format gate was meant to play that role and it defaulted. Which is why the other seven dimensions return 'N/A - insufficient information' — not laziness, honesty. Frame two: entity extraction. One line stopped me — the instruction reads 'identify from the information points above', and the information points list is empty. That is a self-referential failure: the instruction waiting on its own input. In review-room language, the third umpire has been asked to examine a frame that was never cut. I thought of the fourteen-part VAR explainer series I built through June and July 2026, cutting each of the World Cup's record twenty-nine penalties into forty-second breakdowns with the law text burned onto the screen. Six million views in three weeks; Indian viewers arguing about handball in Hindi. The lesson of that series was simple: without the clause number, a frame is a photograph. With it, a frame is evidence. Fourteen VAR films taught me that a record twenty-nine penalties is a story about process, not chaos. The empty entity column held the photograph, without the clause. Frame three: the one surviving signal, cricket_asia. It is the most interesting thing in the document and the least usable. The system read nothing and still left a routing tag. That is the broadcast truck's split-screen: syncing two feeds is a production decision, not a cricket one. Sitting in the chair at Indore, I knew which feed would sync first was not mine to choose. It was the producer's. cricket_asia is the same artefact — taxonomy residue, not a cricket fact. It hints at Asian regional cricket: an ACC competition, a South Asian bilateral, an Asian franchise league. But 'might be' and 'is' sit as far apart as a soft signal and the actual decision. The label cannot separate the IPL from the PSL, the BPL or the LPL, and those four sit on entirely different rungs of revenue, auction arithmetic and NOC politics. Frame four: time. No date, and time sensitivity 'not assessed'. Cricket information decays fast — selections, injuries, auction values, rankings all move on a weeks-to-months scale. Between September and November 2026, sixty IPL matches were played in the UAE with no crowds and stump mics pushed to the limit. I filed from Ahmedabad at four in the morning and wrote the desk a one-page silent-ground checklist: what a stump mic catches, when a no-ball is audible, how canned crowd noise buries the edge. On 19 December that year India were bowled out for 36 in Adelaide, and that number carried weight only because its date and venue were recorded. Without a date, 36 is a meme. With one, it is a protocol document. Sixty silent IPL matches left a louder transcript than any crowd could provide — it just has to be filed on the right day. Frame five, and the largest risk: the temptation to write a fluent, plausible cricket story on an empty input. The report calls this phantom-content fabrication and rates it High, correctly. I know the trap because it built my career. With a tag and no content, the easy route is to stitch Indore, Mumbai, a spinner's angle and a captain's burnt review into something elegant. It would read as real. It wouldn't be. That is the difference between the work I do and the work I left. A review burned in the eighth over is a story — but only with the scorecard, the over number and the reviews remaining. Ball-tracking is the same discipline. The graphic looks like measurement, so it feels like the antidote to punditry. It is a model with an error band, and umpire's call exists to institutionalise that uncertainty. Whenever a projection decides a match, I name the model, the margin and the clipping window. That is a design feature, not a loophole. The report applied that feature to every dimension: where there was no model, there was no claim. One disclosure, because it is the least pleasant part of the job. That report names no team, no player, no league, no figure. So nothing in this piece has been inferred or invented. I will not name briefers, because there were none; the questions that went unanswered are the ones above — what was the format, what was the match, which teams, which date. I keep a firewall: a sourced detail and a verdict do not appear in the same piece unless the gap between them is stated. This time the gap is the length of the report. Now the turn. Take the boring, conventional read first: the tool failed, therefore there is no story. Clean and tidy, and most people stop there. Stopping is the failure. The news is not that the file was empty. The news is that an industry which conducts every major argument on paper has no habit of recognising blank paper. Chaos in cricket is almost always an artefact of a process nobody published. Pitch ratings don't get printed, match-referee reports don't get printed, board show-cause replies don't get printed, RTM arithmetic doesn't get printed — and then we call the silence a controversy and run it for three weeks. The match report is never the whole match; the minutes are where the pressure leaves fingerprints. This time the minutes were open and the fingerprints were visible: the entity step never received its input, the format field that should have been mandatory was optional, and a routing tag outlived the content. That is the governance disease I have covered for twenty-three years. The process stays unpublished, so the outcome looks sudden. I resigned once from a chair in Indore, and I have reviewed every comfortable verdict since. The comfortable verdict here is 'broken tool, look again next week'. I won't take it. It isn't the tool that broke; it's the habit of checking. So what changes. Make format a mandatory, non-nullable field — if it is empty, the whole output goes back, not forward. Let entity extraction fail loudly instead of quietly printing an instruction. Record the date and a decay rate every time, because undated cricket information is opinion. And store regional scope separately from domain: Cricket is the domain, Asia is the boundary, and collapsing the two is how you get reports that are alive in the eighth slot and dead in seven. I would pin one line from that report above my desk, because it is the best rule in my trade: this time, nothing was fabricated. The question is next time, when the screen shows seven N/As and one live tag — how many people will write that sentence, and how many will fill the emptiness with a beautifully rendered scorecard?