Not Out, Not Certain — How Cricket's Umpire's Call Divides the Sovereignty of the Decision

Last Sunday, the final session of day three. A single LBW review ran 142 seconds. The on-field umpire raised his finger — out. The batter reviewed. On the ball-tracking screen the ball clipped the inside edge of the stump, but did not fully strike it. The familiar words appeared — Umpire's Call. The decision stood. One side of the ground roared in relief, the other in anger. From the back row of the press box I wrote a single number in my notebook — what percentage of the ball would have entered the stumps. That is the only question here; the rest is emotion.

Rewind the tape; the truth usually hides between two frames.

DRS first walked onto a field in July 2026, in the India–Sri Lanka Test at the SSC in Colombo. Nobody then imagined that eighteen years later the most contested word in cricket would be a call named after the umpire himself. The curious part is that DRS was never designed for perfect decisions. It was designed to correct clear errors. Two unsuccessful reviews per team per Test innings — that limit alone tells you the system was built for caution, not for perfection.

The mechanism deserves unpacking. When a review is triggered, three things are checked: where the ball pitched, where it struck the pad, and whether it would have hit the stumps. The first stage — pitching — carries no Umpire's Call; it is fully reviewable. But the second and third — impact and stump projection — are exactly where Umpire's Call enters. By the rule, if ball-tracking shows less than half the ball would have hit the stumps, the on-field umpire's decision stands. Out stays out; not out stays not out.

Here is the first realisation: Umpire's Call is not a verdict on correctness; it is the name of a threshold. We treat it as a question of right and wrong, but engineering-wise it is a tolerance boundary. Ball-tracking draws the path frame by frame, then estimates the position between two frames — interpolation. That estimate carries a margin of a few centimetres. If the ball grazes the edge of the stump inside that grey window, the system itself says: I am not certain, so let the human on the field stand.

For five years I have logged these decisions in my own ledger — who reviewed, what the outcome was, and whose shoulders the failed review fell on. What keeps returning is a strange asymmetry: where the ball strikes the pad in the impact zone depends on the batter's footwork. The batter with a long stride often produces impact outside the line; the one with a short stride produces impact in line. Same delivery, two different review outcomes. This is not umpire bias — it is the geometry of batting technique.

Second realisation: A batter who learns to read the frames wins reviews; one who reads only emotion loses them. The leading batters of this generation — Smith, Kohli, Williamson — weigh three things before reviewing: where it pitched, where it hit the pad, and how far they stretched. Their review success rate is not luck; it is pattern recognition.

Now the counter-question. With all this analysis, why does Umpire's Call provoke so much anger? Because the system speaks in two languages. The language of technology is numerical — percentages, probabilities, margins of error. The language of the spectator is decisional — Is the ball hitting the stumps or not? You cannot even tell me that? The two cannot be reconciled, because they answer two different questions. One says probably yes; the other demands certainly yes. The real weakness here is the idea of clear and obvious itself — where clarity is not objective but a negotiated agreement.

In my eyes the real problem is not the umpire but the protocol. Two reviews an innings, and a red cross flaring on every failed review — this design makes teams strategic but turns the umpire into a vessel of suspicion. In nearly every Test there are one or two decisions where tracking and the human eye disagree; there the human on the field always stays on top, yet the entire controversy lands at his feet.

Third realisation: When an institution runs two different standards at once — certainty and probability — the deficit of confidence belongs to the process, not to the technology. The dual standard is where the limit of DRS hides, not in the spectator's misunderstanding.

The fix is not simple, but one path is clear: either show the percentage line openly to the spectator, or replace the term Umpire's Call with the actual measure — for instance, below 60 percent, the decision is unchanged. As long as a number is kept hidden and run under the name Umpire's Call, every marginal decision will leave behind a small deficit of trust.

I was once the only woman in the Ambedkar Stadium press box, where for six matches I had to file from Row 14 of the stands. There I learned one thing: more important than who takes the decision is how the decision is taken — seeing the process itself. The same question returns in the DRS of cricket.

If a disputed decision lives between two frames, who is at fault? The ball, the system, or that threshold line — which we drew with our own hands?