Ledger vs Tape: Thirty-Four Review-Eligible Moments, Eleven Unchecked — Auditing T20's Review Economy

Hyderabad, 21 May 2026. Mumbai Indians 129/8, Rising Pune Supergiant 128/6. The final was decided by one run, and the scorecard recorded exactly one sentence that night: one run. That season I was a broadcast data logger in Pune, working Rising Pune Supergiant's eight home games at MCA Stadium, Gahunje. After the final I spent three weeks re-watching those eight matches over by over and built a separate register — one that counted moments, not runs. Across eight matches I logged thirty-four moments where a review was available. Eleven of them were never touched by either side. The one-run verdict is settled. The eleven are not.

My job is not to argue with the scorecard. The scorecard is correct. My job is to check where the written record and the broadcast tape disagree, and whether that gap belongs to the law or to the people applying it.

What the laws say, and where they go quiet

A T20 innings carries two reviews per side. The captain must request inside fifteen seconds of the ball going dead. An umpire's call retains the review — the clause spectators understand least and captains misread most. Ball-tracking carries a half-ball-width margin; UltraEdge spikes are read frame by frame; the third umpire works with the frames a producer sends, and the viewer sees frames too, though not necessarily in the same order. That is the border where technology ends and protocol begins.

In 2026, working a review desk, my nights went to the Russia World Cup — the first tournament with VAR, and the one that produced a record 29 penalties. Colleagues called it chaos. I saw a missing checklist. I mapped cricket's DRS against FIFA's four VAR trigger categories and wrote a twelve-page internal memo, 'Review Protocol v0.1', complete with a captain's challenge decision tree. Two franchises asked for copies before the season ended. In 2026, when the IPL moved to the UAE and the stands emptied, I ran a four-person remote review desk from Pune, syncing ball-tracking, UltraEdge and host feeds across 1.5 seconds of latency. With no crowd noise, the audio spike was clean — so I built a manual sync log: sixty frames per over, timestamped by hand. Six time zones taught me that a sync log is a second referee.

A review is a resource, not a right

When I opened the Gahunje ledger, the fastest pattern was this: nineteen of the thirty-four moments arrived inside the first six overs, and most of them went unreviewed. The reviews that were taken went to strange places — a third-over boundary-line lbw where the projection was uncertain — and then, in the last four overs, captains had nothing left. A review's value is set by the over it is spent in, and teams are still not pricing it that way.

A third-over review and a nineteenth-over review are not the same coin. In the first six overs fielding restrictions apply, the wicket is fresh and lbw projections are weakest — meaning success rates are lowest exactly where reviews get burned. In the last four overs every ball moves the match, and the expected value of a review peaks. My ledger showed the inverse: the cheapest reviews were spent where they were worth least.

The fifteen-second window and the question of ownership

This is where the argument stops being about technology and becomes about ownership. In fifteen seconds the captain looks at the keeper, the bowler repeats his appeal, slip shouts something — and the decision is made by whoever is loudest. My Protocol v0.1 had a simple tree: who can testify to a spike, who owns the tracking projection, and does this ball change the direction of the match. Three yeses, and the hand goes up. On the field the tree never runs, because nobody is named as the verification owner.

Every missed check leaves a timestamp; every timestamp leaves a question. The eleven unchecked moments broke down this way: four lbw appeals where my re-watch estimate had the ball tracking toward the stumps, three caught-behind cases with a visible UltraEdge spike, two low catches in the ring where the soft signal mattered, and two where the wide or no-ball count could have changed. This is not official tracking data — it is my re-watch estimate, and I will call it an estimate. The count of eleven is not an estimate.

Misreading umpire's call

The ledger threw up a second pattern that points to a knowledge gap: captains repeatedly declined reviews on umpire's-call cases, assuming the review would be wasted. The law says the review survives an umpire's call. It is the cheapest risk on the field. A team that reads that single line correctly buys three or four free checks a season. That is not a technology failure; it is a training failure.

Broadcast forensics: the frame, the latency, the same question

Whenever a viewer says the third umpire got it wrong, my first question is which frame he saw and when. The empty-stadium 2026 season made this visible. Without crowd noise the spike was clear, but the 1.5-second feed latency was still there. My sync log carries sixty frames per over, each hand-timestamped. That log showed decision quality improving while decision time lengthened — and lengthened time is itself pressure, because everyone is waiting for the next ball. Mumbai Indians won that title; my log became the vendor's default operating procedure for the next two seasons. That is the most honest certificate available for work that never appears on screen.

Emotion versus rule: the scandal is not the wrong decision, it is the unexamined one

The stadium blames the technology. The ledger does not. Not one of the eleven unchecked moments involved a technology error — the technology was never asked. That distinction matters, because it moves the debate from 'DRS is broken' to 'who owns review usage'.

The second unpopular point: teams spend reviews on emotion, not strategy. When forty thousand people shout together, a fifteen-second decision is made under collective pressure. The reverse is also true — sides sometimes let a clear out go in order to protect a review. Both failures share one cause: there is no post-match audit of review usage. The scorecard records runs, wickets, overs and extras. Where reviews were spent, how many survived, how many moments went unexamined — none of it enters an official document. What is not recorded does not improve.

A twelve-page protocol is not a suggestion; it is a checklist with consequences. Until a captain or coach faces a recorded consequence for review negligence, the fifteen-second window will keep working exactly as it does.

The question ahead

Next tournament I will count this: how many reviews were saved for the last four overs, and how many were burned on hope in the third. The ledger says thirty-four; the tape asks why only eleven were opened. Until a match report carries one line naming who requested which review at which second and why, cricket's review system will run on habit rather than technology.