The Third Umpire's Shadow: DRS, "Umpire's Call" and the Accountability Gap in Cricket

Hook: One Ball, Two Decisions, Three Seconds of Silence

The yellow ball flashes past the red line on the big screen. Then the round shadow dips just inside the stump, covering barely half a ball's width. Two words appear in large letters: UMPIRE'S CALL. The stadium splits in a single instant — a roar of frustration on one side, a sigh of relief on the other. I am at my Rangpur desk, thumb on the stopwatch. The review began at second zero; the decision arrived at second eighty-seven. What happened in those eighty-seven seconds, who saw what, who made which call on which frame — that is the least-discussed, least-documented chapter of this game. I started the VAR-Log because Dhaka taught me, on those Mirpur evenings under the floodlights, that the gap between what a spectator sees and what an umpire announces is where the drama lives and where accountability quietly evaporates.

Context: How DRS Arrived, and For Whose Benefit

DRS did not arrive in a single day. It was first trialled in the Sri Lanka versus India Test in July 2026, as a bundle of three technologies: Hawk-Eye ball tracking, Hot Spot thermal imaging, and Snickometer audio analysis. India initially refused to accept it, arguing that cameras and tracking systems would err and would, in turn, undermine the on-field umpire. That board-level split was the original politics of DRS.

By the 2026 and 2026 World Cups, DRS had spread. The ICC made it mandatory across certain tournaments while many bilateral series were played without it, because two boards had to consent. That instability is itself the story: the same delivery, the same frame, the same screen, yet a different outcome because the law of the series differs. I began mapping this practical inequality with an approach I call Rule-Instability Cartography — an audit of how cricket shifts its rules across tournaments, formats, and venues.

The legal core of DRS is complex. Each team receives a set number of reviews — two in Tests, usually one or two in limited-overs, with variations in T20. To review is to challenge the umpire's call. If the review confirms the umpire was right, the team loses the review. This rule is called Retention. Beyond it lies Umpire's Call — the principle that if the projection or the impact on the stumps is only marginally uncertain, the decision remains with the on-field official.

In legal language, Umpire's Call is a benefit of doubt granted to the on-field official. The question is who decides how much doubt justifies that benefit. The answer: the ICC Cricket Committee — former players and match referees — advised legally and technically by Hawk-Eye engineers. The decision therefore does not belong to the game's central actors; it is the product of cricket's committee hierarchy. When a Mirpur crowd howls at Umpire's Call, it is cursing a committee it cannot name. This is precisely why my columns never simply blame the umpire. I ask first: on this frame, what does the tool say, and what law tells us to trust it?

Core: The Frame-by-Frame Anatomy of a Review

Frame Zero: The Trigger

Picture a Test's second day. A pacer fires one at leg stump. The batter pads up. The on-field umpire rules NOT OUT in a fraction of a second. The batter stands, bat in hand, certain he was right. But within a second, the team decides whether to review. This is the first accountability gap: the review decision belongs to players and management, yet their information base is incomplete. Who is watching the top angle? Who is watching Hot Spot? The players do not know. A coach in the pavilion sees partial ball-tracking on a tablet, never the whole picture. A review is therefore near-blind — a coin toss between hope and information. I start my stopwatch here, but first I accept one immutable truth: the seconds of a review decision are the most political, most uncontrolled seconds in cricket.

Frame One: Ball Tracking

After the trigger, the review reaches the third umpire, where Hawk-Eye reconstructs the ball's flight from multiple cameras and projects it mathematically to the stumps. The hard question: tracking occurs as the ball pitches, and a ball's speed and trajectory change through pitch and bounce — how accurate is the projection? Hawk-Eye publicly asserts accuracy, yet the model carries uncertainty, and the size of that uncertainty defines the Umpire's Call margin.

A ball is roughly 3.5 inches wide. The Umpire's Call boundary is commonly half a ball — about 1.75 inches. Where does 1.75 come from? From an imaginary line through the centre of the stump, with half a ball on either side. In the tracking system, any projection within half a ball of the stump centre falls under Umpire's Call. This is a technical boundary, not a political one — beyond it, the system cannot say with certainty whether the ball would hit. I call this boundary the 1.75-Inch Parliament, because it is the product of technology, law, and politics deciding jointly.

Frame Two: Pitch, Impact, Projection

An LBW review carries three separate data points that people wrongly merge: where the ball pitched, where it struck the pad, where it would have gone. The first two are usually treated as certain because cameras capture them directly. The third — the projection — is a model, an estimate, a probability. Yet the projection is the most decision-driving element, while its uncertainty is the least visible. On screen it appears as a simple line — a straightforward stroke the viewer trusts because a line implies no room for error. Behind that line sits a mathematical model, a camera calibration, a bounce model, each with its own error tolerance. My stopwatch tells me the model computes about once a second, while frame-by-frame footage typically runs at fifty frames a second or more — meaning more information exists than the model consumes. That asymmetry is the hidden defect no camera catches.

Frame Three: Camera Angle and Shadow

