Soft Signal Abolished, Doubt Intact: The Open File on DRS Protocol

A low catch at slip. The ball kisses the edge, dips towards the fielder's left, and for one question the whole stadium stops: did it settle in the fingers, or touch the turf and rise again? The on-field umpire was not certain, yet his soft signal was out. The third umpire rolled the same footage back and forth six times, hunted for the difference between two angles, and then overturned it. The roar of the crowd, the captain sprinting in, the scoreboard holding its breath — and in that instant it becomes clear that the weight of the decision no longer rests with anyone on the field.

In May 2026, on the recommendation of the ICC Cricket Committee and with the approval of the Chief Executives' Committee, the soft signal was formally withdrawn. With it went both the on-field umpire's provisional call in catch reviews and the mandatory starting point for the third umpire. The reasoning was simple: in the act of taking a catch, the on-field umpire is often outside the line of sight, so making his call the foundation of the process amounted to giving uncertainty an official seal. The question, however, has now moved elsewhere, and nobody has kept the ledger of that shift.

The DRS is not old. It was first trialled in the 2026 India-Sri Lanka series, and became mandatory at ICC events from the 2026 World Cup. At first the technology's job was merely to sharpen the boundary between out and not out — lbw, catches, stumpings. But once technology sits at the centre of the decision, the question is no longer where the ball pitched; it is what we mean by proof. The soft signal was a provisional answer to that question: the on-field umpire's decision was the presumptive evidence, and the third umpire held the burden of breaking it.

Since 2026 I have kept a personal ledger of every ruling. The habit began with an abandoned football match — a game in Chattogram that was halted in the 89th minute — and while writing up how many rules and how many prior precedents shaped that verdict, I understood something: a ruling's value is set by the discipline of its reasoning, not by the intensity of emotion around it. In cricket the same method applies. Every review is, to me, a block — chained to the one before it, with law, playing conditions and umpire notes bound into a single thread.

Bangladesh does not sit outside this discussion. For a long time Bangladesh was hesitant about adopting DRS, and it took time to accept the system in bilateral series. The reasons were not purely tactical — board politics, broadcast costs and technological infrastructure are all tangled up in it. When the ICC removed the soft signal, the message for teams like Bangladesh was double-edged: an opportunity to raise the standard of decision-making on one side, a greater dependence on expensive technology on the other. That is where an invisible inequality forms, unannounced by anyone, visible only on the home ground scoreboard.

The soft signal was a procedural courtesy, never a law. The MCC Laws define what a catch is — the ball must come under the fielder's control, before touching the ground, and that control must be complete. But how "complete control" is to be measured is nowhere in the pages of the Law. The on-field umpire sees it once, from one angle, with the naked eye, in a tenth of a second. The third umpire sees it from several angles, frame by frame, minute after minute. The question is: if neither can be certain, who decides — and by what standard?

This is where the question of the standard of proof surfaces. Criminal law has one threshold of proof, civil law another. In cricket, the soft signal effectively gave the on-field call something like the benefit of the doubt. The third umpire was told: do not overturn the on-field call without conclusive evidence. The problem is that "conclusive" has no unit. What is conclusive on a 50 frames-per-second camera may be blurred at 300 frames — and the reverse can happen too. The standard of proof therefore shifted invisibly with the quality of the hardware, while not a single sentence changed in the rulebook. That silent shift is the least discussed problem in cricket administration — the law is written for one technology and enforced on another.

During the 2026 World Cup I logged every review by the minute — which minute, under which law, from which angle the decision came. The weakness of the soft signal was visible even then: the real issue is not a technological error; the issue is dressing a technological limitation in legal language. When the camera cannot decide, the burden was pushed onto the on-field umpire, as if he alone should carry that uncertainty. The process looks like protection; in practice it is a strategy for avoiding responsibility.

With catches, the geometry is crueller still. Slip catches, short-leg catches, or a dive at point — the ball and the hand sit almost on the same plane, and the camera is usually far away. In forcing three-dimensional depth out of a two-dimensional screen, the resulting parallax turns the question of whether the ball is under the fingers into something close to guesswork. From one angle the ball seems to have touched the ground; from another it seems not to have. Sometimes the ball hides in the shadow of the fingers; sometimes the pixel boundary erases the edge. Which angle the broadcaster shows first, and which later, is what builds the picture of the decision in the viewer's mind.

The protective zone known as "umpire's call" in the review system was born from the same philosophy. If ball-tracking shows the ball hitting half the stump, the on-field call stands. To a fan it looks absurd — the ball is hitting the stumps. To a technologist it is an acknowledgement of the machine's margin of error. If the machine's accuracy falls within a defined band, then inside that band the human call is final. Curiously, when the soft signal was withdrawn, that same logic was not applied — no protective zone was kept for catches. Machine error is conceded in lbw; it is not conceded in catches. That inconsistency is the seed of the next controversy.

