In Search of the Immutable Ledger: Cricket Officiating, the Empty Archive, and the Chain of Accountability

Three seconds. Before the last point of the ball-tracking projection freezes on the screen, the third umpire's cabin has roughly that much time. Then the decision rises on the giant screen, and with it rises the crowd's instant verdict. I have spent years at a desk in Rangpur trying to hold those three seconds still, stopwatch in hand, frame by frame. Last week a structural analysis sheet landed on my desk, and every field in it — title to information points — was blank. I found it empty, and the first thing that came to mind was not a match. It was a review cabin where the monitor glows but no feed arrives. In cricket that is the most dangerous moment there is, and that moment is what this piece is about.

I am not suggesting an empty archive equals a conspiracy. I am saying that a person forced to decide in front of a blank screen stops producing information and starts producing guesses. That tension sits at the centre of cricket's officiating system, and the best way to see it is to walk back through my own log.

Context

Cricket umpiring was never a solo job, but the two-umpire era survived for roughly a century. Two men, one at each end, conferring when in doubt — that was the whole system. Video technology entered in the 1990s, first for run-outs. As television coverage grew, so did the number of cameras, and trust in the umpire's naked eye fell in proportion. In July 2026, a Test between Sri Lanka and India became the first played under a full Decision Review System, putting the challenge in the players' hands. That was a turning point, because from then on cricket officiating was no longer a field event; it became a data pipeline.

Let me state my own method plainly. I watch games as replays, not highlight reels. I isolate a decision, rewind frame by frame, check it against the stopwatch, then widen the lens to the officiating system and the rulebook that produced it. My long-running VAR-Log rests on three pillars — review-timer accounting, broadcast-camera geometry, and rule-version divergence. When any one of those three springs a gap, the credibility of the decision falls with it, and the damage is not confined to the field.

Core analysis: the clock is the real referee

The most under-discussed and most powerful official in modern cricket is a countdown timer. A team must raise its hand within a set window to request a review; hesitate and the chance is gone, whatever the truth. In my log I have watched fortunes turn on decisions that were really made not by the batsman's eye but by the watch of a team analyst standing near the boundary rope. What the eye sees, the clock often overrules.

Over rates, session breaks, revised DLS targets after rain, the length of a drinks break — every one of these is an officiating decision, and none of them gets replayed. Nobody notes whether a third umpire took five seconds longer to reach a frame, or where those five seconds carried the rhythm of the match. I started the VAR-Log during Dhaka's new-media boom, counting penalty-area incidents in football, but within a few years I understood that the clock's accounting works the same way across football and cricket: it signals to the audience that the process is professional, while the haggling over time inside the process stays hidden.

What the archive keeps, and what it loses

Across a five-day Test, the broadcast cameras never catch most of what happens. What we see is the director's chosen angle — the bowler's release, the batsman's pad, one camera behind the stumps. But where a run-out decision depends on exactly which frame the bail left its groove, the frame-rate and shutter speed of the camera become the judges. If something happens faster than the camera can shoot, the archive goes silent — and that silence later hardens into 'out' or 'not out'.

Broadcasters rarely sit beside that decision, yet the match producer and television supervisor decide where each camera stands. So the hardware is supplied by a technology company, operated by the broadcast carrier, and interpreted by the umpire — and the responsibility scatters between three parties. My notebook carries a simple picture of that scattering: a gap exactly where the event occurred, and two kinds of confidence on either side of it.

The ICC has made several large changes in recent years that are really attempts to repair this gap. The 'soft signal' rule for years pushed the third umpire to lean toward the on-field call; retiring it was an admission that half-certainty is no certainty at all. In the same spirit, the 'umpire's call' margin in ball-tracking concedes that technology has a limit, and that inside that limit the human call keeps primacy.

A map of rule instability

Cricket's most famous archive gap is probably the 2026 World Cup final. The match was tied, the Super Over was tied, and the result was settled by counting boundaries — England twenty-six, New Zealand seventeen, the trophy to England. The scoreboard showed two equal totals, yet the trophy went to one side, because the final arbiter was a clause of the playing conditions that nobody had really considered beforehand. It shows how one paragraph of the rulebook can overshadow an entire match and take ownership of a result.

