The Half-Ball Rule: The Frame Where You Cannot Win a Review, Only Explain It

On the big screen, ball-tracking froze just beside leg stump. Two words lit up in the corner — Umpire's Call. A few thousand people in the stands exhaled at once, and the scoreboard did not move. The on-field umpire had already given it not out. Ball-tracking said the ball was hitting the stumps, but less than half of it. The decision stood.

I watched it from a desk in Dhaka, on a remote feed. Commentary in the headset, three angles on the monitor next to it, the green line of ball-tracking in the corner. What the screen said was insufficient evidence. The real question was never evidence. It was the threshold. Who decided that half a ball means certain, and forty-nine per cent means uncertain? From Doha to a remote desk, distance is measured in latency, not miles — and here a decision is measured in thresholds, not truth.

Behind that moment sits a design choice, and design choices are understood from outside the pitch.

Context: how the review arrived, and how it settled

DRS entered cricket in 2026, in the Test series on India's tour of Sri Lanka. It began as an experiment, dependent on the consent of two boards. Over several stages it became a permanent structure of international cricket — ball-tracking, Snicko and UltraEdge, real-time stump mics, a full apparatus of evidence.

At first many boards refused it, citing cost, reliability and the pace of the game; for several seasons teams chose for themselves whether to use it at all. That experimental phase is over. Today a major match without reviews is hard to imagine. The real change is that the responsibility for a decision no longer sits only on the umpire's shoulders; it is shared with an operator in a room.

The design is simple. Two reviews per team per innings. A successful review is returned; a failed one burns. A review is a limited resource, much like the overseas quota or the NOC a franchise holds during a transfer window: spend it badly, and you have nothing left when you need it.

The arithmetic differs by format. In Tests there is time, so the risk of spending a review is lower; in limited-overs cricket every review costs more, because one decision there settles the whole match.

That resource logic has changed the strategy of the game. Fielding captains once appealed on instinct; now they do arithmetic. The fast bowler says it hit him, but the captain knows that if the line is uncertain, the review burns. Experienced captains in the ring now decide on three separate pieces of information — where the ball pitched, where it struck, and how certain the line to the stumps really is.

A review is also a strategic pause. It breaks a batter's rhythm, relieves pressure in an over, shifts a team's body language. Some innings, a review is spent on time rather than on a decision.

This evidence apparatus works like an immutable ledger. Every review is appended, every decision is recorded, and nothing is deleted. Ball-tracking, Snicko, stump mic — separate nodes offering separate testimony about the same event. When those testimonies contradict each other, who is final?

Core: three legs, three different thresholds

An LBW review is never one question. It is three in sequence, each with its own limit.

The first leg is where the ball pitched. The threshold here is near-absolute: pitch it outside the line and the review fails, whatever happens afterwards.

The second leg is impact — where the ball met the batter. On the line or outside it, another line-dependent limit, with the on-field umpire's call still carrying a small advantage.

The third leg is whether the ball would have hit the stumps. This is the half-ball rule. If ball-tracking shows more than half the ball striking inside the stumps, the decision changes. If less, it is Umpire's Call — the on-field decision survives.

Those three thresholds are not equal, and that is the story. The first two carry little room for error, because pitch and impact are close to direct observation: the camera records, it does not predict. The third leg is pure prediction. The ball has not reached the stumps; the system draws a forecast from trajectory, spin, bounce, air. Forecasts carry their own margin of error, which the manufacturers themselves acknowledge.

So Umpire's Call is not a standard; it is the administrative form of a margin of error. When the system is not confident enough in its own forecast, it hands the decision back to the umpire on the field. That is an admission of weakness, and it is also the system's honesty.

Conditions change the picture. On the slow, low-bouncing surfaces of the subcontinent, ball-tracking's forecast is comparatively easy, because the path of the ball changes little. Where bounce is uneven, where seam movement is high, where the air moves, uncertainty on the third leg grows. The same ball, the same player, a different verdict on a different ground. That is the limit of the technology — and that limit has never been written into the laws.

The catch review is a different world. Outside LBW, the question becomes whether the ball touched the edge. Snicko and UltraEdge catch the sound, but the stump mic, the brush of pad, the noise of the crowd can bleed into it. Here the soft signal mattered: the on-field umpire gave a preliminary call, and the third umpire was reluctant to overturn it. Over recent seasons the ICC has reduced the soft signal's role, so the third umpire can decide alone.

In an empty stadium, sound is the witness. In 2026, when the game had stopped, I watched matches without crowds and logged referee audio cues. That is where I learned that the language of sound is the language of decision. A call, a hesitation, a no — the stump mic catches them, and later they become evidence in a review. The angle you refuse to watch is usually the one that changes the call, and it is often hiding in the audio.

The review economy. Two reviews mean two chances, but the real accounting is more complex. A successful review comes back, so a team that keeps getting them right can keep playing for a long time. A failed review does not only cost a chance; it leaves a mark on a team's belief. Late in a match, when one decision could settle everything, having no review left means the control sits with the opposition. Much like a franchise that spends its last overseas slot mid-season.

When a Bangladesh captain stands in the field — Shakib Al Hasan or Najmul Hossain Shanto — he has fifteen seconds and his own eyes. With a senior batter at the crease, Steve Smith or Babar Azam, the fielding side knows one decision can turn the tempo of a match. That pressure is not visible from outside; the feed shows only the outcome.

What the feed does not show me. The biggest limit of a remote desk is that I am not standing on the ground. What the feed cuts, I do not see. Pitch moisture, the seam position, the wind — I estimate them on a screen. So my verdict is always conditional: if ball-tracking is right, if the camera's frame rate is enough. Those ifs cannot be removed. Distance is a limitation here; writing the limitation down is the honest part of the job.

The umpire's psychology remains an open question. Whether reviews have changed how umpires decide is something my notebook holds two kinds of samples on. Some hesitate to give it out under doubt; others trust that technology will correct them. Which happens more needs more match footage. Reaching a verdict without knowing the answer is the biggest trap in this piece, and I will not step into it.

Contrarian: Umpire's Call is about authority, not accuracy

Here is the most uncomfortable truth. Umpire's Call survives to balance authority.

Imagine the technology said: the ball hit the stumps by forty per cent, so it is out. What role would the on-field umpire have left? None. He would be a man in a chair reading a result. The Umpire's Call threshold is exactly what keeps a human element valid inside the structure.

In plain terms, it is a constitutional compromise. The technology knows a great deal, but it does not have the right to know everything — not yet. Football's VAR carries a version of this problem: there, VAR breeds a culture of fear; here, Umpire's Call keeps a culture alive.

There is no moral question here; the question is one of management. Management does not always ask what is true. It asks who decides, and how quickly the decision becomes final.

So when someone says the ball hit the stumps, why is it not out, the answer is not in the law. It is in the distribution of power. And that distribution does not change until the alternative proves itself better.

The replay does not argue; it just waits for you to catch up.

Looking forward

Ball-tracking is getting more accurate, sensors are getting denser, and machine learning is sharpening trajectory forecasts. On that path, the half-ball threshold will shrink one day — the only questions are how fast, and under whose pressure.

When it shrinks, we win a more accurate game and lose a human structure. Which do we need? Do you want the decision to be right, or to be final? When you can answer that, you will understand that cricket's hardest review does not happen on the field. It happens in the law book.