The Review Ledger: How Cricket Records Its Proof, and Where the Books Do Not Balance

Stop. Freeze the frame. Then balance the books.

On 29 June 2026 at Kensington Oval, Barbados, the light was going. A T20 World Cup final, South Africa's chase in its last third, and a stadium holding its breath. David Miller lifted the ball towards long-off. Suryakumar Yadav ran back, took the catch, felt his feet slide near the white rope, released the ball, recovered, caught it again. A third umpire sat in front of a screen. One question: did the foot touch the rope.

Four cameras, half a dozen angles, slow motion. The review ran for minutes. The verdict came. Out.

The whole argument about modern cricket lives inside those minutes. The question is not about Miller's bat, or Suryakumar's hands, or even the umpire's eyes. The question is how the decision was built, and who kept the record of it. The replay does not argue; it just waits for you to catch up.

I watch from Dhaka. My time zone belongs to the feed, not the ground. What happens at the Oval reaches my screen seconds later, and the audio arrives later still. That distance does not make me neutral; it makes me limited. Which angle the broadcaster cut, which audio stream lagged, which frame was never captured — all of it goes into my notebook. My Dhaka notebook has more questions than answers, and that is the point.

My core observation is simple: cricket's review system produces evidence but does not keep an account of it. A ledger nobody audits is not a ledger. It is belief.

The Grammar of the Protocol

To understand a decision you have to separate three layers: the law, the machine, the person. Errors happen when we collapse them into one.

Ball-tracking asks three things. Where did it pitch? Where did it hit the pad? Would it have hit the stumps? The first two are usually binary. The third is the real one. More than half the ball inside the outer edge of the stump means a wicket. Less than half hands the decision back to the on-field umpire — umpire's call.

That half-ball threshold is a constitutional act. It concedes that projection carries uncertainty, and it places the weight of that uncertainty on a human shoulder. The logic is honest. The side effect is that the same delivery, the same tracking, the same frame can produce two outcomes purely because of what was signalled on the field. Viewers read that as inconsistency. It is not inconsistency; it is structure.

There is also the three-metre limit. When impact occurs far down the pitch, the protocol itself accepts that the projection is less reliable, and the weight shifts back to the human. Two thresholds — half a ball, three metres — tell you the system knows its own limits. The problem is not that the limits exist. The problem is that they are never published. Nobody tells you which calculation was running inside which boundary.

Audio is murkier. UltraEdge and Real-Time Snicko try to catch bat on ball. But sound travels. Ball past the edge picks up pad, glove, pitch, even the crease of a boot. Frame rate and audio sampling rate move at different speeds, so picture and sound do not always meet at the same instant.

In May 2026, with global sport shut down, I watched Hertha Berlin against Union Berlin in an empty stadium. I was nineteen, inside a Discord server of South Asian referees. I logged fourteen on-field conversations and three fouls the officials missed. In an empty stadium, every boot strike becomes a confession, because there is no crowd to hide behind. The same thing happens in cricket when stump mic audio leaks. You hear what an umpire is thinking, not only what he is saying.

The third layer is the human. The soft signal is the cleanest example. On a contested catch, the on-field umpire gave a preliminary verdict, and the third umpire could only overturn it on conclusive evidence. In May 2026 the ICC Cricket Committee recommended removing it, and it was scrapped from June. The reasoning was sound. The reality was the problem: the same video, the same frame, and two umpires still reaching different answers, because the soft signal's weight crept in invisibly. Removing it was an admission — invisible weight destroys trust in the system.

Five Ledger Entries

One: Lord's, 2 July 2026

Second Ashes Test, final day. Jonny Bairstow ducked a bouncer and walked out of his crease, assuming the over was done and the ball dead. Alex Carey threw down the stumps from behind the wicket. The third umpire gave it out.

My interest is the law, not the Long Room. When is a ball dead? At the call of over. The over was not complete. Carey threw immediately. Under Law 39, a wicketkeeper may break the stumps with the batsman out of his ground. The dismissal was legal.

Many called it against the spirit of cricket. The spirit of cricket is a preamble, not a law. The real gap is elsewhere: the law was applied, but the boundary between a live ball and a dead one was never made visible to the batsman in advance. A protocol must publish not only its verdict but its clock.

Two: Lord's, 14 July 2026

Fifty overs gone in the World Cup final. Ben Stokes hit towards deep midwicket, ran two, and Martin Guptill's throw deflected off his bat to the boundary. Six runs were awarded — two run, four overthrow.

The rule turns on whether the batsmen had crossed at the instant the throw was released. To apply it you need four things in one frame: the release, both batsmen's positions, their distance from the stumps, and the ball's path. Television rarely gives all four at once. So the umpires judged on the eye and on memory.

Kumar Dharmasena later acknowledged the award should have been five. That admission is the most important piece of evidence in the whole affair — because it shows the decision came from memory, not from proof. Memory is not written into any ledger.

Three: Delhi, 6 November 2026

Bangladesh against Sri Lanka. Angelo Mathews arrived, his helmet strap broke, and he spent time fixing it. Two minutes passed. Shakib Al Hasan appealed. Timed out — the first in international cricket.

