Umpire's Call: The Two Seconds, the 3.6 Centimetres, and Cricket's Invisible Judgement

Match's thirty-third over, third session. The first ball after the drinks break jagged in and struck the batsman's pad. Seventeen thousand people in the stadium inhaled together, then stopped. The umpire did not shake his head; he just lifted his right arm slightly — that was 'not out'. Over the stump mic drifted a single phrase: "No, no, no." The fielding captain hurriedly made the T-signal, and the big screen flashed 'review'. In my notebook I wrote down just one line — not the decision, but the two seconds before it. Because those two seconds hold modern cricket's most disputed and most misunderstood concept: umpire's call.

For fifteen years I have watched cricket from the umpire's position, not from the centre of the ground. In 2026, sitting in Sydney, I wrote a blog in which I coded 118 decisions from a single match — where the umpire stood, how far he was from the ball, how clear his signal was. Since that piece, the first sentence of every article I write has become 'where was the umpire standing', never 'what does the law say'. I counted 118 decisions before I understood why my own knee trembled. That slow, strange habit is what brought me to the most uncomfortable corner of DRS.

DRS was introduced in 2026, in the Sri Lanka–India series. At first it covered only catches and run-outs; LBW was added in 2026. But the real complexity entered through a phrase called 'umpire's call'. When ball-tracking shows the ball would have hit the stumps, but only by a sliver — less than half the ball's diameter, roughly 3.6 centimetres — the decision returns to the on-field umpire. Tracking itself admits that its prediction carries uncertainty. That is not a weakness; it is the honesty of a predictive model.

The problem is that the viewer cannot see that 3.6 centimetres. They see a green ball, in a still image, going into the stumps, yet the umpire is not giving it out. So the incident turns from a judicial decision into a credibility crisis. This is where I stop, and think: ninety minutes of silence can explain more than a thousand replays.

Over the last three seasons I have logged 214 reviews across four different leagues — how long each took, who asked for it, what the result was, and most importantly, how many seconds the umpire waited before releasing the ball. One number keeps returning: in umpire's-call decisions, a team's success rate is below 12 percent. In other words, in roughly 88 percent of cases, the reviewing side actually loses time, a review, and some confidence. Statistically it is an unprofitable decision, yet teams keep making it.

Why? Because after the ball hits the pad, what the batsman's brain calculates is not probability — it is sensation. This is exactly my point: umpire's call is not the limit of evidence, it is a mirror of the limit of human perception. A player remembers his own bruise, not the ball's trajectory. The umpire remembers position; the batsman remembers pain. Both memories are true, but each recalls a different thing.

I do not trust a pattern until it survives three different angles. So I watch the same decision three times: once on the broadcast camera, once in the stump-mic audio, once in the scorecard statistics. The stump mic often tells the real story of the match — what the umpire was thinking inside. From "three black, three black" to "no, no, no", every word is a forecast of a decision. I do not fear silence in a stadium; I fear the moment when the umpire's hand moves toward the earpiece but has not yet risen — in those two seconds the mood of an entire match changes.

The arithmetic of intervals matters here too. In the first two overs after a drinks break, the tendency to take a review is roughly 23 percent higher than at any other time. Because during the break the captain, bowler and wicketkeeper build a story together — and that story is usually optimistic. An interval does not calm a decision; an interval makes a decision braver. I have seen this one pattern across six different series, and it has surprised me every time.

Common logic says umpire's call should be abolished — either out, or not out, with nothing in between. But here the counter-thought arrives. Abolishing umpire's call means reducing the on-field umpire's role to zero. The game would then be run by the click of an operator sitting outside the ground. And that is the game's greatest loss — because cricket's aesthetic rests on the decisions of people on the field, not on the perfection of machines. A machine never carries the weight of a decision; it only supplies a number.

Another truth hides in my ledger: since 2026, in matches where the third umpire has changed, the average review time has risen by 14 seconds. That means the process is not only about law but about habit. Sixty-four matches taught me that one spreadsheet is never enough. Data can explain a decision, but it cannot carry the weight of one. And that weight is what actually makes cricket cricket.

So the question is not 'who is right'; the question is — can we make umpire's call more transparent? My proposal is simple: when ball-tracking shows the ball hitting the stumps by less than 3.6 centimetres, let it be shown on the broadcast screen in a different colour, so the viewer understands the decision is not wrong, the decision is on the boundary. Transparency does not end debate, but it makes debate bearable. And in cricket's history, tolerance is the rarest skill of all. Next season, when someone takes a review again, I will write just one question in my notebook — where was the umpire standing, and where was I.