Slow Motion Does Not Lie, But It Does Not Tell the Truth Either: Re-Examining That Asia Cup Review

The review appeal came in the 43rd over, and the moment the umpire raised his hand, I logged the time in my diary. The decision in this Asia Cup fixture arrived in about three-quarters of a minute, but it took spectators three days to digest it. What I have is not the television cut but the scorecard and the protocol. And by protocol, the call was lawfully sound — but cricketing-wise, wrong. That distinction has been the most muddled thing in today's debate.

In a tournament like the Asia Cup, every over carries a nation's emotion behind it. This was a group-stage match where the win-loss column directly shaped the route to the semi-finals. In such fixtures, the review is not just a mechanism of the rulebook but a weapon of psychological pressure. When in the 43rd over the ball struck the batsman's pad and the fielding side appealed, the on-field umpire said 'not out'. The captain reviewed. The third umpire watched for two and a half minutes and overturned it.

I need to clarify something that disappears from common discussion. Under the ICC review protocol, the third umpire has the authority to overturn an appeal only when the evidence is conclusive — that is, when one of 'out' or 'not out' is clearly right. Language like 'largely' or 'probably' has no place in the protocol. This is where slow motion reveals its true nature. Slow motion does not remove doubt; it gives doubt a timestamp.

I have sat around this chair for 45 years. From Doordarshan replays to ball-tracking and now ultra-motion, the technology has changed, but the umpire's dilemma has not. The question is not what the camera shows; the question is which frame the camera shows. The monitor in front of the third umpire freezes on one frame. In that frame, the ball is striking the pad — but the fifty frames before and after are not shown to anyone. This is 'freeze-frame inflation': we want to read both intent and guilt into a single picture, when that picture is only a moment, not the whole story.

The ball-tracking report in that review showed 'impact in line', and the wicket collision was within 'umpire's call'. This detail matters because it is where cricket's law and cricket's reality diverge. By protocol, if more than half the ball is hitting the wicket, the decision should be overturned. But 'more than half' does not mean the ball was going fully onto the wicket. It is the mathematics of 'probability', not 'certainty'. The third umpire treated the mathematics as proof, and this is where the decision moved beyond pure procedure to influence the cricketing call.

Writing this, I remember the Wankhede of 2026. In the Ranji final, that short-leg catch decision was 'not out', and after stumps I walked to the umpires' room — to read Law 32 for twenty minutes. At the time I thought that if I understood the law properly, the decision would clarify itself. Thirty-five years later, I know that is half a truth. The law can be clear; the application of the law is never clear. The third umpire has the same dilemma, only with a better camera.

Here comes the angle no panel raises. After that review, the fielding side's bowler broke his spell over the next two overs — this won't show in the scorecard, but the delivery-by-delivery sheet I keep alongside the scorecard shows that after that over, both his line and length changed. The fastest jolt is not the one that hits the stumps; it is the one that hits a review. A decision does not change a match's tension, but it certainly changes the fine balance within a match. This is the thing that cannot be closed by saying 'the decision was right'.

On the other side, the batsman did not challenge the decision — that too is worth reading. If the batsman knows the ball hit the bat before the pad, he should have no complaint even after the review. But his silence is not proof that the decision was right; it only shows he knew the review would be shaped by the freeze-frame, and no further argument could be made on the field. There too, the law favoured the visual over the intent.

Seen from the umpire's perspective, this whole episode is a game of numbers. The third umpire has to choose whether the evidence before him is 'conclusive' or 'insufficient'. When ball-tracking shows both 'impact in line' and 'hitting within umpire's call', the most correct procedure would have been to hold the appeal as 'not conclusive' and preserve the on-field decision. But the protocol also contains the phrase: 'If ball-tracking shows impact in line, the umpire has the authority to overturn.' The difference between 'authority' and 'obligation' is exactly what tilted the decision towards overturning in that review. This is not a procedural error but an error of procedural interpretation — and this is what should be added to third-umpire training.

I spent eleven nights with the CBI report in 2026. In those nights I learned that 'data' and 'evidence' are not the same thing. Among the matches listed in the report, there were two where the fixing window and the over sequence did not match. The number that seemed to fit on paper did not fit in actual sequence. I removed both claims. No one outside the desk ever knew. Today, when I look at that review's ball-tracking, the same lesson returns: a number that 'fits' is not necessarily 'true'.

There is another professional aspect that matters greatly in this context. In India, the real subject of cricket journalism is the board, not the player. Every BCCI decision — selection, training, or a change in review protocol — should be recorded with a date, a rule, and an outcome. When we talk about reviews, we often forget that the responsibility for improving the review protocol also lies with the board. If the board does not clarify the definition of 'conclusive evidence' in third-umpire training, the same debate will return in every tournament. And the debate returning is fine — but starting it with 'the decision was wrong' or 'the decision was right' is wrong. The question should be: did the umpire have the evidence the protocol calls 'conclusive'?

This is the same 'lawful versus right' distinction that should be separated in every report. Was the review correct per process? Yes. Was it correct per the spirit of the review, which implies correction of 'clear error'? Perhaps not. The answers to both questions are different, and merging them into one sentence makes the debate not complex but useless.

I have another perspective that comes from outside. I grew up in England, but for several years now I have been sitting in India watching Indian cricket. From this distance, one thing is clear: the Indian viewer treats the review not just as technology but as a means of justice. So when the third umpire 'sees' something in slow motion and overturns, the viewer treats it as 'technology's victory'. But that is not technology's victory; it is the victory of technology's interpretation. Explaining this difference is the journalist's job, not the panel's. The panel makes noise; the journalist logs time.

One scene from that night I will never forget. After that Asia Cup match I was sitting in the press box, and beside me was a young photographer who sat quietly for hours. The Eden Gardens night of 2026 was similar — I filed until 11:40 p.m., and that photographer also sat quietly because the route to the team bus was closed. I never wrote about him in the copy. Some things do not make it into the report, but they shape the report's perspective. I still sometimes see that young man on social media, and wonder how he remembers that night's decision.

There is both a consolation and a warning here. The consolation is that technology has made the umpire's decision more transparent than before — today a viewer can see the same replay the third umpire sees. The warning is that transparency and fairness are not the same thing. Behind the screen, fairness is a habit, not a headline. That habit must be developed in training, in the interpretation of protocol, and in the way board decisions are recorded.

Looking at the rest of this tournament's road, I suspect this debate will not end here. Every review in the knockouts will be weighed with emotion, and every decision will have someone hunting for an 'if'. My advice is direct: the next time you watch slow motion, first ask what was there in the frame before and after. And if there is no answer, accept that the law may have made the decision, but cricket may have lost its balance.

Finally, a question not just for the board but for all of us: when a review takes 2.5 minutes in an over, are we respecting cricket's uncertainty in those 150 seconds, or erasing it? I have the date logged, but the answer is still pending.