The Third Umpire's Silence: The Two Seconds of DRS Where the Real Match Hides

The Third Umpire's Silence: The Two Seconds of DRS Where the Real Match Hides

On the screen, the ball-tracking stopped at the exact moment the right hand was still holding the wire of the earpiece. The clock said two point one seconds. Then the hand went up—elbow folded, then straight. Out. Six thousand voices in the stands collapsed at once; some lowered their heads, some slapped the board in front of their seats. Yet the real decision had been made long before—silently, in a small room where no one claps, where no one swears. There, a single voice says: ball tracking, wickets, out.

I have sat down to write about those two seconds. Not the decision. Because the decision is momentary, and those two seconds—the pause between the earpiece and the raised arm—are the match's hidden blueprint. Of all the reviews I have logged in my notebook, the one I have written about most is exactly this pause. From football I borrowed a habit—where, after counting 118 decisions, I learned to understand my own knee—and in cricket I understood that the real work of counting is not tallying verdicts but measuring the silence before a verdict.

Last Sunday, in a match, I saw this scene again. The thirty-fourth over, a left-arm spinner, ball on pad. The on-field umpire gave it out. The batter reviewed. On the screen the ball appeared, the tracking began, then suddenly stopped for about a second and a half. In that second and a half there was no sound in the stands—only a collective intake of breath, something I log in my notebook as: silent noise. And right then I understood that this match's turning point was not a shot or a wicket, but this second and a half.

My claim is simple, and it is the centre of this piece: the outcome of a review matters far less than how the review was produced—where the umpire was standing, from which angle he was watching, what his ear was hearing, and why it took so long before the arm went up. Not the story of the decision, but the story of how the decision was made—that is umpiring forensics.

---

Context: The law, the technology, and the birth of those two seconds

DRS first entered international cricket in 2026, in a Test on Sri Lankan soil during India's tour, in that match at Colombo. Since then the technology has changed, the law has changed, but the curious thing is that the core structure of the process has stayed almost the same. The on-field umpire gives a decision, a review comes, the third umpire sits in a room and verifies it, and at the end a result floats onto the screen. The part in the middle that no one watches—that is the part I have been logging for eight years.

The names of the machines matter to the reader, because each instrument has its own limits. Ball tracking uses Hawk-Eye—it predicts the ball's path from release to pitch to pad. Edge detection uses UltraEdge, also known as Snicko—it listens for any sound just before or after ball meets pad. Sometimes HotSpot is used, which shows the mark of friction on the ball. These three pieces of evidence—sight, sound, mark—tell separate truths, and they do not always agree. And that disagreement is the most honest, least discussed part of DRS.

The law must be known. In Tests and ODIs, each team gets two unsuccessful reviews per innings; in Tests, they are refreshed once the innings passes eighty overs. That means a review is a limited resource—the more a team spends on unnecessary reviews, the fewer remain when they are truly needed. I call this limited resource the 'review budget'. And my notebook says most teams track this budget about as badly as they track the innings breaks.

This is where 'umpire's call' enters. When the ball hits the pad, if the projection shows the ball would hit the stumps—but it falls within a margin of half a ball's width—the technology upholds the on-field umpire's decision. That margin is not small: half a ball is nearly three centimetres. In other words, the system admits that it, too, has uncertainty. A system that admits its own uncertainty is imperfect, but it is not a liar.

In 2026, the ICC removed the 'soft signal' rule. Previously, when a catch was in doubt, the on-field umpire gave a preliminary indication, and the third umpire needed very strong evidence to overturn it. Now the third umpire is fully independent. To me this change is huge, because it has shifted the centre of umpiring power from the field to the room. When the centre of power shifts, the question of accountability shifts too—and that is the biggest gap today.

In 2026 came the stop clock—a sixty-second limit between overs, introduced to enforce over-rate discipline. On paper it looks like a matter of time. In reality it is a matter of psychology. Because a review, a drinks break, a tick of the stop clock—these three together can change the rhythm of an entire innings. And when the rhythm changes, the quality of decisions changes too.

---

Core analysis: Where a review actually comes from

First, position. Where the on-field umpire stands determines what he sees. An umpire standing on the leg side sees the angle of ball meeting pad of a left-handed batter differently, and the off-side umpire sees it reversed. An LBW decision is really a geometric estimate—where the ball pitched, where it hit the pad, which line it was travelling on. The umpire sees from one place, the camera from another, and the batter feels from a third. I do not trust a pattern until it survives three different angles—that is the first rule of my notebook.

Speaking of these three angles, one thing becomes clear: a review is not really an argument about evidence; it is an argument about position. An umpire who stands in a good position has his decisions overturned less by technology. An umpire hidden behind bodies has his decisions overturned more. Over the years I have noticed that those who consistently lose fewer reviews are not more intelligent—they simply stand in the right place.

Second, the margin. Spectators get angry about umpire's call because they believe technology knows what the truth is. But technology does not know. Technology knows probability. Ball tracking is an estimate with its own margin of error—the angle of the pitch, the seam of the ball, the amount of grass, even the age and condition of the ball all influence it. Umpire's call is not the failure of technology; umpire's call is the honesty of technology. A system that knows it has dust in its eye tells you about that dust.

Third, sound. For edge detection my favourite evidence is UltraEdge, because it gives a truth beyond the visual. But this sound has a trap too—the sound of ball on pad, the sound of ball on the bat's edge, and the sound of ball on pitch can all occur almost simultaneously. When the third umpire separates these sounds, he really becomes an audio engineer. In my notebook I call this work 'the trial of sound'.

