Umpire's Call: Fourteen Frames, Half a Ball, and a Decade of Forgotten Habit

Mirpur's Sher-e-Bangla Stadium, an April evening in 2026. I am in row five of the western gallery, a worn notebook and a ballpoint pen in hand. The 34th over of the match. The left-arm spinner delivers, the batsman pushes his front foot forward, the ball strikes the pad. The on-field umpire thinks for a moment, then raises his finger — out. The gallery erupts. But the moment ball-tracking appears on the big screen, a silence descends. The ball is brushing the outer edge of leg stump — umpire's call, the decision stands.

The man sitting beside me, well past sixty, puts his head in his hands and says, "But the ball was hitting the stumps, brother."

That very night I went home and began stepping through a phone recording of the broadcast, frame by frame. Fourteen stills. Fourteen frames. In one of them it is clear that, just before the ball struck the pad, it pitched a fraction outside leg stump. Hawk-Eye's projection, however, showed it going inside. The question lodged itself in my head at once: do we actually know what 'out' means, or have we only learned that 'whatever the screen shows is out'?

Context: The Birth of a Technology, the Death of a Habit

DRS, the Decision Review System, is no new invention. It was first used in July 2026 at the Sinhalese Sports Club Ground in Colombo, during the India–Sri Lanka Test series. From 2026 it spread step by step into every bilateral series, was used in every match of the 2026 World Cup, and from 2026 the ICC made ball-tracking and edge-detection compulsory in almost all international matches. In barely fifteen years an optional experiment has become the central decision-maker of the game.

It is important to recognise the technologies working inside this system separately. In ball-tracking the main names are Hawk-Eye and Virtual Eye, with Eagle Eye in some tournaments. For edges there is UltraEdge and Real-Time Snicko. Front-foot no-balls use a separate camera setup. In my forty-eight years in newsrooms I have seen that viewers routinely mistake these three technologies for a single machine. In fact they tell three separate truths, and each carries its own chance of error.

This is precisely where umpire's call was born. Under the ICC Playing Conditions, when ball-tracking shows the ball hitting the stumps, a fine calculation follows — what percentage of the ball is entering inside the stump line. If the ball is merely clipping the line, or less than fifty per cent of it falls inside the stumps, that is umpire's call. In other words, the technology is saying, 'we are not certain.' And that uncertainty favours the on-field umpire — his decision stands, whether it was out or not out.

The logic behind the principle is simple: to protect the umpire's authority and the natural flow of the game. But a crack hides inside that logic, one ordinary viewers never notice — this 'half-ball' rule is not a perfect geometric truth, it is a compromise. A political decision born from the friction between the limits of technology and the traditions of the game.

In the rest of this piece I will try to show how that compromise has settled inside every decision — and why fourteen frames can overturn a decade of habit.

Core Analysis: Frames, Geometry and Millimetres

Ball-Tracking: Not a Measurement, a Forecast

No discussion of umpire's call is complete without understanding this. The ball-tracking cameras can only see where the ball actually went — up to the moment of contact with the pad or bat. After that, the point where the ball would have reached the stumps is not a photograph. It is a mathematical model, a projection of the trajectory, calculated from the pace, spin and bounce of the preceding frames.

So the green ball on the big screen that appears to strike the stumps never actually did so. The technology is saying it should have. Once a viewer grasps this single sentence, many complaints quietly deflate — and new questions are born. How much the ball will spin after pitching, how much it will bounce, the model decides. On a damp pitch after rain, or a rough fourth-day surface, the model has more room to err. That is why, on worn wickets, I personally always hold some doubt about the ball-tracking projection.

This is where the fourteen frames come in. Every time I have frame-stepped my own recordings, I have seen that in the six to ten frames before the ball strikes the pad there is a subtle deviation in trajectory, invisible at normal speed. In slow motion that deviation is plain. In one frame the edge of the ball shows to the right, in the next to the left — and that small difference is exactly what creates the gap between leg stump and off stump. Fourteen frames can overturn a decade of habit, because a field umpire decides in 0.3 seconds, while the technology decides by reconciling fourteen images.

