When the Light Lies: Decision, Camera and the Archive of Silent Bias in Cricket's DRS Era

It is 2:40 AM in an edit suite in Mumbai. I let my tea go cold and loop the same sequence on screen - how much the ball deflected off the pitch, how much it wobbled in the air, and how many millimetres it had entered before striking the pad. What the camera captured is clear. But what the camera left out - that is the subject of this piece.

Over the last few weeks, whenever I opened my own logbook from 2026 and looked at the DRS controversies flooding Indian fan feeds across recent Test series, a pattern emerged. A controversy almost never begins with 'was the ball out or not'. It begins with 'where exactly was the line drawn'. In other words, the question is not about the verdict. The question is about the data pipeline.

I went back to the 2026 VAR log to see what the broadcast missed. Across 64 matches and 29 reviews at the Russia World Cup, the central lesson was singular: the frame from which a slow-motion replay begins often carries more power than the final decision itself. In cricket, that power is even larger - because whether the ball touched the boundary line, and what it did before pitching, both depend on the same footage.

Before I was selected in India's first VAR certification programme in March 2026, I had spent twelve years as a professional footballer in the I-League and eight years as a match official. The first lesson of that course was restraint about technology - certification does not mean certainty. In 2026, I learned that certification is not the same as certainty. Today, when cricket debates 'UltraEdge', 'Snicko' and 'ball tracking', that line returns.

A clarification before moving further. Cricket's Decision Review System (DRS) welds three distinct technologies together - ball tracking, sound-based edge detection, and visual replay. Each carries a different confidence level. Ball tracking predicts the trajectory, but if the ball seams after pitching - what we call 'late seam movement' - or deflects off the surface, a pocket of uncertainty opens inside the prediction model. In the ICC playbook this is called 'pitch-to-pad trajectory tolerance' - practically a 20 to 25 millimetre uncertainty buffer.

Now to the real work.

The reviews that have generated the loudest noise across recent Test matches, I sorted by type - exactly the way I built my 47-slide 'The VAR Ledger' in 2026. Four categories emerged: one, 'appeal-driven reviews' - taken under pressure from a bowler or wicketkeeper, where the fielding side itself is not certain. Two, 'broadcast-driven reviews' - where the captain, watching the big screen, thought the replay would work. Three, 'system-triggered reviews' - where the umpire himself refers, knowing his first decision could be wrong. Four, 'protocol reviews' - where system rules mandate verification because a milestone is at stake.

Across these four, my scorebook shows the highest rate of 'out'-turnover in category three - where the umpire himself initiates a review. This naturally raises a question: how much of the gap between the umpire's original decision and the system's final decision is cricket-reality, and how much is technology-uncertainty?

An acoustic-evidence empiricist needs a caveat right here. The confident on-air claim that a 'tick' was heard on stump mic often places trust in the wrong place. Edge detection works within a specific frequency band, at a specific sampling rate. If synchronisation is two frames late, or compression compresses that 'tick', or ambient crowd noise covers the band - the system cannot say anything. But a commentator sitting before a camera can, because they are 'assuming'. This 'assuming' versus 'verifying' distinction - that is where my greatest discomfort lies.

On micro-margins, one question returns constantly: how many millimetres inside off stump was the ball? When DRS graphics show 'ball tracking', the viewer sees a clean visual - the ball heading in a straight line to the stumps or not. But behind that visual there is a statistical confidence interval, called within tracking systems a 'trajectory confidence bond'. In practical convention, the line drawn on a DRS map carries roughly 15 to 25 millimetres of uncertainty. This means that a ball three millimetres inside off stump will be called 'stumps hitting', and a ball on the boundary will trigger 'umpire's call' - yet in both cases the viewer believes everything is precise. The answer is not precise. It is probabilistic.

I think about this uncertainty in two different ways. One borrowed from football - where VAR does not intervene under the 'clear and obvious error' standard, because the convention is no interference without clarity. The other from cricket - where 'out' and 'not out' are binary, and DRS insists on preserving that binary even while standing on probability's ground. This contradiction is hidden, because admitting it weakens the system's core appeal - the narrative of 'precise technology'.

Now to the contrarian note nobody wants to strike.

Everyone says 'technology has made umpiring more just'. I would say technology has made umpiring more accountable - and accountable is not the same as just. Accountability means every decision has a written reason behind it. Justice means all sides are judged by the same standard. DRS does not guarantee the second, because the standard's core calibration - ball tracking algorithm, stumps-hitting prediction - is trained on a specific track, a specific camera configuration, a specific session dataset. Different venues with different camera angles mean a different confidence bond. The same ball, the same pitch, at two different grounds, can produce different outcomes. This is nobody's conspiracy. It is a system-design limitation never shown on screen.

I am used to this type of analysis, because my core work is verifying the data pipeline before, during and after play - who is inputting what data, how it is being processed, where errors enter the output. The same logic applies to the transfer market: the 'young player premium' everyone is now discussing tells the same story. When a club spends over 100 million euros on a player with fewer than 50 top-flight appearances, it is the football-culture version of cricket's three-millimetre-off-stump problem. Trust in prediction over long track record. Aggressive but immature modelling.

Behind this enormous system-trust lies a financial logic nobody states openly. Cricket boards now sign deals with data-vendor systems, tying into tournaments, B2B media and sponsorship contracts. DRS's brand-dependence means public doubt about technological accuracy collides with the board's commercial interest. In football, with club IPOs - where fan emotion is monetised and financial reporting pressure often sidelines footballing decisions - we have already seen that path. In cricket, the same direction is visible. Critical voices are not silenced; only their platform is recalibrated.

So the question becomes - what is the path forward?

I see three levels, none of them about blaming individuals, all of them about system design. First, adding 'uncertainty disclosure' to DRS output. Every ball-tracking decision should carry a small confidence interval shown to viewers - much like a '70% probability' on a weather forecast. Second, a change in commentary protocol: commentators should not present the system's estimate as final verdict, but should make the divergence between system estimate and umpire decision explicit. Third, a long-term 'decision audit archive' for cricket - where each season, every review is re-verified and venue-wise system-performance data is published. This was the core lesson of the 28-page decision audit I submitted to FIFA's Asian development archive back in 2026 - and cricket still does not have it. The integrity of the game sustains itself when the system is unafraid to acknowledge its own weakness.

One final point - for those still believing technology equals neutrality. Remember, the camera sees light, but understands nothing. What UltraEdge captures is a frame; what we see on screen is human judgement sitting on that frame. The silent distance between them - uncertainty, calibration, venue-bias - is the real character of today's cricket controversy. Next season this debate will grow, because the number of decisions is growing, while honest conversation about the confidence behind decisions has not yet begun. Until it does, I will open my logbook again, and count - what the broadcast left out this time.