Umpire's Call: 118 Reviews, One Stance — Where Proximity Outweighs the Verdict

Hook

The third ball, outside off, angling back in. The umpire's arm stayed down. The batter had already begun to walk — two paces, then stopped. The captain looked at the camera and raised his arm into the T-sign. Ball-tracking appeared on the screen: two of the three projections hit the stumps, one missed. The line crawled forward and stopped short of the flag. Two seconds later, the words arrived — umpire's call.

I wasn't writing down the line of the ball. I was writing timestamps: the gap between the third umpire's hand moving to the earpiece and the on-field umpire's arm going up. Across the 2026-25 season I coded 118 reviews, five columns each — stance, distance, signal clarity, review duration, and the length of silence before the verdict. What follows is an explanation of that notebook, not a verdict on any one decision.

Context: Where the line came from

Review technology in cricket was not born of a dramatic moment. It was born of arithmetic. July 2026, the Sinhalese Sports Club ground in Colombo, India against Sri Lanka — the first Test in which ball-tracking and Snicko were trialled. Before that, the only witness to a decision was the umpire's eye, and the resolution of that eye depended on where his feet were.

The framework today runs like this: if a batter is given out, the batting side may review; if not out, the bowling side may review. Two reviews per innings in Tests, topped up after eighty overs. Two in ODI cricket, one in T20Is. The batter has fifteen seconds to decide. In practice that window is almost never used in full, and I will come back to that.

There are three technology layers, and each answers a different question. Hawk-Eye ball-tracking answers where the ball pitched, where it struck, and where it would have gone. UltraEdge and Snicko answer whether the ball touched the bat's edge — a question of sound, not sight. Hot Spot looks for heat on the bat by infrared. Three separate devices, three separate kinds of evidence, and in the eyes of the law they do not weigh the same.

The most argued part of ball-tracking is the umpire's call zone. Whether the ball would hit the stumps divides into three outcomes: hitting, hitting but within the tolerance band outside or inside that projection margin, and missing. Inside the tolerance band the on-field decision stands, because the technology cannot confirm the ball would truly have struck. The technology does not speak truth here; it speaks probability — and umpire's call is where that probability runs out.

Of my 118 coded reviews, 41 ended on umpire's call. That is roughly 35 per cent of cases where the final language of the review was not the technology but the on-field umpire's earlier decision. I counted that number three times before believing it.

Core Analysis: Where he stood is the first question

1. Position before law

My method never opens with “was it out?” It opens with: where was the umpire standing, and at what angle to the ball?

When a left-arm spinner turns one into a right-hander's pad, the law turns on whether the ball pitched on the line of leg stump. But if the umpire stands behind the wicket, in line with leg stump, he cannot see the line from release to pitch. He sees pitch to pad — half the information. The rest he estimates, and from that estimate comes the decision that later collapses under projection.

Of my 118, 57 were pace and 61 spin. Among the spin reviews, 29 upheld the on-field decision, and in 17 of those the umpire had not stood close to the pitch — present at the moment of pitching, roughly four metres away at impact. Widen the distance and the angle widens; widen the angle and the estimate widens; widen the estimate and the reviews arrive.

A stranger pattern emerged here. My ledger put the batting side's review success rate against spin at about 28 per cent, against pace at 39 per cent. The difference is not the quality of the bowling; it is the height of the bounce. When the ball climbs, the umpire's head-line does not change, so his stance holds from the previous delivery. When the ball stays low, he leans onto the front foot, and the angle along the line of the pad is erased.

2. The two seconds of silence

The most important part of a review is the part no broadcast shows: the silence before the verdict.

I tracked audio across all 118. On average, 47 seconds elapsed between the referral reaching the third umpire and the announcement. But those 47 seconds are not equal. There are two distinct blocks: the ball-tracking computation, and the formation of the decision. The first is roughly fixed, 20 to 25 seconds. The second oscillates between 8 and 35. Where the time stretches, there is usually not one decision but two.

Why? Because when ball-tracking and UltraEdge are both relevant — bat and pad together, then LBW — the third umpire has to test two separate pieces of evidence separately. Those two pieces frequently testify against each other. If the ball touched the bat's edge, the LBW question disappears; but if the sound was the pad, it does not. UltraEdge shows a small spike, and reading the height of that spike requires knowing how fast the ball was travelling.

Twenty-three reviews in my notebook carried an ambiguous spike — the height sitting in the grey zone between pad sound and bat sound. Nine went the batting side's way, fourteen against. No consistency. This is my deepest distrust: the technology supplies evidence, but it does not supply interpretation — a human does, in a room outside the camera's frame.

I do not trust a pattern until it survives three different angles. So I checked the grey-spike cases three ways: the scorecard, the second I heard the announcement, and the on-screen caption time. Average drift across the three: 1.8 seconds. Everything cannot be synced, and that is the problem.

3. The evidence of the stump mic

For three years I have watched matches on headphones, not on speakers. It is a habit that came from the 2026 New South Wales hub, from an empty stadium with zero spectators, where I heard the umpire's voice — from “no, no, no” to “green, green”.

Live cricket's stump mic gives us far less than we assume. Broadcasters pick a stream and set a gate; the sounds the producer needs are the sounds you hear. The thud of ball on turf, the brush of pad, even the umpire saying “no idea” — often cut. Of my 118 reviews, only 31 caught a bowler's or batter's voice cleanly.

