From Timed Out to Ball-Tracking: Who Actually Writes Cricket's Review Ledger?

November 6, 2026, Delhi. Under the floodlights of the Arun Jaitley Stadium, Sri Lanka's Angelo Mathews walked to the crease, then turned back toward the dressing room because his helmet strap had snapped. The clock was running. Two minutes.

Inside those two minutes, international cricket's history changed. Shakib Al Hasan appealed, the on-field umpire raised his finger. Timed out, in a World Cup, against a senior batter.

I have watched that footage twenty-seven times since, always with the umpire's clock in mind. What I found was not a scandal tape. It was the tape of a procedure that cricket has never bothered to name.

So I reopened the 412-clip taxonomy I hand-tagged in 2026, and found a pattern no one had named.

Start with the law. MCC Law 40.1.1 states that the incoming batter must be ready to receive the next ball within two minutes of a wicket falling or an over ending. This is cricket's only hard, measurable time limit that belongs to the umpire rather than to a machine.

Everything else now leans on technology. DRS was first used in July 2026 at the SSC in Colombo, in an India-Sri Lanka Test. From the 2026-18 cycle the ICC made DRS mandatory in all men's Tests. Each team now gets two reviews per innings, topped up at 80 overs in Tests.

Then there is umpire's call: when ball-tracking shows the ball striking the stumps but the centre of the ball falling within the narrow margin outside the outer edge, the on-field decision stands. In May 2026 the ICC scrapped the soft signal for catches, which until then had made the on-field umpire's suspicion the legal default.

Inside this framework, hundreds of decisions are processed every week. One role, one process, is written down nowhere. That is what I went looking for.

One. The two-minute clock is cricket's only unforgiving limit. In the Mathews case the law was clear and the breach was clear. Umpires are under no obligation to warn; the MCC has stated plainly that they should not remind a batter of the time. Shakib's appeal was lawful, and the umpires' decision was compliant. Yet the stadium roared and social media delivered an instant verdict. This is the first fracture I can see: when law and emotion share a stage, cricket almost always applauds emotion, and the umpire stands alone in the middle.

Two. The twelve-second call is cricket's most powerful and most invisible post. Watching replays, fans assume the captain decides. In reality the captain stands in the middle while an analyst sits in a dressing-room room with two or three screens, watching previous deliveries simultaneously, delivering an answer in twelve to fifteen seconds. In a powerplay or a spin-squeeze phase the window narrows further. Working as a junior VT logger at a Dhaka production house in 2026-18, I understood for the first time: reviews are not taken on the field, they are taken in a room. The field only announces them.

Three. Umpire's call: the review that fails and succeeds at once. At the 2026 World Cup I worked a Dhaka broadcast desk as one of three remote loggers, cataloguing 31 on-field reviews and 22 overturned decisions across 64 matches, filing a nightly ledger at 4 a.m. before the desk opened. That habit followed me into cricket. A lost review is not a failure. When tracking shows the ball hitting enough of the stump, but its centre inside the margin, the decision stands while the umpire's accuracy is recorded. I file umpire's call in a different colour, because it is not a team's win-loss account. It is an annual accuracy report.

Four. The soft-signal era, when suspicion became law. Before May 2026, a fielder's catch stood unless the TV umpire found clear and conclusive evidence to overturn it. The guess was the law; the proof was the exception. Between the two on-field umpires' viewing angles, the camera's angle and millimetres of ball edge, thousands of catches were settled in the wrong direction. The ICC's amendment was an admission: an umpire's doubt and a camera's data cannot be measured on the same scale.

Five. Big-screen politics: the replay operator judges first. Stadium crowds do not watch decisions, they watch replays. Which angle, which frame-rate, when to slow it down, is chosen by the broadcast replay operator. The same incident, shown from a different angle, produces a different roar. Across domestic broadcasts I have watched this happen repeatedly, not by accident but by design. Home broadcast is never neutral, because the rhythm of replays sets the length of the break, and the break is ad inventory. I cannot write this ledger, because I have not sat in the replay operator's room. I name the gap rather than guess at it.

