The Truth Between Two Frames: Cricket's Silent Umpiring Balance Sheet in the DRS Era

For four weeks I kept a separate notebook beside the scorecards of Tests and one-day matches. I called it the Referee Decision Ledger. For every review I filled three columns: the on-field umpire's position, the number of ball-tracking frames, and the last image shown on screen before the verdict. Nine matches, fifty-seven reviews. Twenty-four of those fifty-seven survived inside the safe harbour of "umpire's call". The technology raised a hand, but the last word was spoken in a human voice.

The scorecard never records this part. It records outcomes, not process. Yet the biggest controversies of modern cricket are born inside that very process. Rewind the tape; the truth usually hides between two frames.

Context: The birth of a technology

DRS entered international cricket in July 2026, in a Test between India and Sri Lanka. In its first year India refused the system. The reason was not technical doubt but institutional caution. One group of players feared the review would create a crisis of trust in the umpire; another feared the technology itself was biased. That same year the ICC fixed the rules: two failed reviews per innings, returned if successful, lost if not.

The interesting point is that DRS never arrived as a "truth machine". It arrived as an "evidence machine". The distinction is subtle but decisive. Evidence means showing what can be seen; truth means determining what actually happened. Evidence never equals truth, because evidence too has a perimeter, a margin of error.

How many frames per second ball-tracking captures changes with the broadcaster. One camera records fifty frames a second, another a hundred. When the ball pitches and changes direction, what happens between two frames no camera sees — the software estimates it. Estimation means a model, a model means an assumption, and an assumption means an acknowledged margin of error.

That margin of error is written into the laws as "umpire's call". If less than half a ball's width enters the stumps, the on-field decision stands. Some call this a flaw. I call it honesty, because a technology that knows its own error does not steal the decision — it shares it.

Core analysis: three frames, three questions

Every review divides into three frames. Frame one — did the ball pitch in line. Frame two — did it hit bat or pad. Frame three — would it have hit the stumps. Uncertainty in any one of the three throws the whole verdict into doubt.

In frame one the problem is shadow. In late-afternoon light a ball's shadow is larger than the ball. If the camera angle comes from fine leg, the shadow may fall outside the pitch while the real ball is inside. The software is forced to guess. Eleven of my fifty-seven reviews stalled exactly here — not in leg-before logic, but in shadow.

In frame two the problem is sound. Snickometer or UltraEdge catches noise, but the stadium may hold the scrape of bat on pad, a shout, or wind. A sharp spike is not always proof of the bat's edge; sometimes it is a pad strap. This is why the "soft signal" exists: an umpire unsure of himself keeps his call light so it can be overturned on review.

In frame three the problem runs deepest. The ball is tracked from pitch to pad, then the software extrapolates the path to the stumps. This extrapolation breeds the most dispute. How much the ball spins after pitching depends on pitch moisture, the seam position and wind speed. No model captures all three perfectly. So a ball that would have hit the stumps may drift outside in the model — or the reverse.

The umpire's sightline: the ledger's most neglected column

Before I entered the Ambedkar Stadium press box in 2026, I filed six matches from Row 14 of the stands. There I learned one thing: a decision is made not only by where the ball is, but by where the umpire stands. A few inches of movement means part of the ball disappears from his sightline.

Modern cricket never records this column. Ball-tracking shows where the ball was, but not whether the umpire could see it. Yet the law's idea of a "clear error" depends on the on-field call. The real question should be: did the umpire err, or did he simply not see? Those are not the same thing.

The balance sheet: who gains, who loses

An education in economics teaches one habit — every rule hides an incentive. Ask who benefits. With DRS the answer is not simple.

For the batter, the benefit is a second look. For the bowler, the benefit is that ball-tracking may fall his way on a wicket call. But both face one condition: the fear of running out of reviews. That fear shapes strategy mid-match. To save a review for the last over, a batter may skip a review on a clear error — and that error turns the match.

This behaviour contradicts the spirit of the game. The rule was built to increase accuracy, but it became an asset to be hoarded. When accuracy becomes a limited resource, players review for advantage, not for correctness. My ledger shows the success rate of reviews in the last ten overs is lower than in the first ten. The cause is not a lack of courage but a narrowness of calculation.

Contrarian angle: umpire's call is not a flaw

One side of the debate says umpire's call is dust in the technology's eye — the technology knows the ball would hit the stumps, yet the law keeps the on-field call. I say that argument is emotional, not arithmetic.

Imagine umpire's call is abolished. Every marginal lbw verdict then rests on the ball-tracking estimate — an estimate with a known margin of error no one denies. The decision would move from a human eye to a machine's guess, and that guess is also imperfect. What is gained? Only an illusion — "the technology said it, so it is true."

The real problem is not precision but consistency. If a batter knows a marginal ball always goes the same way, he can play to that rule, just or unjust. But in practice the same kind of ball is out one day and not out the next. That inconsistency breaks a player's trust. So the question is not whether the technology is right, but whether it behaves the same way every day.

Environmental context: shadow, weather and soil

A game is never played in a vacuum. Environment manufactures the conditions for decisions. In a morning session, dew not yet dry, the tracking model may behave differently. In an evening session under artificial light, shadow sharpens and frame-two decisions shift.

So before I call any umpire biased, I log four things: pitch, light, moisture, and the frame-rate the broadcaster uses. I start with a null hypothesis, then look for proof. Only if the same umpire gives different calls in the same conditions do I consider a pattern. Pattern and proof are different things; confusing one for the other is journalism's biggest trap.

My own position: why I watch from outside

I was born in Bangladesh, work in Delhi, and write cricket for the India market. I treat that distance as method, not detachment. Inside a market, that market's blind spot can enter your own eye. So I keep the ledgers of two markets side by side, so one does not become a mirror of the other.

I admit my notebook of fifty-seven reviews is not an official document. After the 2026 I-League, the federation returned my forty-column ledger marked "not an official document". I published the full ledger anyway, with methodology. My argument was simple: a document not being official does not make it false.

Not a conclusion, but a question ahead

Cricket stands at a threshold. Technology improves fast, ball-tracking grows more precise; yet the laws still lean on old concessions — the half-ball margin, two reviews, the soft signal. If technology is truly perfect, why keep umpire's call? And if technology is not perfect, why keep it at all? The future of the whole system hides in the answer to those two questions.

Next time ball-tracking rises on the screen, do not watch the scorecard — watch which frame is shown before the verdict. Rewind the tape; the truth usually hides between two frames. And to finish the arithmetic, in the end the ledger is all we can trust.