Umpire's Call: The 3.6-Centimetre Band Was Never Written for Asia

September 10, 2026, Colombo. India versus Pakistan, Asia Cup Super Four, R. Premadasa Stadium. The most read document in world cricket that week was not a scorecard but a set of playing conditions — the Asian Cricket Council's file that kept a reserve day, but a reserve day written for exactly one fixture. If the rest of the tournament drowned in rain, points were shared. Only one match had an extra square on the calendar. I read that file three times. Not out of curiosity but out of habit. Seventeen years of this work has trained me to chase decisions backwards — who made it, under which clause, and who wrote the clause. The question that lodged itself was not about the reserve day. It was this: when a regulation is pre-built for a single anticipated scenario, it stops being a regulation and becomes back-filling for an expectation. Yet another number bothered me more that season, and it got far less attention. It sits around three and a half centimetres. Cricket calls it the umpire's call zone. It is also the quietest place where Asian cricket's favourite proverb — common sense — does its work. I have frozen that review frame by frame many times. I stop at the same place every time: the error was not in the pixel. It was in the premise. DRS arrived in 2026. Its first Test use came in the Sri Lanka-India series at the Sinhalese Sports Club in Colombo that July. From day one it carried two objectives — remove error, do not destroy the tempo of the game. Those two objectives work against each other. Protecting the second required a compromise with the first, and that compromise is called umpire's call. A review has three components. One: where the ball pitched, and whether that was outside leg. Two: where the ball struck the pad, and whether that was in line with the stumps. Three: whether the ball, had it not stopped, would have hit the stumps, and if so whether it would have struck them. The first two are questions of fact. The third is a question of prediction. Here is a fact that gets buried: umpire's call is not in the Laws of Cricket. The MCC's law book does not contain the phrase. It lives in playing conditions, in ball-tracking protocol, in umpire workshop notes. It is procedure, not law. And procedure is far easier to change than law — if anyone wants to. How is the band built? The wicket is 22.86 centimetres wide. A cricket ball measures 22.4 to 22.9 centimetres in circumference, which is a diameter of roughly 7.1 to 7.3 centimetres. Half a ball is therefore about 3.6 centimetres. The rule says: if the ball is projected to hit the stumps but less than half a ball's width falls inside the inner edge, the on-field decision stands. Roughly 16 per cent of the target area is a grey zone, and that grey zone has produced more argument in Asia than any other clause in the game. Hawk-Eye's tracking cameras capture at around 340 frames per second. Every frame up to the point of impact is measured. Everything beyond the point of impact is modelled — estimated, not measured. The margin of error lives inside that estimate. Asian resistance to DRS was never purely technological. There was politics in it, cost in it, and a legitimate suspicion: the technology was built and calibrated somewhere else, and so the unilateral power to overturn home umpires was being handed to whom, exactly? That suspicion was not baseless. But the question is different now. Asian spinners win matches through reviews, and the outcome of those reviews is settled by a fixed band that shows every sign of having been calibrated with a flat London pitch in mind. Two reviews per innings. Two more after 80 overs in Tests. Two per innings in ODIs and T20Is. Winning a review means trusting the ball-tracking. Losing one means a hope dies. For a Babar Azam or a Rohit Sharma that arithmetic becomes a career ledger. Nobody wants to look at the premise that ledger rests on. I am not talking about review outcomes. I am talking about the calculation that precedes them. That is where my objection sits. Take a leg-spinner. The ball lands in a footmark and turns eight to ten centimetres across the length of the pitch. The batter plays with the pad. The ball stops. The point of impact is perhaps more than two metres from the stumps. What does ball-tracking do? It takes everything measured up to impact and extrapolates forward. Two metres — roughly a tenth of the pitch — is pure inference. Now take a right-arm quick bowling a yorker. The ball hits the pad inside a metre and a half of the stumps. The extrapolation is short. Same law, same 3.6-centimetre band, but the uncertainty in the two situations is not the same. The rule operates with a constant; nature operates with a variable. Where does that asymmetry bite hardest? On Asian spin pitches. When Ravindra Jadeja or Ravichandran Ashwin bowls a fuller length, the impact point is frequently more than two metres from the stumps. The review then rests on a long projection, and the longer the projection, the wider the error envelope. The rule does not recognise that variation. The band stays the same — morning or afternoon, Multan or Melbourne, finger spin or wrist spin. Let me be precise, because people overclaim here: I have no evidence that Hawk-Eye or VMP ball-tracking measures wrongly. What is measurable, it measures finely. The problem is not in the measurement. It is in the projection — and more precisely, in a method that refuses to acknowledge the projection's own uncertainty. That leads to my second observation, less discussed and no less important. Two different standards operate inside one review, and the umpire is never asked to explain either. Standard one: conclusive evidence. To overturn a decision on pitching or impact you need clear, definite proof — usually something visible on replay. Standard two: projection. On the question of whether the ball would hit the stumps, the standard shifts without notice. Now conclusive evidence is not required. Inside 3.6 centimetres, the decision simply survives. Consider what that means. In one review the umpire plays judge. In the other he plays translator of data. The outcome then depends most heavily on the least reliable component — the estimate. In Asia that is unusually uncomfortable, because a large share of reviews here are projections off spin. When Kuldeep Yadav or Dunith Wellalage bowls, whether the ball will travel on to the stumps is far harder to model, because how much it turns off the surface depends on soil, humidity and the age of the ball. On a dusty pitch the deviation is large and unstable. Unstable input, static band — and the beneficiary of that equation is whoever is lucky, while the loser is the umpire. Now the third premise. Where the error is not in the pixel but in the decision taken before play began. That reserve day in Colombo. What I saw was not impropriety. It was impropriety in a polite, written form. A regulation was extended to save one match and not extended to save the rest of the tournament. An India-Pakistan fixture is not only cricket; it is an economic event — broadcast rights, audience figures, advertising obligations. The rule was not neutral in writing because it was never designed to be. A second example arrived in November 2026. The ODI World Cup final, November 19, at the Narendra Modi Stadium in Ahmedabad. Australia won by six wickets. The biggest question afterwards was not a fielding decision. It was the pitch: the final was played on the surface already used at the same venue for the India-Pakistan match on October 14. Reporting on the match referee's rating later indicated the surface did not earn a favourable assessment. The question is procedural, not diplomatic. The tournament's playing conditions grant the host board wide discretion in pitch selection. There is an ICC pitch consultant, there is a rating process — but by the time the process runs, the match is over. The only instrument for holding a pre-match decision to account is a report nobody reads and nothing changes. These belong to the same family. Reserve days, pitch selection, over rates, declarations, fielding conditions — all written in the language of playing conditions. And the preamble of playing conditions often defers to the Spirit of Cricket. Courtesy, understanding, the spirit of the game, common sense. Every word lovely. Every word vague. And vagueness carries a bonus: it cannot be appealed. Now the fourth angle, and here I have to speak from where I stand, because the inheritance is different and the vocabulary is not the same. In Dhaka I first learned the game's internal logic — how a wicket behaves, how light fades, what a wet outfield does, how a crowd presses. When I began working with rulebooks in Liverpool, the first realisation was that the same event is explained two ways in two languages. 'He took advantage' versus 'he arrived at an advantageous position'. The first is an allegation of intent. The second is a description of process. Every time an umpire or match referee reaches for common sense, a question forms: whose common sense? Common sense is not a neutral base. It is memory — memory of which game, which ground, which broadcast image. An official's common sense is shaped by the tempo and rhythm of the cricket he grew up watching. The rhythm of Asian cricket is different. When a match's fate rests on that vague interpretive difficulty, what is being done to the audience is the performance of the greatest possible confidence. I keep a small ledger. I call it the positioning log. Every week I note the matches where an umpire's position could have influenced a decision, and from which camera angle the evidence was clearest. The log tells me where the ball was not in frame, where the evidence was partial, and where it was pure estimate. Honestly: my log adjudicates nobody. It is an error map that delivers no verdicts. And that is the problem, because we now measure only where a human erred. We never measure where we asked a human to answer a question he was never meant to be able to answer. Jasprit Bumrah, Mohammed Siraj, Jadeja — all of them answer the same silent question. What if. Now the part where I disagree with the popular fix. Abolish umpire's call, the argument goes, and it is getting loud. The logic is simple: if technology can trace the ball's path precisely, why keep a grey band justified by human uncertainty? End it. Give every decision to the pixel. The emotion behind that demand is human. My conclusion is that it is the wrong remedy. The reason is procedural. Abolition moves authority one step further away — from a standing umpire into a closed program whose uncertainty limits nobody publishes. Today, if that greyest band did not exist, every marginal decision would go to review, with the outcome of matches settled by two millimetres on a line. There is something worse than 3.6 centimetres, and it is zero centimetres. One concession: the anger is justified. At the 2026 final, a spectator who bought a ticket, travelled, and sat for seven hours waiting for a trophy was not watching a paperwork issue. He was watching a promise broken. Whatever the fact sheet says, the game runs on human feeling, and disrespecting that feeling is not the same thing as getting a decision wrong. The final's pitch question was a genuine grievance, and it should be said plainly. But abolition is still the wrong road, because it moves the problem rather than solving it. My position is specific: keep umpire's call, but stop fixing the band. Where the projection distance is longer, the error margin is wider, and the band should widen with it. And the margin should be published. What would change my mind? If it could be shown that tracking error is practically constant regardless of projection distance, and that it is reliably measurable, then a fixed band becomes defensible. That is my falsification condition. On that day I will abandon my argument, gladly. Nobody has yet published per-projection accuracy data, and that absence is the real scandal. Football offers a lesson here. I still think about Japan versus Spain at Qatar 2026. The goal stood because semi-automated offside technology measured Kaoru Mitoma's cutback as 1.88 millimetres inside the line. I spent 72 hours building a three-dimensional reconstruction of it. The lesson was not the millimetre. The lesson was that football put a visualisation of an apparently impossible decision in front of a global audience. Everyone saw the evidence. Everyone was then free to be furious. Cricket does not. We get a snapshot, a beep, a verdict. The audience gets no error band, no sense of how much confidence sat inside that 3.6 centimetres. In a sport that distributes explanations at speed, there is no reason to hide the evidence. The hiding is the outrage. So what should be done? What should go before the cricket committee is not abolition but disclosure. Every projected ball-tracking path should display its margin. The band should stop being a constant and be indexed to projection distance and sample size. If a projection runs two metres, do not apply the same 3.6-centimetre protection as a yorker's half-metre; either widen the band, or mark the decision as genuinely uncertain, let the on-field call stand — and show the reason why. Asian boards should add their voice here, and not to demand abolition but transparency. Spin, dust, low bounce, slow surfaces are Asian cricket's identity. The more data accumulates, the more these hidden margins will surface. A technology that can predict a ball's future should stop hiding its own uncertainty. Finally, the question. How often have we said the technology is wrong, the umpire weak? Rarely do we ask who wrote the rule, and whether the sample it was written from was ever Asian enough. Until we know the answer, that three and a half centimetres will keep finding us — next series, next final, from two metres away, in exactly the same error.