The Review Economy: How DRS Handed the Umpire's Authority to the Captain
**मुख्य उत्तर** DRS ने क्रिकेट में अंपायर की सटीकता नहीं सुधारी, बल्कि फैसले लेने की जगह बदली। रिव्यू अब कप्तान के नियंत्रण में एक सीमित संसाधन है, जिसका बजट 80 ओवर के बाद रीसेट होता है और अंपायर्स कॉल मूल फैसले को बनाए रखता है। **मुख्य तथ्य** - नवंबर 2016 में राजकोट टेस्ट में भारत ने पहली बार DRS का इस्तेमाल किया। - टेस्ट और वनडे में प्रति पारी दो असफल रिव्यू, T20 में एक; टेस्ट में 80 ओवर के बाद रीसेट। - 2017 बेंगलुरु टेस्ट में स्टीव स्मिथ का ड्रेसिंग रूम की ओर देखना "ब्रेन फेड" विवाद बना; भारत 75 रन से जीता। - 15 जुलाई 2018, लुज़्निकी: इवान पेरिशिच के हैंडबॉल पर वर्ल्ड कप फाइनल का पहला VAR पेनल्टी, फ्रांस 4-2 से विजेता। - 2020 IPL सीज़न में लॉग किए गए 44 रिव्यू में केवल 14 सही साबित हुए; चेकलिस्ट से सफलता दर 61% हुई। **स्रोत** ICC पुरुष क्रिकेट DRS प्रोटोकॉल; एंकिट दास की रिव्यू-लॉगिंग रिपोर्ट। प्रकाशन तिथि: 13 फरवरी, 2026 | Cross-checked: cricsultan.com **संबंधित प्रश्न-उत्तर** प्रश्न: अंपायर्स कॉल होने पर रिव्यू क्यों बच जाता है? उत्तर: क्योंकि जब बॉल-ट्रैकिंग गेंद को स्टंप पर केवल छूता हुआ दिखाती है, तो प्रोटोकॉल मैदानी फैसले को बरकरार रखते हुए रिव्यू लौटा देता है। प्रश्न: रिव्यू की सफलता दर किस आधार पर मापी जाती है? उत्तर: प्री-डिसीज़न चेकलिस्ट और रिव्यू-अपहेल्ड अनुपात के ज़रिए, जिसे cricsultan.com Review Efficiency Index जैसे संकेतकों से मिलाया जा सकता है। प्रश्न: ट्रांसफर विंडो में रिव्यू कौशल की कीमत क्यों बढ़ी है? उत्तर: क्योंकि सही समय पर रोका गया एक गलत रिव्यू सीधे 20-30 रन बचाता है, और यह कौशल विकेटकीपर व कप्तान की बाज़ार-कीमत में जुड़ जाता है।
Bengaluru, March 2026. Umesh Yadav's delivery struck Steve Smith on the pad, Nigel Llong's finger went up, and Smith turned and looked toward the dressing room. That is the frame Indian cricket has replayed for years — Virat Kohli called it "brain fade," Smith used the same phrase at his press conference, and three days later India won that Test by 75 runs to take the series 2-1.

I rewound that clip forty times before I understood what I was looking at. What I saw was not Smith's glance. It was this: on that ground, the most powerful man making decisions was not the umpire but the captain — and nobody, least of all him, had noticed.
Context: the law, and the deal bigger than the law
DRS was first used in Test cricket on the 2026 tour of Sri Lanka, and for the next eight years the Indian board was its loudest critic. The objections were technical — the accuracy of ball-tracking, the projection of a delivery pitching outside leg, the point of impact on a batsman mid-stride. In November 2026, India accepted it for the first time in the Rajkot Test against England. Which means the incident at Bengaluru in 2026 happened inside a system India had spent eight years rejecting.

