No Verdict Without the Review Log: Evidentiary Limits in Cricket Reporting and the Case Study of an Incomplete File

Three things happened in one over. On the first ball the batter made a loud appeal, on the second the umpire raised a finger, and on the third the broadcaster put up the ball-tracking graphic. On screen the ball struck the stumps, the crowd rose, and the commentary box said the obvious words: that was clearly out. In my notebook that moment occupies three lines — who appealed, what signal the umpire gave, and what the projection margin was. The third line stayed empty, because nobody stated the margin. That empty line is the subject of this report.

A cricket story cannot be written without evidence, and that is a technical limit, not a moral one. Over the past several years I have read hundreds of reports built on a scorecard, a social-media clip and one sentence from a team spokesperson. Strip that scaffolding away and what remains is very little cricket and a great deal of atmosphere. The draft that reached me arrived with an analysis in which the match format, the teams, the players, the publication date and the source were all unavailable. Eight analytical dimensions were provided, and all eight returned the same answer: insufficient information. I read it twice. Then it became clear that this was itself a story, because that condition is becoming the norm in cricket journalism.

Before anyone reads this as an excuse for a missing source, three concrete points drawn from the documents that govern cricket give a scale for measuring this file's limits. First, the ICC's playing conditions are published in separate editions for each competition — Test, ODI, T20 and franchise league conditions are not the same document. Arrangements such as the soft signal, since retired, remain alive in old archives and are still misquoted in new reporting. Second, the process involving the third umpire and review produces a threshold decision, not a binary one: overturning the original call requires sufficient evidence, and Umpire's Call does not mean the original umpire was right — it means the evidence was insufficient to overturn. Third, arithmetic and regulation are part of the sport: net run rate calculation, Impact Player usage, slow over-rate sanctions and super over procedure are sentences drafted in a boardroom that surface in the seventeenth over as a captain's choice. If none of those elements appears in a report, the report is not about cricket.

Now the incomplete file. The analysis I received carried eight dimensions — format and match analysis, player technique and data, team landscape and rankings, league and commercial ecosystem, rules and governance, risk analysis, public narrative and expectation, and industry transmission. All eight carried the same entry: unavailable. The domain label was cricket_asia, and that was the only signal. Consider how many conclusions that single label could support and how many it could not. A writer could have built an India–Pakistan fixture story from the words Asian cricket, or a Bangladesh domestic-structure piece, or a Sri Lanka rebuild piece. Three different stories, three of them unsourced, three of them readable. That is precisely where cricket reporting's most common defect is born: treating a label as a fact.

For years I have read match reports the way a match referee writes one — chronology first, clause second, verdict last. My first Test assignment in 2026 taught me that the most valuable line in a report is the one the writer declines to write. As video review became standard in cricket, that lesson sharpened. The real contribution of review technology is not that it corrects umpires; it is that it builds institutional memory — who appealed, what the broadcaster showed, what the ball-tracking margin was, what the protocol permitted, what the room was not told. Without that log, a bad appeal never becomes history; it becomes a mood that has to be rediscovered every season.

This is where the instinctive argument starts. Some readers will ask why write at all without a source; others will ask what further proof is needed when the ball is visibly hitting leg stump. Both are half right, and both make the same error: they place the conclusion ahead of the evidence. The spectator sees the final projection image; the umpire sees the projection margin and the band of uncertainty. One ball, two information sets. My notebook records that difference with a single method: timestamp the decision, record the information available at that moment, and write the outcome last. The discipline matters even more when writing about past events, because the replay makes every decision look obvious, and a writer who already knows the answer will find every umpire wrong.

The other face of that discipline is vocabulary. A writer arriving from football reads a cricket review through the lens of clear and obvious error, because that is football's register. Cricket's register is different — third umpire, Umpire's Call, UltraEdge, ball-tracking. Mapping one sport's threshold onto another is not merely a slip of language; it misapplies an evidentiary standard, and it is visible in most of today's cricket arguments.

Back to the file that prompted this report. Its most important warning was that assigning a high, medium or low risk rating would manufacture false precision. I liked that line, because it does what a good referee does — when evidence is insufficient, the referee declines to decide. Declining to decide is itself a decision, and often the most honest one available. But one gap appeared even there: the analysis flagged the absence of information as a risk while offering no direction of inquiry. Saying the data is missing is not enough; it should also say which document would change the picture if found. My own notebook keeps that distinction — a question mark beside every blank space, and a name beside every question mark.

One personal note. In 2026, when the domestic league was suspended and I was cut to three days a week, I spent four months watching more than two hundred matches with the commentary muted. What emerged was that crowd noise had been covering a decade of referee communication failures. That experience rewrote my format: every column now splits into what the law permits, what the referee saw, and what the referee heard. The translation to cricket reporting is direct. The first part comes from the edition of the playing conditions in force for that competition, dated. The second comes from the scorecard and the ball-tracking file. The third is what appears in no document — why the captain appealed, why the umpire sought consultation, what team management was saying. A verdict written without one of those three is incomplete even when it turns out correct.

One further point the incomplete file exposed concerns the data trade. Cricket has become a real-time data sport, and the largest buyer of that data sits outside the game with a one-way relationship to it — ball-by-ball feeds, projection probabilities, player status. When a reporter has no evidence of their own and the numbers arrive from a third party, the report slowly begins speaking in the language of the feed the market already owns. That is cricket's quietest intrusion: the reporter looks independent while someone else has set the boundary of what they can know. Which is why the most valuable line on my page remains the empty one — the one I can fill, and the one I can refuse to fill.

Finally, a question larger than this file. When a tournament, a controversy, a selection argument arrives, do we look at the screen first or the document first? If the answer is the screen, we will keep writing reports where the conclusion precedes the evidence, and we will keep feeling that atmosphere outruns fact. Review was introduced into cricket precisely so that evidence would outrank emotion. Journalism has not yet adopted that procedure, and perhaps that is the profession's largest unresolved review — one whose appeal has still not been filed.