The camera angle is the most neglected variable. Hawk-Eye projects from a camera behind the stumps and then projects that onto the frame from a camera in front. If the optical axes of the two cameras tilt even slightly, the ball's shadow shifts position slightly. Logging reviews from 64 matches in 2026, I saw the same type of frame show the line four inches right, then three inches left — because of camera placement and tracking start points. Here is a brutal truth the crowd does not know: the accuracy of a review depends on which over, which pitch, which end, and which camera was active — logistics. If cricket hands accountability to technology, who owns the accountability for the technology's setup? In legal terms, the answer is unclear.

Frame Four: Ultra-Edge, Snicko, and the Politics of Sound

Edge detection is equally unstable. Ultra-Edge can show whether the ball touched the bat, but the ball moves so fast that a touch can hide between frames — even with cameras running up to 960 frames a second. Across that gap, sound is used. If a Snickometer or stump mic picks up a sound matching the bat, it becomes a probable signal — but the source of the sound (bat, pad, ground, helmet, or crowd) is nearly impossible to separate. Keeping this multimedia rule in mind, I built a trigger list logging the probability relationship between ball contact and sound source. Matching that probability to decisions taught me repeatedly that sound can come from the bat's edge, the handle, or the ground through the stance. To prove bat-on-ball is not a motor reflex; sometimes the sound is actually tape around a sleeve touching the bat. These tiny details shift a decision from 50-50 to 60-40 — enough to flip any review outcome.

Frame Five: 2.5 Metres, 3 Metres, and the Arithmetic of Law

A long-standing LBW rule holds that if the ball strikes the pad beyond three metres from the stumps, and if it pitched outside, the matter falls under Umpire's Call. The rule protects the batter's benefit because, as the ball moves beyond the defence line, its chance of hitting the stumps grows — so that decision belongs to the on-field umpire. But a confusing technical detail persists: 2.5 metres and 3 metres apply to different cases — one to the ball before it pitches, one to the moment of pad impact. So one umpire calls Umpire's Call while another says NOT OUT, purely because the calculation variable differs. The law is not fixed prose; it is arithmetic.

Frame Six: Time

I keep the stopwatch. Across the 2026 World Cup I logged reviews from 55 to 207 seconds, averaging 84 seconds. In those 84 seconds, cricket's rhythm changes — the bowler's rhythm breaks, the batter's focus breaks, the team's tactics shift. A coach glances at another match on a stream. A nearby review decision, arriving almost simultaneously, can become bigger news than the score itself. This human impact is the least-discussed yet most real part of review. As a writer of stopwatch narratives, I see this time in two layers: a spectator's time and a player's time. For the spectator, 84 seconds is a sip of tea. For the player, it is a slice of a professional career. The gap between those two times is the central question of review accountability.

Core: Emotion versus Law — Why the Crowd Feels Right While the Law Differs

Here is the real argument. When a stadium or television crowd sees a large portion of the ball inside the stump, they believe it is out. When the screen reads UMPIRE'S CALL, they feel cheated. Their grievance is clear: they see a truth — the ball hitting the stumps — yet the decision is not out. But the law says truth and decision are not the same. The law says a decision depends on the level of proof. When the probability of hitting the stumps exceeds fifty per cent but is not one hundred, the responsibility stays with the on-field umpire. In other words, the law tells the viewer: you may say the ball hit the stumps, but I cannot say it would hit — because I am still not certain. That grammatical gap is the essence of Umpire's Call.

| Trap | Why It Pulls Me In | Fix | | Over-verification paralysis | An INTP frame-by-frame verifier can keep rewinding indefinitely | Three decisive frames, one rule citation | | Officiating tunnel vision | A Referee's Eye spots errors everywhere, so analysis can lose the human | Pair every officiating analysis with a human consequence | | Rule-instability as theme without account | Mapping contradictions endlessly | End with a named mechanism: who writes the rule, who enforces it | | Archive fetishism | The Dhaka VAR-Log can mystify missing footage | Ask what the archive is for: accountability, access, or reputation |

I draw a comparison. Think of a traffic light. You know red means stop. But if the light is faint, what do you do? Grammatically, the light is red; visually, it is unclear. You may drive on, but the liability is yours. Similarly, when ball tracking is vague about impact, the umpire's call stands and the team loses its review. The problem: a traffic light's faintness is visible to all; ball tracking's faintness is visible only inside the system. The viewer never sees it. This is why law and public opinion diverge.

Confidence Interval: In the Language of Statistics

I use my log to quantify this gap. A review decision quantifies to: the probability the ball hits the stumps, P, and the system's accuracy, A. If P and A both say the ball hits, who decides — the human or the machine? The ICC position: the machine is only an aid; the final decision rests with the on-field umpire. That position rests on faith in the human, but as machine accuracy rises, the faith is questioned. If the technology is ninety per cent accurate, why leave the remaining ten per cent to the umpire? Is that the system's inefficiency, or its flexibility? I do not know the answer, and honestly, neither does anyone. But I understand that until the question is settled, every Umpire's Call will seed controversy.

Core: Cricket's Three Layers of Accountability

Layer One: The On-Field Umpire

