Fourteen Frames of Evidence: How DRS 'Umpire's Call' Is Rewriting Match Outcomes

What caught my attention over the last five Test matches is that umpire's call decisions are swinging matches without any clear error by the official. This piece digs into the mechanics behind that.\n\nOn Saturday night, the third day of the Bangladesh-Sri Lanka Test in Mirpur, an LBW review came in. The ball pitched outside leg stump, impact in line, but the projection showed the ball hitting middle and leg. The on-field umpire had given it not out. On review, ball-tracking said it would have hit, but umpire's call kept the not-out verdict. The batsman survived. In the next over he scored 42. The match turned. This scene is not new, but each time the same question returns: is DRS actually reducing errors, or shifting the centre of decision-making from the umpire to the tracking software? Let us pull the law card. Clause 3.6 of the ICC Playing Conditions says 'umpire's call' means that when ball-tracking projection proves the ball would have hit the stumps but there is doubt about impact position or pitching line, the on-field decision stands. The key point here is that DRS is not really a decision-overturning machine, it is a margin-of-error preservation machine.\n\nI was on a Dhaka studio panel on 16 June 2026 for France versus Australia, and I counted the first VAR-awarded penalty in World Cup history, which lasted three minutes and twenty-six seconds. From that day I began keeping a review clock for every televised match. I brought that habit into cricket after the 2026 World Cup. In Bangladesh's domestic circuit, the variance in on-field umpiring standards is still so wide that the rate of umpire's call differs from the international norm. My own ledger has the numbers for 38 reviews from the 2026 Dhaka Premier League, and 19 of them stood simply because of umpire's call. That means half the reviews were wasted on decisions where the technology told the truth but the law protected the umpire. This is where the real arithmetic hides. In November 2026 I was frame-stepping a review from the Bangladesh-New Zealand Test in Sylhet. The ball pitched outside off, impact in line with leg. Tracking said the ball would have grazed the outer edge of the stump. Umpire's call. The batsman was not out. But on the very next ball he was LBW to a sliding delivery that no review could have saved. At the end of the match it became clear that the innings, and the match result, would have tilted one way if only that fifth-stump ball could have been declared out. This fact is not a mere incident, it is a pattern. From January to December 2026, in Test cricket, 47 percent of all LBW reviews ended with umpire's call preserving the decision. That data comes from ESPNcricinfo's review log. In ODIs it is 38 percent, in T20Is 29 percent. The rate is higher in Tests because uncertainty about the pitching line and trajectory is greatest in the longest format. Now the question is why this number is so high, and what it means.\n\nFirst, one must understand how ball-tracking works. Cameras determine the ball's position frame by frame, then build a projection based on the trajectory. But between the frame just before the ball hits the pad and the frame in which the ball is inside the pad, the model has to interpolate a small gap. The uncertainty of this modelling is recognised in ICC documents as the 'margin of error', calculated at a 50 percent confidence interval. The final guideline for umpire's call states that if more than 50 percent of the projection lands on the stumps, the decision stands, and if it is below half, it is out. In this sense DRS is not a court of objective truth, it is a probability calculation where the burden of decision-making is left on the umpire's shoulders. Batsmen now weigh two things before taking a review: the impact line and the pitching line. But the biggest error I have seen comes with the height of the ball. In many reviews, the ball would have hit the stumps, but how much of the ball's top was above the stump is not clear from the camera angle, so umpire's call stands. In February 2026 in Chattogram, an ODI between Bangladesh and Pakistan had precisely this type of review. Ball-tracking said the ball did not clear the stump height, but the on-field umpire had given it not out. Looking at the side angle of the camera, the pitching line looked doubtful. So umpire's call. Pakistan eventually lost by 4 runs. In this match, the outcome of one review meant ten overs of momentum, that batsman's strike rate, and in the end the match result.\n\nNow to the truly audacious question. We have so far assumed that umpire's call preserves consistency. But my numbers suggest that consistency is holding up so often that the burden of decision is slowly shifting from the umpire to the software, and the umpire is becoming a somewhat indecisive character. Of the 38 domestic reviews in 2026, in 11 the on-field umpire's decision was clearly wrong, but technology said the decision would stand. In those 11 cases, what really happened? A batsman's career changed, a team's runs changed, but there is no explanation, no accountability. We are spending hundreds of reviews every year to protect an umpire from his own accountability. The other side will argue that without umpire's call the number of small errors would balloon, the game would slow down, reviews would run out. That argument is correct, but it does not mean the current definition of umpire's call is the best solution.\n\nThere may come a time, in fact it should come today, when the DRS system replaces umpire's call with a 'review panel' arrangement, where three umpires decide frame by frame, just as cricket extended the strike zone. Currently DRS gives only an opinion based on ball-tracking projection, and the entire burden falls on the umpires. But in every other international cricket decision where clear evidence is absent, there is a panel system. Why not for LBW alone? Economics is the barrier. Each review costs roughly five thousand dollars for ball-tracking service, camera angles and the second timer. In the Bangladesh Premier League last year there were 147 reviews, costing about six hundred thousand dollars. All of this spending now goes only to preserving the boundaries of a decision, not to making the actual decision. Yet in football VAR, video review by a referee panel is now standard. In cricket the picture is reversed. Here technology is actually making decisions harder, not easier. That is the curiosity, that is my core observation.\n\nThis trend is most pronounced in Bangladesh cricket. Umpiring standards in our domestic league are inconsistent, so the rate of umpire's call differs from the international standard. ICC statistics show that in 2026 the average rate of umpire's call in Tests worldwide was 47 percent, but in Bangladesh's domestic first-class cricket the rate is 52 percent. That means our reviews are failing in more cases. The reason is clear: we have not yet been able to install the number of cameras required at the stadiums for ball-tracking. At the Mirpur pitch last season, ball-tracking was done with four camera angles, whereas ICC guidelines require eight. As a result the frame calculation remains incomplete, the margin of error rises, and reliance on umpire's call also grows. What cricket's stakeholders actually need is transparency in the decision itself, panel management, improvement of angles, but none of these is discussed as the root cause of the review controversy. The discussion only covers wasted reviews, changed fortunes of two teams, and the familiar bitter sentiment. What the scoreboard says is the truth, the rest is the arithmetic of frames.\n\nFourteen frames can change a habit, but cannot change a tradition preserved for a hundred years. Behind every big decision in cricket are walls of law, protocol and calculation. The threshold for changing a decision, between the declared outcome of DRS and the number of umpire's call outcomes, has not changed year over year, it is only being documented more. The statistics of this Test Championship will end, but the question around umpire's call will not stop, because every review video placed before us is like a question mark: who made the decision, technology or the umpire? Where the question is born, the decision actually begins.