The Five-Point Review Protocol: DRS, Umpire's Call and the Truth on the Big Screen in Asia's Tournaments

One review. Three frames load on the big screen — pitch, impact, stumps. Forty thousand people in the stands hold their breath, yet the umpire hears only the sound of a referral. On the third umpire's monitor, the scan runs frame by frame. Forty-seven seconds later the screen reads: Umpire's Call — Original Decision Stands. An uproar. Some say the match has been stolen, others say the rule is the rule.

From my desk in Dhaka, what I see inside those forty-seven seconds looks nothing like the roar in the stands. I see a protocol — law, camera angle, contact, the clear-and-obvious threshold, and the final call. Those five steps must be walked in order. Skip one, and the maths collapses, and the argument over the result becomes inevitable.

The pressure of an Asian tournament makes this five-point log even more essential. Here the pitches are slow, the bounce is low, and spin dominates. This is exactly where ball-tracking predictions come under the heaviest scrutiny. I built the five-point log in Dhaka because memory is not a review protocol — and under tournament heat, memory is the first thing to change.

Context: the birth of DRS, the law, and Asian conditions

DRS was first used in 2026, in the India-Sri Lanka Test series. It began as an experiment, switched on and off country by country. Later the ICC made DRS mandatory in all T20 internationals in 2026. Today there are two reviews per innings in ODIs and T20Is, and three in Tests. These numbers are not merely rules — they are a strategic limit that directly shapes a captain's decision-making.

Based on my years of watching matches, the real battle in a review is not on the field but in the definition of a threshold. In the language of the law it is called "Umpire's Call." When ball-tracking shows the ball striking less than half the stump, it becomes Umpire's Call — and the on-field decision stands. The question is whether this half-rule is a limitation of technology or a deliberate choice to protect the umpire's authority. The answer pulls in both directions.

In Asian conditions that tension is sharper still. Subcontinental pitches are generally slow, low-bouncing, and spin-friendly. The ball slows after pitching, and the line on a spinner's delivery is often uncertain. When ball-tracking predicts in such conditions, its margin of error widens, because the system projects the final segment of the trajectory, and on slow pitches that projection is least reliable.

To me the matter is clear: an Asian tournament means not only cricket's pressure but technology's pressure too. When a captain in the dressing room takes a review, he is not only challenging the umpire's decision — he is trusting a prediction model whose reliability depends on the nature of the pitch. That dual pressure sits at the centre of Asia's review controversy.

Core: the five-point log, step by step

A live tracker taught me that chaos is just data waiting for a sequence. In a review, that sequence can be arranged in five steps. I examine each step separately, because one wrong step distorts the whole decision.

Point 1: The law. First question — what kind of appeal is this? LBW, catch, stumping, or boundary? Each has a different test. In LBW, three conditions must be met at once — the ball must pitch in line with the stumps or outside off, impact must be outside leg or in line, and the ball must hit the stumps. Fail one condition and the review fails. Under tournament pressure many captains take a review without doing this three-condition maths, and that is the biggest mistake of all.

I have seen that most failed reviews come in cases where the impact was clearly outside leg. The on-field umpire gave not out for exactly that reason. The captain reviews out of emotion, and one review is lost. Losing a review in a knockout means the entire innings strategy shifts.

Point 2: Camera angle. The limits of the technology become obvious here. Ball-tracking depends on three things — camera calibration, frame rate, and the ball's speed. On a slow spinner's delivery, the system takes longer to pick up the ball's spin axis, and the chance of error rises. On a fast bowler's yorker, the ball crosses the stumps within a few frames, and the prediction window shrinks.

In my tracker notes I found a pattern: the most controversial decisions mostly came from deliveries where the ball's path was unusual — either very slow spin or very fast yorker. Ball-tracking is most reliable on medium-paced, normal-line deliveries. Because Asian pitches favour spin, the rate of controversy is higher too.

Point 3: Contact and impact. This is where UltraEdge and Snicko come in. When the bat's edge is grazed, UltraEdge shows a spike, but stadium noise or the bat handle's vibration can sometimes look like a spike. The difference between contact and impact has to be caught. I have seen that the biggest errors in catch reviews happen exactly here — whether the ball touched the bat, the pad, or flew off the glove.

