From the Timed-Out Clock to the Audit Ledger: Who Is Actually Writing Cricket's Officiating History?

On 6 November 2026, at the Arun Jaitley Stadium in Delhi, Bangladesh played Sri Lanka in an ODI World Cup league match. A wicket fell in the middle of Sri Lanka's innings, and Angelo Mathews walked out. His helmet strap snapped; he went to fix it. At that exact moment, a clock was running. Under the playing conditions, the incoming batter is allowed two minutes to be ready. The two minutes expired, and Mathews was not ready. Bangladesh wicketkeeper Mushfiqur Rahim appealed, and captain Shakib Al Hasan refused to withdraw the appeal. For the first time in the history of international cricket, a batter was timed out — and that decision was adjudicated by a clock, not by a replay frame.

I started the Dhaka VAR-Log for exactly these moments. Sitting at a desk in Rangpur, I log match decisions frame by frame — who appealed, when, how many seconds elapsed, which camera angle showed what. On the day of Mathews's timed out, the first question in my notebook was not about whether the decision was right or wrong. The question was: who was actually running that two-minute clock, and where was the record of it kept? A decision that rewrote the history of an international match has no public, verifiable record. That is the real subject of this piece.

To understand this, we have to look back. The Decision Review System (DRS) was first used in July 2026, in the India-Sri Lanka Test series at the SSC in Colombo. It began as a trial, then gradually became permanent across Tests, ODIs and T20Is. As the layers of technology grew — ball-tracking, UltraEdge, real-time Snicko — the burden of the decision also shifted toward the technology. But the rules differ by format, and the playing conditions are written separately for every tournament. In Tests, each team gets two reviews per innings, topped up after 80 overs; in limited-overs formats the arithmetic is different again. These variations confuse spectators, but for working umpires and match referees they are the everyday rules of the job.

At the centre of my interest is a question — how 'stable' are cricket's decisions, really, and who keeps their accounts. On 14 July 2026, after the England-New Zealand World Cup final at Lord's ended in a tie, the winner was determined by the boundary countback rule. That rule existed before the match, but only after the result did the cricket world realise a trophy had been decided by a convention unrelated to the game's core purpose. The ICC and MCC later abolished boundary countback. In other words, a rule does not change because it was wrong; it changes because it became publicly uncomfortable. That pattern is the central thread of my rule-instability map.

Placed on that map, the timed-out incident becomes clearer. The law is ancient — MCC Law 40.1. Incoming batters were once given three minutes, later reduced to two to speed up play. But in practice, which camera ever shows the audience that two-minute clock? The footage of Mathews's helmet strap snapping was replayed endlessly, but the clock itself was rarely on screen. I went through the match clips frame by frame — what happened before and after the appeal, at which frame the umpire looked toward the crease — and that timeline is incomplete in the broadcast archive. This is my first major observation — an officiating decision can only be re-examined when the relevant clock and camera frames are public; and in cricket, they almost never are.

The second layer is the review clock. Teams must signal a review within a set time on the field — usually 15 seconds. What happens under that 15-second pressure is a statistical problem. In my log I have seen that when a decision is clearly wrong or clearly right, teams take less time; but when a decision is borderline, teams rush and take the wrong review. So they lose the review, and a rule like timed out then bears down on them. In my view this clock does not merely measure time; it actually governs the decision-making psychology of teams. The review clock is not an aid to accuracy; it is merely a device of speed.

The third layer, and the most contentious in cricket, is 'Umpire's Call'. When ball-tracking shows the ball would have hit the stumps, but the centre of the ball would not have entered more than half a ball's width inside the outer edge of the stump, the on-field decision stands. That is, the technology gives a decision, but it leaves the 'doubt inside the decision' in the name of the on-field umpire. Here I want to do a simple calculation — the manufacturer's stated error margin is only a few millimetres, yet the fate of an entire match turns on that margin. My log contains many reviews where the ball-tracking line was a few millimetres from the stump, and the decision became entirely 'the umpire's call'. Umpire's Call actually transfers the uncertainty of technology onto the human umpire — a subtle system for moving responsibility.

The fourth layer is the non-striker run-out, popularly known as the 'Mankad'. In October 2026, the MCC moved it from 'unfair play' to 'run out', Law 38 — meaning the team is not at fault; the batter is out. The rule had been disputed for decades, but the change came not all at once, but step by step, each step under pressure from media and cricket diplomacy. This change shows me that rules are not written in a neutral laboratory; they are written by a mix of lobbies, board politics and broadcast interests.

The fifth layer — the officiating of time. Over rates, slow play, session breaks, hydration intervals — these are not merely administrative matters. The 2026 T20 World Cup, and the 2026 and 2026 Asia Cups, were held in the United Arab Emirates, where heat and humidity force different rules for hydration breaks and match-time management. From my desk in Rangpur I compared the timelines of those tournaments — the length of the mid-innings break, Duckworth-Lewis or the later revised-target calculations — and every one of those changes alters the context of a decision. Even when a match is played at a neutral venue, the rules are not neutral, because the centre of rule-making is not in Dhaka or Colombo, but in Dubai and London.

