Umpire's Call: Who Actually Draws the Grey Line of DRS?

August 2026, the fourth day of the third Ashes Test at Headingley. In a ten-by-twelve-foot room in Mymensingh I was running the footage at 50 frames per second — the six frames after Nathan Lyon's ball struck Ben Stokes' pad. The on-field umpire said not out. Australia had no reviews left; they had spent them earlier. The gap between what ball-tracking showed and what was announced on the field became, that night, the most expensive grey line in cricket. I began with one bedroom, one rulebook, and a suspicion the table was lying. Seven years later that suspicion has moved from football's VAR to cricket's DRS, and the question is identical — who owns the decision, the technology or the human? DRS was first used in Test cricket on 23 July 2026, at the Sinhalese Sports Club in Colombo, in the Sri Lanka–India Test. The expectation was that errors would fall. Eighteen years on, the ledger is mixed. DRS is not merely a technology; it is an administrative procedure containing MCC Law 36, the ICC playing conditions, a quota of one or two reviews, and a broadcaster's ball-tracking model. Cost keeps full DRS out of many bilateral series. Several home series involving Bangladesh or Sri Lanka have been played without ball-tracking at all; there a player's only recourse against an umpire's decision is a raised arm and a helpless appeal. Two teams operating under one law therefore receive access to different quantities of truth. That inequality, not umpire's call, is the real weakness of DRS. Umpire's call is structured as a decision tree. For LBW there are three branches: where the ball pitched, where it struck the pad, and whether it would have hit the stumps. On the first two branches the on-field decision changes only when tracking speaks unmistakably. On the third there is a defined tolerance band — if the projected contact with the stumps falls inside less than half the ball's diameter, it is umpire's call: the field decision stands and the review is retained. That half-diameter line is not written in any law book. It is a setting inside the tracking model, and it is set by the technology vendor, not by the lawmaker. This is where my objection sits. The law says the umpire decides on what he sees; technology offers a correction when it disagrees. But if the tolerance band belongs to the technology, then in practice the on-field umpire is either protected or wounded by a vendor's configuration — and the difference between those two states can be two pixels. In my own log I recorded 134 reviews frame by frame across 48 matches of the 2026 ODI World Cup. Forty-four of them ended as umpire's call: the technology saw something and changed nothing. Of those forty-four, eighteen involved contact with the stumps at a margin narrower than one centimetre. One centimetre — that is the most contested distance in modern cricket. The review quota is an economy too. Two in Tests, one in limited-overs cricket — that number determines when a captain gambles. Australia had burned their reviews at Headingley, so on the sixty-something that struck Stokes' pad and was heading for the stumps, no review existed. Some will call that poor team management; I call it a systemic fault, because the system has tied the quality of a decision to a quota. A correct umpiring outcome should survive on the position of the ball, not on a team's remaining balance. The quota has an unspoken effect as well — umpires know how often their decisions actually get overturned. In my football ledger, of 455 VAR checks only twenty became on-field reviews, and seventeen decisions were reversed. Cricket runs the other way: reviews are taken far more often and succeed far less. In my 2026 World Cup log roughly six of every ten reviews failed, meaning the original decision stood. That suggests captains are reviewing on instinct, with no data behind them — teams do not keep public ball-tracking histories for their own or opposing batters, or if they do, those files sit in an analyst's private workbook. Now the counter-argument that critics of DRS usually skip. Suppose umpire's call is abolished tomorrow and a ball clipping the stumps by a millimetre is given out. Will controversy fall? No. It will move to the calibration of the tracking model, the frame rate, the inference of seam trajectory, the friction model of the pitch. Where the argument is currently about an umpire's eyesight, it will become an argument about the mathematics of Hawk-Eye or Virtual Eye — and that is less transparent and less verifiable. The problem is not technological perfection; the problem is who owns it, who inspects it, and who can audit it. Nobody publishes the error margin of ball-tracking. The document showing where uncertainty lives never reaches the spectator. When the stadiums emptied, the numbers finally spoke without the crowd. After the 2026 lockdown I tracked 306 matches — fouls fell, and the home-win rate dropped from 43.2 to 38.1 per cent. What emerged? A decision is not only a matter of eyesight but of environment. Even after DRS arrived in cricket, home advantage never fully disappeared — because the tracking model is the same everywhere while pitch reports, weather and crowd pressure are not. A system built to reduce error has now produced a new inequality: teams in series with DRS and teams without it are playing under one law in two different truths. I do not count the points until I have audited the cells beneath them. Three things are needed, all documentary. First, before every series, the error margin and tolerance configuration of the ball-tracking system should be published. Second, and more important, minimum camera and tracking standards should be mandatory in every bilateral series, so DRS stops being a rich board's luxury. Third, every review log — which frame, which angle, what the model showed — should be recorded and released, so an outsider like me can verify it and the procedure stops being grey. The Russia ledger taught me that memory is a spreadsheet with redactions. Cricket's DRS needs an account of those redacted cells. Next season, when a review dies on half a centimetre, the spectator will ask: who drew the half-diameter line? If the answer is 'the model', then humans are not playing this game — software is. And if the boundary of the law drifts into software, the referee's eye no longer owns its own decision. It becomes a translator of settings. — Root: Referee