Umpire's Call: Auditing the 50 Per Cent Threshold and Cricket's Review Culture

Late one night last March, in a small flat in Kuala Lumpur, I was watching the closing ten overs of an ODI with an open spreadsheet beside me — three columns: minute, decision, law applied. On screen the ball-tracking graphic spun; the third umpire, calm through the headset, announced that the ball was going on to hit the stumps, but less than half of it — umpire's call, on-field decision unchanged. My friend beside me yelled that it was obviously out. I wrote: over 47.3, review type — ball tracking, law applied — LBW, final outcome — on-field decision upheld, review retained.

In Kuala Lumpur, I began logging VAR incidents; the pattern was already there — this is the cricket edition of that same log. In 2026, as a student in this city, I recorded 12 VAR reviews across 12 FIFA Confederations Cup matches, building a spreadsheet of minute, law and outcome. That grew into a 12,000-word VAR Protocol Audit across all 64 matches of Russia 2026 — 29 penalties, 20 overturns, categorised by law and average review time. The biggest lesson from that audit was simple: arguments are about the verdict, but the problem hides in the definition of the threshold. Cricket's Decision Review System is far more auditable than football's VAR in exactly that respect — and for that very reason its gaps are more visible.

Protocol first, controversy later

DRS was first used in July 2026, in the Colombo Test between India and Sri Lanka. It began as an experiment, tournament by tournament; it was not used at all at the 2026 World Cup. Since then the ICC Playing Conditions have changed in stages — the soft signal for catches, ball-tracking accuracy, the point of impact, even the number of reviews. From June 2026 the soft signal was removed; on-field umpires no longer give a preliminary call and simply send the decision upstairs, and the third umpire must have conclusive evidence to overturn it.

For LBW there are several decision gates. Did the ball pitch outside off stump, or in line? Was the impact in line with the stumps? Did the batsman offer a shot? And if the point of impact is more than three metres from the stumps, ball-tracking must prove the ball would hit the middle of the stumps — this is where general viewers get most confused. Each of these gates is a law, a specific condition, and a specific confidence level.

The decision tree: how a review is actually judged

From my 2026 audit I borrowed a four-step template: trigger, review type, final call, law citation. In the cricket log I added a fifth box — confidence level: low, medium, high.

The trigger is the moment the field umpire gives out or not out. Review type is what the team is challenging — ball-tracking, UltraEdge, point of impact, or something like the playing condition for out-of-stumps. Final call means the on-field decision stands, is overturned, or is umpire's call. And the law citation — the LBW clauses of the Playing Conditions and the condition about whether the batsman offered a shot.

Which trigger is the most contested? My log shows clearly that ball-tracking reviews are the ones most often ending in umpire's call, whereas reviews about the point of impact are frequently overturned outright. The reason is mathematical. The point of impact is a static event — where the ball hit can be examined frame by frame. Ball-tracking is an inference — the path after contact is a simulation, a prediction. Every ball-tracking verdict therefore carries an unavoidable margin of error, and in legal language that margin is called umpire's call.

The invisible line at fifty per cent

That line is written nowhere and never appears on screen. If the ball is projected to hit the stumps but less than half of it falls inside the stump zone, the decision stays with the on-field umpire. The logic is the centre of the ball versus its edge — half a sphere inside the stumps means the simulation is reliable enough. Anything less is too much pressure on an estimate.

The problem is that viewers never see that logic. They see the graphic of the ball's trajectory and the stumps. If it is roughly close, they assume out. Then when they hear "umpire's call", they think the umpire is suppressing evidence. What is actually happening is that the system is acknowledging its own error limit. This is my central observation: umpire's call is not an umpire's weakness, it is a declared error budget. A protocol that admits its own uncertainty is the most auditable protocol of all.

The referee's eye is a frame-by-frame threshold test, not a whistle. A whistle is an event; a threshold is a concept. And cricket expresses that concept far more openly than football.

UltraEdge and the blind spots of the spike

There is a subtler thing about UltraEdge, or snicko, which matters even more in catching reviews. A spike shows that a sound occurred, but what produced it — bat, pad, or ground? Because of frame rate and microphone placement, the three events often collapse onto the same time axis. The third umpire then has to go deeper into the frames to find visual contact — whether bat and ball genuinely came closest.

In my log, roughly a quarter of catch reviews produced a conflict between the UltraEdge spike and the visual frames. In that situation the real question is what constitutional basis exists for overturning an on-field decision on the strength of incomplete information.

The gap nobody watches: the incentive to retain a review

Now to the place where discussion is thinnest. Under the protocol, if a review ends in umpire's call, the reviewing team keeps it. That sounds fair — the team was not wrong, the system's uncertainty settled the decision. But the side effect is an incentive structure.

When I know that any close review will be returned to me at no cost, the risk of a medium-probability review on my batsman's behalf rises. The result: the marginal ball-tracking cases attract more reviews, and those are precisely the ones that end in umpire's call most often. The very threshold meant to increase transparency creates a selection effect — the sample of reviews is no longer the sample of natural on-field decisions.

That selection effect has no direct parallel in football. There, the VAR protocol is automatic; teams do not burn time requesting reviews, so team strategy matters less. Cricket's beauty lies exactly here — and so does its weakness.

The second thing I have carried over from football to cricket: cricket is not ashamed to publish its auditability. Ball-tracking graphics, spikes, replays — all appear on screen. Football kept its VAR conversations secret for years and only released audio under pressure. One lesson: transparency does not arrive under pressure, transparency has to be designed into the decision.

Person versus process: the viewer wants data, not emotion

Much of the criticism of Tim Paine's review management during the 2026 Ashes was the product of not knowing the protocol's boundaries. It is generally observable that those who wait three or four seconds before reviewing — the calm heads, like Kane Williamson or Virat Kohli — succeed more often. They are thinking about which gate the team will lose at, not merely checking whether the ball hit the pad.

That is what I wanted to measure in the log. If the reasoning behind each review were recorded, I could say which gate produces the most errors. That data does not exist yet, and that gap belongs to the audit, not to the game.

Looking ahead

The ICC has a clear opportunity in front of it — something football could not manage, cricket can. At the end of every tournament, a public review audit could be published: how many reviews, under which law, how many umpire's calls, average time, and which gate was overturned most. That would not reduce confidence; it would increase it.

Another proposal: burn a team's review even on an umpire's call verdict. It sounds harsh at first; within a season the quality of reviews would change.

Root: 2026 Kuala Lumpur incident log + INTJ pattern recognition | Scenario: introducing data-driven sports culture analysis. In that hard-drive folder from six years ago, two domains now sit side by side — football's VAR and cricket's DRS. Two streams of the same river, the same grammar of error. The question is no longer who is right and who is wrong — it is who is willing to publish the account of their own errors.

Russia — Root: 2026 Russia World Cup protocol audit | Scenario: exploring how high-stakes moments shift officiating standards. On the biggest stage, pressure does not move the threshold, but it shortens the patience needed to understand it — for players, for viewers, and sometimes for umpires too. That is the real game, and the real audit.

Methodology note: sources for this piece — ICC Playing Conditions, the LBW and review clauses; the ICC Cricket Committee recommendation to remove the soft signal (effective June 2026); the first application of DRS in the 2026 Colombo Test; the absence of DRS at the 2026 World Cup. The author's personal review log is first-person observation and not institutional data. Error level: low to medium.