Umpire's Call: How the Review Ledger Exposes a Team's Decision Culture

The screen flashes two words — Umpire's Call. Twenty thousand people in the stands read it in a different language. To them it is not geometry, it is a verdict on honesty. The big screen shifts, the lights dip, and the colleague in the next seat whispers: “It was that close. That should have been out.”

I have watched this same moment for fifteen years. In 2026, at Colombo's Premadasa Stadium, the Player Review System was used in a Test match for the first time. Nobody in the press box that day realised the technology would not merely settle out-or-not-out; it would begin tracking people as well.

My interest sits elsewhere. It sits on the decision itself — how a human being reaches a verdict in fifteen seconds, inside twenty thousand voices, between the keeper's plea and the bowler's shout. After the match, everyone picks up the scorecard. I pick up the ledger.

Let the tape finish before the verdict writes itself.

The phrase “Umpire's Call” needs unpacking first, because Bengali commentary has never settled on a translation, and that untranslated gap is exactly where most of the confusion is born. In an LBW review, ball-tracking asks three questions — did the ball pitch in line, did it strike the pad in line with the stumps, and would it have gone on to hit. The first two stages are mechanical: no prediction, only record. The third stage is the problem, because the ball has not yet reached the stumps. The tracking is estimating.

The laws say that estimate needs a margin before it can be fully trusted. If the projection shows the ball going on to hit, but less than half the ball was inside the line of the stumps at the point of impact, the on-field umpire's decision stands. To overturn a call on the field, the evidence has to be beyond doubt. That margin is what we call Umpire's Call.

In any Test or ODI, each side gets a fixed number of unsuccessful reviews per innings before it loses the right to challenge at all. So a review is not only a court of appeal; a review is an asset — finite, exhaustible, worth preserving for the length of an innings. I see a review the way I see a batter's wicket: spent once, never returned. Where a team spends it tells you how conscious that team is.

That is where my ledger begins. For nine years I have kept every match as a row — which over the review came in, who called it, what kind of delivery it was, how many seconds it took, and what the outcome was. More than four thousand rows. Honestly, my interest in this ledger is less about cricket than about human behaviour.

In 2026, covering the VAR World Cup in Russia, I learned that statistics are not a mirror but a confession. That tournament I logged all twenty-nine reviews and found handball to be the least consistent category. I brought that lesson back to cricket and reached a conclusion: a process reveals less through its success rate than through the timing of its failures. When someone burns their first review in the tenth over, that is an admission of emotion. When someone hoards it until the final over, that is an admission of arithmetic. Both are data.

Domestic cricket is the biggest mirror here. Across eight different assignments I have sat at Mirpur, in Dhaka club grounds, and on the outfield of the National Cricket League. There is no live ball-tracking, no live Umpire's Call, and an over does not take fifteen minutes because a broadcast is replaying angles. In Dhaka league cricket I still watch a wicketkeeper appeal, then stand still at his mark, because there is no structure in front of him for taking the evidence apart.

That unpreparedness is Bangladesh's real deficit, not a deficit of technology. A player who has never rehearsed a formal review decision before arriving in international cricket will, in those fifteen seconds, hear instinct instead of process. What our keeper or slip fielder does at national level is not a reflex learned in childhood; it is guesswork.

Under Najmul Hossain Shanto, a large share of Bangladesh's reviews have been for LBW, and within that, a large share on front-foot play. That pattern is normal for South Asia. Wickets are lower, batters press forward, ball meets pad more often, so doubt multiplies. But doubt alone cannot produce a review.

The first replay is the biggest liar in the building. The broadcast shows the tracker first — where the ball went, how far inside the line, and finally the red circle. The viewer takes this as the complete testimony. Yet the real basis of the decision was laid before the ball was even released: the bowler's release point, the batter's stance on the crease, the keeper's position and the height of his gloves. Those sit in the frame behind the camera and never return in the replay.

