Millimetres of Umpire's Call: DRS Review Arithmetic, the Data of Silence, and the Dark Corner of Broadcast Capital

The sixteenth over of a T20 match in 2026. A left-arm spinner's delivery thuds into the batter's pad, the fielding side screams, the umpire shakes his head — not out. The captain reviews. The green dots of ball-tracking clip the inside edge of the stumps and slide away — umpire's call, decision unchanged, the review burned. Next over, same bowler, almost the same length, another appeal, another review, another umpire's call. Two reviews gone in two overs; the captain's hands are effectively tied for the remaining fourteen.

My laptop has two tabs open — a live stream, and an empty spreadsheet. Four columns: timestamp, review number, final decision, and the seconds between appeal and the third umpire's signal. What the scoreboard never shows is the real match. Neither review that night succeeded, because in both the ball struck less than half the stumps. Not out, and not out — the most uncomfortable truth of modern cricket.

The spreadsheet was my first whistle. In November 2026, sitting in the canteen of a Rajshahi coaching centre, I logged all 41 reviews of the Bangladesh Premier League one by one — ball-tracking frame, whether it was umpire's call, the seconds between appeal and signal, and which umpire was overruled. Before the final I posted that table on a page I called Third Umpire Notes. My first authority came from a column of numbers, not an opinion.

DRS arrived in cricket in 2026, at Colombo's SSC ground in a Sri Lanka-India Test. There was scepticism at first, then it slowly became inseparable from the game. Under the playing conditions, teams get two reviews per innings in Tests, and one per innings in ODIs and T20Is. The process is not complicated, but the outcome is brutal: ball-tracking shows where the ball pitched, where it struck, and its predicted path to the stumps; UltraEdge shows whether the bat's edge was touched. The question remains in one place only — how much of the ball hit the stumps.

That is where umpire's call is born. If more than half the ball strikes the stumps, it is clearly out or clearly not out; but if less than half, the decision on screen stays with the on-field umpire. Same delivery, same ball-tracking, but the call shifts on the earlier nod of a man in the middle. Two reviews in Tests make the risk tolerable, but in T20Is there is only one — and that is the captain's biggest gamble.

From a hostel room, logging a World Cup one frame at a time, the habit has never left me. Even then I learned that a review is never a moment — it is a timeline: appeal, wait, replay, wait, signal. A writer who cannot write that timeline cannot really write about umpiring.

Umpire's call is not a weakness; it is a tolerance band. When the third umpire draws a predicted path across several ball-tracking frames, every point carries its own error margin — camera frame rate, the ball's spin, friction on the pitch. When the ball clips half the stumps, that is not scientific certainty; it is science's polite way of admitting uncertainty. Those raised on millimetres and frame rates know a machine can say almost, never certain.

The trouble lies elsewhere. When a captain reviews, he cannot see ball-tracking; he sees an emotion and a scoreboard. The review becomes a strategic resource, and most teams spend it at the worst moment. In my 2026 table a pattern was clear: the success rate of reviews taken in the first six overs was far lower than in the last six. The reason is simple — early on the ball is new, impact is obvious, the umpire is alert; late on the ball is old, the pitch is slow, the umpire is tired.

The World Cup review data reveals something else: umpire's call is not the captain's mistake, it is the system's design. The ICC could have removed the threshold — given it out even when less than half struck. But then the on-field umpire would become irrelevant. The balance of power between live umpiring and technology hides inside umpire's call. It is incomplete, but deliberately so.

The same philosophy governs UltraEdge and Real-Time Snicko. If the bat's edge produces a faint spike on the microphone, is that proof or probability? Wind, pad friction, even a ball passing close to the stumps create a small sound. So the spike's height and timing must be read together. When the machine offers probability rather than proof, the burden of decision returns to human shoulders.

And this design pulls me toward an odd idea. Every review in cricket is really a ledger entry — timestamp, frame, decision, who requested it. If those entries were written to an immutable public ledger, after every match we could say: how often this umpire was overruled this series, where ball-tracking and UltraEdge contradicted each other. Blockchain's real use is not in crypto, but in cricket's silent log. When an umpiring decision is immutably written down, the room for secrecy and convenience shrinks.

It may sound perverse, but a third umpire's decision is sometimes seen by more people than the stadium holds. And the stranger thing — the longer the wait from appeal to signal, the louder the crowd. An empty stadium taught me that silence has a data trail: the whistle's tone, the gap in the crowd, those few seconds before the signal — all the acoustics of a decision. In the behind-closed-doors matches of 2026 I counted those seconds off the microphone, because there was no crowd roar — only the machine's waiting.

Here is the biggest conflict. The crowd wants emotion, the rule wants millimetres. When ball-tracking says the ball struck a third of the stump, the gallery roars about injustice — yet the rule said exactly what it always said. To the human mind, almost out and out are the same thing, but in the playing conditions there is a half-ball-wide gap between them. We refuse to admit that gap, so we blame the machine.

And that emotion is the biggest product. Here comes the money. The company that builds ball-tracking and UltraEdge is owned by the same commercial group that holds the game's broadcast rights. The same entity shows the match and supplies the technology for its decisions. This is no conspiracy; it is a structure — and structure means the possibility of interest. The more cricket's broadcast rights have cost, the more the review controversy has been worth, because controversy means debate, debate means views, views mean advertising. A system that manufactures controversy also sells it.

In my view the broadcast-rights bubble is now at its peak. Platforms losing money buying cricket rights are repeating television's old mistake — assuming a higher price means more viewers. Real audiences grow from transparency of decisions, not from controversy. If every review sat on an open ledger, if the umpire's call threshold and ball-tracking's error margins were public, views would grow from understanding.

Just as every transfer rumour needs a timestamp and a source, every review controversy needs a frame number and seconds. Umpire was wrong is easy to write; ball-tracking frame 47, prediction uncertainty 3.6 millimetres, on-field decision stands is hard to write. The second sentence is my profession.

In the next five years, review management will become a distinct skill in cricket — coaches will hire review analysts, just as they now hire match-up analysts. The umpire's call threshold may change; ball-tracking's uncertainty may begin to be shown live. But as long as a human decides between appeal and signal, millimetres and milliseconds will remain the final judge. The question is genuinely simple: do we want a game where every decision has a timestamp — or do we prefer the controversy, because controversy is fun to watch?