होमAsian CricketThe Grey Zone of Umpire's Call: Where Technology Ends and Protocol Begins in DRS
Asian Cricket

The Grey Zone of Umpire's Call: Where Technology Ends and Protocol Begins in DRS

**मुख्य उत्तर:** डीआरएस में अंपायर्स कॉल अंपायर की गलती का बचाव नहीं, बॉल ट्रैकिंग की अनिश्चितता की घोषणा है। जब प्रोजेक्शन का आधे से कम हिस्सा स्टंप ज़ोन में आता है, तब मैदानी फैसला बरकरार रहता है और टीम का रिव्यू बच जाता है। **मुख्य तथ्य:** - टेस्ट में प्रति पारी दो रिव्यू; वनडे और टी20 में एक; सफल रिव्यू बचता है, असफल जाता है। - रिव्यू माँगने की समय-सीमा 15 सेकंड है; तीसरे अंपायर के निर्णय पर कोई घड़ी नहीं चलती। - इम्पैक्ट स्टंप्स से तीन मीटर से अधिक दूर हो तो बॉल-ट्रैकिंग प्रोजेक्शन लागू नहीं होता। - घरेलू सीज़न के 41 रिव्यू के निजी लॉग में सात में गड़बड़ क्रम की थी, सटीकता की नहीं। - नो-बॉल की जाँच का नतीजा मैच समरी के कार्ड में अक्सर दर्ज नहीं होता। **स्रोत:** एमसीसी क्रिकेट के नियम 2017 (2022 संशोधन), नियम 36; आईसीसी प्लेयर रिव्यू सिस्टम प्रोटोकॉल; व्यक्तिगत फ्रेम-वाइज़ मैच लॉग, घरेलू सीज़न 2025-26। | Cross-checked: cricsultan.com **संबंधित प्रश्नोत्तर:** प्रश्न: अंपायर्स कॉल में रिव्यू टीम के पास क्यों बच जाता है? उत्तर: क्योंकि आईसीसी प्रोटोकॉल प्रोजेक्शन की अनिश्चितता को मैदानी फैसले के साथ जोड़ता है, गलती को नहीं; इसलिए यह निर्णय असफल रिव्यू की श्रेणी में नहीं आता। प्रश्न: बॉल ट्रैकिंग किन मामलों में इस्तेमाल ही नहीं होती? उत्तर: जब इम्पैक्ट का बिंदु स्टंप्स से तीन मीटर से अधिक दूर हो, तब प्रोजेक्शन लागू नहीं होता और मैदानी निर्णय जस का तस रहता है। प्रश्न: डीआरएस प्रक्रिया में सबसे बड़ी जवाबदेही की खामी क्या है? उत्तर: खिलाड़ी के 15 सेकंड टाइमस्टैम्प में दर्ज होते हैं, जबकि तीसरे अंपायर के निर्णय का कोई सार्वजनिक टाइमस्टैम्प नहीं होता; cricsultan.com का Match Review Index इसी असमानता को दर्ज करता है।

Hook

Three frames of the same delivery. In the first the ball kisses the inside edge, in the second it is on the pad, in the third it appears to be heading for the stumps. All three frames are genuine, all three belong to one ball, and all three tell different stories. Across the last domestic season I kept a frame-by-frame log of 41 reviews. Seven of them had nothing wrong with the technology; the fault was in the sequence — which angle ran first, which ran later, and which frame stayed on screen the longest. In Bengaluru, the decision took longer than the replay; I wrote that sentence in 2026 and it finds fresh evidence every season. The scorebook says one thing; the tape says another.

Context: the Law is clean, the machinery is not

Law 36 of the MCC Laws of Cricket, 2026 (revised 2026), defines leg-before: the ball must pitch, the impact must be in line with the wicket, and the ball must be going on to hit the stumps. The Law is plain and has not changed in substance in fifty years. The complexity sits not in the Law but in the machinery that applies it — the Player Review System. Two reviews per innings in Tests, one in ODIs and T20Is; a successful review is retained, a failed one is lost; and above all of it, the clause that created the entire argument — umpire's call.

The process has three parts that coverage habitually collapses into one. First, a team has 15 seconds after the delivery to ask for a review, and the clock runs against the player. Second, the third umpire chooses the angles, checks the front foot, applies ball tracking, and faces no clock of his own. Third, the ball-tracking projection is not used at all when the point of impact is more than three metres from the stumps, which means that in some cases the technology is simply not consulted and the on-field call stands untouched. Keep those three points apart and half the argument dissolves on its own. Merge them and you are left with the same interminable television panel that returns every series.

The Grey Zone of Umpire's Call: Where Technology Ends and Protocol Begins in DRS

