The Monitor's Truth: DRS in Asian Cricket, 'Umpire's Call' and the Audit Log of Decisions

On the big screen at the pavilion, the last frame of ball tracking froze on the inner edge of the stump, and a line appeared above it — 'Umpire's Call, decision stands'. Thousands in the ground raised their hands, then stopped together. The decision did not change. My notebook entry for that night began with a single line: the monitor does not lie; the angle does. At 62 I still watch every week with a stopwatch and a notebook in hand. On the first page sit seven points — angle, offence, point of contact, speed, offside line, restart, communication. In 2026, while building the Premier League VAR pilot log at Stockley Park, those seven points were my toolkit; average review time there fell from 84 to 52 seconds. Coming to cricket, I found the principle identical but the language different. What football calls a 'clear and obvious error', cricket has turned into an odd doorway called 'umpire's call'. DRS first took the field in July 2026, in the Test between India and Sri Lanka at the Sinhalese Sports Club in Colombo. In those early years, the fiercest tug-of-war over the system was inside Asia — some argued technology would eat the umpire's authority, others that ball tracking was unreliable on grass. Sixteen years later the picture has reversed: subcontinental spin-friendly pitches, low bounce and immense crowd pressure have made Asian cricket the hardest laboratory for DRS. Ball tracking is easy on a green European pitch; it is hard on a turning track in Sharjah or Chennai. The technology stack matters. Hawk-Eye handles ball tracking, using six cameras to trace the ball's path and predict its future one. UltraEdge detects edges through microphones beside the stumps, reading the sound wave. Some venues add Real-time Snickometer and HotSpot. The higher the slow-motion frame rate, the more precise the point of contact — but no camera 'understands' the gap between bat and ball by itself; it only shows pictures. Humans do the interpreting. This is where the law arrives. Under Law 36, an LBW needs the ball to hit the stumps, the contact to be inside or outside the pitch, and the ball to strike bat or pad first. Ball tracking answers these three inferential questions, and precisely there 'umpire's call' is born. 'Umpire's call' is really a tolerance threshold. When the ball clips the stump by only half its width, the system says the evidence is insufficient, so the on-field decision stays. That threshold is not hidden, but it usually hides from the viewer, because the screen shows only 'out' or 'not out' — the grey zone in between is never displayed. In 2026 the ICC abolished the 'soft signal', effective from June. Previously, if a catch was in doubt, the on-field umpire gave a soft indication, and if the third umpire lacked proof, that indication survived. With the soft signal gone, the logic simplified: either there is evidence, or there is none. But simplicity has a price — the burden of proof now rests entirely on technology, and when technology hesitates on low bounce, both viewers and umpires are left helpless. I applied the seven-point checklist to cricket and drew each caught-behind review as a decision tree. First branch: did the bat touch the ball? The answer comes from UltraEdge — spike or no spike. Second branch: did the ball hit the ground? Here the game of frame rate and angle plays out. Third branch: were the fingers under the ball, or had the ball already touched grass? That question still belongs to humans, not machines. On the third umpire's screen, six to eight angles often open at once. One angle shows fingers under the ball; another shows a slight gap. The slower of the two is not always the truer one, because moving the camera position moves the trap of light and shadow too. Three main causes of long reviews recur in my log: an ambiguous angle, a small gap between ball and hand, and a mismatch between speed and frame rate. The predictive part of ball tracking is the most contentious. After the ball pitches in front of the stumps, its path is inferred from the data of the previous few metres — that is a forecast, not a measurement. Slight bounce on grass, the position of the seam, air pressure — any change shifts the forecast. Some say the error is three to five centimetres, others less. Whatever the number, the question is one: is it right to cover a three-centimetre uncertainty with a binary 'out' or 'not out'? On Asian turning tracks the problem deepens. When a spinner releases the ball, it floats, kicks, and dives in front of the stumps. When the ball bounces twice, detecting the second bounce becomes difficult, and the batsman's pad position shifts within half a second. That is why LBW reviews take longer on subcontinental grounds than on European ones. Another note sits in my book — empty stadiums made the audio protocol louder than any crowd. Reviewing 92 matches behind closed doors in 2026, I found that without crowd noise the gap between the referee's whistle and the signal rose by 0.8 seconds. Applying that to cricket: without disciplined communication, however good the technology, decisions slow down. 'Check complete', 'on-field decision stands' — these phrases are not just words, they are time-saving instruments. Now to the uncomfortable part. Much of the anger over 'umpire's call' in Asian cricket is not against technology but against uncertainty. The crowd wants certain truth; the law gives a disciplined process. Standing in that gap, 'umpire's call' does something odd — it protects the on-field umpire while telling the viewer the evidence is incomplete. So a safeguard sometimes breeds suspicion. There is another gap. The tolerance threshold of ball tracking is not drawn the same way in every tournament — generous in one series, strict in another. Players question this inconsistency openly, yet the number itself is never stated publicly. In my view this concealment is DRS's biggest weakness, bigger even than the accuracy of the technology. Here I make a simple demand that some may already be considering. Cricket needs an immutable ledger of decisions — much like a blockchain record, where every review's frame, time, angle and tolerance threshold is written permanently and no one can alter it later. What is missing today is transparent accounting; the general viewer cannot know why any 'umpire's call' was reached. The transfer market has offside lines too; you just cannot see them — just as many limits inside DRS are invisible, visible only if you read the decision log. Until that log is public, every contentious review will end in resentment rather than a conclusion. From Russia, with a remote desk and a five-second delay — as I learned at the 2026 World Cup, the speed of a decision and the truth of a decision are not the same thing, and Asian cricket is now learning that a flawless screen cannot replace an incomplete law. Looking ahead, I want three things. First, the tolerance threshold of every 'umpire's call' should be shown publicly on the ground screen. Second, a single standard for review time limits and frame rates should apply across all formats, so the rule is the same in Tests and T20s. Third, every review should have a permanent, immutable log that umpires, players and viewers can all check together. Because in the end the question is not of technology but of trust. If the viewer knows how a decision was reached, they will forgive a decision that goes against them. And that is what the Referee's Eye truly seeks — not the monitor's truth, but the transparency of the decision.