The Limits of Pixels, the Gaps of the Eye: The Quiet Failures of Cricket's Review System

The screen in the third umpire's booth never lies outright, but it never tells the whole truth either. A review arrives; the soft signal's answer hangs in the air; the raw line of ball-tracking flickers to life; and the person inside the booth has to deliver a verdict within seconds, sometimes on a foundation of pure inference. I have watched this moment for seventeen years — first as a player, then from outside the boundary, and finally as a referee analyst. The same lesson returns every time: where there is no information, a decision stops being a decision; it becomes a guess, and we mistake that guess for a verdict.

This piece is not about any single scorecard. It is about the system that claims something larger than a scorecard — the claim to deliver a final verdict on truth. And that claim is what is being tested here.

The System That Admits Its Own Uncertainty

Cricket's review system, the DRS, began in 2026, as a trial project during the India–Sri Lanka series. Nobody then imagined that within twenty years a white line, a snickometer spike and a ball-tracking projection would determine everything from match results to a player's career. The architecture is simple: an umpire's decision can be challenged a limited number of times; the television umpire verifies it using limited technology; and where the evidence is not "clear and obviously wrong," the on-field decision stands.

This is the first legal subtlety. The DRS is not a truth machine; it is a reconsideration process. Its goal is not to catch every error but to correct clear errors. The lawmakers knew technology had limits, so they left room for probability. The umpire's call provision is the result: if ball-tracking shows less than half the ball hitting the stumps, it is treated as the on-field umpire's call, even though the projection reads "out." This is not weakness; it is humility. A system that can admit its own uncertainty is the one that is actually reliable.

The internal mechanics of an LBW review seek answers to three questions: did the ball pitch in line? Was the impact in line? Was the ball hitting the stumps? Uncertainty in any one of these three stages throws the decision into doubt. I am always struck by how much controversy a simple three-question structure still generates — because each answer carries its own small uncertainty within it.

I learned this lesson directly in 2026, explaining the first VAR penalty decision at the Russia World Cup — where technology screams "handball" while the law says "check whether it was deliberate." Cricket has the same tug-of-war, only the language differs. In 2026 the ICC abolished the soft signal, because it became clear the on-field umpire's instinct was influencing the evidence. This is the true shape of system reform: when you see the process itself manufacturing outcomes, you change the process.

The Geometry of Ball-Tracking: Cones, Frames and Room for Error

It is essential to understand the geometry on which ball-tracking stands. Cameras capture a set number of frames per second; the system identifies the ball's position in each frame; it then joins them into a mathematical curve to estimate the future path. Note the word — "estimate." The projection is not truth; it is a probable path with a cone of uncertainty on either side. If the ball is right at the edge of the stumps, the width of that cone determines the decision. Yet the ball we see on television is often drawn at a single, precise point — as if no doubt existed.

Here is the first gap: the audience never sees the projection's uncertainty, only the final line. So the system appears far more confident than it actually is. At the Qatar World Cup I spent eighteen hours building a three-dimensional model from twelve camera angles on one goal-line question — my editor called it overkill; I called it the only way to see the law clearly. In the same way, if cricket showed ball-tracking's uncertainty cone on screen, half the umpire's call debate would never have been born.

The second gap is camera perspective. Ball-tracking cameras are fixed in place; along the path from bowling crease to stumps, the ball, the pad, the batsman's leg — any of these can occlude the view. The system then infers from other frames. And snicko-edge or ultra-edge detects a sound spike, but stadium noise, bat-on-pad friction, even a spectator's sound can leak in. I have seen many times a ball showing a spike in one frame and none in the next.

The third gap is calibration. Every stadium's camera setup is different, its pitch height different, its light different. A projection that is flawless at one venue can shift a few centimetres at another. This venue-dependent variation is rarely fully acknowledged by anyone — player, broadcaster, or official.

The camera's perspective and the human's perspective are never the same — and the difference is the real story.

Human Limits: Reaction Time and the Pressure of the Field

We talk most about technology's limits, but the system's weakest part is often the human. The on-field umpire must decide within a window that sometimes approaches the natural limits of human reaction. When a bowler delivers above 140 kilometres per hour, the ball reaches the stumps from the pitch in less than the blink of an eye. In that time, the umpire must reconcile line, length, the point of pitching and the batsman's foot position — all at once.

