The Umpire's Call Ledger: The Truth That Hides Between Two Frames

One image from last season is still stuck on the inside of my eyelids. Final session of the fourth day. The spinner released, the batsman pressed forward on to the pad, ball struck leg. The on-field umpire shook his head — not out. The fielding side did not hesitate for two seconds before sending it upstairs. The giant screen floated a ball-tracking projection: the ball was thudding into the leg stump, but not entirely — fractionally less than half. Two words appeared: Umpire's Call. Thirty thousand people roared at once, the batsman shook his head and stayed at the crease, and the umpire did not take his decision back. The scene is no less theatrical than a VAR argument in football, but the machinery underneath is completely different. In football, a human makes the decision and video merely supplies eyewitness testimony. In cricket, software forecasts the ball's future path, and then the umpire's original decision is stacked on top of that forecast. That is where the trouble lives. The question is no longer whether the call was right or wrong; the question is who exactly we are putting on trial, and under whose ledger. DRS arrived in Indian cricket in July 2026, at Colombo, in the India-Sri Lanka series. Then came a long political pause. In 2026 India stood against the technology in an ICC vote; in November 2026, during the home series against England, it accepted it in full. In those five years the argument was never technical — it was about trust. A board's trust, umpires' job security, and the fear of control migrating into a broadcast producer's hands. The rule needs stating plainly. For LBW, if ball-tracking predicts the ball would have hit the stumps, and more than half the ball would have struck, the decision is overturned. If less than half, the on-field call survives — that is Umpire's Call. There is a second condition: when impact occurs two and a half metres or more from the stumps, tracking's reliability drops, and that threshold enters the arithmetic too. Now look at the real crack. Hawk-Eye claims tracking accuracy of a few millimetres — in the company's own language, 3.6 millimetres. The Umpire's Call threshold, meanwhile, is half the width of the ball, roughly 35 to 36 millimetres. The band in which a decision flips is about ten times wider than the error the technology claims. Independent researchers have questioned that claim too — when a ball turns in the air, turns off the pitch, tracking error grows. This is where my work begins. I do not watch matches; I watch frames. Broadcast gives us roughly 50 frames a second. That means 20 milliseconds between frames. A ball travelling at 140 kilometres an hour covers about 78 centimetres in those 20 milliseconds. Suppose the actual contact between bat and ball happened exactly between two frames. The moment of contact exists in no frame at all. What we hold is one frame with the ball in front of the bat and the next with the ball behind it. Rewind the tape; the truth usually hides between two frames. That is precisely why the ICC abolished the soft signal in September 2026. Previously, for low catches, the on-field umpire gave a soft signal and the third umpire then hunted for evidence to overturn it. The flaw was procedural. Once a soft signal existed, the third umpire quietly loosened the standard of proof; instead of searching for evidence, he protected the decision. Now there is no decision without evidence, and that is correct. In my own ledger over the past three seasons I have charted 147 disputed catch and LBW reviews frame by frame — which camera angle produced the decision, which angle buried the event, how much the umpire's own positioning allowed him to see. One pattern returns again and again: in roughly one-third of cases the error was not in the technology but in the sightline. The truth lay where no camera had been placed. And this is where environment enters the ledger. Cricket's review infrastructure does not run on any country's rules; it runs on a broadcaster's budget. Melbourne has 340-frame ultra-motion cameras, Hot Spot, Snicko; Dhaka or a smaller venue sometimes has none of it, sometimes less of it. The same international match, the same laws, but two different standards of proof at two ends. The much-argued timed-out incident — 6 November 2026, Angelo Mathews dismissed — was correct in the application of the law, but the environment was a helmet strap and a shortage of time, and that environment is what turned it into a controversy. The second threshold is discussed even less, though a spinner's fate depends on it heavily. If impact is two and a half metres from the stumps, tracking's forecast loses confidence and the review threshold hardens. Yet that is exactly the distance from which a spinner loves to bowl, because it forces the batsman forward. The most cunning deliveries are therefore the weakest in evidence. Another shift is visible. Teams no longer review the incident; they review the umpire. There are only 15 seconds to send a review up, and in those 15 seconds the analyst's shout is heard more than the batsman's. Under Rohit Sharma, India's pattern of reviewing has become more calculating, more driven by a consultant's signal. The trouble is that this calculation measures probability, not truth — how close to the line, how far inside the half. So where a genuine error exists, teams fear wasting a review; where no error exists, they gamble on the arithmetic. Now the other side. The popular belief is that Umpire's Call means technology defeated and justice delayed. I disagree. Umpire's Call is not a defect; it is a deliberate rule. Its job is to divide power. If tracking were allowed the final word down to the last millimetre, the on-field umpire would cease to exist — an operator and an algorithm would remain. Cricket still does not want the outcome of a match arriving from a broadcast van. The half-ball threshold is therefore not the limit of the technology but the limit of authority. Here is the uncomfortable truth: making the technology more precise will not reduce controversy, it will increase it. New questions will arrive — at which millimetre did the ball pitch, where exactly was the fold in the grass, how much of the seam was scuffed. Even today, pitching and impact are disputed on plenty of deliveries. That will not diminish, because we will keep asking questions tracking cannot answer. There is a further discomfort. The review system is unequal between teams. A side with live feed at its analyst's elbow counts frames before reviewing; a side without reviews on emotion. In my ledger India's review success rate has fallen this season, but the cause is not a shortage of skill — the window is 15 seconds, and a rule guaranteeing every team's strategy consultant the same quality of broadcast feed still does not exist. From years of sitting in the Ambedkar Stadium press box as the only woman, the lesson I carry is this: the people in the box are not watching the events on the field, they are watching a version of the events on a screen. A referee's eye does not mean looking down from above; it means looking at that screen with suspicion. So where is the reform? Not in claims of technological precision, but in equality of infrastructure and transparency of the ledger. Publish every venue's camera list before the match. Declare the tracking error band in advance. And instead of that 15-second review window, guarantee a minimum standard of frame handling at every venue. Next season, when the words Umpire's Call float on to the screen again and the gallery roars as one, ask yourself a question. Did we see the truth, or did we hand someone the job of finding it for us somewhere between the two frames we happen to hold?