The on-field umpire is a worker. The match starts at noon and ends at dusk. He watches, decides, and records. But who records the accuracy of his decisions? In the ordinary picture of the game there is no quantified ledger of an umpire's right and wrong. How many decisions were overturned in a match, how many stood — only the review log shows that, and it is largely invisible to the public. The only witness to umpire accountability is the log, and those logs are rarely made public. I once assumed such tracking occurred. Later I understood: the data exists, but it is enclosed among the MCC, the ICC, and the broadcaster. The on-field umpire relies on that log for his own career, so he cannot publish it himself.

Layer Two: The Third Umpire

The third umpire is not on the field. He sits in a room before a screen showing limited information — a few specified cameras, a clear angle (there is a rule for this: narrow angle first, then broadcast). He decides within seconds, sometimes over long minutes. His decision has no grammar, because what he announces is only OUT or NOT OUT, often without explanation. One question: does his screen hold all the information? Answer: no. He is shown a selected portion of evidence; the rest sits with the producer or technicians beside him. So the quality of the third umpire's decision depends on what the technician chooses to show him. This relationship is asymmetrical, and it is the hidden layer.

Layer Three: The Technician and the System Operator

Hawk-Eye, Ultra-Edge, Snicko — these are private companies. They operate, they store data. But are they accountable for the decision? Legally: no, because the system is a tool. A hammer never bears the guilt of a killing; the striker does. The third umpire wields the tool; the decision is his. But if the hammer strikes the wrong spot every time, the question becomes: who calibrates the hammer? This is why calibration is political. What producers tune shapes the horizon of decisions. Having examined many review logs, I found roughly half a ball's width of difference in stump-line determination between two tournaments. Coincidence, or a tuning decision by operators? I cannot prove it, but I can ask.

Core: The Bangladesh Angle

In Bangladesh cricket, this system carries a specific weight. Mirpur and Chattogram reviews are both technology-heavy and frequently controversial. On pace-friendly pitches, measuring bounce is difficult because the ball's height drops or rises sharply after pitching. In that instability, every Umpire's Call breeds a store of resentment. Sitting in Rangpur, I tried to understand that resentment at home. If a team knows a ball outside leg stump projects onto the stumps, yet is saved by Umpire's Call, it will hesitate to review next time. That hesitation is tactical. Losing one review in a Test's second innings means the first innings' disputed decision is compromised. In Bangladesh matches, this arithmetic often becomes the driving force.

There is another factor: ICC and Asian Cricket Council review quotas are set by tournament. Two reviews in a West Indies series, one in Asia — sometimes only one in a Bangladesh series. This inequality is a cricket-political reality. It should be discussed across Asian cricket, but it is not, because review quotas are set mainly on commercial grounds — broadcast timeframes, ticketing, over rates. In T20 cricket time is precious, so in the ICC's arithmetic, raising or lowering reviews is a game of time, not a game of cricket.

Contrarian: Two Arguments Nobody Makes

Argument One: Umpire's Call Is Actually an Instrument of Freedom

The common thread of controversy is that Umpire's Call is an abuse of technology. But I want to offer an alternative view: Umpire's Call is a safeguard for player freedom. Suppose a team's best batter, in the fourth match of a series, is on nought when a ball strikes his pad with a sixty per cent probability of hitting the stumps. If out were declared with certainty, the batter would never get the chance to review. The decision might favour him, so the review rule grants him leeway — once he can say, at the level of the machine I am in doubt, so I deserve the benefit. This is why the ICC tends to be conservative about widening or narrowing Umpire's Call: it must balance the game against the player. Those who want unconditional automation may not realise that a hundred per cent automated game would leave no room for sympathy and uncertainty — two emotions cricket needs.

Argument Two: The Debate Is Not About Technology, But About Power

My second argument: the Umpire's Call debate is really a debate about power. Who operates the technology, who keeps the data, who draws the line — those are the real questions. If viewers knew who decides, their anger might lessen but their questions would grow. This is why, in my Rule-Instability Cartography, I always write beside the frame: under which law, in which version, at which venue, and who wrote the rule. It is the list of invisible authors whose names nobody speaks.

Takeaway: Who Writes the Next Rule

The future of Umpire's Call in cricket turns on one question: if everyone can see better than the machine, why should the machine's boundary become law? My estimate is three changes to the ICC rulebook within five years. First, review counts will vary — not one per innings, but one per target milestone. Second, the Umpire's Call boundary (ball width) will shrink — today's half will become perhaps a third as machines grow more precise. Third, review-decision data will become public — tracking data, frames, timestamps all visible. That third shift would be the largest, because it would open a new era of accountability. Cricket's history has always kept power in secret — where rules are written, by whom, for whose benefit. If tracking data become public, power disperses rather than hides. This change would not damage the game's pace or integrity; it would build mutual trust between spectators and players. The most painful gap in my own log remains this: I do not have quantitative ball-tracking data, because it never reaches my hands. I see only television frames, then I think. For twenty-five years, that thinking has been my work. But if tonight's match produces another Umpire's Call controversy, I will log it in my spreadsheet — frame number, ball width, decision, time. Because I know that the day this log can be opened to the public, nobody will simply curse; they will ask who drew this line, and why that answer was ever the best available — the least-discussed sentence in cricket, still unread.