Umpire's Call: Who Owns the Verdict in Cricket's Chain of Custody

Lord's, 14 July 2026. England needed 15 from the last over, Trent Boult bowling. A throw struck Ben Stokes' bat and ran away towards the third-man boundary. The umpire raised his arms: six runs. The question was not about a four or a six. It was this: had the batsmen crossed for the second run at the instant the throw was released? Six if they had, five if they had not — and that single run decided the match and the ownership of the trophy.

There were at least thirty cameras at Lord's that day. Anyone in the production truck could have replayed every angle in slow motion. But no screen had jurisdiction over that calculation. The ICC's player review list contains no entry for 'overthrow run count'. Whether the ball touched the rope is reviewable. How many runs were completed, and when the batsmen crossed, is the on-field umpire's eye and experience. I went back to the ledger, and the story changed — because a World Cup hung on a decision with no chain of evidence.

What the law says, and who runs the chain

Cricket's Decision Review System began in 2026 during India's tour of Sri Lanka. In nearly two decades it has stood on three pillars: ball-tracking (Hawk-Eye or Virtual Eye), UltraEdge for sound and spike, and high-frame-rate slow motion. In an LBW review, three questions are asked — where the ball pitched, whether impact was in line with the stumps, and whether the ball would have hit. If any one of them lands in 'umpire's call' territory, the on-field decision survives. The stumps threshold is simple: if less than half the ball is projected to hit, it is umpire's call. There is a second boundary — if impact is more than three metres from the stumps and the on-field call was not out, that too is umpire's call.

The number of reviews is fixed by law. Two per team per innings in Tests, retained on success. Two in ODIs and T20Is, but not retained even when successful — and that asymmetry is where captains' headaches begin.

Now the real question: who owns this process? The chain runs like this. The two on-field umpires make the first call. If a player reviews, the decision travels to the third umpire. The third umpire watches a projection supplied by the ball-tracking vendor. The final report goes to the match referee, and the match referee to the ICC's discipline department. The problem is that every joint in this chain has a blank cell, and those cells do not publicly account for themselves. Match referee reports, the detail of code-of-conduct charges, the arithmetic of over-rate penalties — the public version is thin. Media gets a headline, not the sheet.

There is a second asymmetry of geography. DRS is a bilateral agreement item — meaning whoever pays for it gets it. A full ball-tracking and UltraEdge set-up costs thousands of dollars per match. As a result, many Associate member matches and numerous women's bilateral series run without full DRS. Where a men's franchise league has twelve to sixteen cameras, a women's series runs on three or four, with no ball-tracking at all. Two tiers of justice are created at the very first step of the chain. The question is not about technology. It is about priority.

Frame one: geometry and the illusion of precision

Ball-tracking is a projection, not truth. From camera frames, the ball's speed, spin and air resistance are used to draw a future path — and that drawing carries a margin of error, naturally a few centimetres. An LBW decision can sometimes rest on fifteen or twenty millimetres of arithmetic. On television we say 'the ball was missing leg, a big error'. In reality that 'missing' contains the projection's uncertainty, and that is exactly the justification for umpire's call.

Based on my years of watching matches, I keep a small private log: how long each review took, which camera angle fed the verdict, and what the outcome was. From that ledger I can say the average review takes 80 to 85 seconds, and much of that wait is the processing of the final ball-tracking frame. As a viewer it feels like delay. The ledger says the delay is part of the process.

The referee's eye sees the rule before the reaction, and the rule says this: technology does not remove doubt, it relocates it — from the field to the screen, and from the screen to the vendor's software.

Frame two: review economy and the captain's arithmetic

Look at review management and you find players often using the mechanism not as an error-correction tool but as a tactical challenge. With a new ball, against the quicks, there is a strong urge to burn a review early — and then the hands are empty at the death. One pattern recurs in my log: reviews taken in the first ten overs succeed less often, and reviews taken in the last five overs succeed markedly more. The reason is psychological. Under pressure, players listen less to their own doubt and more to the noise of the team. A wicketkeeper raises a hand, and the captain does not think again.

Here lies an arithmetic regret: in ODIs and T20Is a successful review is not returned. The whole equation becomes risk management. Where a Test innings banks a successful review, a T20 innings ends after two bad guesses. Two formats teach two different philosophies of management, yet the difference is rarely discussed in training.

Discipline, I learned, is a ledger, not a mood — and that holds for reviews too. What teams praise as a 'brave review' is, in the ledger, usually a scattered decision.

Frame three: ownership, paperwork and the quiet rooms

This is where the real flaw sits. We argue about the geometry of DRS, never about accountability. When a review ends, where are the audio recording of that decision, the confidence interval of the ball-tracking, and the third umpire's reasoning stored? In no central public database. Ownership of ball-tracking data sits, in most cases, with the technology vendor and the broadcaster, not with the governing body.

I followed the money, then I followed the paperwork. What I found is this: cricket's administrative layer has a budget for buying technology, but no budget for archiving and auditing technology's decisions. In code-of-conduct cases the fine is published; the reasoning is summarised, often in one line. Over-rate sanctions travel the same road — the result is known, the worksheet is not.

The same picture appears in franchise cricket's money flows. Retention fees, undisclosed contracts, signing-on payments — none of it lands in a balanced ledger, yet it decides who plays. When those who own the discipline of the game and those who own the bookkeeping of the game are different groups, reform arrives but culture does not.

The counter-argument: emotion versus rule

The natural reaction now arrives — abolish umpire's call. The argument is simple: if the ball hits the stumps it is out, if it misses it is not out, with no grey zone in between. I do not advance towards that argument without care.

In Russia, at the 2026 World Cup, I watched the screen become a second referee. I catalogued every review across all 64 matches — 29 penalties, the new handball interpretation, a record number of on-field decisions overturned. In football it did not reduce controversy; it moved its centre. Remove umpire's call in cricket and that is precisely what happens: the umpire's role shrinks, the decision shifts to a software estimate whose error margin nobody publicly admits. That is not transparency. It is the shadow of transparency.

The real problem is not a weak decision but an unauditable one. A bad call spoils a match; an unaccounted call spoils trust in the system. And administratively, rolling out technology is often just advertising for modernity — the costume changes, the foundations of accountability do not.

Last word: the ledger, and one question

My proposal is simple. For every reviewable decision, build a public, time-stamped, tamper-resistant ledger — match ID, over and ball, on-field call, whether a review was sought, the third umpire's name, the ball-tracking projection and its uncertainty band, the duration, and the match referee's final disposition. If each entry is linked to the previous one, nobody can quietly amend the arithmetic later. What has been sold as sports blockchain over the past few years is almost entirely fan tokens and NFT ticketing; nobody has built the ledger. Yet the chain of custody over decisions is where the technology is most needed.

I am 80 per cent confident that such a ledger would reduce controversy more than any further change to the threshold. I would be wrong if it turns out the complaint is not about decisions at all but about the pain of losing — then no database will cure it. That prediction is the test.

The next time a World Cup is settled on the final ball, the question will not be whether the ball was hitting the stumps. The question will be this: will we have the ledger, or the same argument again?