Umpire's Call: Cricket's Last Inviolable Fortress, or a Protocol for Avoiding Liability?

At Mirpur, the second session of the third day of a Test. The 47th over. A leg-spinner releases the ball fractionally flatter, the batsman is trapped on the front foot, the ball hits the pad. The on-field umpire does not raise the finger — not out. The captain at slip waits two seconds and signals the review. On the third umpire’s screen the ball-tracking loops: pitch profile, impact point, then the projection. A line flickers up — the projected ball’s centre has brushed the outside edge of the stump, but the whole ball has not entered. The decision stands. The review is gone. The captain has no review left. On the big screen the words ‘Umpire’s Call’ drift across the grass. The batsman stays; the bowler walks back to the top of his mark with his head down. To two million people in the ground this is a defeat, not a victory — it is the victory of a process. I have stopped that frame and replayed it many times, because those few millimetres produced the most contested rule in cricket’s last decade. DRS was never merely technology. In 2026, in the Test series between India and Sri Lanka, the Player Review System entered international cricket, and from its first day it posed a legal question — who owns the final decision, the man standing at the bowler’s end or the man sitting behind the cameras? After the 2026 World Cup, the ICC gradually made DRS mandatory across bilateral series, and every member board’s consent note reads slightly differently. In the early years India refused the system outright; their argument was that ball-tracking software could not measure the point of pitching and the friction off the surface with sufficient accuracy. That objection is now obsolete, but the question buried inside it is still alive — who bears the liability for the technology’s error? The ICC playing conditions make the DRS protocol ask three questions. One, can ball-tracking prove the ball would have hit the stumps? Two, what is the standard of proof — ‘probably’ or ‘conclusively’? Three, if the standard of proof leaves doubt, which side gets the benefit? The answer to the third question is ‘Umpire’s Call’. The rule runs like this — if the wicket projection predicts the ball will strike the stumps, and the centre of the ball falls less than half a ball’s width inside the outer edge of the stump, it is treated as Umpire’s Call and the on-field decision stands. The machine is saying ‘it would have hit’, but the machine’s own certainty is not sufficient — so the human wins. In my own compiled notes, this protocol has a strange quality that almost never surfaces in cricket commentary. The rule is not written in the language of advantage and disadvantage for players. It is written in the language of the standard of proof. Umpire’s Call is in fact a judicial concept — the benefit of the doubt to the accused. Only here the batsman is the accused and the on-field umpire is the judge. And this judicial resemblance is not mere metaphor; the playing conditions use precisely this vocabulary — ‘insufficient evidence’, ‘benefit of doubt’, ‘not conclusive’. This is where I stop. Because I froze the first VAR penalty of 2026 until it became a legal precedent. On 16 June 2026, France versus Australia, referee Andrés Cunha reviewed Josh Risdon’s handball and awarded the first VAR penalty in World Cup history; Griezmann scored, France won 2-1. The real significance of that penalty was not on the scoreboard but in the IFAB protocol’s phrase ‘clear and obvious error’. Football drew a boundary there — technology intervenes only when the referee’s error is sufficiently plain. Cricket has drawn the opposite boundary — the burden of overturning the on-field decision sits on the technology, yet cricket has never issued a declaration of the technology’s own accuracy. Based on my years of watching matches, I can say that the ordinary spectator learns what Umpire’s Call means precisely when their own team is harmed by it. At the 2026 Ashes it appeared in another form — after Steve Smith was struck on the head, Marnus Labuschagne was brought on as a concussion replacement, and within months the question arose whether the mechanism was being used according to match situation. That was when I understood that technology and protocol are not the same thing. A protocol is a rule written by people; technology is merely one doorway into that rule. Why half a ball, and not the whole ball? I have chased this question for three years, and the honest answer is that its basis is not physics but metrology. The margin of error of a ball-tracking system lives inside camera frame-rate, ball rotation, and the estimate of surface friction over the final few metres. The semi-automated offside technology that football deployed in Qatar in 2026 announced a tolerance of 3.5 millimetres, and that is exactly the same line of thinking — the system declares its own silence, and within that silence the human or on-field decision is treated as truth. Cricket’s half-ball threshold is the product of the same logic. But this is where the asymmetry begins. There is no such threshold for the line of the stumps — if any part of the ball, even a millimetre, is heading towards the wicket, it counts as ‘hitting wickets’. Because the line is a line, and the wicket is a boundary. Crossing a line is a black-and-white decision; the degree to which a ball strikes a stump is a spectrum. One question is left in doubt, the other is declared as certain truth. That inequality is the rule’s greatest weakness, and it almost never enters the full debate. I watched the real shape of this problem in another sport at the 2026 Qatar World Cup. On 22 November, Argentina versus Saudi Arabia, three Argentine goals were disallowed in the first half because semi-automated technology was working to a 3.5-millimetre boundary. I built frame-by-frame models of Lautaro Martínez’s shoulder and Messi’s knee purely to understand Law 11 and FIFA’s calibration rules. The result of the match — Saudi Arabia won 2-1 — I set aside. Because football proved that day that technology does not make decisions; technology only draws the boundary of a decision. In cricket, the task of drawing that boundary falls to a human being called the third umpire. And this is my central observation: DRS does not fail, DRS is not allowed to fail. Error is traditionally loaded onto the machine, but has the machine ever said it was certain? The ball-tracking interface reads ‘Predicting’, not ‘Predicted’. That is a prediction, not a truth. Yet on the scoreboard that prediction ultimately carries legal weight. Now to the part where the game becomes law. In my own data table I have kept review outcomes separate for every major tournament since 2026 — who takes how many reviews, on what kind of delivery, in which over, and in what session situation. The pattern is clear. On slow, low pitches, where the prediction of the ball’s height and rotation is least certain, the greatest number of reviews are lost to Umpire’s Call. On pace-and-bounce pitches, where the ball’s trajectory advances along a comparatively straight line, the machine’s prediction is far more confident. In other words, the rate at which reviews are lost to Umpire’s Call relates more to the nature of the pitch than to a team’s batting or bowling skill. That is a structural inequality. In the subcontinent, where slow, spin-friendly pitches are prepared, the consequence of a home captain taking the same review differs from that of a captain standing on another ground — and it depends on the pitch curator, not on the captain’s judgement. This structural inequality matters most because Umpire’s Call gives batsmen a safe harbour. ‘If it cannot be known, the decision does not change’ — in practice that converts uncertain evidence into not out. And on slow pitches the prediction is least certain, so off-spinners and left-arm spinners suffer most. If anyone wants to claim the rule is neutral, they must explain why its sensitivity to pitch type varies so widely. How much, literally, is half a ball? Three stumps set together are roughly 22.86 centimetres wide, and a cricket ball is about 7.2 centimetres in diameter. So the half-ball threshold is a corridor of roughly 3.6 centimetres. From the stands that corridor is invisible. The ball-tracking replay shown on television is not the whole truth, because it is a two-dimensional translation of a three-dimensional estimate. The ball the spectator sees is not actually turning; it is calculated. I learned to read a foul as a fact pattern, not a moral story. In the same way I learned that it is meaningless to call a cricket review fair or unfair unless we first decide that the question is one of the standard of proof. Then comes the second question — once we accept the standard of proof, ornament falls away from the game and the game becomes only the application of rules. This is where I think the ICC has still not decided which game it is running — an entertainment that wants dramatic decisions, or a law that wants consistency of decisions. Look now at football’s law. Studying UEFA’s disciplinary articles and the mindset of referees, one thing always strikes me — in IFAB the ‘clear and obvious’ threshold fundamentally protects the interests of management. The VAR protocol openly concedes that technology can err, and in that case liability does not fall on ‘both’; rather the system is in theory indemnified and authority is restored to the on-field decision. Cricket does exactly the same work through Umpire’s Call, but with a more precise technique. In football the referee must admit ‘I did not see it in the frame’; in cricket the umpire can say ‘I merely fixed the limit of the machine’s error’. Here lies my strongest objection, and it has nothing to do with any one team or board. The technology that is used competitively contains data on the ball’s trajectory, the point of impact and the certainty of the wicket — yet the third umpire’s screen does not display that data alongside the ‘out’ or ‘not out’ verdict. The team receives a decision but not a reason. And in any legal process, a decision without reasons is not accepted. This is where Manchester City becomes useful. On 13 July 2026, during the global sporting hiatus, the Court of Arbitration for Sport overturned Manchester City’s two-year European ban and reduced the fine from €30 million to €10 million. I read the 93-page award, especially two sections — how admissible the leaked emails were as evidence, and how ‘disguised equity funding’ was inadequately defined. And the announcement came on an evening when the grounds were empty, and I only wondered: who does exactly this work in cricket? Who will say whether a board’s revenue-distribution model is fair? Who will say under which law a franchise’s decision not to release a player to a draft or trade is justiciable? When will cricket have a permanent and accessible tribunal? The ICC’s revenue model is the example. At the ICC Annual Conference in 2026, a distribution model was approved for the four-year cycle out of roughly 600 million US dollars of annual revenue, in which the share of the large boards is conspicuously larger and the share of associate members comparatively limited. This is not merely politics; it is structural development policy. And it shapes which boards can afford the technology, the medical staff and the legal departments that modern cricket demands. The duty-of-care chain follows the same architecture. I traced the Eriksen collapse from emergency to legal duty. On 12 June 2026, Christian Eriksen collapsed in the 43rd minute of Denmark versus Finland; I analysed UEFA’s medical emergency protocols and the legal duty of care that permitted the match to resume. Then on 11 July 2026, after Italy beat England in the Euro final, UEFA charged England under Article 16 for crowd disorder at Wembley. I compared both cases in a 5,000-word essay, because they expose the same question from two directions — who owed what to whom, and when? Cricket has its own version of that chain. Concussion replacements, heat protocols, air quality, the safety of a batsman facing a bouncer after a helmet change, the medical clearance of a fast bowler returning from a stress fracture — each of these is a duty-of-care question dressed as a playing condition. When a concussion replacement is approved, who is legally responsible if the protocol is gamed? The match referee, the team physician, the board, or the ICC? My answer, after years of reading disciplinary codes from both sports, is that cricket has built an accountability vacuum and filled it with procedure. Procedure is not accountability; procedure is the appearance of accountability. Umpire’s Call is the purest expression of that — it is a beautiful procedure that quietly relocates responsibility away from every human being involved. And here is the contrarian turn. The intuitive reform is to abolish Umpire’s Call — let the ball-tracking verdict stand, let the machine speak. I tested that inversion against the documents, and it fails. Abolishing Umpire’s Call does not increase justice; it relocates error. The prediction error does not disappear when you remove the threshold; it merely becomes invisible and unappealable. At least under Umpire’s Call the uncertainty is declared. Remove it and you get a system that claims certainty it does not have, which is the precise failure mode that football’s ‘clear and obvious’ language was invented to avoid. The real problem is not the threshold. The real problem is that the threshold is the only thing published. Cricket publishes the boundary of its doubt but not the evidence within it. A visible, reasoned, auditable decision — with the projection data, the margin of error and the confidence interval displayed to both teams and to the broadcast — would do more for legitimacy than any change to the half-ball rule. That is also how you separate a bad decision from a breach of duty. A wrong Umpire’s Call is a bad decision. A system that hides its own error bars while punishing players for reviewing is a breach of duty. Cricket has spent a decade arguing about the first and ignoring the second. The next reform will not come from the field. It will come from broadcast rights, player welfare cases and the quiet spread of sports-law jurisprudence into cricket’s disciplinary chambers. When the first serious challenge is filed over review data transparency, Umpire’s Call will not be defended as physics. It will be defended as policy. And the question the tribunal will ask is the one nobody in the commentary box wants to answer: if the game knows its own margin of error, why does it refuse to publish it?