Counting the Third Umpire's Seconds: DRS Protocol, the Death of the Soft Signal, and Bangladesh's Review Ledger

Last season a match turned on a caught-behind appeal. The on-field umpire said not out. The fielding captain signalled for a review. At my desk in Rangpur I started the stopwatch. The third umpire worked frame by frame — 47 seconds, 53, 61. Then the spike. The UltraEdge line jumped at the exact moment the ball brushed past the edge of the bat. But in that same frame the bat had already touched the pad. Two sounds, one frame window. The screen flashed: not out.

The ground erupted. The broadcaster showed a three-second animation. The third umpire had watched more than forty frames, two audio channels, and carried one decision. I started the Dhaka VAR-Log because the Decision Review System is the place in cricket where truth and evidence never quite meet. Nothing that happened inside those 61 seconds reaches a scorebook. It can still change the result of a match.

DRS entered Test cricket in July 2026, in the India-Sri Lanka series at Colombo's SSC. It arrived in ODIs and T20Is in stages afterwards. The system rests on three pillars — Hawk-Eye ball tracking, UltraEdge or real-time snicko, and HotSpot. Each carries its own error margin, and those margins differ from venue to venue.

Around 2026, Umpire's Call became a permanent part of the protocol. If ball tracking shows the ball would have hit the stumps but less than half the ball is covered, the on-field decision stands. That single line of geometry has produced more cricket controversy than any other.

In May 2026 the ICC Chief Executives' Committee approved the removal of the soft signal, effective from that year's World Test Championship final in June. Previously, when the on-field umpire expressed doubt over a catch, the third umpire had an anchor. That anchor is gone.

Bangladesh matters here. Not every bilateral series carries the full technology suite. Some have no ball tracking, some no snicko, some only slow-motion replays. When Bangladesh won that historic Test series against Pakistan in Rawalpindi in August 2026, the umpiring pressure was of a different kind — and even there the complete technology set was not always available.

What keeps returning in my log is latency. Across the matches I tagged frame by frame over recent seasons, the third umpire's average decision time fell between 70 and 95 seconds. The question is where that time goes.

The first calculation is frame rate. Broadcast usually runs at 50 frames per second, which means 20 milliseconds per frame. The ball leaves the bat in 20 to 30 milliseconds. Only one or two frames capture that contact. If a third umpire looks for continuous proof, he will never find it, because the proof is discrete.

The second calculation is audio-video sync. The UltraEdge spike comes from an audio channel. A few milliseconds of offset can sit between the camera frame and the audio track, and it shifts at every stage of the broadcast chain. The protocol specifies no tolerance limit for that offset. A spike can be bat, or it can be pad. The decision rests on which frame the third umpire's eye places it in.

The third calculation is the geometry of ball tracking. Hawk-Eye itself acknowledges that its tracking error sits in the range of a few millimetres. On screen we see a flawless cylinder, an exact prediction. The graphic erases uncertainty — what the crowd sees is not a picture of probability but a picture of certainty. That is exactly where the half-ball rule suddenly looks absurd.

The fourth calculation is what changed after the soft signal was scrapped. The third umpire used to know what the on-field umpire was thinking. Now he is alone. The gain is that a layer of guesswork is gone. The cost is that the full weight of a low-resolution frame now sits on one person's shoulders. Stop the stopwatch and the picture is this — the responsibility did not disappear, it concentrated.

For Bangladesh, that concentration is sharper. In a series without ball tracking, a review becomes a negotiation with whatever the broadcaster captured. The first lesson of the Dhaka VAR-Log was exactly this — what an archive preserves and what it drops. In cricket the question cuts deeper, because the evidence for the review and the broadcast of the match sit with the same company.

When Najmul Hossain Shanto, who leads Bangladesh's Test side, calls for a review, it is not merely a request — it is a strategic bet. The wicketkeeper Litton Das hears a sound; the spinner Mehedi Hasan Miraz sees an angle. Their evidence does not always meet in the same frame. The third umpire sees both, and must choose one.

A human calculation belongs here. A wrong decision is not one wicket. It is a batter's series, a bowler's figures, a night in a dressing room. When I logged 240 penalty-area incidents across 120 football matches, what I found was that the explanation of a decision does more damage than the decision. In cricket the explanation is harder still, because the technology claims more clarity than it delivers.

The anger in the stands is not really about the law. It is about the asymmetry of information. The crowd sees a three-second animation; the third umpire sees forty frames and two audio channels. A decision that looks reasonable to one side looks like a conspiracy to the other, because the two sides are not watching the same evidence.

This is where the conventional view flips. Technology has not reduced controversy; it has relocated the address of controversy. The old question was, did the umpire see it? The new question is, did the camera capture it? And no single person owns the answer.

A second counter-intuitive observation: a review is no longer an instrument of justice, it is a strategic resource. Captains weigh how many remain, and which umpire's call is likely to survive. In Bangladesh's case a pattern repeats — reviews come late, under pressure, pushed by emotion. The bench makes the call, the camera supplies the proof, and the third umpire carries the blame.

I do not believe lowering the Umpire's Call threshold would quiet the argument. The problem is not the threshold, it is the disclosure. On a map of rule instability, each reform draws a new grey zone, and the fate of a match walks straight into it.

The ICC Cricket Committee writes the rules; the Chief Executives' Committee approves them. Frame rate, camera angles and audio sync are set by the host broadcaster. Member boards pay for the technology. Responsibility is split four ways, yet accountability is demanded from one man standing in the middle of the ground.

One proposal is simple: publish the review log for every decision — timestamp, frames used, audio offset, final reasoning. If an archive exists for accountability, it has no reason to stay hidden. The question now is whether cricket wants to preserve the evidence, or only the verdict.