Now look at the numbers. The pattern in my ledger shows that the overturn rate in catch reviews fluctuates more than in any other category of review — because here the decision rests on a single frame, and the quality of that frame depends on the number and placement of cameras in the stadium. Where there are ten cameras, what counts as "conclusive evidence"; where there are five, it counts as "unclear". Same law, different outcome — purely on infrastructure.

The gap between playing conditions and law is also worth noting. The MCC Laws say what a catch is; the ICC playing conditions say what the process is. The soft signal was part of the playing conditions, not the Laws. So changing it required no legal reform — a single administrative decision was enough. The lesson is clear: cricket's most contentious decisions often come from the layer where the governing body can act fastest, which is the playing-conditions layer. That layer is less discussed, less documented, and therefore less accountable.

In Bangladesh's domestic cricket the debate sharpens further. In the BPL, DRS is used in a limited number of matches; in the National Cricket League it is almost absent. Where there is no technology, the umpire's decision is final — and young players learn not the value of technology but the habit of its absence. The gap between their expectations and reality upon reaching the international stage shapes a generation's technological literacy. When an experienced keeper like Mushfiqur Rahim calculates before a review, and a young keeper in domestic cricket merely guesses, the two are in truth playing two different games.

At the administrative level the matter is more tangled. The soft signal was withdrawn on the Cricket Committee's recommendation and with the Chief Executives' Committee's approval, and written into the ICC playing conditions. But its implementation depends on per-series broadcast contracts, camera configurations and the limits of the technology provider. The match referee's report usually does not record these subtleties, because the report is written around outcomes, not methods. This is the gap I keep noticing: there is a record of the decision, but no record of the decision's reasoning.

The match referee's role here is dual. He watches the discipline of the game, but he has no jurisdiction to test the quality of a decision. If a team believes a third-umpire call was wrong, its remedy is nearly zero — a complaint can be filed, but the call cannot be changed. This one-way system accumulates grievance among teams, and that grievance later erupts in small incidents — a batter standing his ground after being given out, staring at the umpire, vague complaints in a press conference.

The player's perspective cannot be left out either. A review culture has grown around an unwritten strategy — the fear of losing out if you do not use it. When an experienced cricketer like Shakib Al Hasan decides with a cool head, and an aggressive batter like Litton Das reviews on emotion, two different outcomes follow. A bowler like Mehidy Hasan Miraz sometimes spends a review where the chance of gain is thin. The review system, in effect, tests the player's own standard of decision-making, which is no lower than the umpire's.

There is also an accounting of the cost of technology that nobody states openly. Keeping DRS running requires cameras, ball-tracking software, operators and a broadcast set-up per match — which can eat a large share of a domestic league's entire budget. Technology thus creates a two-tier system: those who can afford it buy justice, those who cannot leave it to chance. The cost figure appears in no public document, just as a club's private deal never shows up in the ledger.

I opened the abandoned-match file, and the precedent ledger answered. Just as in football, when a match is halted by disaster or disorder one must think about the code and prior rulings, so in cricket a similar discipline is needed for decisions. The difference is that in cricket this discipline is built through ICC playing conditions, match referee reports and Cricket Committee recommendations — not through a club's or league's own code. So changing a ruling here requires shaking the whole system at once, which is slow but also durable.

This is where the most comfortable assumption is disproved. It was assumed that removing the soft signal would make decisions cleaner. The opposite happened: responsibility moved from the field to the booth, but no standard of accountability was added. Previously the viewer knew who decided — the on-field umpire, open-faced, named, with a familiar vocabulary of explanation. Now the decision arrives from a room with no interview, no explanation, only a result.

The second point concerns the order of replays. Which angle the third umpire sees first is set by the broadcast director — who is not a participant in the game but a participant in the business. A particular camera's viewpoint can sometimes shape the mind two seconds early. The process looks technology-driven, yet at its centre sits an editorial decision. And the fan's emotion? The fan wants black-and-white truth; the system can offer grey probability. That distance keeps the controversy alive — soft signal or no soft signal.

The next step is not technological but one of transparency. If the ICC keeps a public log of every third-umpire decision — which angle, which frame rate, which law, which interpretation — then fan and player alike could read the same document. In a game where every run lives in a ledger, why should every ruling stay outside it? That question belongs to the administration, not the referee.

The referee's eye is trained on angles, not applause. And my experience says this: reaching a conclusion before the full match data arrives means creating a wrong precedent for the next ruling.