Half a Ball of Umpire's Call: The DRS Review Ledger Nobody Keeps

The ball-tracking projection builds slowly on the big screen, stretching across nearly two and a half seconds. The ball holds the stump line and turns in, but not through the middle — it grazes the leg stump, almost the edge of it. Two lines surface on the screen: 'Impact in line,' and 'Wickets — Umpire's Call.' Twenty-seven thousand people in the ground make a single sound with no language but an unmistakable meaning: we have been robbed.

I logged that entry. I did not write down the batter's name or the match score; I wrote the category. For me DRS has never been a story about one batter's bad luck. It is a ledger. Batters change, scores change, tournaments change, and the projection lands in almost the same place every time.

The habit comes from football. In officiating-data work I used to time the lag between whistle and foul and put it in a notebook — across closed-door recordings the median was one point four seconds. Cricket changed that ledger's vocabulary. Here the unresolved question is not delay but boundary: how much of the ball must enter the stumps for it to be contact, and how much makes it only a probability.

The ICC's 2026 Playing Conditions state that if less than 50 per cent of the projected ball is hitting the stumps, the on-field umpire's decision stands. There is another, less-discussed clause: if the point of impact is more than three metres from the stumps, ball-tracking's projection is treated as unreliable and the call again reverts to the umpire. The technology is not answering here; it is declaring its own limits.

History matters. Ball-tracking first reached cricket broadcasts in 2026 in England. DRS took the field in 2026, in the India–Sri Lanka Test series. What began as a television luxury is now a strategic asset rationed by a review count: two per team per innings in Tests and ODIs, retained on success, with T20 internationals moving to two from 2026. The arithmetic is simple. A review is currency, and a wrong review is expenditure.

The Asian context sharpens that expenditure. Subcontinental pitches take less bounce, spinners attack the stumps, and umpires have historically been quicker to raise a finger on front-foot LBWs. Put those three conditions together and Umpire's Call naturally multiplies. The side that hits the stumps hardest runs into Umpire's Call most often — and that same side carries the highest risk of burning reviews.

The biggest error is not the technology's. It is the protocol for asking for a review.

I sort reviews into eleven categories, the same way I once tagged every penalty-box fall and offside flag. The buckets are these: leg-stump projection, impact outside, three-metre-plus impact, inside edge, glove or catch, ball pitching outside, pad-first disputes, high full toss, stretching catch, boundary-saving referral, and catch-behind disputes.

The ledger says the first two categories absorb the most reviews and lose the most. The reason is mathematical. On leg-stump projection the ball's path does not run through the centre of the stumps but grazes the edge; judged in millimetres, it can dip below the 50 per cent threshold and the decision survives. Batter and bowler both know the ball was going on; the machine knows it too. The question is not where it was going but how much of it was going there. That gap keeps the noise in the ground permanently separated from the arithmetic of the law.

The second observation is more uncomfortable. Who actually decides to review? Usually whoever is closest: the bowler and the wicketkeeper. The bowler's angle is emotional — he always imagines his own delivery holding the line. The keeper's angle is better but his eye is trapped between pad and glove, not on stump height. The captain at mid-off or cover has fifteen seconds and several voices. If a side does not know its own success rate by category in those fifteen seconds, the decision is not analysis. It is a vote.

A team that does not know its own bowling map does not know its own review ledger.

The ledger catches something else the broadcast almost never mentions. Sides bowling fuller, stump-to-stump, win more reviews and lose more reviews, because the same delivery that yields an LBW one day returns as Umpire's Call the next. Sides bowling wide of off see fewer reviews because their doubt usually dies at impact outside. Review conversion is therefore largely a bowling philosophy in disguise. This is a story about craft, not luck.

When the words 'Umpire's Call' flash on screen, the viewer reads a technology failure. My ledger reads something else. The technology is doing exactly what the law instructs. The failure is communicative: the screen shows the label and not the number. Had it read 'ball 41 per cent on stumps,' the roar in the ground would likely have sounded different.

Now the part many will not accept. Umpire's Call is not technological incompleteness; it is deliberate humility. When someone argues that in the age of technology half a ball on the stumps should mean out, they are asking the machine for a certainty the projection does not contain. Remove the uncertainties of frame rate, seam movement and pitch wear, and ruling on the sub-50 per cent margin means deciding on guesswork. The law has chosen to stay behind that guess.

When I held that argument against the ledger, my own framework broke. I had assumed the problem was an institutional instinct to protect umpires. It turned out to be resource allocation: two reviews to cover an entire match, and who asks for them is decided in the team room. A side without a dedicated analyst is effectively playing on instinct. This is where the smaller Asian markets fall behind structurally — a wider gap than fitness or technique.

The ledger's limits deserve stating before any of this hardens into a claim. My log covers a stretch of Dhaka matches and four Asia-level events, a few hundred review entries — not an official dataset but one person's hand-built classification. What a captain was thinking behind a review is not in my notebook. Decisions taken inside the room are invisible to my ledger.

One more layer exists that television never shows. Review data travels into live feeds, and from there into markets. The temptation to sell a play-by-play probability on what the umpire will decide is obvious, and it is better left undescribed. Follow that thread and the conversation leaves the Laws of the Game and ends up at a betting counter, which is no longer cricket writing.

So what is the fix? Nothing exciting. First, place the review call with one person — a review captain who feeds the captain, not a committee. Second, before the match, map stump-line and length against historical review conversion, so the geometry of the 50 per cent threshold is rehearsed rather than remembered. Third, publish the number on the screen, 41 per cent or 53 per cent, because hiding the figure thickens resentment without reducing bias.

And fourth, keep a ledger of your own. The history of cricket's technological turn is a history of systems moving from hesitation toward precision, from the 2026 broadcast experiment to fully automated tracking. Audit the pattern before the next tournament starts, and score your own calls afterwards. The question that remains is not who was robbed. It is whether a review will still be a verdict, or finally a measurement.