From Ball-Tracking to Bookmaker: The Missing Audit Trail of Review Data in Asian Cricket

From Ball-Tracking to Bookmaker: The Missing Audit Trail of Review Data in Asian Cricket

One Clock, Three Versions

November 6, 2026, Arun Jaitley Stadium, Delhi. Sri Lanka's innings is in progress; Sadeera Samarawickrama has just been dismissed. Angelo Mathews walks to the crease, and at that exact moment the strap on his helmet snaps. He signals toward the dressing room and asks for a replacement. Minutes later he is out — timed out. The first such dismissal in the 146-year history of international cricket.

That night I opened my ledger, and my attention was not on Mathews. It was on a number — two minutes. The question was simple: who was counting those two minutes? The clock burning on the giant stadium scoreboard, the countdown running along the bottom of the television feed, the clock on the scorers' desk — were all three showing the same time? Did the clock the third umpire used to reach his verdict have any mechanism of review?

It did not. Cricket now has review for the ball, review for the body, but no review for time at all. This piece is about that gap — and about where the data generated inside that gap travels every single day.

A Law That Waited Forty-Three Years

The phrase "timed out" entered the Laws of Cricket in the 2026 code, as Law 40.1.1. Across the following 43 years, and across 140 years of Test cricket, no batter was ever dismissed under it — not in ODIs, not in T20Is. The law sat in the book and nobody called on it. In 2026 it was called on, mid-tournament, in the middle of a points-table squeeze.

Among the things cricket has lost in those 43 years is the innocence of time. A modern one-day international runs on several clocks at once. Fifteen seconds of review window after the ball goes dead, inside which a batter must signal an appeal. The two-minute innings-start limit. The stop clock the ICC began trialling from December 2026 — sixty seconds between overs, with run penalties on the fielding side, in ODIs and T20Is only. On top of that sit rain calculations and Duckworth-Lewis-Stern recalculations, which can single-handedly swing a tournament, and against which no side has any right of appeal.

At the 2026 World Cup in Russia, the first VAR tournament, I covered all 64 matches and logged 31 on-field reviews and 22 overturned decisions. Tracking 27 semi-automated offside interventions in Qatar in 2026 taught me that technology speeds decisions up, but human beings draw the boundaries of those decisions — and those boundaries are never written on a clock. They live in oral convention.

The problem is sharper in Asian cricket, and the reason is geographic. In European conditions, ball-tracking prediction is comparatively simple — the ball pitches and travels on, wind influence is limited. On Asian spin pitches the ball turns after pitching, dust rises, and the final stretch of the trajectory becomes a matter of estimation. Hawk-Eye publishes its own tracking accuracy at millimetre scale, but when a ball turns two feet, the uncertainty in the prediction no longer lives in millimetres. And that is precisely where Umpire's Call sits.

Clock Decisions: Eight Categories Nobody Named

Across the 2026-18 BPL season I hand-tagged 412 clips — every penalty-box fall, every offside flag, every red-card tackle. The first version of that taxonomy collapsed on handballs and I had to rebuild the whole system twice. That was a football taxonomy. After 2026 I began building a parallel structure for cricket and called it Clock Decisions — rulings determined not by the ball's path, the batter's body or a fielder's position, but by time.

Eight categories emerged. One, the innings-start clock — the two-minute limit, whose only sample is 2026. Two, the signal clock — fifteen seconds after the ball goes dead, with no automated timer and no visible countdown. Three, the over-rate clock — the sixty-second stop clock, and because it is visible, this is the least contested category. Four, the concussion protocol clock — from screening to approval of a replacement. Five, the rain-break clock — over reductions and revised targets. Six, DLS recalculation — a silent change of a number mid-match. Seven, the interval clock — drinks, innings breaks, where light and dew calculations mix in. Eight, the fielding-restriction clock — powerplay limits, fielders inside the circle in the first ten overs.

I opened the 412-clip taxonomy and found a pattern nobody had ever named: in five of the eight categories, the final decision is made by a human reading a broadcast feed clock, not the stadium's official clock. Which means the fate of an international match can be settled by a television production's cut point. When the broadcaster is busy cutting replays, the countdown is not on screen — and that invisible stretch of time becomes the basis of the ruling.

The Mathews case made this plain. Under the World Cup playing conditions, an incoming batter must be ready to face within two minutes of the previous wicket falling. The question is where the two minutes begin — at the fall of the wicket, at the umpire's out signal, or at the television cut? Those three moments never align to the second, and in a packed Asian stadium they align even less. The third umpire has a broadcast feed, a stopwatch and a clause. It was not enough.

What Is Actually on the Third Umpire's Screen

In 2026 I began isolating whistle timing and player shouts from closed-door BPL footage in Dhaka. Across 260 incidents, the median gap between whistle and foul call was 1.4 seconds. That habit taught me something: when the stadium emptied, the microphones started testifying. In cricket that testimony is not preserved, let alone published.

This is where a real fracture has opened between cricket and football. In 2026 the English Premier League launched Match Officials Mic'd Up, broadcasting audio of referee and VAR-room conversations. After the 2026 World Cup, FIFA released the VAR audio from the final. Football has begun treating its officiating process audio as public property.

