What We Misread About Umpire's Call: Ball-Tracking, Soft Signals and the Dark Side of Cricket Data

What We Misread About Umpire's Call: Ball-Tracking, Soft Signals and the Dark Side of Cricket Data

An evening at Mirpur's Sher-e-Bangla. The spinner releases, the batter pushes forward, the ball pitches and turns in. The on-field umpire raises his finger. The batter reviews. On the giant screen the projection appears — the ball is grazing the inside edge of the stumps. The announcement comes: "Umpire's call, out stands." The crowd roars, social media erupts. Some say the match was robbed; others say the umpire was bought. Yet what the screen showed was not wrong. The error was in our eyes, our expectations, our illiteracy in reading data.

From my 52 years of watching the game and my years running Referee's Eye since 2026, I will say this plainly: umpire's call is nobody's personal mistake. It is a deliberately designed margin — an acknowledgement of ball-tracking's own uncertainty. Yet after every review we blame precisely that margin. Let us go to the tape, slowly, and let the frame speak.

To understand the context, we must first accept a truth. Technology entered cricket not to replace the umpire but to assist him. DRS was trialled around 2026 in Sri Lanka-India series and became permanent from 2026 onward. Ball-tracking, Hawk-Eye, Snicko, Ultra-Edge are different instruments with different error profiles. Ball-tracking does not predict the future; it predicts a probability. Around that probability sits a confidence interval, projection trials, pitch friction, air speed and camera frame-rate.

This is where my favourite analogy lives — football's VAR. At the 2026 Russia World Cup VAR was used for the first time, and there were 29 reviews in total. By my own count, 17 of those 29 overturned the on-field decision. France versus Australia's 58th-minute penalty for Griezmann remains the most debated frame of that series. I followed all 29 reviews remotely from Chattogram and wrote a 12-part series, "VAR and the Death of Referee Intuition." It was shared 8,000 times. The reason was simple: people were only beginning to learn that technology does not make decisions, it reveals the information behind them. Cricket's DRS teaches the same lesson, more quietly.

Recall my 2026 database. When the Bangladesh Premier League was cancelled during the pandemic, I watched 500 match tapes from 2026-2026 and, using my economics background, built a database of 1,200 refereeing decisions, each tagged by law, minute and outcome. That database taught me an uncomfortable truth: umpire's call is the least discussed and most misunderstood decision in the game.

Umpire's call is not a verdict; it is a measured acknowledgement of uncertainty. When ball-tracking shows the ball hitting the middle of the stumps, that is a certain out. But when the projection shows the ball grazing the very edge, the system itself is saying: I am not certain. That uncertainty band is usually taken as half the width of the stump. Only if the ball strikes more than half the stump is it treated as certain. On the very edge, the decision returns to the on-field umpire. That is the protocol.

Watch a soft-signal incident frame by frame. The third umpire first goes with the on-field soft signal, then sees a spike on Ultra-Edge — but the spike is pad, not bat. The decision is overturned. Who is at fault? Not the soft signal; it was the most reasonable estimate at that moment. The fault lies in interpreting the spike, in the weight of the evidence. Here is my core observation: we often keep every step of the process correct and still arrive at a wrong decision, because each step carries a different uncertainty, yet we add them together as one.

Snicko, Ultra-Edge and ball-tracking have different frame-rates. One runs at 300 frames per second, another at 340. The instant the ball touches the bat may fall between two frames, and that is when a spike is missed or misread. For ball-tracking, the number of cameras, calibration accuracy and pitch condition together determine projection reliability. In 2026 I wrote my first explainer citing IFAB Law 11 and the 2026-17 Laws of the Game; in cricket the same idea applies — every decision must be tied to a specific law or playing condition, otherwise it is just emotion.

My 2026 Qatar analysis of Morocco's 4-1-4-1 low block was a turning point. Morocco conceded only one open-play goal in five matches, because referees allowed an average of 14 tactical fouls per match without cards. Morocco's 38 percent possession survived on that lenient foul threshold. The same logic holds in cricket: if a spinner bowls slowly and the umpire relaxes the rules in the name of the "spirit of cricket," the result is set by the umpire's tolerance, not the player's skill. I wrote then about semi-automated offside, which averages 25 seconds per check, and called it a new variable in match control. Cricket's third-umpire system is exactly such a variable.

Now consider the contrarian angle. We all assume umpire's call exists to protect the umpire. The data says otherwise. In my database of 1,200 decisions, across the cases that ended in "umpire's call," the on-field decision was in fact correct in a large share — because wherever the margin fell, the decision lay in the uncertain zone, and in that zone the on-field umpire's position is generally more consistent with the ball's line. In other words, umpire's call does not protect the umpire; it protects the system's limitations.

The second error we make — we often read home advantage as umpiring bias. Yet when I run consistency tests between home and away teams on my logged decisions, the difference comes mainly from crowd pressure, review psychology and captaincy quality — not umpire intent. I apply the same frame-by-frame test to Bangladesh decisions and to neutral ones, because my referee's eye does not depend on partisan loyalty.

The third error is subtler. We assume better technology means fairer decisions. The lesson of the 2026 World Cup's 29 reviews is that the problem of review design is larger than the problem of technology. VAR's first rollout was criticised most for protocol ambiguity — uncertainty over who intervenes and when. The same applies to DRS: who reviews, when, and how certain the third umpire must be before overturning — those rules are the real game-changer.

This is where the dark side of data enters. The very ball-tracking data shown on screen — finer and faster — is streamed live to betting companies. I have long argued that the darkest side effect of sports datafication is live data flowing to betting firms. And this is where blockchain becomes relevant. Imagine a public, immutable ledger where every ball-tracking projection, every confidence interval, every third-umpire decision is recorded with a timestamp. The argument might not shrink, but the question would change — who got the data, when, and where it went.

Technology does not deliver transparency; transparency must be earned — and the first condition is verifying the truth of the data. An immutable ledger can do exactly that: prove a data point was not altered later. But there is a trap here too. Blockchain proves authenticity, not fairness. If the ball-tracking system itself is mis-calibrated, that error sits immutably on the ledger — appearing more credible, yet still wrong. Technology can immortalise an error; it cannot correct it.

In my personal style guide I follow one rule: every claim must be tied to a specific law or precedent. Another rule — no anecdote counts as evidence unless supported by at least 50 logged decisions. That discipline turned my writing from emotional match reports into forensic legal analysis.

Now let us lift our eyes from the tape and look forward. My proposal is simple, in three steps. First, publish a public data trail with every third-umpire decision, including confidence intervals, so fans can see where the decision was uncertain. Second, release ball-tracking calibration reports before the match for everyone. Third, impose clear controls on the commercial use of live officiating data — especially toward betting markets. Do all three and the roar over umpire's call may not fade, but at least the question will be the right one.

The question is this — do we really want fairness, or do we want a decision in our favourite team's favour? My 52 years tell me most debates are not about fairness but about outcomes. And that is the real danger. For the moment we deliver a verdict before the evidence, we commit a larger error than any umpire — we become judges of a process we have not even read. Let the frame pause. Let the frame speak. And let us listen.