In the Shadow of Umpire's Call: The Captain's Mind Hidden in the DRS Ledger

Sher-e-Bangla National Cricket Stadium, Mirpur. The twelfth over of the match. The left-arm spinner releases, the batter pushes forward, the ball strikes the pad. The on-field umpire shakes his head — not out. A review signal comes from the dressing room. Ball tracking begins on the big screen. The projection arrives: the ball is hitting the stumps, but only grazing the very edge. The result — Umpire's Call. The on-field decision stands. The stands erupt, and the word 'robbery' circulates on social media. The episode is not a failure of the umpire or the technology; it is a rule applied letter for letter. The real question lies elsewhere — should that review have been spent at all? What happened inside the twenty-two yards was not merely an LBW; it was a frame in a captain's decision-making process. Had he not reviewed, a decisive opportunity might still have been available in the third session.

Context

The Decision Review System, DRS, first entered international cricket in 2026, during the India-Sri Lanka Test series. At first it was entirely optional; whether a series used it was decided by the host board. Over the following decade the ICC gradually folded it into the regular framework of all international matches. DRS was used at the 2026 ODI World Cup, and by the 2026 World Cup it had become an inseparable part of every match. Around the mid-2010s the ICC made it effectively mandatory for all member nations.

The system rests on three pillars, and it matters to know them separately. First, ball tracking — Hawk-Eye or its equivalent, which follows the ball's trajectory and predicts whether it would have struck the stumps. Second, edge detection — UltraEdge or Snickometer, which analyses the sound and vibration of bat-on-ball contact. Third, the third umpire, who re-examines multiple angles and frames before reaching a final decision.

This is where the concept of 'Umpire's Call' enters, and without understanding it the entire system is misread. In an LBW, if ball tracking shows the ball hitting the stumps but less than half the ball's width making contact — that is, the ball merely grazing — it is Umpire's Call. Likewise, if the batter does not offer a shot and the point of impact is more than three metres from the stumps, the on-field decision again stands. In the language of the law, this places technology not as the decision-maker but as the setter of the 'threshold of proof'. One word deserves recognition here, one the crowd never utters — threshold. Technology only shows; the law decides how much certainty is required before a decision is overturned.

The arithmetic of reviews is not simple either. In Tests each team receives two reviews per innings, but a successful review is retained. In ODIs and T20Is the number differs. This 'retained on success' rule is the psychological heart of the whole apparatus, because it turns a review into a limited resource — something that can be spent, or hoarded for later use.

Core

At the 2026 World Cup in Russia I began logging every single VAR review myself — 29 reviews, an average of 82 seconds, 17 decisions overturned. That log taught me a habit I later applied directly to cricket: the number of reviews says nothing on its own; who reviews when, and with how much conviction, says everything. Across a decade of my personal database, one pattern returns again and again, and it can be captured in three numbers. First, by over, the urge to review peaks in the first fifteen overs of a match. Second, the success rate of those early reviews is significantly lower than in the next two sessions. Third, reviews taken in haste by the bowling side outnumber those taken by the batting side.

This is better called behavioural data than statistics. A review in the first fifteen overs is not a decision of conviction; it is a decision of hope. The swing of the new ball, the seam movement, the behaviour of the pitch — everything is still unstable. The bowler believes the ball pitched and took the inside edge; the captain believes him, because the team is under pressure and needs a wicket. But at the moment the review is taken, the frame that would confirm it has not yet been captured. The frame arrives later, not before the decision — that is the biggest trap, and it is the one the television replay conceals.

Sitting in the Rajshahi press box, I have watched many times how a single failed review shapes the course of a match. Burning a review is not merely losing an opportunity; it is selling a probable wicket in the third session before the match has reached it. A review spent in the first innings is simply not there in the final hour, when it matters most. This cost-benefit calculation is the most neglected part of a captain's job. In Bangladesh's Test history, Shakib Al Hasan and Mushfiqur Rahim have both led the side for long stretches; the difference that experience makes lies exactly here — who keeps the ledger in mind and who is swept by emotion.

A caught-behind review and an LBW review are never the same thing. For a catch, UltraEdge is near-conclusive proof — both sound and vibration are present. But LBW is a game of pure prediction; the ball's path is extrapolated, and that is where the margin of error is largest. So the same captain is confident on a catch and hesitant on an LBW — even though the review budget is identical.

The domestic circuit is the real laboratory. In the Dhaka Premier League or the National Cricket League I saw this pattern long before it surfaced in Test cricket. In domestic matches at Mirpur, captains often review out of habit — on the bowler's emotion, under crowd pressure, or from a desire to 'have a look' at the opposition. Where there is no culture of keeping a review ledger, the spending is unconscious. The same captain then arrives in international cricket without an evidence-based ledger, and pays for the errors.

Yet one thing must be added here, something the first replay never shows. Broadcasters usually show the front-on angle, because the story looks clearest there. But the angles that matter most for overturning a decision are the side-on view and the stump-mic audio. How much the ball curved, how much the bat turned, whether the batter was attempting a shot — all of this is captured only in the side-on frames. The stump mic catches the sequence of bat and pad, even the sound of the footfall. Audiences never watch these two elements closely, yet they are the foundation of the decision. The angle the first replay buries is very often the real witness.

There is another layer — field placement. The positions fielders take before the ball even lands tell you what the bowler is attempting. A dense slip-and-gully cordon signals that the bowler is hunting the edge; a fielder pushed up on the leg side signals that the plan is LBW-centric. This information is generated before the decision, yet almost nobody uses it when analysing the decision.

Contrarian

Now to the question the crowd roars about most — 'that was clearly out, the technology robbed us.' Two separate things get conflated here: the outcome of the law and the feeling of justice. If technology shows the ball hitting the stumps but only grazing, the law says the decision does not change. Because the law does not want a valuable wicket erased on the basis of a ball that merely clips. Here technology is not making the decision; technology is only showing, and the law is deciding. The spectator shouting 'robbery' is really blaming the technology for a rule he has never read.

The reverse also deserves acknowledgement. Not every review fails, and not every Umpire's Call is controversial. Many times I have seen the on-field umpire's 'out' turn out to be correct, with the review merely confirming it. Nobody likes to write about such episodes, because 'the obvious was right' is not a compelling story. But fairness demands it be written. There is no law that every contentious call must conceal a conspiracy; sometimes the on-field umpire was simply right, and that is the least-discussed truth of all.

One more thing must not be forgotten — the umpire had fifteen seconds, not fifteen angles. He decided on the basis of what he saw at the instant of release; the luxury of frame-by-frame analysis was not his. So it is the process, not the outcome, that must be judged. A process that is the same for everyone is correct — even when its outcome feels partisan every single time.

Takeaway

The solution lies not in better technology but in transparency. First, bringing the third umpire's communication audio — what he is seeing, what reasoning he is applying — directly into the broadcast would defuse much of the crowd's anger, as the closed-door matches of 2026 made clear. Second, the review-retention rule deserves reconsideration: if a review is clearly and demonstrably correct, allowing it to be returned even after a failed review would make captains less hasty. Third, a culture of keeping review ledgers must begin in the domestic circuit itself, so that captains on the international stage decide on data rather than guesswork.

If next season we see a series in which the number of reviews falls and the success rate rises, we will know the system is working. If not, the question will remain: are we judging the umpire, or our own patience?