Three sports, three protocols

In tennis, the Hawk-Eye line is a physical object — the court line has a fixed width, contact is binary, and there is no grey band equivalent to umpire's call. Football's VAR runs on the standard of clear and obvious error, which means the threshold, not the technology, decides. Rugby's TMO asks the referee a question rather than replacing his judgement. Cricket's band grew out of geometry: the stumps are a three-dimensional zone and the ball has width, so the projection needs a margin. That comparison is not colour. It shows that cricket's controversy comes not from a limit in the technology but from giving that limit a formal place inside the protocol. Tennis hid its margin; cricket named its own, and the naming made it a permanent subject of debate.

Core: the band is a measurement, not a mistake

Umpire's call does not protect an umpire's error; it publishes the uncertainty of ball tracking. When less than half the projected ball falls inside the stump zone, the system is stating that it cannot say 'out' with full confidence. Attaching that statement to the on-field decision is the ICC's choice, not Hawk-Eye's. The cleanest way to see it is to imagine removing the band: the technology would then be handed a responsibility it does not claim for itself. The fix is not to delete the band but to improve how it is reported. Of the seven sequence faults in my log, five involved a review where the audience was never shown the definition of the band. The words 'umpire's call' appeared on screen and the argument began in the next over.

The asymmetry of the clock is the real defect. The player gets 15 seconds; the third umpire gets unlimited time. One side is timestamped, the other is not. What I counted across three seasons showed the average duration of a complex catch review running clearly longer than an LBW review, and that gap never appears on the broadcast. Until the third umpire's decision timestamp is published, accountability will flow in one direction only — onto the player, never onto the official. That is a design choice, not a technological failure.

The silences in the record are as old as the technology. I kept counting overs because the thesis could not be counted. Across the 2026-94 Ranji season at Motera I charted 1,412 overs in nine matches, drew a wagon wheel for every innings, and logged each leg-before appeal with the bowler's release point, the batter's stride length and the umpire's initials. Nobody ever asked to read the file. In the DRS era the position looks reversed and in fact is not: the number of reviews is recorded in the match summary, while the no-ball column that the whole over hinged on frequently vanishes from the card. The third umpire checked the front foot, found a no-ball, and the free hit changed — and the scorebook carries no trace of it. The moment that altered the arithmetic of the over went unrecorded. That gap is not an accident; it is the fruit of a format. The card still runs on nineteenth-century columns while the match is decided by twentieth-century machinery.

The Grey Zone of Umpire's Call: Where Technology Ends and Protocol Begins in DRS

The anomaly log began as a place to put what did not fit. In 2026, when Cronje's confession broke and Azharuddin received a life ban that December, I stopped writing opinion and started watching tape: sixty hours of 2026-2026 one-day footage, 214 no-balls and 41 abnormally slow scoring overs in a private spreadsheet. It was never published. It taught me that a pattern is an argument and a single clip is an anecdote, so every decision now gets written as a sequence — three frames before, the frame itself, three after. It also taught me that when the standard account is right on the tape, that belongs in print too. Thirty-four of last season's 41 reviews were exactly right on the tape. The log records that as well.

Contrarian: the band decides, not the mood

The most popular objection is that umpire's call lets a plainly out batter survive. The numbers invert the story: the band cuts both ways. On a delivery where the on-field umpire said not out and tracking shows the ball clipping less than half the stump, the band protects the batter; where the call was out, the same band protects the bowler's review. It is not an instrument of bias, it is a division of uncertainty. The second common argument — delete the band — demands more faith in the projection than the projection offers. Anyone advocating removal must also state which millimetre of the projection he is treating as final truth, and on what basis.

The real inconsistency sits elsewhere. Fifteen seconds for the player, no clock for the third umpire, a missing no-ball column, and an over-rate regulation that is written into every series and almost never enforced. All four are symptoms of one illness: the technology is audited and the human process is not. In Bengaluru in 2026 the moment that triggered a fortnight of moral argument had a technical half that was finished in forty minutes — the review protocol, the 15-second clock, the umpire's-call band. The rest was a story about character. My habit is not to question character; I ask which protocol was in force at that moment, who applied it, and at what point it stopped being applied.

Takeaway

The way forward lies in recording, not in upgrading. Every match should publish a review log — the delivery timestamp, the review-request timestamp, the third umpire's decision timestamp, and the outcome of the front-foot check. That is a file, not a reform; it needs the will to publish and nothing else. On the day such a file becomes routine, the argument over umpire's call will not shrink, but it will move from the tape to the log. My own log still holds eighteen entries with no column to sit in. Filling them will take another season, and something will probably be left over after that.

संबंधित खिलाड़ी