Behind Umpire's Call: Where Cricket's Review System Learned to Bend

On the giant screen at the Sher-e-Bangla National Cricket Stadium, the final frame of ball-tracking froze. Whether the centre of the ball had grazed the outer edge of leg stump — on that single inch, the whole gallery held its breath. The third umpire's voice came through: "Umpire's call." The on-field decision would stand, because the ball-tracking projection had not crossed the line of a "clear and obvious" error. I marked the minute in a fresh page of the notebook I have kept for every match since 2026. Four columns, bound: minute, incident, law, outcome. "Umpire's call" is cricket's most debated, least understood, and most political phrase. The boundary was placed inside the design of the technology on purpose. I went back to the whiteboard to see where the whistle first learned to bend.

Open the law first. MCC Law 36 defines LBW through three simultaneous conditions — pitching, impact, and the line of the stumps. On paper the arithmetic is clean. On the field it is not, because a human judges in a tenth of a second across twenty-two yards. In July 2026, at a Test between Sri Lanka and India in Colombo, the "Umpire Decision Review System" entered the playing conditions for the first time. It began as a trial; it took roughly four years to become permanent, and by the 2026 World Cup it was mandatory in every match. Three pillars hold the system — Hawk-Eye, Real-Time Snicko, and ball-tracking. Then came the "soft signal": when the on-field umpire gave an initial indication of out, the third umpire needed "conclusive evidence" to overturn it; in 2026 the ICC withdrew the soft-signal mechanism.

The number of reviews also shifts by format — two per innings in Tests (topped up after 80 overs), and initially one in the short formats. The real question, though, is not the count but the boundary. The "umpire's call" line is born from the tracking margin of error — half the width of the ball. If the technology says the ball would have hit the stumps, but the ball's centre is so close to the leg-stump line that the technology itself is unsure, the decision returns to the on-field umpire. The technology knows that it does not know — and in that instant, authority returns to the human hand.

I do not write this history merely to write it. In 2026, after watching all 64 matches of the Russia World Cup twice — live, then on tape — and logging 455 VAR checks against the 20 decisions ultimately changed, I learned that a review system is not technology; a review system is a struggle over who keeps the power to decide. Cricket's DRS is the same architecture. Three questions guide the audit: who designs the review, who audits the auditor, and how "clear and obvious" turns into a political threshold.

The first layer — who designs it. The ball-tracking technology is built by commercial firms, and the ICC buys and operates it. But how wide the margin should be, how much room "umpire's call" should occupy, is set by the ICC's Cricket Committee, largely composed of representatives of member boards. The very people who gain or lose from decisions on the field sit at the table drawing the boundary. Here is the first bend. "Clear and obvious" is not a technical definition but a political threshold — widened whenever it suits the hand that holds the pen.

The second layer — who audits the auditor. The final call comes from a third umpire who is not on the field. He watches a screen, hears a producer's voice, receives the technology's output. There is no appeal against his decision, no second opinion. How many reviews in a match were right, how many wrong, is not regularly published anywhere. I have logged it for nine years; but that ledger is mine, not institutional. A private ledger settles nothing in public — the minute marker came before the argument, and the argument stayed with me.

The third layer — how the threshold turns political. Suppose a review shows the ball hitting just above the leg-stump line. The technology says out, but the margin is so fine that it is itself in doubt. The decision becomes "umpire's call" — the on-field verdict survives. Here is the real curiosity. If the on-field umpire was right, why was a review needed at all? And if he was wrong, why does the technology protect him? The system is not a truth-finding instrument; it is an authority-preserving instrument. DRS does not remove human error; it rehabilitates human error inside the technology's margin, so the mistake can no longer be read as a mistake.

Now look at the data. From 2026 to 2026, my ledger kept returning one pattern in the ratio of "umpire's call" verdicts. Catch reviews overturn far more often, because the evidence there is visible — whether the ball touched bat or ground can be seen frame by frame. But the LBW "umpire's call" verdict is almost immutable, because the evidence there is predictive — the path the ball would have taken is a forecast. The system is least effective exactly where it is most needed. Where the evidence is visible, DRS works; where it must predict, DRS hands the decision back to authority.

Bring Bangladesh into it and the point sharpens. Two reviews per innings in Tests, but initially only one in the short formats — a side with limited resources hesitates to spend that single one. When the ball strikes the pad of a batter like Shakib Al Hasan or Mushfiqur Rahim, reviewing the on-field umpire's raised finger means risking not only a lost opportunity but a relationship with the umpire. That psychology sits outside the protocol, but inside the result. Where larger boards spend reviews freely, smaller boards audit their own honesty over a single one.

The postcolonial map follows from here — and my vantage point, born in the UK and working in Bangladesh, is where it earns its keep. The law, technology, and disciplinary language of the review system travel from Lord's through the ICC to Dhaka, but "benefit of the doubt" is distributed unevenly. The English phrases — "clear and obvious", "umpire's call", "conclusive evidence" — come from a specific legal culture built at Lord's. In a match in Dhaka the decision is read in the same words, but the hand that makes it is never the same. The language of the game belongs to everyone; the language of power does not.

Watching matches, I notice something no statistic captures — the captain's hand signal before a review. Where the technology is certain, the signal is quick and confident. Where there is doubt, the signal is late, and the eyes drift toward the dressing room. That delay is the real data; it shows whether a side trusts the technology or fears the protocol. The muffled "let's check it" caught on the stump microphone is not emotion to me — it is the notation of an institutional uncertainty.

The fourth layer is broadcast, rarely discussed. The third umpire sits in a room with six to eight screens and a producer beside him choosing the frames. The viewer reaches the evidence of a review only through the images selected by the broadcast director. A frame not shown might as well not exist. A subtle power hides here — controlling the visibility of an incident means controlling its judgability. If the game's ledger were a public, immutable record — where no one could erase a frame, a margin, or a verdict — broadcast and decision would no longer be the same hand. Cricket is moving toward that day, and it is not far off.

Timing matters too. Each review takes minutes; the tracking is built, the frames slow, the wait grows. Under over-rate pressure a captain is forced to decide fast — the protocol is itself locked inside a time limit, where caution and delay are two faces of one coin. I have seen many matches where a rushed, needless review emptied an innings' entire stock of reviews. The quality of a decision depends not only on the accuracy of the technology but on the discipline of time management.

Let me state the mainstream case in its strongest form. DRS has made cricket fairer, reduced human error, and made decisions faster and more transparent. That case is not wrong — the number of overturns itself proves the system works. But the counter-question rises here: if the system can truly catch error, why are some errors erased through "umpire's call"? The answer is clear — because the system is not an instrument of justice but an instrument that balances authority. "Umpire's call" saves the on-field umpire from public humiliation and, at the same time, covers the technology's limits. So the viewer blames the umpire, when the fault lies with the protocol. In this tug between emotion and rule I stand with the rule — but a rule that refuses to explain itself in public is a rule no one can stand beside.

My proposals for the future are clear and threefold. First, the tracking margin and the width of "umpire's call" should be announced publicly at the start of every season, so viewers know what arithmetic runs in which frame. Second, each match's review outcomes should be recorded in an institutional, publicly auditable ledger — not a private notebook like mine. Third, "clear and obvious" should carry a written definition, free of technical and political influence.

Three reviews, three questions — who takes it, who verifies it, and who writes it down. If the answer stays in the same hand of authority, then cricket is not using the technology; the technology is using cricket. I leave the question open: when ball-tracking knows that it does not know, who draws the line of that ignorance — the law, or power?