Every angle confesses something the first replay hid. On the stump mic, a dozen voices surface in those fifteen seconds — the keeper's “definitely front pad,” slip's “no, no, it's going down,” the bowler saying nothing, and the captain's long silence. The voice you hear least carries the real information.

This is worth pushing further. In 2026 the stadiums emptied, and that emptiness gave me an opportunity twenty years of full houses had never offered. Analysing the audio of forty closed-door matches, I found that officials took an average of seven to nine seconds to arrive at a decision, and that delay was not fear — it was verification. Nobody shouts in an empty ground, so the decision-making process becomes audible. Silence in an empty stadium can be louder than a crowd.

Cricket never had that silence in full, but a small version arrived. In pandemic-era series without crowds, the conversation in the umpires' box became clearly audible, and it revealed how much hesitation an on-field umpire actually carries. What looks obvious on the tracker is often fog in real life. The review system does not claim umpires never err; it claims the error is part of the system.

Now the real question. Who speaks in fifteen seconds? By standard protocol, the keeper sees first, the bowler asks first, and the captain decides last. In Australia and England, those three roles have been divided for years — one person speaks the language of evidence, the others stay quiet. In Bangladesh, three people often compute simultaneously, and the fifteen seconds are spent so that the decision ends up belonging to the loudest voice.

The review problem was never a shortage of information. It was a shortage of structure — who owns the decision and who merely advises. If a team finds its weakness in the ledger and the weakness is communication, the answer is not a new tracking camera. The answer is a clarified role: one review captain, and a rule of waiting for everyone else.

The easiest explanation, the one everybody repeats, is that Bangladesh wastes reviews. Checked against the ledger, that is half true, and the other half is the interesting half.

In my ledger, a large share of Bangladesh's failed reviews fall in the middle of an innings against spin, when no signal from the batter's end appeared anywhere on screen. Scattered shouts of “out, out” floated in from mid-off or square leg, and that was enough. This does not show a team that calculates badly; it shows a team borrowing the right calculation from the wrong source.

Now the truth nobody enjoys. Umpire's Call protects the accuracy of the technology while hanging the blame around the players' necks. When ball-tracking says the ball would have hit, but it was inside a half-ball margin, the outcome is decided by the on-field call. So the technology takes no responsibility for the most contested sliver of its own projection; the responsibility goes to the person who never saw the television replay.

Yet here is what nobody says — some reviews are won and still teach you the wrong lesson. If a team trusts the wrong voice once and succeeds, the tendency to trust that same voice grows, because the process looked correct. Victory can be a bad teacher; defeat is the most honest one.

One thing must always be remembered: in real time, nobody had all the information. Take an innings where my test channel's microphone was dead, the stump camera angle was low, and the tracker had one broken frame. I sat through exactly that in a Sri Lanka tour match — out on the screen, a question mark in my ledger. What matters is remembering the process that produced the call, not the call itself, because the process is the teacher.

One row in my ledger, perhaps the most frustrating of my professional life, is not a review record at all — it is four batters dismissed. In an ODI we had exhausted our two reviews, then a genuine appeal came from the middle that we could no longer challenge. Two valuable wickets might have been saved that day, which is not a question of evidence but of process.

But let us be honest — not every review is a matter of theory. Some are written purely by a player's emotion, and some on-field calls were correct in the very first frame; all the argument afterwards is only the crowd leaning one way.

The least discussed gap in Bangladesh cricket is the one that needs saying now. There is no structure for rehearsing reviews at home, and that is not a selection problem or a talent problem; it is a structural one. The arithmetic is simple: what does not exist at domestic level will not be conjured in fifteen seconds of emotion in front of a small red screen at international level. Across my ledger this is the firmest pattern, and it is proven at Mirpur, on the edges of the National Cricket League, long before any international fixture.

To today's players I would say this — your bat, your patience, your discipline are as much in your hands as your fifteen seconds are not. In modern cricket the most valuable assets still rest on human shoulders. Compared with what came before, whatever a team has learned came from embarrassment, not from victory. What I am still waiting for is the day Bangladesh reads its own ledger, not the scorecard.