Fourth, the economics of intervals. This part is the most neglected. Drinks breaks, tea, stumps—these intervals are not mere rest; they are a trade in attention. In my notebook I have seen a pattern: in the two overs immediately after a break, the number of reviews rises. Because after a break both batter and bowler start recalculating, and new calculation means new error. I keep this claim as a hypothesis, and I test it against the full over-by-over tally, because a connection between a break and a review is not the same as proof.

Fifth, those two seconds. What is the time between the earpiece and the raised arm? It is not the time to watch the technology—the technology was already shown. It is the moment of revision before the verdict is announced. In this time the third umpire is alone with himself. To me this time is a language whose grammar is uncertainty and whose broken grammar is confidence. Silence for ninety minutes can explain more than a thousand replays, and the silence of two seconds is the most eloquent of all.

Sixth, the third umpire's room. I have never seen this room from inside, but I have heard it from outside. Two or three people are there—one operates the technology, one watches the score and the law, one keeps communication. A team makes the decision, but one person announces it. The blame goes to a name, while the work belongs to a team—this mismatch is the biggest ethical gap in the umpiring system.

Seventh, the interaction of over-rate and the stop clock. Since the stop clock began, a new pressure has appeared—the umpire must keep time, and in keeping time, sometimes the fine calculation of a review is rushed. I do not have a full season of data to say this, so I write it as a caution, not a conclusion: the pressure of speed is the enemy of accuracy, and cricket is now swinging between the two.

Eighth, the roar of the crowd. This is my favourite evidence, because it is the most unreliable, yet the most honest. When it is out there is a roar, when it is not out there is a roar—both. So the roar is not really a reaction to the decision; it is a reaction to expectation. In my notebook I do not log the roar as a decision; I log it as mood—to understand which team broke at exactly which moment.

Ninth, let us walk through one match, as a hypothesis. Suppose in the thirty-third over a batter goes for a drive, takes an edge, and is caught at slip. The on-field umpire is not sure, looks up, and sends it to the third umpire. The third umpire first checks UltraEdge—is there a sound? If there is no sound, he will not go to ball tracking, because it did not touch the bat. If there is a sound, he checks whether it came from the bat, the pad, or the ground. This whole task happens in six to eight seconds. And in those six seconds the fate of a team is decided.

Tenth, suppose in the same innings, in the forty-fourth over, there is an LBW. The batter reviews. Ball tracking shows the ball hitting the stumps, but a part of the projection falls inside the margin. The result: umpire's call, the original decision stands. The batter shakes his head, someone says something from the dressing room, the commentator says 'unlucky'. Yet the actual event is that technology honestly admitted its own limit, and the spectator read that honesty as failure. Here is the junction of emotion and rule.

Eleventh, these two cases—catch and LBW—together form a structure. A catch depends on the combination of sound and sight; an LBW depends on the combination of geometry and margin. In the first, the question is 'what happened'; in the second, the question is 'what would have happened'. In the first, the truth is in the past; in the second, the truth is in the future. When a system judges two truths—past and future—in the same room, error is inevitable; and admitting that error is its strength.

Twelfth, a reckoning from my own notebook. Sixty-four matches taught me that one spreadsheet is never enough. Because a spreadsheet captures outcomes, not process. If I write only 'review successful' or 'review failed', I lose those two seconds where the real story lives. So I have now added a new column to my notebook—'the pause before the arm goes up', measured in seconds. So far this column speaks more than all my other columns.

---

Contrarian angle: Why we ask the wrong question

When a spectator gets angry about a review, he is really angry about the outcome. But if I judge the process instead of the outcome, the picture flips. A review can fail in a perfect process, and succeed in a weak one. The process tells more truth than the outcome, because the process is repeatable and the outcome is not.

A second reversal: a review is not a gamble, but teams play it like one. My notebook says that when a team has only one review left, it becomes far more careful, and when it has two, it spends unnecessary ones. In other words, the quality of a review depends not on the team's confidence but on how much it has left. The accounting of a limited resource is the real strategy—and it is the least discussed strategy.

A third reversal: criticism of umpire's call. Many say the half-ball margin should be reduced, otherwise technology loses its very purpose. But I disagree. Reducing the margin means trusting the estimate more—an estimate that is itself uncertain. A technology that shrinks its room for error does not move closer to truth, it moves closer to confidence. And cricket's history says confidence breaks faster than truth.

A fourth reversal: home advantage. In my notebook I have glimpsed a hint—at home, the rate of taking reviews is higher, and the success rate slightly higher too. I do not press this claim, because my sample is small and my method limited. But if it is true, it is not a question of technology; it is a question of psychology—because the same technology cannot give different results in two grounds, but the crowds and the confidence of the two teams can.

---

Instead of a conclusion: Looking forward

If I had to write the essence of this whole notebook in one sentence, I would write: cricket's biggest decisions are made in the room least seen, and their results appear on the screen most seen. The distance between these two places is my eight years of work.

What may come next? I expect one change: if, beside the third umpire's decision, the count of seconds and the type of evidence—sound, sight, or tracking—were also shown, then spectators would learn to judge the process rather than the outcome. This is not a change of technology; it is a change of transparency. And more transparency does not reduce anger, but it changes anger's address—which is good for the game.

I leave one question behind. When a review returns to umpire's call, do we really believe the system knows, or do we only want the system to be certain, so that we can be certain ourselves? The answer to this question lies hidden in the two seconds of every review, silently, just before the arm goes up.

--- Root: Referee