The Officiating Ledger: Why Cricket Review Decisions Need an Audit Trail

Last night a caught-behind review ended on a soft signal of "out." UltraEdge showed no clear spike, the ball-tracking margin was two millimetres. The third umpire gave the decision, the match moved on. After the game, nobody could say at which step, on what evidence, under which clause of the law, that call had been made. The umpiring log held a single line for the day: "Review — out, final." Nothing left to audit.

In Kuala Lumpur I began keeping a review log from 2026, and the pattern was already there. The controversy attaches less to the decision than to the invisible process behind it. When a review ends, the spectator sees only an outcome. A decision is really the sum of four separate layers: trigger, process, final call, and legal citation. Two of those are usually recorded nowhere.

Cricket's real deficiency is not technology; it is the audit trail.

Cricket's review architecture is older and more structured than football's. DRS began with the 2026 Sri Lanka-India Test, then UltraEdge, HotSpot, ball-tracking and the restrained "Umpire's Call" rule were layered in — where a ball striking the stumps still leaves the on-field decision intact. Football's VAR arrived far later, trialled at the 2026 Confederations Cup and applied fully at the 2026 Russia World Cup. The two sports have different review philosophies, but the structural question is identical: is the decision verifiable afterwards?

At the Russia World Cup I logged every review across all 64 matches with minute, law and outcome; I sorted 29 penalties and 20 overturns into law-based categories. What emerged: more reviews do not reduce controversy, they relocate it — from pitch to booth, from booth to broadcast room. At the 2026 Confederations Cup, just 12 matches produced 12 reviews, four of them overturned goals — Chile versus Cameroon, Portugal versus Mexico. Not one of those four decisions had a full audit record in public.

In Kuala Lumpur I began writing down that very absence, because my years of watching matches tell me a rule is credible only when it is reproducible. The recurring debate over Mushfiqur Rahim's review decisions in Bangladesh matches is another face of the same missing audit trail.

Draw the anatomy of a review decision and four layers appear. The first is the trigger: who called the review, in how many seconds, on what doubt. The second is review type: player review, umpire review, or an automatic technology trigger. The third is the final decision. The fourth is the legal citation: which clause, which interpretation. Recorded together, those four layers make a decision auditable; pulled apart, they leave only an opinion.

For each incident I use a decision tree and attach a confidence level — high, medium, low. The root node is the question: "If this decision were to fall again, would the same input yield the same result?" If the answer is no, the problem belongs to the system, not the umpire. The referee's eye is a frame-by-frame threshold test, not a whistle.

A decision without evidence is an opinion; a decision with evidence is a precedent.

This is where cross-sport comparison earns its keep, provided the limits are stated. Cricket's DRS and football's VAR share review logic, but the data is not the same in kind. In cricket, ball-tracking is a geometric projection, so confidence can be measured; in football, the subjectivity of handball or a foul cannot be put into numbers. The Russia audit showed five of 20 overturns rested on subjective handball interpretation — where the same incident can yield two different outcomes under two umpires. So I compare at the level of principle, not outcome.

My 2026 "Silent Pitch" study of empty stadiums opened another face of this. Analysing the Bundesliga's 81 behind-closed-doors matches, home win rate fell from 43.3% to 33.3%, and home penalties dropped from 0.29 to 0.18 per match. Comparing against a control group of 225 matches, I understood that crowd pressure affects not only the umpire but the player. A decision's quality is a function of an environmental variable — and that variable is logged nowhere.

So human factors — angle, fatigue, crowd noise — are not errors; they are integral inputs to the system.

In cricket this human layer is acknowledged through "Umpire's Call," which football lacks. Here cricket can offer another discipline a structural lesson.

Now the counter-intuitive turn. The common belief is that more technology means less controversy. My log says the opposite. Every new camera angle adds a new layer of dispute, because each angle shows a different "truth." UltraEdge shows a spike, HotSpot does not, ball-tracking gives a different margin — three pieces of evidence, three answers. The problem is not a shortage of evidence but a shortage of coordination between pieces of evidence.

The second counter-intuitive fact is more uncomfortable. In the review log I keep in Kuala Lumpur, the biggest errors arrive in "big decision" moments, not in routine matches. Under pressure an umpire jumps to a decision without process. The more pressure a system carries, the less it follows its own rules. Technology does not reduce that tendency, it only accelerates it.

Cricket's "Umpire's Call" rule — where the on-field decision stands when doubt remains — is in truth an honesty clause: if the evidence is incomplete, the decision is not changed. Football's VAR has not yet learned this restraint; there, overturns have occurred even in the face of doubt.

Not changing a decision under doubt is not weakness; it is the maturity of a system.

My view is that in the coming decade the real evolution of officiating will happen not on the pitch but at the data layer. Every review's trigger, evidence set, legal citation and confidence level should be stored in a single, version-controlled record — where no one can alter an old entry next week, only append a new version. The core lesson of blockchain technology — immutability — applies here to cricket officiating. I call it the "officiating ledger": time-stamped, publicly readable, beyond any single party's control.

Right now cricket's technology is world-class, but its bookkeeping is limited. However precise ball-tracking becomes, if the decision cannot be verified afterwards, precision is only a moment of self-assurance. The question now is this — is building that ledger more urgent than mounting another camera at the ground?