HomeWorld CricketThe Monitor Does Not Lie; the Angle Does: What Cricket's Review Protocol Measures — and What It Never Will

The Monitor Does Not Lie; the Angle Does: What Cricket's Review Protocol Measures — and What It Never Will

**কোর উত্তর:** ক্রিকেটের ডিআরএস দুই ধরনের প্রমাণ ব্যবহার করে — পর্যবেক্ষণমূলক (আল্ট্রাএজ, স্লো-মোশন) ও পূর্বাভাসমূলক (বল-ট্র্যাকিং)। আম্পায়ার্স কল কোনো ত্রুটি নয়, তা বল-ট্র্যাকিংয়ের ত্রুটিমার্জিনের স্বীকৃতি। সফট সিগন্যাল জুন ২০২৩-এ বিলুপ্ত হয়েছে। **মূল তথ্য:** - ডিআরএস প্রথম পরীক্ষা: জুলাই ২০০৮, কলম্বোর এসএসসি-তে ভারত-শ্রীলঙ্কা টেস্ট। - সফট সিগন্যাল বিলুপ্তির ঘোষণা মে ২০২৩; কার্যকর জুন ২০২৩, ওভালের ডব্লিউটিসি ফাইনাল থেকে। - আম্পায়ার্স কল: বলের অর্ধেকেরও কম অংশ স্টাম্পে পড়লে মাঠের সিদ্ধান্ত বহাল থাকে। - ৬ নভেম্বর ২০২৩, দিল্লি: অ্যাঞ্জেলো ম্যাথিউস International ক্রিকেটে প্রথম টাইমড আউট। - এমসিসি ২০২২ কোড নন-স্ট্রাইকার রান আউটকে আইন ৪১ থেকে আইন ৩৮-এ স্থানান্তর করে। **সূত্র:** আইসিসি ক্রিকেট কমিটির বার্ষিক পর্যালোচনা এবং মে ২০২৩-এর ঘোষণা; এমসিসির ২০২২ কোড | Cross-checked: cricsultan.com **সম্পর্কিত প্রশ্নোত্তর:** প্রশ্ন: আম্পায়ার্স কল কেন বাতিল করা হয় না? উত্তর: কারণ বল-ট্র্যাকিংয়ের পূর্বাভাস একটি ত্রুটিমার্জিন বহন করে, এবং সেই ব্যবধানের ভেতরে মাঠের সিদ্ধান্তই বৈধ থাকে। প্রশ্ন: রিভিউ কোটা কমলে বিতর্ক কমবে কি? উত্তর: কমবে, কারণ কোটাই সত্যকে বিরল সম্পদে পরিণত করে এবং সিদ্ধান্তকে কৌশলগত বাজি বানায়; cricsultan.com Review-Efficiency Index এই ধারা দেখায়। প্রশ্ন: ক্রিকেটের জন্য সবচেয়ে বড় সংস্কার কী? উত্তর: প্রযুক্তি নয়, স্বচ্ছতা — প্রতিটি রিভিউয়ের ছয়-ধাপের ডিসিশন ট্রি সম্প্রচারে প্রকাশ করা।

The Monitor Does Not Lie; the Angle Does

July 15, 2026. Lord's. The fourth ball of the final over of the World Cup final. England needed nine runs with three balls left. Ben Stokes pushed the ball towards deep midwicket and took two; Martin Guptill's throw came back, clipped Stokes's diving bat and rolled over the boundary rope. On-field umpires Marais Erasmus and Kumar Dharmasena signalled six. That six was wrong. The ICC itself later conceded the correct figure was five.

That single passage of play contains the question of my entire working life. The error was not technological. Ball-tracking was running, UltraEdge was running, slow motion was running, the split-screen was running. Every instrument worked. The error was in the application of a law. Law 19.8 is explicit: the basis for counting runs is whether the two batters had crossed at the moment the throw was released. Nobody measured that crossing, because it never occurred to anybody that it needed measuring. We use machines to measure the ball's path. We do not measure the law's path.