Cricket has not. The conversation inside the third umpire's room — which frame shows what, which frame is being discarded, which moment of the clock is being frozen — is recorded, stored, and never released. The viewer receives only a final announcement. Where the reasoning is invisible, there is no way to argue with the reasoning.

The crowd tells you what happened; the tape tells you what actually occurred. In cricket, the tape is still in a sealed envelope.

Who Actually Owns Ball-Tracking Data

Here the issue leaves simple refereeing and arrives at a commercial question. Ball-tracking, UltraEdge, Snicko — none of this runs for free. Hawk-Eye Innovations has been owned by Sony since 2026; Virtual Eye was built by Animation Research Limited in New Zealand. These systems generate every frame: pitch angle, ball rotation, point of impact, distance to the stumps.

Those frames produce a decision. But after the decision, the frames are not thrown away. Ball-by-ball data is sold through the ICC's licensed data partner, and part of that feed reaches the market in real time. When I say that live data flowing to betting companies is the darkest side of sport's datafication, I am not making an abstract moral complaint — I am describing a timeline.

Consider what happens inside a review. The ball strikes the pad, the umpire gives it out, the batter reviews, ball-tracking shows the ball heading into the stumps, the decision stands. The whole process takes one to two minutes. Inside those one to two minutes, the tracking frames, the impact point and the rotation data sit inside the technology provider's system — before the final verdict is announced. The data used to reach the decision therefore has a time advantage over the decision itself, and an opportunity to leave the system before the verdict is public. In Asian cricket, where in-play markets are vast and bets can be placed on every delivery, two seconds of lead time is a silent advantage.

To be clear, this does not mean any system is corrupt. It means the audit trail is not public, so the question cannot be closed. And a question with no route to an answer hardens into a crisis over time.

Hash Chains: The Difference Between Proof and Trust

This is where blockchain becomes relevant, and relevant in a very narrow sense. Cricket's blockchain applications so far have been consumer products. In 2026 a licensed digital collectibles initiative with the ICC was announced, letting fans buy unique moments as tokens. That is entertainment, and it has zero relationship to officiating.

The real use case is different and far less glamorous. What I propose is a hash-chained officiating log. For every review event, the data generated — tracking frames, UltraEdge audio stream, clock timestamps, the moment of the third umpire's decision — is combined into a cryptographic hash, and that hash is linked to the previous event's hash to form a chain. Alter any single record later and the chain breaks, and any independent observer can verify it without the raw data ever being published.

Systems like OpenTimestamps in Sweden have worked on exactly this principle for years: embed a file's hash into the Bitcoin blockchain and you hold proof that the file existed in that state at that time. Cricket's review data needs nothing more elaborate. It needs one commitment — that every decision carries a verifiable timestamp.

But here is my caveat. A blockchain log can prove tampering; it cannot manufacture trust. If the underlying rule is itself ambiguous — as with where the two minutes begin — an immutable log simply makes an ambiguous rule permanent. Technology does not replace law; technology keeps the record of law.

The Contrarian Read: The Problem Was Not Shakib, It Was the Clock

After Delhi, Asian cricket split in two. One camp said Shakib Al Hasan's appeal offended the spirit of the game. The other said the law is the law. That day I wrote down a boring hypothesis so I could later try to beat it with data: Mathews was late, the law is clear, the appeal was legal, and there is no institutional defect in this incident.

Reading the ledger back, that hypothesis was three-quarters right. Mathews was indeed late. The law is indeed clear. Shakib's appeal was indeed legal. Bangladesh did nothing wrong. The large section of the cricket public that rushed to a moral verdict had chosen a symbolic target. But the boring hypothesis lost one quarter of the argument, and that quarter is the real story.

The controversy was about the application of a regulation, but the defect was in a measuring instrument. Umpire's Call exists as an admission of weakness — where ball-tracking prediction is not certain enough, the on-field umpire's call prevails. Technology admits its own error margin and declares it. The clock does not. Two minutes, fifteen seconds, sixty seconds — none of these numbers carries an error bar, a tolerance band, or an Umpire's Call.

That is the counter-intuitive finding I filed. Where technology is honest, it publishes its uncertainty. Where humans hold a clock, they hide theirs. Cricket has spent three decades putting ball-tracking in the dock. It has never once interrogated the clock.

The Next Crisis Will Be Two Hundred Milliseconds Long

I stopped trusting my eye and built a calibration protocol instead, because an eye gives testimony, not evidence. Cricket's next step in officiating is exactly that journey: from eye to clock, from clock to timestamp.

My forecast: by 2028 the ICC will have introduced a centralised official match clock, with every frame logged and reviewable in narrowly defined circumstances. That is more than blockchain and less than technology — mostly an administrative decision cricket has not yet taken.

The second forecast is less comfortable. The next major integrity crisis in Asian cricket will not come from a fixed match. It will come from a two-hundred-millisecond advantage in a data feed, where a bet is placed before a decision is announced — and nobody will ever see the violation, because it will not occur on a scoreboard. It will occur inside a timestamp.