Umpire's Call and the Spike in the Ear: What Actually Happens in DRS's 71 Seconds

The sound of ball on pad reaches the ear before the finger goes up. The stump mic catches only a short "no" — almost bored. Then the turn towards the captain, the T-sign, and the third umpire's voice: "Check the front foot, please." That gap is where my work actually lives. Across four seasons I have logged the duration of 212 reviews — the clock stops on the appeal and restarts on the announcement. The average is 71 seconds. The longest ran 3 minutes 47 seconds, on the third day of a rain-hit Test, while the Snicko archive refused to load.

The verdict was never the story for me. I understood my own knee only after counting 118 decisions, and cricket handed me the same question in a different shirt — where was the official standing before anyone was given out, and what could he actually see from there. I do not argue with review outcomes. I audit how the review was produced.

DRS entered Test cricket in 2026, not on a wave of faith in technology but through an experimental ICC decision. The Laws of Cricket contain no clause called "umpire's call"; it is a compromise inside the DRS protocol. Two reviews per innings in Tests, one in ODIs and T20Is. A successful review is retained, a failed one burns. In 2026 the ICC abolished the soft signal, meaning the third umpire no longer begins from the on-field official's guess but owns the decision outright. That sounds minor. It rearranges who holds authority.

From outside, the process looks like a three-step animation: pitching, impact, wickets. Inside, three separate evidence streams run in parallel, each with a different margin of error.

The first stream is ball tracking. Hawk-Eye does not show the ball's future path; it estimates one. A mathematical model is built from recorded frames and then extended to the pad. The further the ball pitches from the point of impact, the wider the projection band. That is why deliveries clipping the edge of the stumps generate so much argument — there the model's error margin and the physical stump geometry touch each other. Almost every review that ran long in my ledger involved a ball pitching well away from the pad. The technology was not slow. The uncertainty was.

The second stream is sound. An UltraEdge spike speaks through its shape as well as its presence. Bat and pad arriving almost together produce one thick spike; pad alone produces a thin one with no sharp flick before it. In the clips I have replayed most, the third umpire's phrasing gives the process away — "nothing on UltraEdge" and "there is bat, and pad as well" point the decision in different directions. This is also where errors creep in: crowd roar, the bowler's own footfalls, even the thump of ball on stump bleed into the same channel. Sound is not proof. Sound is a lead, and it misleads unless triangulated against the scorecard and the positional note.

The third stream is position. Where the umpire stands decides what he can see. Bowling over the wicket from the bowler's end puts the sightline almost parallel to the pitch, which makes height at impact easy to read but shifts the angle on the leg side for a left-hander. That is why some lbw calls sound impossible from the field and reasonable on review. I do not trust a pattern until it survives three different angles — the on-field official's once, the third umpire's screen once more.

Read together, those streams reframe the famous lbw at Headingley in 2026. Ben Stokes was given not out off Nathan Lyon; Australia had no reviews left, so the technology was never called. Ball tracking later showed the delivery would have hit the stumps. The decision did not belong to the technology. It belonged to the arithmetic of review retention. In a match where a side fails to bank its reviews, the technology never sat in judgment at all.

That is the real fracture. A review is no longer an instrument of justice but a finite resource — closer to a timeout than to a trial. Teams hoard them for the final session and refuse to spend them on a new-ball spell. The question shifts from whether the technology is correct to who is permitted to use it.

The crowd's roar belongs to that arithmetic too. The roar arrives when the three-step animation ends, and it does not match the law — people see the ball strike the stumps and think out, even when umpire's call keeps the on-field verdict alive. Umpire's call is not a rule protecting accuracy; it is a rule protecting the on-field official's authority, an administrative decision dressed as a measurement.

Sixty-four matches taught me that one spreadsheet is never enough. My numbers show average review duration rising, and reckless reviews rising with it. But a number alone says nothing. You have to say who lost what in those 71 seconds.

The next reform will be about time and display, not accuracy. Review durations should be published, a hard ceiling should exist, and the big-screen animation should stop running before the third umpire speaks. The question is small: if the technology really is right, why is the job of making people believe it given to the screen rather than to the official?