But what it caught was valuable. Before a review, a bowler often says one word to his captain — “heard it”, or “pad”, or “line”. Which word he says frequently predicts whether the review will succeed. Reviews opened with “heard it” succeeded 54 per cent of the time; reviews opened with “line” or “pad”, 22 per cent. A bowler's ear is never better evidence than his eye, because a bowler knows the sound of his own delivery but not the line of it.

There is a suspicion I cannot yet prove: the wicketkeeper's role. From behind the stumps, the keeper sees both pitch and impact — a better angle than the umpire, in some cases better than the batter. My notebook has no separate keeper column, because the television camera almost always shows the keeper's back, never his face. That is a gap in my ledger, and I will say so plainly.

4. The economics of the interval

Drinks, tea, stumps, rain — people call these rest. I call them the market for decisions.

I measured review density per session across a Test. The pattern repeated almost every match. Reviews arrive rarely in the first session. They spike at the start of the second. They climb sharply in the third, especially in the first ten overs after tea.

By my count, 43 of 118 reviews came in the half-hour following a break. That is 36 per cent of all reviews inside 14 per cent of the day's play.

One hypothesis: a break is when a batter reconciles his own decisions. He watches the ball he survived, talks to the coach, and returns in a more aggressive reviewing mood. Another: a break is a seam in the umpire's concentration. An umpire back from tea spends two or three overs resetting.

I could not separate the two — these remain hypotheses, and I label them as such. What I could separate is the killer moment. If a wide or a no-ball falls in the first over after a break, the probability of a review on the next ball rises above any other point in the match. Break the rhythm of the game and you break attention, and broken attention decides fast.

5. The problem of fifteen seconds

A batter has fifteen seconds. I timed them, against the stadium clock and the broadcast feed.

The mean decision took 6.4 seconds. The longest, 14.2. The shortest, 1.1 — an off-side umpire's call that, correctly, was not one. The useful fact: batters do not use the full fifteen, and those who do not are not more accurate — the reverse. Reviews taken in under a second succeeded 19 per cent of the time; those taken after six seconds, 41 per cent.

A fast review is not confidence. A fast review is habit. And a review taken by habit is not a decision, it is a reflex.

A personal number here: my ledger holds more than seventy matches, and I have never once sat beside a ball-tracking system at a ground. Only broadcast pictures, audio, and my own notes. What I am describing is not how well the technology works. It is how the technology is used.

6. The players, who caught and who let go

My notebook does not distribute review leadership by captaincy. It distributes it by who stood in front of the decision — because who takes the review matters less to me than who carries the responsibility for it.

The regular captains of 2026-25 — Rohit Sharma, Ben Stokes, Pat Cummins, Babar Azam, Kane Williamson — show distinct patterns. One takes his reviews from slip, a man who cannot decide far from the dressing room. Another stands at long-leg, where the angle itself is different.

And there is one who almost never reviews. That may be part of his method, but in my ledger it is a column left unfilled. Across eight matches I recorded Jasprit Bumrah initiating only four reviews during his own spells — a broadcast-based count, and one I would not ask anyone to treat as exact.

Why do I write a line like that at all? Because the richest archive of review decisions sits between slip and the keeper, and no television camera goes there. Sixty-four matches taught me that one spreadsheet is never enough.

Contrarian: Verdict is process, and process is not proof

The language of cricket argument is now entirely correct versus incorrect. The umpire got it wrong. DRS failed. Give me 110 per cent proof and the decision flips. No technology supplies 110 per cent proof. Ball-tracking runs a model — it projects a shadow from the ball's path. UltraEdge reads an audio file. Camera frame rates are finite. We use the word proof where we should be using estimate.

Of my 118 reviews, only 11 overturned a decision in a situation where the gap between the on-screen projection and the on-field umpire's prior call was under one centimetre. In each of those 11, the decision stopped being a technical factor and became, literally, a matter of the match's atmosphere.

Now to the part I most want to write about — umpire's call.

People say “it's out, Hawk-Eye shows it.” Hawk-Eye shows the ball hitting the stumps; it does not show it passing through an X-ray. Where would it hit, at what angle? Some projections lose two stumps; some drop the ball lower. Umpire's call is not for or against any side. It is an admission — the human eye is not behind the tracking; it is a few centimetres behind it.

To me that is not failure, it is a boundary. And where that boundary lies is a political question in cricket: some want the tolerance band narrowed, some want it kept. Watching this sport for thirteen years teaches one thing — the umpire is being abused over a number the technology itself will not guarantee.

One more thing. It is often said that Indian, English or Australian batters get more reviews, or that home sides enjoy an advantage. My ledger does not support that. What it does support: a touring side took roughly one extra second of silence inside its review decision. And inside that one second is a number — but it is a number that does not measure the same thing for everyone.

Ninety minutes of silence can explain more than a thousand replays.

Takeaway: What comes next

The ICC's cricket committee re-examines tolerance statistics roughly every two years. Every time the band changes, the number of reviews ending on umpire's call changes — while the number of umpires on the field does not. That is not scientific equivalence; it is a philosophical choice. So the question is this: does cricket want a decision that is correct, or one that is accepted, and that carries a human name behind it?

One practical note, and I am writing it for the second time in this ledger — my largest suspicion sits with the stump mic. When the production lights and the camera crew go home, the game's most honest evidence goes unheard. Restoring it would not require humiliating an umpire. The best film is not seen, it is heard — and anyone who puts the last piece of evidence to their ear once will understand. Sixty-four matches taught me that, and now it seems to me that 118 decisions are scattered less across the field than across one room — a room whose door is open, and which nobody enters.

_ROOT: REFEREE_