Three and a Half Centimetres: What the DRS Ledger Keeps Off the Screen

That night still carries a yellow mark in my ledger. A knockout match of the T20 World Cup, two overs left. A leg-spinner released the ball, the batter was struck on the pad, and the on-field umpire shook his head — not out. The fielding side reviewed. Ball-tracking returned to the screen, predicting the ball would have hit leg stump. How much of it? Two words appeared on the big screen: Umpire's Call. The decision stood. The batter stayed at the crease, and the match swung the other way.

I froze the frame and wrote in my ledger: under three and a half centimetres. The ball would have struck the stump, but less than half the ball's diameter would have landed inside the stump zone. The law says that is the umpire's call. The man standing in the middle kept his verdict. Nobody won, nobody lost — a prediction engine simply stamped a human decision.

I went back to the ledger, and the story changed.

DRS entered international cricket in July 2026, with the India–Sri Lanka Test at Colombo. Back then it was called the player review. Seventeen years on, the system rests on three pillars: ball-tracking, UltraEdge for edge sound, and the third umpire's screen room. Tests, ODIs, T20Is — two unsuccessful reviews per team per innings in every format. On paper, everything is in order.

The problem is not in the numbers of the law. It is in the gaps of the law.

The phrase 'umpire's call' operates in two different places. The first is ball-tracking's wicket projection: whether the ball would touch the line of the stumps, and if so, how much of the ball falls inside the stump zone — the imaginary line running along the inside edge of the stumps. If less than half the ball's diameter lands inside that zone, the tracking returns 'umpire's call', meaning the on-field verdict stands. The second is the pitch-impact threshold for spinners: if impact occurs more than three metres from the stumps, the prediction loses reliability, and the umpire's call applies there too.

Both rules sound reasonable. On paper. To the person standing in the middle, they are a comfort. To the person watching the screen, they are a discomfort. Because the screen never shows the threshold itself.

Who operates the technology is the central question here. The ICC writes the playing conditions, but ball-tracking and UltraEdge setups generally sit with the rights-holding broadcaster. Camera frame rates, camera counts, calibration schedules — none of this appears in detail in the match-referee report, and none of it reaches the ordinary viewer. So the audience sees a verdict, not a process. And a system without a visible process can lend a decision legitimacy, but not belief.

Football has touched exactly this nerve. In Russia, I watched the screen become a second referee. At the 2026 World Cup, VAR's debut produced a then-record 29 penalties, with 17 on-field decisions overturned. For three weeks I catalogued every review by camera angle, duration and outcome. My table settled on an average review time of 82 seconds. The question sits there — in those 82 seconds, what did the referee see, who selected it, and why was the viewer shown a different picture?

In cricket, DRS runs roughly a decade ahead of football. But on the ledger of accountability, cricket still trails.

Across the 55 matches of the last T20 World Cup, I logged every review on a separate sheet — which innings, which over, who reviewed, what the appeal was for, what the outcome was, and how many seconds the decision took. My ledger filled with 79 reviews. Of those, 31 were overturned and 48 stood. Among the overturned, 22 were lbw, and eight of those turned directly on the ball-tracking prediction.

The first crack appeared right there: prediction errors cluster in the places where the ball's line changes sharply and the bounce is irregular. Slow, low pitches, leg-spin, and the T20 staple of the pace-off cutter — exactly where cricket is now played most.

The second crack is UltraEdge. The sound technology shows a spike, but whether that spike belongs to bat or pad is a human decision. When selecting the frame, the third umpire typically has a window of five to seven frames. Shift that window by a single frame and 'bat first' becomes 'pad first'. The result of the match does not change, but belief does.

The third crack is the largest, and it is procedural, not technological. Impact frame, impact projection, wicket projection — the three layers ball-tracking passes through, none of them shown live. The viewer sees a small animation of the final prediction. That is not a crime, only an incompleteness. But that incompleteness breeds conspiracy in the stands.

I went back to the ledger, and the story changed. When I sorted those 79 reviews without prejudice, I found overturned reviews averaged 94 seconds, while reviews that stood averaged 67. Where decisions are simple, things move fast; where they are complex, they drag. That is good news. The bad news is that nearly half of the reviews taking more than 90 seconds occurred between the 17th and 20th overs — exactly when the match's pace matters most.

A human point needs making here, or the arithmetic goes cold. The umpire in front of the camera is a person. He stands for four hours at 55 metres, sometimes sees the same ball six times, sometimes sees it wrong. If an on-field decision is wrong, he knows his name will be in the scorecard the next day with an asterisk beside it. DRS has protected him, and blurred him at the same time. A system that removes an umpire's room to err makes him dispensable — and yet the accountability for the decision still sits on his shoulders.

If I sat in the match referee's chair, I would change three things. First, a ball-tracking calibration report filed to the match referee at the end of every session — not a confidential document, but a certificate for the equipment. Second, the UltraEdge frame window and spike timestamps shown on broadcast, even at the cost of ten extra seconds per decision. Third, review data published at the end of every tournament, exactly as match-referee reports are published.

The Russian experience taught me that technology is not the guilty party; ownership and transparency are. Football's loudest VAR criticism was never about wrong decisions, but about why the viewer spent ten minutes not knowing what was happening inside the room. In cricket, DRS carries the same risk. The shield is simply turned differently: in football the viewer distrusts the referee, in cricket the viewer distrusts the owner of the ball-tracking.

Now the argument that is unpopular in cricket circles. After nearly every tournament, a call returns: abolish umpire's call and let the prediction be final. Sorry — that will not reduce error.

The reasoning is simple: the calibration is the same, the frame is the same, the engine is the same. Abolishing umpire's call does not erase the error, it only hides it. Two new problems arrive instead. First, a ball travelling six centimetres outside the stump will be ruled a hit by a one-centimetre margin — and that will not be a decision from the field, but from a mathematical model with no umpire's name attached. Second, spin reviews would effectively stop, because without the three-metre limit spinners would appeal and review almost every length delivery. The match would keep its reviews and lose its cricket.

The real reason for the backlash is searched for in the wrong place. Viewers rage at umpire's call because they read it as cowardice. In reality it is the only point in the process where a human name survives. Removing umpire's call hands the machine power without handing it responsibility. And power without responsibility is the actual problem.

My sense is that within three years this argument will no longer be about the limits of a decision, but about the disclosure of a process. Because the cricket viewer is no longer like the football viewer of 2026 — they are used to VAR posts, multiple camera angles, time stamps. A sport that publishes its scorebook will, one day, publish its ball-tracking calibration log.

I am 80 per cent confident that within the next two World Cup cycles the ICC will be forced to release review data as a small public log — average review time, overturn rate, the percentage of umpire's calls. That would be proven wrong if broadcasters block calibration data behind a claim of commercial confidentiality. The question then would remain: where does the screen end, and where does the game begin.

Discipline, I learned, is a ledger, not a mood.