Ball Tracking, UltraEdge and Umpire's Call: Where Does Technology's Boundary Lie on Asian Pitches?

Three frames flash on the big screen, then two words in yellow: Umpire's Call. It is 12 September 2026 at the R. Premadasa Stadium in Colombo, the Asia Cup Super Four. Dunith Wellalage has taken 5 for 40 and broken India's batting order. Every time the ball hits the pad that evening, an invisible distance opens up between the on-field umpire's raised finger and the third umpire's monitor. I was watching two screens at once from my home in London — one showing the broadcast, the other a live fan forum thread. Both were asking the same question: if the ball is hitting the stumps, why is that not out?

That question is cricket's longest-running technology argument. In my 'Ref's Eye' column I keep returning to the frame just before the decision — the moment the ball pitches, the moment it strikes the pad, and the second afterwards when software draws a picture of probability.

Context: a three-layer system built on one estimate

DRS was first trialled in 2026, on India's tour of Sri Lanka. It still works in three separate layers: where the ball pitched, where the impact happened, and where the ball would have hit the stumps. The first two are broadly reliable — a camera frame can measure them directly. The third is a projection. Once the ball strikes the pad, the camera stops seeing it; ball speed, revolutions, bounce and pitch friction are fed into software that calculates which part of the stump the ball would have struck.

This is where Asian pitches become a separate story. Subcontinental surfaces are usually low, slow and spin-friendly. When the ball turns after pitching, the path after impact becomes far harder to predict. A delivery that has turned eighteen inches across twenty-two yards carries the greatest uncertainty over the next twelve. On a seaming English pitch the ball travels almost straight; the estimate is comparatively easy.

The ICC removed the soft signal from 1 June 2026. Previously, when a catch was in doubt, the on-field umpire gave a preliminary decision and the third umpire needed clear evidence to overturn it. There is no soft signal now; if the evidence is inconclusive, the decision goes to the batter. On paper the change is small. In practice it is enormous. It was first tested on a major stage at the 2026 World Test Championship final and that summer's Ashes.

Ball-tracking providers undergo ICC accuracy testing every year. The detailed error margins from those tests never reach the broadcast. Viewers see only the final image — pitch, impact, wickets. The uncertainty in between stays invisible.

Core: rolling the tape back, frame by frame

Roll the tape back to the moment before the decision. After the ball leaves the hand, the first thing required is the point of pitching. The tracking graphic shows a small red dot. Depending on camera angle and ball height, that dot can shift by two or three centimetres. For spinners that centimetre is decisive, because the ball enters from outside the line and turns in — move the pitching point slightly and the entire projection changes.

The second layer is impact. Bat, pad, ground — which came first? This is where UltraEdge comes in. A stump microphone picks up vibration and draws a graph. The problem is that a bat striking the ground or the pad also produces a spike. On broadcast we often see a narrow spike while the commentary says 'bat first'. But the strength and the timing of that spike must be read together. When bat and ball meet in the same frame, the technology cannot give a clean answer.

My first contentious observation: UltraEdge is not a truth machine, it is a sound timeline. The resolution of that timeline is finite, and cricket decisions are made in milliseconds. Where two events occur in the same frame, the technology shows probability, not certainty.

The third layer, the wicket projection, generates the most argument. The system shows how much of the stump the ball would have covered. If more than half is covered, the decision is out. If less, but the ball still clips the stump, the on-field decision stands — umpire's call. The ICC's logic is straightforward: the projection's error margin is wide enough that, on borderline calls, the human on the field should be respected.

The logic is honest. The problem is communication. A viewer sees the ball hitting the middle of the stump, then the result comes back 'not out'. Nobody explains why. During the 2026 Asia Cup I ran a poll in a fan forum — roughly two-thirds of respondents said umpire's call simply looked like 'out' to them. The poll is not evidence, only a picture of the mood. But that mood tells you exactly where the explanation is missing.

Where technology's limits begin

Asian conditions add another pressure on ball tracking — the amount of spin. Say the ball turns three degrees off the pitch instead of two. That cannot be measured directly; it has to be inferred from revolutions and surface friction. The rate at which spinners took wickets in the 2026 Asia Cup tells you how much of the tournament's decision-making rested on inference. Wellalage's 5 for 40 and Kuldeep Yadav's 5 for 25 are not merely bowling records; they are evidence of how the pitch behaved.

On 10 and 11 September 2026, again in Colombo, India beat Pakistan by 228 runs in the Super Four. Kuldeep took 5 for 25, Virat Kohli made an unbeaten 122 and KL Rahul made 111. The reviews from that match have been debated ever since. For me a different measure mattered: how long the third umpire took on average. Several complex calls ran past ninety seconds. For those ninety seconds, twenty-five thousand people in the ground and millions on screens were waiting. Technology delivers the decision; the waiting is done by people.

That leads to the second big question: transparency. The ICC tests provider accuracy every year, yet the results never appear on broadcast. We see the final image, not the error margin behind it. That is inconsistent in a data-driven age. A system that can shape a career on a one-and-a-half-centimetre projection should not keep its own margin of error hidden from the public paying for it.

In the final on 17 September 2026, Mohammed Siraj took 6 for 21 to skittle Sri Lanka, and the match ended inside ten wickets. There was little controversy that night because the decisions sat well clear of the boundary line. That is the real lesson: arguments happen at the margins, not in the clear cases. The flaw is not in the system's centre but at its edges.

Contrarian: rules against emotion, and technology's false promise

There is a counter-truth here that technology critics tend to skip. What would happen without the system? Before 2026, an LBW decision rested on one pair of eyes — eyes running at the speed of the ball, from a viewpoint that was never ideal. The review system broke that monopoly. Players now have a route to appeal.

The real error is not in the technology but in our expectation of it. We assume more cameras mean more certainty. That assumption is wrong. Every new angle supplies new information, and new information does not always deliver new certainty. Sometimes it multiplies the argument.

On 14 July 2026, the World Cup final at Lord's. The ball deflected off Ben Stokes' bat to the boundary, and the umpires awarded six runs when the correct award was five, because the batters had not crossed. The match turned on an arithmetic error. No extra review or extra camera would have helped there; what was needed was a clearer law and its correct application.

Similarly, the arrangement that put all of India's 2026 Champions Trophy matches in Dubai was never a technology question — it was a tournament-planning question. Technology measures decisions on the field, not structural advantage built off it. When fans use the word 'unfair', they are talking about the whole apparatus, not one review.

Acknowledging a mistake and branding someone a culprit are two different jobs. An umpire got it wrong — that can be said. An umpire acted unjustly — that cannot. Likewise, technology is limited — that can be said. Technology is pointless — that cannot.

Takeaway: what to watch from here

Two things are worth watching over the next two years. First, whether the ICC publishes ball-tracking error margins. If it does, the explanation of umpire's call becomes far easier for viewers and needless anger drops. Second, whether broadcasters put a short reason on screen alongside the final image — a fifteen-second explanation can sometimes prevent a thirty-minute social media storm.

Technology has not made cricket flawless. It has put cricket in front of more transparent questions. That is its real contribution.

What do you think — should umpire's call survive, or should everything on the borderline go entirely to the machine? Your answers will shape my next column.