The Arithmetic of Umpire's Call: Why DRS Reviews Get Burned, and Where Bangladesh Goes Wrong

Two screens are open on my Dhaka desk. One carries the broadcast feed, the other the ball-tracking overlay. A T20 World Cup night: the seamer hits the deck, the batter is a long way forward on the front foot, the umpire shakes his head. The captain raises his arm for the T. Three minutes later the screen reads: Wickets — Hitting. Decision — Umpire's Call. Not out. The review is gone.

By then the social feed has settled on the word "robbed". I wrote nothing. Since 2026 I have logged every review in a notebook, and the column that has earned its keep is not "was it out" but "was it overturnable". The replay does not argue; it just waits for you to catch up.

DRS: sixteen years of one system

DRS arrived in a Test series in July 2026, on India's tour of Sri Lanka. Since then it has split into three layers — ball tracking (Hawk-Eye, Virtual Eye), audio (UltraEdge), and frame-by-frame ground contact. Two unsuccessful reviews per innings in ODIs and T20Is; two in Tests, topped up to three after 80 overs. In June 2026 the ICC abolished the soft signal for low catches, effective from the World Test Championship final.

Inside that architecture sits a rule captains read less often than they should, and it is the one that burns reviews: a review is returned only if the on-field decision is fully overturned. Umpire's Call means the review is spent. The system is not a truth machine; it is a threshold machine, hunting for a margin that clears its own declared error bar.

Two standards of proof, one match

The real inconsistency is here. There is no Umpire's Call on a run-out or a stumping — the third umpire looks at the frames and decides himself. If a batter's boot is two millimetres inside the crease line, he is out, no leeway. Yet in the same match, with the same ball-tracking hardware, an LBW where almost half the ball is inside the stump line leaves the decision untouched.

Same day, same screen, same technology — two different burdens of proof. Zero tolerance on one decision, fifty per cent on another. The reason is not technical, it is constitutional. A run-out is an event; an LBW is a projection. The system takes responsibility for events and refuses it for projections.

The arithmetic of Umpire's Call

Ball tracking is not a photograph; it is a cone of probability. If the projection shows the ball hitting the stumps but less than half the ball's diameter inside the stump line, that is Umpire's Call. Whatever the on-field decision was, it stands.

There is an asymmetry nobody talks about. Give it out, and if the projection reads Umpire's Call, it stays out. Give it not out, and if the projection reads Umpire's Call, it stays not out. Umpire's Call does not favour a side; it favours the ground decision. The review is not hunting truth, it is hunting margin.

What captains actually review

"It looked out" is a sensation. Decisions where the evidence is independent overturn most often: edge, stumps, ground contact, run-out. Decisions with an interpretive layer — impact, pitching — carry the highest chance of Umpire's Call.

For Bangladesh the loudest pattern is the front foot. Our batters take a big stride against spin, and a big stride pushes the point of impact well past the crease. Pitching in line is no help if impact is outside off — and that is a question of interpretation, not proof. Reviews burned in the first six overs do not come back in the last over.

There is also a forgotten character: the keeper behind the stumps — Mushfiqur Rahim or Litton Das — is the first review sensor. The captain stands at mid-off; the ball's line is not in his eyeline. The call is built from the keeper's voice and glove, and that is precisely where review training gets the least investment.

The limits of distance

I watch from Dhaka, so my claim is bounded. I see the angle the broadcaster chooses to give me; audio arrives six to eight seconds late; I never get stump-mic bleed and the delivery frame in the same instant. From Doha to a remote desk, distance is measured in latency, not miles. The angle you refuse to watch is usually the one that changes the call, but from a remote desk I do not get to pick that angle. So what I can adjudicate is not the pitch, it is the process.

Contrarian: Umpire's Call is the system's honesty

People treat Umpire's Call as a defect. I read it as the only honest part of the machine. Ball tracking is a projection, not a picture. Path, bounce, seam position, pitch abrasion — together they produce a probability, and the fifty per cent threshold is the system saying out loud, "I do not know." The rage at Umpire's Call is really rage at a refusal to pretend certainty.

That does not leave captains powerless. Teams treat Umpire's Call as bad luck when it is one of the most predictable events in the match. Log your own reviews with timestamps — who asked, which over, which umpire, what result — and within three matches you have a distribution. A captain who knows his side's Umpire's Call rate stops buying that review.

The second blind spot is investment. Franchises and boards pour money into batting swing data, bowling-load models and field-placement charts, while spending almost nothing on review-decision training for captains and keepers. A review is worth two to three runs in a match, and far more in a knockout. The side that treats a review like a capital allocation wins the marginal games.

Looking forward

The next edge is not a better camera; it is a review expected-value model — probability of overturn, cost of losing the review, and match phase, in one simple sum. And the question for the ICC is this: if ball tracking admits its own margin is fifty per cent, why is the burden of proof weighted to one side? My Dhaka notebook has more questions than answers, and that is the point. Whether the threshold moves is the ICC's decision; playing the threshold is the captain's.