The law is a clock. It says a new batsman must be ready within two minutes. Does fixing a helmet count as getting ready? Yes, because ready means standing on the field with your protective equipment. There is no exemption for a broken strap. But a clock is not a moral test. The problem is not the law; it is that the appeal sits with the fielding side, and in their hands time becomes a tactical weapon. Lawmakers should now decide whether the clock stops for equipment failure.

Four: Arnos Vale, 22 June 2026

Afghanistan against Australia, T20 World Cup. Rain was around, and Afghanistan were ahead on Duckworth-Lewis. Gulbadin Naib, fielding at slip, went down clutching his hamstring. Minutes later the rain came and play stopped. Naib later bowled.

Nothing in the Laws or the playing conditions covers this. There is no mandatory method for proving the severity of an injury. A physio walks on, looks for a few seconds, reports. That report never enters the public record.

This is where the chain of proof is weakest. DRS counts frames across six angles while the integrity of a body is verified by one person's word. The system is unevenly strict — ferocious where it can measure, gentle where it cannot.

Five: Melbourne, December 2026

Fourth Test of the Border-Gavaskar series. Yashasvi Jaiswal on 84. The ball passed the bat, the keeper took it, up went the appeal. Slow motion could not settle whether bat made contact. A spike appeared on the audio trace. The third umpire gave it out.

The difficulty is obvious. A spike cannot be attributed to bat, glove, pad or pitch unless the picture shows the contact. Here it did not. When the picture is silent and the sound is talking alone, the value of the evidence rests on one question: was the source of the sound visually confirmed? If not, the decision stands on inference, not proof.

The Other Ledger

Cricket's accounts are not kept only on the field. IPL auctions, franchise windows, NOCs, club-versus-country clashes — every signature is a workload liability entered in advance.

In August 2026, during the Dhaka transfer window, I was involved in a case where video evidence exposed an age discrepancy around Nigerian striker Emeka Obi, and his move to Abahani Limited collapsed. A document and some old match footage changed a decision.

Cricket does far less of this auditing. A young player's price is set by potential rather than by how many top-level matches he has actually played. That premium bubble is bursting. Paying a hundred million euros for someone with fewer than fifty top-flight games is not investment; it is gambling. Data models overrate youth and underrate dressing-room chemistry, because what cannot be measured does not appear in the model — and not appearing in the model does not make it unreal.

Machine Versus Law

There is a trap in all this. Respect for process slides easily into deference to process. When DRS hands a decision back through umpire's call, many treat the question as closed. For me that is where it opens. I state my own verdict first, then explain where the official threshold diverges from it.

At the 2026 World Cup in Qatar I worked a remote desk in Dhaka. In Japan against Spain, Ao Tanaka's goal had the ball 1.88 millimetres in play. In the Argentina-France final it finished 3-3, 4-2 on penalties. Before each review closed I drafted two possible outcomes, then published the confirmed one with the exact law. Sixty-second explainers inside eight minutes. That habit taught me the value of a ledger: if the framework is not written in advance, the explanation arrives late, and a late explanation does not answer the question — it buries it.

Distance needs a warning label. From Doha to a remote desk, distance is measured in latency, not miles. At Euro 2026, Xavi Simons' 69th-minute goal for the Netherlands against France was disallowed because Dumfries impeded goalkeeper Maignan. I saw that on a screen, not from the stands, and my copy should say so.

The greatest risk I carry is filing early. Pre-write the framework, not the conclusion, and print the condition for being wrong: state what would have to happen for this piece to be disproved.

Open the Chain

My proposal is simple. Some football leagues release referee audio so everyone hears why a call was made. Cricket does not. Third umpire conversations, ball-tracking calibration reports, audio sampling data, the weighting applied after the soft signal was scrapped — none of it is published after the match.

Make it an auditable ledger. For every review, one entry: match, over, ball, question, angles used, technology used, decision, and the legal basis. Publish it after the game. Anyone who wants to check, can.

This does not reduce umpires' authority; it increases it. Today the criticism lands on individuals, because the individual is the only visible part. Open the ledger and the criticism moves to the machine and the protocol, which is where it belongs.

The Angle You Refuse

Most cricket argument is about identity, not law. When a call goes against our team we distrust the technology; when it goes for us we celebrate it. That instinct is human and it ruins the conversation. The angle you refuse to watch is usually the one that changes the call.

At The Oval in July 2026, during the fifth Ashes Test, the ball was changed. The replacement swung more than the original. England were furious, because the replacement was chosen from a box and nobody published the selection criteria. Australia won by 49 runs. There is no camera angle for that, no spike, no tracking — only a question about how many balls were in the box and who chose. The ledger has no entry.

There is also the trap I am most prone to. Slow motion rewards obsession, so one delivery can swallow eight hundred words while the arc of the match disappears. One frame per argument. If the frame does not change the conclusion, cut it. Precision is a tool, not a style.

Takeaway

The 2026 T20 World Cup is coming to India and Sri Lanka. Tournament cycles compress everything: more decisions, more reviews, more argument. The question is no longer how accurate the technology is. The question is who audits the claim of accuracy.

My notebook has a new column. It used to read: match, over, ball, decision. Now it reads: match, over, ball, decision — and who will be able to verify this. That last column is almost always blank. Those blank cells are cricket's next big reform. When they fill, we may no longer need to say that the replay does not argue. The ledger will be doing the talking.