The Hidden Budget of DRS: A Review Is a Cost, Not a Lottery

On July 14, 2026, at Lord's, the final went to a Super Over tie and the champion was decided by a clause about boundary count. Years later I rewatched the match and the conclusion was unavoidable: the controversy was never about technology. It had simply moved into the rulebook. I have an old habit with reviews. In every match I watch, I note down who asked for the review, in which over, and what came of it. Two seasons have produced roughly sixty entries. It is not a large sample, but a pattern surfaced. Reviews spent between the fifth and twelfth overs have the lowest overturn rate, yet that is exactly the window where teams burn through them fastest. The question is not whether the ball was hitting the stumps. The question is whether spending the review at that moment was worth it.

DRS is not new. Its international life began in July 2026, in the Test series between India and Sri Lanka, and in the decade and a half since, the system has changed mostly in the number of rules, not in how well the technology reads the game. In Tests each side gets two reviews per innings, retained if successful; in ODIs and T20Is the allowance is smaller. Three layers split the decision on the field: ball-tracking draws the trajectory, UltraEdge looks for the edge, and the split screen puts the two together. One condition hangs over all of it. If ball-tracking shows less than half the ball hitting the stumps, the on-field umpire's call stands. That is the so-called umpire's call.

What the television feed never shows is the boundary of information. After the umpire raises the finger, the window for the decision is measured in seconds, and inside those seconds four people offer four different readings from four different places: the batsman at the striker's end, the bowler, the wicketkeeper and the captain. The analyst in the dressing room can see ball-tracking on the broadcast feed, but he is not permitted to speak directly to anyone on the field. Messages travel through the twelfth man, at the drinks break, or between overs. So the decision-maker and the information-holder sit in separate rooms with the bridge closed between them. Dig into the VAR arguments in football and the same architecture appears: information in one room, decision in another.

There is a subtler layer that I see more clearly from behind a second screen. Since the 2026 A-League Grand Final I have written tactical notes regularly, and I keep returning to the same thought: the second screen is now part of the stadium. At home I see ball-tracking within eight or ten seconds. The captain standing on the field does not have that answer yet. Under the ICC protocol, replays are not shown on the big screen until the player has decided whether to review, a fair safeguard against influence. The result is a partial information flow on the field, made of crowd noise, the keeper's confident body language and the bowler's raised arms, while the complete version sits in the hands of a viewer on a sofa.

Now to the core accounting. A review is an irreversible expenditure: once spent it cannot be returned, and if it fails it is gone for good. Put simply, the expected value of a review is the product of two things: the probability of an overturn, and the value of that wicket at that moment. The second half of the equation is the one teams neglect most.

Take an example. In the powerplay, the new ball swings, so the chance of an lbw is higher, but the wicket usually belongs to an opener who has not yet set himself. In the fortieth over the ball is old, the swing is gone, but the wicket might belong to a set batsman, and his dismissal reshapes the next ten overs of the innings. When Travis Head made 137 in Ahmedabad in November 2026 and bent the entire final to his will, I went back to that match many times; the value of that single wicket exceeds the value of two early ones. My notes say teams behave in precisely the opposite way, gambling on optimistic reviews in the powerplay and arriving at the death with empty hands. The cost of protecting an unset batsman with a review is smaller than the cost of losing a set batsman because no review remained.

The second problem is who owns the information. For an lbw, the two measures that matter most are the height of the ball and the point of impact. The best observer of both is the wicketkeeper, because the ball passes beside him and he can read the angle relative to the line. The next best placed is the captain at mid-off or slip, where the sense of that angle is almost nil. The worst placed is the bowler, because he hopes, and hope manufactures bias. In practice the call for a review usually comes from the bowler, the final decision from the captain, and the keeper's information is the least consulted. The best information source and the decision-maker are rarely the same person, and that is the system's real design flaw.

The resentment around umpire's call is not a technology failure; it is a rulebook choice. When less than half the ball would have hit, the burden of uncertainty is placed on the on-field decision, on the logic that the difference is finer than the technology's margin. The consequence is that controversy does not shrink. It relocates from the pitch into the clause and the review room. I cannot say with confidence exactly where the line on that half-ball calculation should be drawn. What I can say is that as long as the grey zone is written into the laws, DRS will not solve controversy; it will only change its address.

Then there is the cost my notes treat as the most ignored of all. A failed review means roughly ninety seconds of standing around. For a batsman that is a small habit. For a fast bowler it means going cold: the friction goes, the rhythm breaks, and the pace has to be rebuilt. In limited-overs cricket those ninety seconds cut the batting side's tempo, which is why some call it a free timeout for the fielding team. In Tests the arithmetic flips, because time is cheap there while a bowler's physical load must be managed more tightly. I count fatigue as a tactical variable now, and a pointless review is a small but genuine line item in exactly that ledger.

Now comes the part where I argue against my own favourite easy fix. The familiar tune is that teams should get more reviews, three or four each. I think raising the number will not reduce error; it will redistribute it. With a scarce allowance, captains tend to be a little conservative. Widen the allowance and marginal reviews get spent faster, and the success rate falls. Loosen the rule and the error frontier simply expands, with the difference that the cost is now carried by the captain's judgement.

The real question is ownership. Not how many reviews, but who decides and when the information arrives. A comparison with the basketball timeout is available here. That too is a limited, irreversible resource that cannot be spent freely. But the similarity ends there, because a basketball timeout is a designed event, whereas cricket's review delay is accidental, never part of the game's architecture. The shared variable across both codes is genuine: a finite resource that should be saved for the most valuable moment of the match. The limit is equally clear. Without a live channel between the analyst outside the boundary and the captain on the field, the timeout analogy stalls halfway.

One more idea needs dismantling, the claim that the wicketkeeper should own the review decision. It sounds neat, but the keeper is also the man appealing for the wicket. Loading the roles of information source and advocate onto one person does not erase the bias; it hides it. I cannot claim my small sample is sufficient to isolate that effect from pitch conditions. Even so, the pattern is worth a question: in my notebook, reviews initiated on the keeper's cue fare slightly better than reviews driven by a bowler's appeal. Captains like Pat Cummins and Rohit Sharma clearly think about this, and their field placements give it away.

In the next series, watch one specific moment. The eighth over. Watch who walks to the captain, and whose voice the captain accepts. Then watch whether the analyst's message at the drinks break actually changes a decision, or arrives as an explanation for a choice already made two overs earlier. If the best information is fifty metres away and eight seconds ahead, then who is really taking the review?