When the Replay Shows Nothing: Verification Discipline in Cricket Decisions

On 1 December 2026, in the group stage of the Qatar World Cup, Kaoru Mitoma's cutback in the 51st minute of Japan versus Spain was ruled in play by a margin of 1.88 millimetres. The figure came from semi-automated offside technology and the tournament ball sensor: a camera array, a 500Hz ball chip, and a declared tolerance. Football argued about a number that day. But the real question was different — what the evidence actually proves, and what it does not. I have seen this match from three angles, and the truth is still in the replay — but the replay is never a perfect witness. From passing my refereeing exam in 2026 to taking charge of 311 matches, I have learned this: the weight of a decision splits into three separate questions. Was the process correct? Was the protocol followed? And was the decision actually right? These three are not the same. Confusing them is today's biggest professional error. In August 2026, Manchester's Piccadilly Radio hired me as a referee analyst at £180 a broadcast. That season I covered 46 matches and never missed a Monday slot. The player's sense of contact and the referee's sense of law fused into one voice. Since then I write every explanation in two layers: what the player felt, then what Law 12 actually said. The habit forces me to cite a specific law, not a feeling, in every column. Player to referee, referee to broadcaster — this path taught me how modern officiating culture became a media voice. When my hamstring tore in 2026 the running stopped, but the attention to law did not. The 2026 shift — from studs to whistle, whistle to microphone — still works in every sentence I write. Cricket has walked a parallel road. DRS, UltraEdge, ball-tracking — each technology promised the same thing: decisions would no longer depend on a person's eye. But on 14 March 2026, at 57, when I turned the box room above my Didsbury garage into a studio and launched a weekly referee-review channel, the first twelve videos averaged just 380 views. I refused to change the format. By year's end, 11,400 subscribers and 1.9 million total views — all from six-to-eight-minute decision breakdowns. That experience taught me a hard lesson: the replay gives a number, but the number is not always a truth. The 1.88 millimetres of 1 December 2026 is the proof. The number is real, the system is declared, the tolerance is fixed — yet questions remain: which frame was chosen, how accurate is the ball chip, and what is the camera's frame rate? I test every disputed decision from three angles: the live angle, the replay angle, and the system-log angle. The first two are what our eyes have; the third is what the machine has. That third angle is the least discussed and the most decisive. The term 'umpire's call' in DRS is, in my view, often misunderstood. It does not mean the decision was correct. It means the evidence is so close that the process preserves the umpire's original call. In 2026 I audited three group-stage semi-automated offside rulings because I wanted to know how consistent the system was. Without grasping the difference between a correct process and a correct decision, every dispute flares up needlessly. Here is where blockchain becomes relevant. Cricket is now testing blockchain in ticketing, fan tokens, and data verification. The reason is simple: an immutable log means each decision's timestamp, input, and tolerance can no longer be changed. At the 2026 Russia World Cup I imposed a 90-second rule on myself — publishing an explainer within 90 seconds of the full-time whistle, with a median turnaround of 71 seconds. Each of those 64 videos carried a timestamp, and that later became my evidence. Blockchain institutionalises the same principle. But here is my warning. During Project Restart in 2026, 92 Premier League matches were played in empty stadiums, and I logged 1,104 whistle events and 63 on-pitch verbal confrontations. Sound stopped being atmosphere and became evidence. No crowd taught me that the roar of the crowd had masked refereeing failure for decades. If a blockchain log also holds incomplete input, it only makes the error immutable. Here is the real counter-intuitive truth. We think technology makes decisions neutral. In practice, technology only draws the limits of the evidence. An empty analysis — where every field is either blank or 'not applicable' — is in fact an honest result. The professional analyst's job is never to fill blank fields with imagination. My fifty years of experience say the greatest damage happens when someone speaks with a confident voice despite having no information. Emotion and law walk two roads here. The fan wants an instant verdict; the referee wants complete evidence. The lesson of my box room taught me that remote analysis looks cleaner than the field, but without contact, sweat, and face-to-face questions to players it is incomplete. So in every decision my first question is: what is the evidence, and where did the testimony come from? I also have doubts about cricket auction data models. IPL-style auction models overvalue young potential and undervalue dressing-room chemistry. But that is a separate discussion; today's subject is evidence. Still, the connection exists — where data is incomplete, the model guesses, and guessing breeds error. Looking forward, my proposal is clear. Every review decision in cricket needs a declared standard: which system, which tolerance, and which timestamp. If an immutable, blockchain-based decision log follows that standard, no future dispute will stop at a person's memory. I have seen this match from three angles, and the truth is still in the replay — but when the replay is empty, the truth is this: we do not know, and admitting that is professionalism itself.