The Invisible Entry of Umpire's Call: Why the DRS Accuracy Ledger Doesn't Add Up

On the third umpire's monitor the ball beat the bat, thudded into the pad, and the projected green line clipped the inside edge of the stump. Two words appeared: Umpire's Call. The on-field umpire had said not out, so the decision stood. The crowd roared, the commentary box went quiet, and a new row landed in my spreadsheet, column heading 'UC'.

I went back to the ledger, and the story changed. For five years I have logged every review separately: who appealed, which leg of the check was questioned — pitching, impact, wickets — what the outcome was, and on what ground the original call survived. That is where the uncomfortable pattern surfaced.

Start with the law. Law 36 stands on three conditions: the ball must pitch in line with the stumps, strike the pad in line, and, by projection, be hitting the stumps. DRS tests each leg separately, and on each leg the on-field umpire's call is protected unless the evidence proves it conclusively wrong.

Two tolerances matter here. If fewer than half of the ball's projected width is hitting the stump, the result is Umpire's Call; if the point of impact is more than three metres from the stumps, that too is Umpire's Call. The batter has fifteen seconds to decide, signalled with a raised 'T'.

The technology was first used in July 2026, in the India-Sri Lanka Test at Colombo's Sinhalese Sports Club. Over roughly a decade it became mandatory by stages; around 2026 the ICC made DRS compulsory in Tests and ODIs, giving some members a transition window. In Tests each side gets two reviews, retained if successful; in the shorter formats the number shifts with the playing conditions, and I update it in my sheet before every series.

In Russia I watched the screen become a second referee — a record 29 penalties at the 2026 World Cup, and a cluster of on-field decisions reversed on the monitor's word. Before drawing the comparison, the threshold has to be named: football's intervention bar is clear and obvious error, cricket's bar is millimetres and frame rate. Same English phrase, different law, different standard of proof.

The gap nobody audits sits in the bookkeeping. The accuracy rate published after every tournament counts each Umpire's Call as a correct decision. But if the projection showed the ball heading into middle stump and the on-field umpire said not out, that was an on-field error. The technology's tolerance may forgive it; the ledger still stamps it green.

When an on-field error and a machine tolerance are filed in the same column, the accuracy statistic stops meaning anything. The number used to assess umpires is itself unaudited.

A second pattern is clearer still. In my sample, roughly half of the successful reviews turned on the impact leg — where the ball met the pad. Pitching and wickets are handled well by the machine, because frames, ball tracking and the bounce model do the work. Impact drags in pad angle, the batter's stride and the umpire's sightline: the most human leg is the one that breaks most often. That is precisely the leg teams burn reviews on.

Out of this comes the real skill: review literacy. In the fielding side, the keeper's voice, the slip cordon's consensus and the bowler's own conviction create a stream of information that outperforms the gadget. On the batting side the job falls to the senior partner, who stops the non-striker and takes the call. In my notes, most sides that finished the last fifteen overs with no review left had burned both inside the first ten.

A review is also time. One takes roughly two minutes: checking the third umpire's angle, running ball tracking, matching the projection. Four reviews in a 90-over day cost about eight minutes of play, and none of it appears on the over-rate sheet. Fall behind by overs and match fees are docked; cross a set threshold and the captain sits out a match. Discipline, I learned, is a ledger, not a mood — and the review-delay column is one nobody writes down.

The larger shift is the transfer of authority. The on-field umpire now proposes; the screen decides. What I sensed across those three weeks in Russia had already happened in cricket: every link in the chain is separate — on-field umpire, third umpire, match referee, the ICC's referees committee, the broadcaster. Accountability lands in the wrong place. The difference between Bangladesh's administrative pipeline and Britain's regulatory culture shows up here too: one asks who signed off, the other asks what the rule says.

I followed the money, then I followed the paperwork. Who owns the ball-tracking technology, host broadcaster or ICC, and what the contract says about data rights — none of it is plainly public. The system's declared margin of error, its frame rate, the reliability of the bounce model: those three numbers never reach the big screen. Yet careers are settled by that same machine's output.

Bangladesh's ledger deserves separate reading here. Under Shakib Al Hasan the side presses hard, so review demand rises; with a senior batter like Mushfiqur Rahim at the non-striker's end the call slows down. I have seen the same pattern in the notes on captains like Virat Kohli and Steve Smith: an aggressive side loses its reviews first and the decision second. That is not a story about weakness; it is a story about not keeping accounts.

There is another layer outside the ledger. DRS is not available equally across bilateral series; plenty of associate matches have no ball tracking at all. There the umpire's word is final and there is no route of appeal. The accounting is written for rich cricket, while the rest appear in the argument only as examples.

Evidence itself comes in tiers. UltraEdge shows the spike at the moment of contact; the Snicko line carries a frame lag. Which camera gets used is the host broadcaster's choice, and inside a two-minute review the frame that counts as proof can change — with no audit of that choice.

Bowling type moves the numbers too. In a seamer's LBW appeal, how much the ball moved after pitching is easy for tracking to capture; for a spinner almost the whole decision rests on impact, the very leg where human sightline matters most. In my log, spinners' reviewed appeals succeed less often than seamers' — the cause is not the technology but where the question is being asked.

Then there is the ledger of post-review behaviour. A batter's reaction when a call is overturned, a bowler's demeanour, a keeper's remark: all of it enters the match referee's code-of-conduct report. The referee's eye sees the rule before the reaction, but the record keeps only the reaction. That is where match management is really tested.

Take a small example. In an ODI each side has one review; burn it inside ten overs and in the last ten a dead-ball decision becomes final. A side that thinks about the review budget before sending out its number four is playing two games at once — one of the ball, one of the protocol.

This is where emotion meets law. When an Umpire's Call saves a batter, the ground calls it theft; when an Umpire's Call denies a bowler, the fielding side calls it a conspiracy. The reaction is identical in both cases, and in both cases it aims at the wrong target.

The popular proposal now is to abolish Umpire's Call and hand everything to the projection. Elegant on paper, dangerous in practice. A single millimetre would then settle a match, and the verdict would rest with a machine whose error margin is never published. Making evidence the final judge without disclosing the limits of that evidence is an evasion of responsibility, not a solution.

And nobody writes about this. The leg umpire stands forty metres away, at a fixed angle, in a contest close to unfair against the speed of the ball. The three-metre rule was framed out of respect for his range of sight and the batter's stride and intent. Now his fate is settled on a monitor that does not count the limits of his eye. The protocol stands beside him; nobody stands beside the man.

The easy fix goes unused: show the margin on screen. If a crowd could see, in one second, how many millimetres separated the ball from the stump, no conspiracy theory would survive under the name of Umpire's Call. And at the end of every tournament, break the accuracy figure apart — what share were true misses, what share survived on tolerance. Two separate columns are the only way that number earns its meaning.

I am 80 per cent confident that within two seasons a major board will begin publishing the projection margin, because everyone has started trying to reconcile the arithmetic. If that does not happen, and review counts keep climbing, I will conclude that commercial pressure beat the protocol. For now I keep the column separate in my sheet: UC — retained on tolerance, and it did not hit.