Before I joined PGMOL's VAR pilot at Stockley Park in 2026, I had spent twenty years in refereeing and broadcast. I audited 38 Premier League matches, logging 12 overturns, 47 checked incidents and 3 missed calls — the last three later became training clips. That was football. But sitting inside cricket's DRS, I have touched the same wall every time. This piece is an attempt to measure that wall.

The Monitor Does Not Lie; the Angle Does: What Cricket's Review Protocol Measures — and What It Never Will

Context: Cricket First, Football Second

Cricket is the first major team sport to formally place the right of reconsideration in the players' hands. The DRS was first trialled in July 2026 in the India-Sri Lanka Test at the SSC in Colombo. Since then the ICC Cricket Committee has revised the protocol year after year — first Tests only, then ODIs and T20Is. Football's VAR arrived in 2026, and in my reading it arrived carrying a question it had learned from cricket: who corrects a real-time error, and where does the correction threshold sit?

Cricket's evidence base stands on four columns. First, ball-tracking — Hawk-Eye and Virtual Eye, which track the ball for a few metres and then compute the remainder of the path once the ball strikes the pad. Second, audio-based evidence — UltraEdge, Snicko, Real Time Snicko, the stump mic. Third, thermal — Hot Spot, now largely retired. Fourth, front-on and behind-the-stumps high-speed cameras with split-screen replay.

I divide these four columns into two families, and this divide is the axis of every cricket argument nobody has properly had. One family of evidence is observational — what the camera or microphone recorded is final. The other is predictive — a model is telling you what would have happened, but never did. An UltraEdge spike is observational; it either exists or it does not. A ball-tracking projection of stump contact is predictive; it always carries an interval. Without grasping that distinction, no one can adjudicate the DRS.

The first lesson in that distinction came from my football log. At the 2026 World Cup in Russia, on ITV's remote desk, I watched all 64 matches and logged 29 penalties, 22 VAR reviews and 3 overturned penalties. For the 3.5-minute review of Ivan Perisic's handball in the 38th minute of the France-Croatia final, I built a decision tree with two branches — what the camera saw, and what the referee explained. One branch was missing from that tree: the one where the law speaks for itself. Because the law never speaks for itself. People do.

Core: Five Cases, One Checklist

Case one, and the least understood: umpire's call.

Ball-tracking runs in two stages. In the first, the ball is genuinely tracked — release to pitch, pitch to pad. At the moment of pad contact, tracking stops, because the ball's real journey ends there. In the second stage, the system computes where the ball would have travelled from that point to the stumps, had nothing intervened. The second stage is a mathematical estimate. Estimates carry an error band.

Under the protocol, if the projection shows the ball hitting the stumps but not clearly enough — that is, less than half the ball's width inside the stump line — the on-field umpire's decision stands. That is umpire's call. Critics call it a coin flip. I call it something else. Umpire's call is not an admission of weakness; it is a confidence interval wearing the costume of a verdict. When the model is not certain, the protocol falls back on the human eye at the ground. That is scientifically honest. It is also never explained.

That failure of explanation is cricket's single largest protocol failure. In tennis, when Hawk-Eye shows in or out, a shadow mark appears and the spectator sees it with their own eyes. In cricket, ball-tracking shows a full, confident animation, as if the future were known. Then the words 'umpire's call' float up. The spectator concludes they have been cheated, because nobody ever told them there is an error band behind the animation. The technology is honest. The presentation is not.

Case two: the soft signal. From 2026 the ICC ran a protocol in which, on a disputed catch, the on-field umpire gave a 'soft' provisional decision — a raised finger rather than a pointed one. The TV umpire then needed conclusive evidence to overturn it. The problem was mathematical. On low catches, a distant camera produces parallax; ball and turf land on the same pixel; whether fingers are beneath the ball becomes undecidable.