In 2026, during the era of empty stadiums, I ran a project on this human limit. During lockdown I logged forty-seven umpiring errors, and found that the silence of an empty ground changes the character of decisions — in some places the umpire over-cautious, in others unusually hesitant. From that experience I began using a "pressure matrix" and writing in the language of probability: "the umpire had roughly a sixty-two percent chance of giving this" — rather than any absolute claim. It makes the writing slower, but honest about uncertainty.

Here is the second great gap: we write about technology's limits, but human limits — reaction time, occlusion, fatigue, pressure — are often left out of the calculation.

An overlooked aspect of this human limit is the person who initiates the decision. A review is requested by a player, within a set time window. But the player sees from a position standing beside, close to the pad — his perspective is also limited. So the roots of a decision carry two layers of uncertainty from the start: what the player saw, and what the umpire saw. Technology adds a third layer of uncertainty; it does not resolve it.

The Broadcast Interface and the Fog of Officiating

The greatest danger in analysis is treating the model as cleaner than the field. The flawless cone of ball-tracking, the clean spike of snicko-edge, the three-dimensional projection — these can make it seem as if deciding is a machine's job. But on the field there is always a "fog of officiating": rain, dew, differences of light and shade, water on a camera lens, and the biggest one — the absence of time. Analyse without that layer and it stops being analysis; it becomes imagination.

The broadcast interface is itself a decision-shaping instrument. What is shown on screen, which angle is held for how many seconds, at which moment the replay is paused — these editorial choices shape the viewer's perception. The same event in two different broadcasts can seem like two different truths, because the sequence of cameras and cuts differs. Working in television analysis myself, I learned that the most controversial decisions are often born of a single dropped frame — nobody noticed, because everything looked smooth on screen.

So in every referee analysis I separate three layers: first, what the law demands; second, what the technology or umpire could actually see; third, what nobody saw — and that is the real story. The whistle is never the story; the angle that missed the whistle is. This structure has guided me since I analysed Victor Moses's simulation controversy in 2026, and even today I write the law, the minute and the camera angle first in every piece, and my opinion after.

The hardest step of this three-layer structure is the third. Because there I must admit I do not have the answer. In an analysis that is the most uncomfortable sentence — "the evidence here is insufficient." Yet this sentence is exactly what makes an analysis credible, because it shows the writer values truth over the verdict.

Emotion Versus Law: Why We Demand Verdicts the Data Cannot Give

Now to the most uncomfortable part. Our reaction to umpiring controversies is almost never legal; it is emotional. The stands, the commentary box and social media shout together "that was out" or "that was not out" — while nobody mentions the uncertainty cone of ball-tracking, the camera's perspective, or reaction time. We want a clean verdict, because a clean verdict comforts the mind. Uncertainty is uncomfortable, and so we deny it.

But here lies the danger. When information is insufficient, the only way to give a clean verdict is to make something up — and that is the greatest sin of analysis. I could have fallen into this trap, had my working method not changed after 2026. From that year I began writing probability and confidence ranges behind every decision. So sometimes, in place of a clear verdict, my writing carries only a sincere "there is not enough evidence."

This humility is not weakness. Rather, a journalist who can answer every question should not be trusted on those answers. A review system is the same — if it never says "insufficient evidence," it stops being a verification tool and becomes a spectacle.

There is a subtle but important distinction here. I do not confuse humility with neutrality. Humility does not mean refusing to answer every question; it means giving a clear verdict where there is evidence, and stating clearly where there is none. When the balance between the two breaks, analysis becomes either overreaching or weak.

My hardest days are those when, after a big match, an editor wants a sharp headline, and I sit down to write and find — I have no real information. Then there are two paths: fill it with inference, or honestly say the foundation is insufficient. I have chosen the second path, again and again, even though it has made me a slower, less productive and far more uncomfortable writer.

Forward: Fewer Verdicts, More Evidence

Cricket's review system and its analysis both stand at a crossroads. Technology will grow more precise, systems like semi-automated offside will make more decisions, and the human role will recede further. But the more technology advances, the more essential it becomes to admit its limits. The broadcaster that shows the uncertainty cone of ball-tracking on screen, the journalist who writes a confidence range beside a verdict, the umpire who can sometimes say "I am not certain" — they are the ones who will keep this system credible.

From my seventeen years of observation one thing can be said with confidence: a game that hides its limits loses the audience's trust; a game that shows its limits endures. The next version of the DRS is not really a competition to add more pixels to the screen — it is a competition to admit the limits of those pixels. And in that competition, the winner will be whoever, before giving a verdict, knows how to ask humbly: do I really have enough information?