Another element enters at this step — the soft signal. Around 2026 the ICC abolished the soft signal for catches. Previously the on-field umpire gave a preliminary decision, and the third umpire needed clear evidence to overturn it. With the soft signal, the controversy was of a different kind — now the third umpire makes the first decision himself, which increases his responsibility.

Point 4: The clear-and-obvious threshold. This is the most ambiguous step of a review. The phrase is simple, the reality complex. How clear does a decision have to be to be "clearly wrong"? The ICC wants clear evidence, but there is no measurable definition of clarity. As a result, the third umpire's personal judgement becomes the final word.

In my log this is the room of greatest uncertainty. I have added a confidence score here — the number of cameras, frame clarity, and how natural the ball's path is. If, taken together, the score drops, I write the decision as "provisional" and do not call it certain. The referee's eye is not intuition; it is a habit built frame by frame. And that habit tells you when to stop.

Point 5: The final call. Here the system and the umpire's authority meet. Ball-tracking offers a prediction, but a human gives the final verdict. At this meeting point comes the real question: is technology helping the umpire or eroding his authority? In the language of the law the answer is clear — the umpire's decision is final, and technology is only a tool for catching obvious errors.

Data patterns: how often reviews succeed

Tracking review outcomes over the years, one quiet truth has emerged: a large share of reviews fail. The reason is strategic, not technical. Captains often forget to account for Umpire's Call. In a Test where spinners are bowling at leg stump, the impact is often in line with leg — ball-tracking may show the stumps, but it becomes Umpire's Call.

The second pattern is that under knockout pressure the success rate of reviews drops. In the group stage players do the maths coolly, but in a semi-final or final even a small delivery invites emotion. My tracker data suggests the per-review success rate in knockout matches is lower than in the group stage. This is not a failure of technology but a failure of human decision-making.

The third pattern — the agreement between ball-tracking prediction and the umpire's call is lowest on Asian pitches. The system was largely trained on English and Australian conditions, where bounce is higher and the ball's path is comparatively simple. On subcontinental low-bounce pitches that model's projection is weakest. This is a story of a global benchmark against local reality.

Contrarian: emotion versus the cold maths of the rule

The crowd sees one thing and the third umpire sees another. The crowd sees a ball heading towards the stumps and concludes it should be out. The third umpire sees that less than half the ball was hitting the stumps, so the on-field decision stands. Two truths, one event. This gap creates the deepest distrust in Asian cricket.

I want to say this plainly: Umpire's Call is not a conspiracy, it is an acknowledgement of a limitation. To force a claim that the technology cannot confidently make would be a greater injustice. But the problem is that the explanation of this limitation never reaches the viewer. They only see a prediction on the screen and demand a verdict on its basis.

This is where the tournament context matters. Under tournament pressure every decision becomes a matter of national emotion. Bangladesh, India, Pakistan, Sri Lanka — everywhere the review verdict is argued over, and that argument is often not technical but takes on a national or political colour. Technology is supposed to be neutral, but if the uncertainty of its prediction is not shown, that itself breeds confusion.

My suggestion is clear: the big screen shows only the final verdict; it should also show a visual confidence indicator. Alongside the ball's path, if viewers could see the system's level of certainty — how reliable the ball-tracking prediction is — the debate would return to the ground of reason. This would raise trust in technology, not lower it.

Takeaway: the protocol is the only standard of truth

What I learned at my desk in Dhaka is that the real strength of a review lies not in technology but in protocol. A captain who first does the maths of law, camera angle, and the clear-and-obvious threshold loses fewer reviews. A viewer who understands the five-point log feels less aggrieved. When the protocol is visible, when the debate turns into data, the game returns to its true form.

Facing Asia's tournament run, my question is a single one: on the big screen, will we see only the verdict, or the protocol too? If technology's transparency does not increase, then every Umpire's Call will give birth to a new controversy — and cricket's greatest loss will be one of trust, which no review can restore.