I like to read that episode across tournaments, because similar rules get read differently in Asian Cricket Council events, bilateral series, and ICC global events. Which DLS version applies where, how long a powerplay runs, where concussion substitutes or impact players are allowed and where they are not — without a map of all this, the same incident produces two verdicts in two places, and the audience concludes the board is biased. Often it is not bias; it is rule-version divergence.

In the Bangladeshi context that divergence is sharper still. How 'umpire's call' is read on the slow, low, spin-friendly Mirpur surface differs from how it is read on a green pitch in Southampton. On a quick home wicket the ball may miss the line of the stumps; in Dhaka the same delivery clips leg stump, and that difference walks straight into the review verdict. A spectator sees two verdicts on two grounds and burns with anger, when behind both verdicts sits one machine and two different geometries.

The precision of technology and its limits

Every time ball-tracking enters a match, the audience feels that judgement has become mathematics. But mathematics needs a starting point — the frame of first contact. If that frame is captured even a thousandth of a second late, the calculation built on top of it looks immaculate while starting from the wrong place. In football I call this the 'armpit offside' — a decision on a hair's-width margin. In cricket its face is different, but the philosophy is identical: the more precise the machine, the more expensive its input error becomes.

One small figure from my log is worth remembering. While tagging penalty-area incidents in football, I found home teams won 0.31 penalties per match, but in empty stadiums that fell to 0.22. Home advantage lives not only in players' legs but in decisions. Cricket has less direct data of this kind because the pressure is spread across more layers — but the question is the same: do crowd, pressure, and time enter review verdicts? They do, but nobody admits it.

A human sits in the third umpire's cabin, watching three or four feeds at once, sometimes listening to stump mic, sometimes ruling on the strength of a single frame. There is no uncertainty indicator on his console — he does not know how confident this frame really is. In the umpire's report we read 'out' or 'not out', never 'out at eighty-six per cent confidence'. Yet the most important job of a modern system should be to preserve exactly that measure of confidence.

Where the chain of accountability breaks

Now to the real question that forced this piece. An umpire gives a decision; a technology company feeds the data behind it; a broadcaster supplies the cameras; the ICC or a relevant board writes the rule; a match referee oversees. But nobody keeps an immutable ledger recording — in which match, which over, which technology, which frame, at what confidence, who decided, and whether it was later corrected.

I take the idea of a blockchain in principle, not in engineering terms: a record no one can quietly alter, where each entry is chained to the last. Cricket officiating demands exactly such a chain, because what happens today is this — controversy flares, two days of debate follow, the file closes. Next month the same kind of decision arrives, and no one can compare it with the earlier one, because there is no ledger to compare against.

My experience tracking Asian tournaments tells me accountability collapses precisely where institutional jurisdictions separate. When the ICC's rule, a board's match referee, and a broadcaster's camera combine to build a decision, no one owns the whole picture. Where there is no owner, there is no immutable ledger. And without a ledger there is no correction — only the next controversy.

A contrarian angle: the crowd's emotion and the rulebook's silence

Now to the place where I argue with myself. When a spectator shouts, he is not being foolish at all. He has correctly sensed that the system has a gap; he is simply placing it in the wrong spot. He assumes the decision was wrong, when often the decision followed the rule correctly and the rule itself was the fault. The boundary count is the clearest example: the umpires broke no rule; the rule was incomplete.

My fear runs the other way. When we sell technology as flawless, every close call drains trust toward the machine and leaves the umpire isolated — afraid to give a decision lest the replay prove him wrong. In cricket this is the natural back-off: when in doubt, the umpire stops deciding and leaves it to technology. That destroys the rhythm of the game, because the game no longer plays; it waits for a screen.

The heaviest damage is statistical. Once a player realises a particular delivery is review-proof, he changes his game away from it — when his real skill lay exactly there. The number of reviews rises, but that is no proof of skill; it shows players no longer trust the umpire's eye. I call this the politics of offloading the decision — where responsibility is pushed onto the machine and the game hides its own errors.

Takeaway

The real fight in cricket now sits where the boundary between machine and human is stitched together — and the next weapon in that fight should be an open, immutable officiating ledger, where every decision is written with its confidence level, camera source, and time stamp. The question is no longer 'how accurate is the technology'. The question is: who keeps the record, and who answers when a gap appears?