The Review Budget: Where Bangladesh's DRS Accounting Breaks Down Before the T20 World Cup

The 17th over ended with the on-field umpire's finger going up. Ball-tracking showed impact outside leg stump, but grazing the line. The batter challenged; the third umpire upheld the original call. That one decision did not change the match, but it cut Bangladesh's two reviews down to one. For the next eighteen balls that single review was the only reserve left, and no clear error worth spending it on arrived. Across Asian T20 cricket over the past year, this scene has repeated itself. The problem is not the review that was lost. The problem is spending reviews without doing the arithmetic first. The rule is plain. In T20Is and ODIs each side gets two reviews per innings. A successful review is returned, an 'umpire's call' is returned, and only a review that fails to prove a clear error is permanently spent. Since DRS entered international cricket in the 2026 India-Sri Lanka series, this budget policy has remained the most neglected part of the game. In 2026 the ICC clarified that an 'umpire's call' retains the review — a major shift, because from then on line-adjacent cases could be challenged at lower risk. Coaches, captains and batters sit for hours over bowling changes, field placements and strike rotation. Yet almost no team has a written protocol for when, in what situation, and on whose signal the two reviews will be spent. Among Asian sides, India and Pakistan are somewhat ahead, because they have built a clear channel between the keeper-slip view and the captain. In Bangladesh that channel is still personality-dependent. The 2026 T20 World Cup begins on February 7 and ends on March 8, hosted by India and Sri Lanka, with twenty teams. In that format each side plays a limited number of group games and gets one shot in the knockouts. Every review therefore carries more weight, because a single wrong call can end a whole campaign. At my desk in Dhaka I have kept a five-point log for every review since 2026: law, camera angle, contact, the clear-and-obvious threshold, and the final call. Memory cannot do this work, because memory is not a review protocol. International data suggests teams succeed on roughly one review in four — meaning three of four challenges are wasted. That single figure tells you a review is not a tool for finding proof; it is a tool for managing risk. Start with the fact that LBW and caught-behind are not the same kind of review. LBW demands three separate questions — pitch, impact, wicket. If any one of them lands on 'umpire's call', the decision stands and the review is returned. So an LBW should only be challenged when at least two components are clearly in doubt. Caught-behind, by contrast, usually turns on contact alone — bat or pad — which cameras capture quickly. The risk thresholds differ, yet on the field both are often taken in the same rush. The pattern that recurs most in my log is the wasted challenge inside the first six overs. New-ball swing creates doubt about the pitch line, the batter looks confident, the captain feels pressure — and a review disappears in the fifth over. A live tracker taught me that chaos is just data waiting for a sequence. Spending a review in the opening overs means empty hands at the most expensive moment later. A single LBW challenge in the last ten overs is worth several times one in the first six, because late in an innings both strike change and run rate hang on one decision. T20's own tempo complicates the arithmetic further. An ODI offers fifty overs to repair mistakes; a T20 offers twenty and no such room. The same law applies in both formats, but the risk of a decision is entirely different. A side that drags ODI habits into T20 often runs out of budget early. The second pattern is communication. The final signal to review comes from four sources: keeper, slip, bowler and captain. Four different readings generally produce a weaker decision. The sides that succeed decide in advance who speaks, who decides, and who holds a veto. Let the captain have the last word, but no decision should be made without the keeper-slip view — the two pairs of eyes closest to contact. The third pattern is timing. After the ball, there are about fifteen seconds to decide. In that window both instinct and arithmetic run. Most teams decide on the batter's confidence, which is the wrong baseline. A batter is always certain — that is his job. The right baseline is the fielding side's reaction and the umpire's position. The fourth pattern: many teams know the review-retention rule but do not use it. An 'umpire's call' carries no penalty. So a challenge with no clear error, but sitting adjacent to the line, can be taken at low risk, because the chance of retention is high. If that arithmetic is done at the table before the match, the rush on the field drops. The fifth pattern is technological literacy. A captain must know what ball-tracking shows and what it does not. Tracking projects; it does not observe. So information like grass contact, bounce height and seam movement stays limited on the tracking screen. A captain who knows that limitation does not take needless challenges. Fan complaint usually points at the umpire — 'no eyes', 'cracked under pressure'. The ground reality is different. Umpires decide within a few frames, and the technology simply exposes their limits. Bangladesh's current problem is not the official's skill; it is the uncontrolled spending of their own resource, the two reviews. We often say after a match, 'if only we had a review left' — when that review was spent in the opening overs and would have changed nothing. A more uncomfortable truth is that a review sometimes becomes a tool of strategic pressure. A frustrated bowler asks for a challenge, the captain agrees to release tension, and the result is a wasted review. A referee's eye is not instinct; it is a habit built frame by frame. Review-taking is a habit too, and habits do not form without a protocol. One caution matters here. Review success is not always the product of protocol; sometimes it is luck. So if a side wins three challenges in one match, treating that as proof of method is a mistake. The real measure is the long-run trend — in which situations what percentage of challenges pay off, tracked consistently. Before February 2026, Bangladesh needs a one-page review protocol: who decides, in which overs a challenge is barred, what happens in 'umpire's call'-prone cases, and who owns the cost. Technology does not answer every question; the question is whether the habit of questioning technology has been built at all.