Reading the Empty Dataset: Cricket's Review Protocol, DRS and the Audit Discipline of Evidence

In Kuala Lumpur, I began logging VAR incidents; the pattern was already there. In 2026, at nineteen, while studying International Communication, I watched the Confederations Cup in Russia and logged twelve reviews across twelve matches — minute, law, outcome. I wrote a three-thousand-word post and called it The Referee's Eye. But the biggest lesson came from an empty column. The spreadsheet had a field titled basis of decision, and I often left it blank, because many incidents had no clean basis behind them — only habit, inference, and the noise of the stands. Those empty cells pushed me toward cricket. The further my VAR audit went, the clearer it became that cricket had done this work earlier, and more honestly. DRS, the Decision Review System, is not merely a ball-tracking camera; it is a complete judicial apparatus. Who may review, when they may review, how often, and what happens when a review fails — every step is written down. Having a protocol does not mean decisions will always be correct; a protocol means every decision carries a traceable, verifiable log. The DRS journey began with a trial in the 2026 India-Sri Lanka series, and from 2026 it became regular in international cricket. At its centre stands the third umpire, who tests the on-field umpire's call against video, ball-tracking and audio evidence. Football's VAR arrived far later, in full use at the 2026 Russia World Cup. I catalogued every review of all sixty-four matches — a twelve-thousand-word VAR Protocol Audit, sorting nineteen overturns by law category. What became obvious is today's core point: the review logic of the two sports is the same, but the institutional discipline is not. Cricket's great advantage is that a review is a scarce resource. A team must ask whether this review is worth spending. Scarcity means an internal filter before verification — players run the first audit themselves. Reviews therefore arrive sparingly, and each carries its own decision tree. In Asian conditions — spin, low bounce, slow surfaces — that filter matters even more, because ball trajectory is hard to predict and the umpire's-call boundary often breeds doubt. When building a bridge between VAR and DRS, I hold one rule: compare frameworks, not numbers. Football's VAR still wavers around penalties, offside and cards; cricket has already institutionalised the concept of a threshold. That difference tells you cricket did not merely adopt technology — it folded the technology's limitations into the law itself. Every incident analysis I write starts with a decision tree I built during the 2026 audit. Four steps: trigger, review type, final call, law citation. Trigger means which event invites a review — LBW, catch, stumping, run-out. Review type means player review, umpire review, or a third umpire's own referral. Final call means whether the on-field decision stood or fell. Law citation means the written article number behind the decision. With all four filled, an incident is auditable; with one blank, it is inference, not evidence. The most disputed part of cricket's review protocol is also the most instructive: umpire's call. On LBW, if ball-tracking shows the ball would have hit the stumps but the projection is so close to the margin that no clean call is possible, the on-field decision stands. Some treat this as error; I read it as a designed human margin — an admission that machines also carry error bars. That idea is almost absent from football's VAR debate, and that absence breeds the loudest disputes. In 2026 the ICC abolished the soft signal. Previously, on close catches, the on-field umpire gave a provisional signal, and the third umpire rarely had the nerve to overturn it. Removing the soft signal means decisions now rest more cleanly on video evidence rather than a weak initial guess. It is a small procedural change with a large message: if evidence exists, a decision follows; if it does not, the on-field call is the default. This is where my empty-dataset lesson applies. A protocol's real test comes when there is no evidence at all. The ball-tracking camera missed the catch, the audio picked up no sound, the replay angle is unclear — what then? A weak protocol guesses; a good protocol writes a default rule. Cricket has written that default. Football has not, in many places, and that gap produces post-match disputes. My own workflow reflects this. After the 2026 audit I imposed a rule: a twenty-four-hour delay before publishing complex incidents, cross-checking video timestamps. That habit cut my corrections by roughly seventy per cent. I also attach raw spreadsheets publicly, so anyone can verify my decision tree independently. The 2026 Kuala Lumpur incident log, the 2026 Russia audit, the 2026 Silent Pitch study — all flow from one discipline: write down an inference, then challenge it with evidence. In 2026, working on empty stadiums, I saw another dimension. When the Bundesliga restarted, eighty-one matches were played behind closed doors, and the data showed home win rates and home penalties both falling. The idea that a home crowd pressures the umpire became a number. In football's VAR debate we often forget this human factor: angle, fatigue, crowd pressure, and the psychological weight of the first call. A protocol is not just a rulebook; it is a contract between people and machines. Here is my central disagreement. The popular belief is that technology reduces controversy. My audit says otherwise: technology does not remove controversy, it relocates it. The question used to be whether he was out; now it is whether the technology was right. Controversy has not shrunk, only moved — and that move often creates fresh uncertainty, because the ordinary viewer does not speak the language of thresholds. The Referee's Eye is a frame-by-frame threshold test, not a whistle. The crowd sees the ball graze leg stump and roars — that should have been out. The protocol sees the same frame and reads a boundary line, a percentage, a pre-written rule. The gap between those two views is not a technical fault; it is the answer to two different questions. Emotion asks where justice lies; law asks where evidence lies. The job of an officiating framework is to hold both questions at once, not to erase one in favour of the other. This is where the cricket-to-football bridge has limits. I stay careful not to turn framework comparison into blind imitation. DRS works because cricket's incidents are often discrete — one ball, one contact, one track. Football's incidents are frequently continuous and compound — a defender's hand, a ball's path, and a body contact in the same frame. So I compare principles, not numbers. Football can learn from cricket how to write a decision tree; cricket can learn from football how to give a player's real-time emotion a place inside the process. My next direction is clear. Cricket already keeps decision logs, but those logs are not open to the public. What I want to see is an audit ledger — where every review's trigger, threshold, projection and final call sit in a verifiable record, exactly as my spreadsheet appendices do. Then a fan no longer has to guess; they can see directly at which step a decision changed, and why. This is not only a question of transparency but of trust. Cricket has understood that a review is not merely a machine for correcting on-field calls; it is a contract with the viewer — that the game is willing to admit its errors, and keeps a written record of that admission. If football wants to walk this path, it does not need more cameras alone; it needs a ledger, in which the absence of evidence is also written down clearly. The question is no longer how accurate the technology is; it is what our rule is at the moment evidence runs out. The day cricket opens its review ledger fully to the public, DRS will stop being merely a camera system — it will become world sport's first genuinely auditable judicial apparatus.