Six. The audio layer: when the stadium empties, microphones testify. In 2026 the BPL was abandoned, the stands emptied, and I moved into audio-first analysis. Studying closed-door footage, I measured foul-to-whistle lag at a median of 1.4 seconds across 260 incidents. Cricket works the same way. How long an umpire takes, whether a batter scratches, when a keeper's breathing changes, all of it is written on the audio track. Cricket can be seen against the law, but it can be heard on the audio track. Even the Mathews strap was registered first by ear, not by eye.

Seven. Outside the ledger. I mark what I cannot see. I can tell where the ball went, never what the umpire was thinking. His positioning, his footwork, the heat of a sledge, whether he apologised an over earlier, none of it is in any ledger. Every review statistic carries a fixed measure of distrust, because the man whose decisions are being counted is not having his feelings counted.

Re-reading the ledger. The outrage over the timed out settled in two places. First, why at a World Cup did umpires suddenly lean on an MCC clause with no warning. Second, whether it offended the conscience of a friendly game. The ledger says something else. Law 40.1.1 has been dormant for a century because teams did not invoke it and umpires did not enforce it. Timed out arrived in the Laws around 2026 without any duty to warn, and nobody enforced it, even in the largest matches. The fair question is not whether the law is right. It is why a provision unused for a century was activated shortly before the closing rounds of a World Cup. That is a question of control, and no orderly answer has been given.

Now the counter-intuitive reading. What happened was an act of law, not a failure of spirit. Deepti Sharma's run-out of England's Charlie Dean in 2026 was the same legal act, and it split the world too. Sofia's mankad, Delhi's timed out: two famous ledger entries decided by people reading law rather than feeling it. The real risk is that applying one law two different ways does not make the game look organised, it makes it look petulant.

Outside the scorecard there is another problem. The review window is now a conversation between the umpire and the TV umpire, and that audio channel is part of the broadcast package. How long a decision hangs is determined by a tower producer. Meanwhile the timeline of nearly every review leaks into in-play betting markets, because signage appears at 2/1/0 before the official call. Ball-tracking aside, how long a decision dangles is no longer technical, it is a broadcast-commercial decision. This is the darkest edge of cricket's datafication: those seconds of uncertainty become legitimate value in a live market.

Ball-tracking makes undeniable errors, and that must be accepted. But the deadlock is elsewhere. Cricket's technology reform is really a process reform, not a broadcast reform. I keep asking for one number: how long does a TV umpire take per decision? Nobody publishes it. The only true measure is the timestamp. Where a timestamp exists, the ledger is written and the decision is transparent. Where it does not, the decision drowns in argument. And behind the invisible gap, the analyst hunched over a laptop, reaching a call in seconds, carries none of the cost of error.

Consider the other direction. In football, after semi-automated offside arrived, average build-up fell from 70 seconds to 25, a shift I noted in 2026 in a 40-page methodology note co-written with a FIFA-listed Bangladeshi referee. In that note I asked whether cricket could walk the same road: automated LBW, with ball-tracking making its own call and the half-ball umpire's-call margin handed to the machine. That day will probably come, and the twelve-second room will be redundant. But one question will remain: a sensor can say whether it was out, but who holds final sovereignty? In cricket law, sovereignty still sits with the umpire, not the machine. I have no objection so long as that sovereignty survives. And for it to survive, every invisible decision needs a public ledger.

The bottom line. Mathews was out. Shakib broke no law. Those who shouted in fury blamed a protocol when they should have blamed a century of non-enforcement. The ICC also created an odd fragility: a rule enforced against everyone, with nobody knowing who activated it, when, or in which room. A century-old convention takes time to break. Break it suddenly, mid-tournament, and it is not a decision, it is arithmetic, and arithmetic has a predictable cost.

The nightly ledger did not lie; it just waited for me to read it again. The stadium tells you what happened; the tape tells you what actually occurred. When the crowd thins and the whistle echoes around an empty ground, remember that the ball-tracking is testifying louder than the judgement. The question is not what the future holds, but who will declare that what happened in this match was just, and whether the same technology will judge the final. That answer will be written in the ledger, or it will not be written at all.