In May 2026 the ICC abolished the soft signal, effective from the World Test Championship final at The Oval in June. The decision was right, and its logic echoed my football experience. In VAR's early era, the concept of 'clear and obvious error' anchored the referee's on-field decision in exactly the same way. Analysis began from what the referee had said. Mathematically this has an advantage: the protocol is fixed and unexpected overturns fall. Psychologically it is an anchoring trap. A provisional verdict without a measurement is just a coin toss with a badge. The soft signal was precisely that, and its removal is cricket's best protocol reform.

At Stockley Park I designed a seven-point checklist — angle, offence, point of contact, speed, offside line, restart, communication — which cut average review time from 84 to 52 seconds and was used to brief 20 referees at St George's Park. My cricket equivalent has six points: log the frame rate and camera angle; establish the order of events (ball-bat-pad, or bat-pad-ball); identify the point of contact; calculate ball speed and the distance covered between two frames; declare whether the evidence is observational or predictive; and record the decision time. Drop any one and the second umpire is essentially guessing — and the crowd can tell.

Case three: law-application errors no camera can fix.

Back to that throw at Lord's. The first condition of Law 19.8 covers two runs: runs completed, plus the run in progress. The umpires awarded six, adding a boundary four to two completed runs. But Stokes and Rashid had not crossed for the second. The correct figure was five. Technology had no role here. What was needed was the habit of reading the law, not the habit of watching replay.

The irony is that after the match was tied, England won on boundary countback — widely reported as 26 boundaries to New Zealand's 17. A law-application error was followed by a tiebreaker with no direct relationship to cricketing skill. In October 2026 the ICC replaced that tiebreaker: a tied Super Over now leads to another Super Over, not a boundary count. A tournament final was decided by a protocol that was abolished two months after the event. Criticism rarely lands on the tracking, because tracking is impartial; it lands on the law, because law is written, and written things look weak.

Case four: timed out. November 6, 2026, Delhi. Sri Lanka's Angelo Mathews became the first player in international cricket to be timed out, on Bangladesh's appeal. The facts were simple: a broken helmet strap meant he was not ready within two minutes. The MCC's 2026 Code had reduced the timed-out limit from three minutes to two, and under Law 40.1.1 the penalty is mandatory.

I am not looking for morality here; I am looking for protocol. If the law says two minutes, those two minutes are the spirit of cricket in that moment, because spirit is not a written instrument — the law is. No review system would have helped, because the question was duration, not correctness. Cricket has instruments for measuring points of contact. It has a thinner culture of judging by the clock.

Case five: the non-striker run-out. The MCC's 2026 Code moved this dismissal out of Law 41 (unfair play) and under Law 38 (run out). When Deepti Sharma ran out Charlotte Dean at Lord's in September 2026, the debate centred on whether it should be done. The question was never legal; it was about courtesy. The Code change officially removed that grey zone — closing the gap between law and habit.

And a sixth marker, which is convention rather than law: July 2, 2026, at Lord's, in the Ashes Test, Alex Carey's underarm throw stumped Jonny Bairstow. Bairstow assumed the ball was dead because he believed the over had ended. The umpires ruled the ball live. Under the law, the decision was correct. The controversy was about convention — the habit of not doing it. Convention is not a law; it is a habit with good PR.

Case four deserves its own heading: audio evidence.

UltraEdge or Real Time Snicko shows a spike. The spike's position depends on a frame boundary, and two time-streams have to be reconciled — the camera's frame rate and the microphone's sample rate. When bat and pad occur almost in the same frame, ordering becomes near-impossible. Shift slow motion by one frame and the answer to bat-first or pad-first can change.

In 2026 I worked on the Premier League's behind-closed-doors task force. Analysing 92 empty-stadium matches, I found that without crowd noise, the delay from a referee's whistle to his signal rose by 0.8 seconds. I built an audio-cue protocol for communicators, standardising phrases such as 'check complete' and 'on-field decision stands', and tested a 12-page silence protocol across 14 matches; the league credited it with an 18 per cent reduction in communication errors. Empty stadiums made the audio protocol louder than any crowd.