Here is the first new piece of information: ball-tracking is never a 'photograph of truth', it is a forecast. And every forecast carries an error margin. That error margin is what gave birth to umpire's call.

The Geometry of Half a Ball

Now to the calculation itself. The width of a stump is a little over two and a half inches. The diameter of a ball is about eight and a half centimetres. Suppose the projection shows the ball will strike the very centre of leg stump. Then the whole ball is inside the stump line — that is 'hitting', out. But if the projection shows the ball grazing the outer edge of leg stump, part of the ball will lie outside. If the part lying outside is more than half, the technology will say umpire's call — the decision will not change.

This half-ball rule has a strange consequence few know. The same ball, the same trajectory, can produce a different result depending on whether the batsman stands a fraction in front of or behind the crease. Because if the point of pitching changes, the projected trajectory changes. In my notebook I have records of two almost identical deliveries from the same bowler, where a two-centimetre difference in the batsman's position made one 'out' and the other umpire's call.

Here lies the cruelty of the principle: the technology itself admits it is not certain, yet the burden of that uncertainty does not fall on the technology — it falls on the on-field umpire's decision. That is, the very human who decided in 0.3 seconds with the naked eye is made the final arbiter by the technology. Some call this 'protecting the umpire's authority'. I call it avoiding responsibility. The technology says 'I do not know', and that 'I do not know' is dumped on a man who was not even trying to know.

A rule is a hypothesis until the replay tests it. In this case the replay tests it and shows the rule is really a compromise — and that compromise always favours someone.

The Review Clock: The Economics of a Stopwatch

Now to the calculation of time. I have an old habit that began at the 2026 World Cup in Russia. On 16 June, in the France–Australia match, the first VAR-awarded penalty in World Cup history arrived, for Antoine Griezmann in the 58th minute. That day I was on a Dhaka studio panel. While the other panellists argued about justice, I counted aloud how long the review took — three minutes and twenty-six seconds. Since then I keep a review clock and a decision ledger for every televised match.

In cricket this clock matters even more. An LBW review takes on average about one to one and a half minutes in international matches, but complex cases run past two. What happens in that time? The field umpire looks at the screen, the third umpire slowly checks the frames, the no-ball is verified, the ball-tracking loads, and the words 'umpire's call' appear. Throughout this process the gallery is silent, the bowler keeps turning his arm, the batsman keeps a hand on his pad.

A subtle psychological shift occurs here, which I have watched from the ground many times. During the wait for a review, the bowler's aggression drops and a helplessness grows in the batsman. I have often seen that after a successful review, in the very next over the bowler pushes one a little shorter, as if to work off the anger of the previous delivery. And after a failed review, a batsman can go two or three balls without scoring — his head is still stuck on the screen.

This is why the economics of reviews must be understood. Each team gets a fixed number of reviews per innings, and loses one when it fails. So the decision is made on two levels: first the field umpire's call, second the team's tactical call — whether this review is worth taking. Many teams, hoarding their last review, squander an obvious out. Others, carried by emotion, take an impossible review and waste it.

The lesson of VAR at Russia 2026 applies directly here: when technology makes the decision, both the speed and the clarity of decisions fall, and the crowd's patience is tested. Cricket has no VAR, but it has reviews — and their cost is the same. I always tell the newsroom that watching the stopwatch and the scoreboard together changes the story of a match.

The Forensics of Fourteen Frames: How a Decision Is Born

Now let me give a full example from my notebook, of how I analyse any contested LBW. Suppose a review arrives, and the screen shows umpire's call. The question: was the decision correct?

Step one — checking the no-ball. In the front-foot camera frame, one must see whether the bowler's back foot was behind the popping crease. I never verify this part from the broadcast replay, because the broadcast does not always show this frame.

Step two — the point of pitching. Did the ball pitch on off stump, middle stump or leg stump? This frame is the foundation of the decision. In my fourteen-frame recordings it often emerges that the broadcast graphic shows the pitching point slightly wrong, because the graphic is hand-drawn, not the technology's actual output.

Step three — the point of impact. Did the ball hit the bat or the pad, and which part of the pad. If the ball struck the bat first, the LBW question never arises. This is where the UltraEdge and Snicko frames come in. I have learned that even a small spike on Snicko can be the sound of a sleeve or of the air — so a decision cannot be made on a spike alone.

