The Two-Review Budget: Who Actually Counts the Cost of DRS in Asian Cricket?

Entry 23 in my notebook. BPL 2026, Rajshahi Kings batting, fifth ball of the sixth over. The on-field umpire said not out, the leg-spinner appealed, the keeper raised his gloves, the captain called for the review. Ninety-seven seconds later the ball-tracking screen showed the ball heading into leg stump — less than half of it inside the line. Umpire's call, on-field decision stands, review retained. I wrote that night: cost zero taka, time 97 seconds, outcome unchanged.

That one entry taught me that a review is not a free spin. It is a budget. In November 2026 I logged all 41 reviews of the BPL season from a coaching-centre canteen in Rajshahi — ball-tracking frame, whether it was umpire's call, seconds between appeal and signal, which umpire was overruled. I posted the table to a page called Third Umpire Notes before the final. Three thousand followers. The spreadsheet was my first whistle, and it gave me authority from a column of numbers rather than an opinion.

DRS entered Test cricket in 2026 on India's tour of Sri Lanka, optional at first, then folded into the ICC playing conditions. Two unsuccessful reviews per innings in T20s and ODIs, two in Tests — and in October 2026 the ICC scrapped the 80-over reset in Tests, so the budget now covers the whole innings. The BPL adopted DRS in the 2026 season, the same season I started logging.

The protocol has two layers. One tests whether the on-field umpire made a clear error. The other runs the projection: ball-tracking, Snicko, UltraEdge. Law 36.1 defines the LBW conditions, but the decision is actually made in a predicted corridor between the ball's path and the stumps. If less than half the ball is projected to hit, umpire's call stands and the review is retained. That is the point where the arithmetic gets difficult, because umpire's call does not mean the decision was wrong — it means the evidence was insufficient.

In my 41 entries, 17 produced umpire's call, 11 were successful reviews and 13 burned. Average duration was 94 seconds, the longest 2 minutes 38. Those numbers belong to one tournament, but the pattern holds: on Asia's low-bounce pitches the umpire's-call rate runs far higher than in European conditions, and almost no team builds that into its review budget.

The reason is geometry. When a spinner like Mehidy Hasan Miraz bowls round the wicket on a good length, the ball hits the pad two and a half to three metres from the stumps. The projection corridor is short, so the tracking model's margin of error occupies a larger share of it. I have two near-identical deliveries in my notebook, one given out and one umpire's call, separated only by a few centimetres of pitching point. Pace is no cleaner: Mustafizur Rahman's cutters arrive low, so the projected height sits near the top of the stump zone, and the half-ball rule usually protects the on-field call. Taskin Ahmed's full lengths produce the opposite, because the whole ball is inside.

Time is the other cost. Ninety-four seconds average means roughly three minutes per innings across two reviews — not just broadcast time, but dead time in which the dressing room changes instructions and the batsman resets his tempo. My log shows teams scoring about 2.3 runs fewer across the two overs after a failed review. The sample is 41, so I am stating this at a low confidence level.

Who takes the review is the largest gap. The law gives the decision to the captain; in practice the proposal comes from the keeper or the bowler. An experienced keeper like Mushfiqur Rahim reads height and drift together and produces better calls. Many sides still run the process on a bowler's conviction, with the captain rubber-stamping.

Here is the contrarian turn. Crowds hate umpire's call because they see the ball hit the stumps and the decision stand. To the crowd it is theft; to the law it is the limit of proof. The question nobody asks is upstream: more technology has not reduced controversy, it has relocated it — from the umpire's judgement to the projection model's error margin. Television does not show that margin, because showing it would end the argument, and the argument is the product.

And the second contrarian claim: a third review would not improve the game, it would make captaincy lazier. When the budget is larger, the marginal value of each unit falls. With two, a captain must count. With three, he spends a hope review in the first over and misses it in the sixteenth. A 90-day plan is just a referee too — without a limit, discipline does not arrive.

Empty stadiums taught me that silence has a data trail. Watching behind-closed-doors matches in 2026, I learned that the roar tells us what feels unjust but never what is unproven. Those are different things, and the laws run on the second.

Looking forward, one change feels inevitable: broadcast the error band itself. Show a shadow zone around the projected path instead of a binary umpire's call, and the crowd will see a decision inside a limit rather than a robbery. Second, review efficiency should become a coaching metric — which over, which bowler's appeal, what success rate. Teams that log it will save two or three reviews a season; teams that do not will play on emotion. Which raises the question: what frame is the last entry in your team's review ledger written in?