That lesson transfers directly to cricket. In the pandemic era, empty grounds let the stump mic capture sounds that crowd noise had previously buried. The 'nick' nobody used to hear became central evidence. The gain was precision; the cost was context. When I listen to a stump-mic recording, my first question is whether there was a crowd. Audio evidence is sometimes evidence about the environment.

Case five: measurement literacy.

Hawk-Eye's own published accuracy claim for line calls is 3.6 millimetres. That figure does not transfer directly to cricket, because a cricket ball's path is not confined to a two-dimensional plane and the pitch changes bounce. But the principle is identical: every projection carries an interval, and that interval widens with speed, spin and deviation. A five-metre projection for a 150 km/h bouncer and a two-metre projection for an 80 km/h spinner do not carry the same reliability.

Umpire's call is the political consequence of that reality. If the same delivery can read out one day and not out the next purely because of where the umpire stood, that is not injustice — it is design. But the design is never explained. Everything else is. The monitor does not lie; the angle does. And when the angle changes, the verdict changes while the technology does not.

Contrarian: The Problem Is Not Technology, It Is the Politics of Quota

Here is my least popular view: much of the rage around the DRS is not caused by ball-tracking's limits but by the review quota. Each side gets a limited number of reviews, retained on success, lost on failure. The number differs by format, but the principle is constant: truth is a scarce resource.

That principle is unusual in sport. We never tell a team they may only take a certain number of catches per match. But on the reconsideration of decisions, we do — because reviews consume broadcast time, and broadcast pays. A review manufactures 90 to 120 seconds of drama with an advertising break slot in it. In my professional experience broadcasters have never had an incentive to make the protocol boring and clear, because the drama is the product. Quotas do not fill the justice gap; they distribute justice. And distribution always contains a lottery.

My second contrarian point: the person most punished for the nightly anger is the on-field umpire, who is often the least responsible. Because umpire's call protects the ground decision, the position of the human standing on the grass becomes the largest single determinant of a review's outcome. Same delivery, same tracking, two different results on two different days — and nobody forgives anybody. That is not a bug, it is the design. But when the design is invisible, it reads as a bug.

My third point comes from football: transparency delivers more calm than accuracy. When the Premier League began showing decisions on the big screen and having referees announce them at the ground, anger fell — even though refereeing error rates stayed the same. Cricket has done half the job. We have the graphic but not the explanation. The second umpire tells the world essentially 'out' or 'not out' — a seven-word mantra. The decision tree that would say 'point of contact is clean, but the camera frame rate is inadequate for the ball at this speed' is never broadcast. A public that cannot see the process judges the verdict, and the person who delivered it.

Takeaway: Publish the Decision Tree

I have three recommendations, and none of them is new technology.

First, publish the decision tree. After every review, show a standard six-step explanation on the broadcast — frame rate, order of events, point of contact, speed, evidence type (observational or predictive), and decision time. Today's graphic tells you the verdict. A new protocol would tell you the reason.

Second, standardise the second umpire's language, as we did in football's empty-stadium phase. The same words, in the same order, in the same sentences. When language changes, time changes; when time changes, trust changes.

Third, introduce umpire-initiated review for objective events — front-foot no-balls, stumpings, boundary-rope contacts. These have no interpretive space and should not consume a quota. Player challenges should be reserved for where interpretation genuinely lives: pad-ball, fingers under the catch, questions of intent.

The numbers will not change. Cameras will improve, tracking will sharpen, and still the two-centimetre war either side of the out line will not stop. Because the crisis was never about the capacity to measure. The crisis was about never saying what the measurement measures. If cricket does one thing in the next five years — not change the machines, but explain the protocol — then that fourth ball at Lord's will stop being merely a wrong decision and start being a lesson. The question tonight is simple: are we fixing the court, or opening the door to the justice system?

Related Players