Now let me give a few numbers from my own log, because in cricket a claim without numbers is merely an opinion. For a Dhaka-based site I have coded penalty-area and review-related incidents across several seasons of the Bangladesh Premier League; that football habit, carried into cricket, changed my method — tagging the time before and after every DRS appeal, whether the review succeeded or failed, and the type of decision (ball-tracking, UltraEdge, stumping). What this tagging made clear is that Bangladesh's pattern of taking reviews is not consistent across competitions — in some seasons they review excessively, in others hardly at all. The cause of this inconsistency is not individual but cultural and informational — teams lack institutional data on the tendencies of on-field umpires.

Another observation from my log — the rate of losing reviews is highest on borderline decisions. When the ball is on the line of the stumps, or when the spike on UltraEdge is ambiguous, teams rely on guesswork. If someone systematically logged that guesswork, a 'review-consideration model' could be built for every team — in which situations a review is profitable and in which it is not. Cricket has not yet done this simple work. Here is my second major observation — cricket has bought the technology, but has not bought the data culture of the technology.

From this point I arrive at an uncomfortable question, one that cricket discussion usually avoids. On the day of Mathews's timed out, a large section of spectators and media were angry with Shakib Al Hasan, some showed sympathy for the misfortune of Mathews's strap, and some blamed the umpires. But nobody asked — how was that two-minute clock measured, which clock, on whose instruction, and where is the evidence of that account? Cricket society argues over whether a decision was 'right or wrong', but does not ask who preserves the 'evidence' of a decision. In a game that does not keep a public record of every contentious decision, justice in decision-making is impossible — only questions of power remain.

This is where I want to raise a fundamental demand, the central argument of this piece. Every officiating decision of a cricket match — every review, every ball-tracking frame, every time calculation, every appeal and withdrawal — should be stored in a public, immutable ledger. I call it the 'officiating audit ledger'. In the language of blockchain technology, it is a simple, append-only record that no single party can alter. In today's arrangement, the owner of the footage is the broadcaster, the owner of the playing conditions is the ICC, and the owner of venue administration is the host board. Information scattered across these three different entities never forms a single picture of the truth. So accountability slips precisely between Dhaka, Dubai and the broadcast booth — exactly as, in my log, the evidence of one decision in many matches cannot be found.

The natural objection to this demand is that it would destroy the emotion and spontaneity of the game, and put excessive scrutiny on umpires. I take this objection seriously, because I myself am an umpire-centred writer. But notice — what happens today does not protect umpires; it leaves them unprotected. When the full information of a decision is not public, the umpire is personally accused, even though the decision is actually the product of an institutional process. In the Mathews incident the umpires followed the law, yet they were almost absent from the media discussion — responsibility drifted toward the players. Where information is hidden, responsibility falls on the individual; where information is public, responsibility falls on the system.

This position of mine comes from my own professional experience. At the 2026 Russia football World Cup I logged 455 VAR checks across 64 matches from my desk in Rangpur, and measured the review time of every decision, finding an average of 84 seconds. That experience taught me that measuring time and decisions together can turn officiating from a story of individual blame into a story of institutional process. Nobody has yet begun that work in cricket. I therefore want to see this piece as a proposal — cricket should adopt a simple habit like the football VAR-Log: the time before and after every decision, the output of the technology, and the final explanation, stored in a common and public structure.

One argument deserves a hearing here — would publishing all the information not increase pressure on umpires? My answer is the opposite. The pressure today is the pressure of guesswork — spectators guess, commentators guess, social media guesses. When information is public, the space for guesswork shrinks, and decisions become explainable. This is what happened with boundary countback — when the rule became publicly uncomfortable, it was changed. The same logic applies to timed out.

Looking ahead, I want to name a specific mechanism. First, every tournament's playing conditions should make decision-related time limits visible on the broadcast — as line-call replays are shown in tennis. Second, the 15-second review clock should not remain a mere administrative limit; public data on its effects should be given to teams. Third, the declared error margin of ball-tracking technology and the output of every frame should be stored on an ICC public portal. Fourth, the decision-related portion of the match referee's report (excluding personal sanctions) should be made public. If these four steps are taken, cricket's officiating history will no longer remain captive to the broadcaster's edit.

I know this proposal will face the resistance of team interests, broadcast commerce and board politics. But the question is no longer about technology; it is about administration. Who writes the rule, who applies it, and who keeps its account — the answers to these three questions today lie in three different places. On that evening when Mathews's strap snapped, cricket made a decision; but nobody took responsibility for preserving it. In the next contentious decision we will return to the same place — the same guesswork, the same anger, the same absent evidence. If cricket truly wants to write its history, it must learn to keep the accounts of the clock, the camera and the rule together in one immutable ledger.