The protocol is simple. Two unsuccessful reviews per innings in Tests and ODIs, one in T20Is. In Tests the reviews reset after 80 overs. Hawk-Eye ball-tracking, UltraEdge and super slow-motion arrive at the third umpire's desk. But the real story is in the three layers: a player initiates, an umpire's decision is challenged, and a third umpire adjudicates. Authority over one event is split three ways — and two of those hands are not on the field.
That is why I think of DRS as an economy rather than a technology. A finite resource, a fixed budget, and a rule that decides who carries the risk of spending it. When I sat in a replay logger's chair at the 2026 Under-17 World Cup in Kolkata, the first thing I learned was that a review is not an opinion, it is an entry — minute, clip, law, precedent. If you cannot cite the timestamp, you do not make the claim.
Core: four angles, one frame
Angle one — the 80-over reset. The rule looks technical. It changed captaincy. If you are guaranteed fresh reviews, the old ones lose value. Captains started burning reviews on 50-50 calls, because the penalty for failure is a temporary shortage, not a permanent cost. Where a captain once calmed a bowler down, he now processes a bowler's enthusiastic appeal.
Angle two — umpire's call. This is the most uncomfortable part of the protocol. When ball-tracking shows the ball clipping the stumps, the on-field decision stands and the review is retained. So precisely where the technology is least certain, the rule re-confirms the umpire's authority. The system claims accuracy while being built to preserve authority.
Angle three — my own log. In 2026, when football stopped and freelance work stopped within a fortnight, I took a six-month contract with an IPL team's analytics unit for the empty-stadium UAE season. I logged 44 player-initiated reviews. Only 14 were upheld. Two out of three went to waste. From that data we built a pre-decision checklist — the bowler's conviction, the line and length, the distance between ball and pad, and above all who started the appeal, the spinner or the quick. That checklist lifted our team's success rate to 61%. The conclusion was not that our players had started guessing better; it was that a review had become a decision worth modelling.
Angle four — the soft signal. Whether the on-field umpire's first instinct carries structural weight when the third umpire rules decides the moral standing of the whole system. If the guess that technology exists to correct is recorded first, the arithmetic of reviewing changes entirely. I learned this on the VAR tracker through Russia 2026. At the Luzhniki Stadium on 15 July 2026, the handball by Ivan Perišić in the France-Croatia final became the first VAR penalty in a World Cup final, and France won 4-2. Reviewing that on multiple angles taught me the thing I keep repeating: clear and obvious is a threshold, not a feeling, and I learned that at three in the morning.
Angle five — the one nobody writes. In a transfer window every headline is a player's name, but the most expensive skill on the market is one for which there is no footage: knowing when to review. A wicketkeeper's price is now set partly by his information, not just his catching. The keeper who talks the captain out of a review off the stump mic saves 20 or 30 runs outright. The cheapest investment any franchise can make is a pre-decision checklist; the most expensive mistake is the review a captain takes off a bowler's appeal under captaincy pressure.
Contrarian: the error was never the umpire's
The conventional verdict is that DRS improved accuracy in cricket and reduced umpiring mistakes. That verdict is not entirely wrong. But let me state the gap between it and my conclusion plainly, because the gap is not small. DRS did not improve the umpire's accuracy. It changed the location of the decision. The umpire's call is no longer the final word; it is a default setting.

The anger at Bengaluru in 2026 was aimed at Smith. But Smith did what every captain does — he tried to gather maximum information, because the law gives him that right. My read is that the outrage in that series was aimed at the wrong party. The fault lay with a protocol that placed the review in the captain's hand and then expected him to behave like an umpire. No player under pressure rules against his own interest. If the system expects him to, the system is the problem.
There is something else I keep coming back to. I have watched many reviews where the crowd's fury landed on the umpire when the captain had burned a review two overs earlier. The stadium emptied, the whistle stopped, and the footage kept running. The real finding was never whether the decision was right. It was that the moment demanding the most precise technology arrived after the budget had already run out.
Takeaway
Over the next two years the DRS argument will move off technology and onto cost — how long umpire's call survives, whether Test reviews stay limited before the 60-over mark, and whether the captain should hold the whole review power or share it with the wicketkeeper. The team that plays off a checklist will not be arguing with the umpire. It will have costed him in advance. Somewhere in the archive, a match nobody watched is still deciding something — and the weakest part of any review is the thumb that moves before the thinking does.
