Three Millimetres of Umpire's Call: How DRS Became Asia's Real Match Referee on Spin Pitches

The review log becomes an account of every moment the stadium holds its breath.

Over the last three seasons I have kept handwritten records of reviews at six Asian venues on spin-friendly pitches, and one pattern keeps returning: teams lose reviews not to a batsman's error but to three millimetres. The ball after the seventieth over grazes the inside edge of the stump; ball-tracking projects the point of impact fractionally below 50 percent of the stump's diameter. The on-field umpire said not out. His decision therefore stands, and the batting side burns a review. What happens in the remaining four balls of that over decides the match.

That evening I understood this as the least-discussed transfer of authority in cricket. The final decision is not being made by the man in the middle but by a projection model — and that model is governed by a 50 percent threshold.

What the Law says, what the protocol does

MCC Law 36.1 requires three conditions to be met together for LBW: the ball must pitch, the impact must be on the pad (where the ball did not first touch the bat), and the ball must be travelling on a path to hit the stumps. The Law contains no quantity. Quantity lives inside the DRS technical protocol, which is not the Law but the administrative mould for applying it.

The protocol is simple. If projection shows the ball hitting the stumps and impact on the line, the decision is overturned. But if the projection shows the ball striking a portion of the stump less than half the stump's diameter, that is umpire's call — the on-field decision survives while the review is spent.

Hawk-Eye cites a tracking tolerance of roughly 3.6 millimetres. The 50 percent line that generates so much argument sits in the immediate neighbourhood of measuring-instrument error. In 2026 the ICC Cricket Committee examined a proposal to remove umpire's call; in 2026 the committee retained it, reasoning that the cost of technological uncertainty should fall on the on-field decision, not on the batsman.

Two governing philosophies surface here. In England, on seaming conditions, the ball tends to enter the stumps near the middle — umpire's call is rare, under one percent of a season. On Asian spin pitches, the ball drifts and grazes the edge — model uncertainty peaks exactly where reviews are spent most heavily.

In November 2026, I started with 3,400 words because one handball deserved a full autopsy; that habit taught me that a single review decision in cricket deserves no less.

Rule, behaviour, outcome

First step, the rule. The 50 percent threshold confers a presumption in favour of the on-field call. The more experienced the umpire, the more finely that presumption works — his "out" becomes protected property.

Second step, behaviour. In Asia, bowlers operating from outside stump line and targeting the pads of left-handers — Ashwin, Jadeja, Shakib, Kushal Perera — treat umpire's call not as misfortune but as design. A batsman brings the pad forward to sweep or reverse-sweep; the ball grazes the edge; if the umpire raises the finger the review confirms it, and if not the review is gone. The bowler wins either way, because the batsman's risk is asymmetric — nothing gained if the call stands, everything handed to the bowler if it falls.

My notebooks show that a large share of failed reviews against spinners in the first 20 overs of a Test fail precisely on these edge-grazing projections. And a burned review costs more than a decision: for the next two hours the batsman plays a different calculation. Front-foot play shrinks, pad fear grows, and the slip cordon becomes the real bowling field.

Third step, outcome. When a side knows tracking will not give it unambiguous proof, review culture shifts. Keepers and captains of the mould of Mushfiqur Rahim and Virat Kohli stop leaning on television replays and start reading umpire body language. The percentage of decisions each umpire overturns becomes de facto scouting data.

The largest tactical shift I have observed is in the timing of reviews. Once a reaction to a severe blow, the review is now an asset, and mature sides spend it late — when one over and three wickets of liability remain.

Against the consensus

The consensus holds that umpire's call is a defect, an imperfection of technology, overdue for reform. My reading differs. Umpire's call is the only fence that keeps the question of technological sovereignty open. Drop the threshold to zero and the on-field umpire has no formal existence left; he survives only in the ledger of error.

Consider this: if a device accurate to 3.6 millimetres cannot be absolute truth, why was the 50 percent line drawn at all? Because rule-makers know ball-tracking is a model — pitch friction, seam position, air humidity are all calculation, and calculation carries uncertainty. In 2026 I wrote 60 pages for an empty season so the return would not be reckless; that taught me the Law cannot take the place of circumstance, only mark its boundary.

This is where the spectator's relationship with the rule strains. The viewer sees the ball kiss the stump — to the eye that is out; to the ledger that is uncertain. Emotion and governance will never speak the same language.

Rules are not walls. They are load-bearing beams, and I test every joint.

A dated prediction

I am filing a dated prediction. Within the next two seasons an Asian tournament will produce a formal proposal on umpire's call — either the threshold moves from 50 to 60 percent, or Test cricket expands the number of reviews per innings to admit openly the scale of the problem. The day the protocol states that the problem is technological, not human, cricket's administrators will have proved they chose reform over excuse.

— Root: Referee