Step four — the projection. Here is that boundary between 'out' and umpire's call. The ball's trajectory is projected, and the half-ball rule is applied.

Combining these four steps, I write a decision ledger: frame number, point of pitching, point of impact, projection, final result. Through this method I have often found that the broadcast's 'out' or 'not out' label is not the technology's actual output at all, but the third umpire's interpretation. And interpretations can be wrong.

The Field Umpire versus the Screen Umpire

This is cricket's deepest conflict. The field umpire decides from a living, moving scene — the pace of the ball, the sound, the batsman's stance, the bowler's arm. The screen umpire decides from still images and algorithms. Their 'truths' are different.

After I moved from cricket writing into the BCB media setup in 2026, I spent a great deal of time with umpires. Most of them say the same thing: since DRS arrived, their confidence in making decisions has fallen. Because they now know that the technology will test their decision. This 'fear of the test' creates hesitation in borderline calls. Many give a needless 'not out', as if to push the burden of proof onto the batsman.

Here a counter-intuitive truth hides. We assume technology has made umpires more accurate. But the reality is that technology has made umpires more cautious — and caution often turns into hesitation. Accuracy and confidence are not the same thing.

Contrarian Angle: The Error That Protects Us

Now I will say something uncomfortable, which many of my peers refuse to accept. Umpire's call is not actually harmful to the game; in some cases it is protecting it.

Imagine if the half-ball rule did not exist — if a ball merely clipping the stump line by a millimetre were out. What would happen? Every fine decision would turn the technology's error margin into final truth. Yet we know ball-tracking is a forecast, with its own error. If we made that forecast the final verdict, we would remove the field umpire and make an algorithm the judge.

Umpire's call is a brake against that audacity. It admits, 'the technology does not know.' That admission is uncomfortable, but it is honest. A system that can admit its own limits is better than false certainty.

But here is the ground for criticism. The problem is not in the principle, the problem is in its application. The same umpire's call becomes fortune for one team and a curse for another, because the decision depends on what the field umpire first said. That is, the same event, two umpires, two results. The principle then becomes not justice but a lottery.

The most memorable example of this conflict is the 2026 Ashes Test at Headingley. Australia's Nathan Lyon appealed for a clear LBW against Ben Stokes, but the on-field umpire, Joel Wilson, gave it not out. Australia's reviews were exhausted, so the decision stood. Stokes survived and went on to win the match. Here the technology existed, but the chance to use it did not — and that decision changed the course of the series.

This episode proves the problem is not in the technology but in its distribution. The limit of reviews, the sense of timing, and the umpire's first decision — the three together create a system in which justice depends on who is the better tactician, not on who is closer to the truth.

There is another dimension, more uncomfortable to me. When technology takes over almost every fine decision, the game slowly becomes a 'screen game'. The spectator in the gallery and the spectator on television watch two different matches. The gallery spectator hears the sound, sees the stance; the screen spectator sees the graphic, sees the projection. Their 'truths' never quite meet. A game once watched by everyone together is now split in two.

And here is my greatest worry: the debate over umpire's call that returns in every tournament is not really a debate against technology — it is a debate against the lack of transparency. The spectator does not know the limits of the technology, so he thinks the decision was unfair. If the information were disclosed, much of this debate would fade.

Takeaway: Not the Rule, but Transparency

On the last page of my notebook is a sentence I have carried for years: a rule is a hypothesis until the replay tests it. In the case of umpire's call, the replay has tested it again and again, and again and again shown the principle to be a compromise — a friction between the limits of technology and the traditions of the game.

In the coming days I want to see two changes. First, the third umpire's decision should be shown clearly on screen — which frame produced which evidence, and why umpire's call was triggered. Hiding information breeds suspicion. Second, the technology's error margin should be disclosed publicly — how many millimetres of uncertainty the technology accepts, the viewer deserves to know.

Fourteen frames can overturn a decade of habit — if we let everyone see those fourteen frames. The question is not about technology, it is about us. Do we want technology as a judge, or as an assistant? The answer is not written in the rules. It must be written on the field, on the screen, and in the transparency of every decision.