The Unfinished Review Ledger: Cricket Got the Technology, Not the Accountability

The big screen at Sher-e-Bangla. The 43rd over, a spinner's ball thuds into the batsman's pad, the on-field umpire says not out. The fielding captain raises the T-sign, the ball-tracking animation rolls, the stands hold their breath, and then the yellow letters appear: Umpire's Call. Total elapsed time: three minutes and twenty-two seconds.

Back in Khulna that night I filled in three columns. Trigger: 43.2 overs, inswing, impact in line. Evidence: ball tracking, less than half the ball projected to hit the stumps. Outcome: Umpire's Call, review retained, on-field decision unchanged.

Three columns, all complete. The ledger still felt unfinished, because nobody keeps the fourth column — who built the evidence shown on that screen, on which frame, at which calibration, in whose hands. As long as the screen shows truth, nobody asks. The question lives on the other side of the screen, in the dark room.

The journey began in Colombo in July 2026, with the India-Sri Lanka Test series. From 1 October 2026 the ICC made DRS mandatory in Tests and ODIs, and from 1 October 2026 in T20Is. The soft signal was abolished in 2026. Two reviews per innings in Tests, retained when the verdict is Umpire's Call.

The law looks simple on paper. Umpire's Call means that if fewer than half of the ball is projected to strike the stumps — the "wickets" element of an LBW — the tracking prediction does not override the on-field call. The ICC never treated this as weakness; it treated it as an admission of measurement uncertainty. The prediction cone, the frame rate, the calibration chain — the rule was born out of that chain's own margin of error.

Blockchain has entered sport, meanwhile, but through the spectator gate rather than the decision room. Juventus launched a fan token in 2026 and Barcelona in 2026 on the Chiliz-Socios platform; in cricket, chain-based tools are spreading through ticketing, collectibles and sponsorship contracts. All of it in the buyer's pocket, none of it in the match-decisions ledger.

At the 2026 World Cup in Russia I kept a ledger of every VAR decision, and the margins told the story. I later carried that three-column template — trigger, evidence, outcome — into cricket. Years on I understood this much: however precise the ledger, whoever owns the evidence ultimately owns the interpretation. That is cricket's real review gap.

Gap one: truth for rent. Ball tracking, UltraEdge, spin tracking — none of it is ICC property. It is proprietary software from private firms, and boards pay per match for its use. Raw frames, calibration data, operator logs: none of it is public. The true path of the ball, the centre of a legal dispute, is a rented asset. In football's VAR debates the host broadcaster decides which angle is shown and when; in cricket much of that power sits with the tracking supplier.

Gap two: the burden of proof is unevenly distributed. The on-field call is the default truth. "Not out" means technology must prove the case beyond the error margin; "out" means the batsman must do the reverse. A batsman can therefore gain from a human error that took three slow minutes to make. And a review is not a truth-seeking instrument — it is a resource calculation, two per innings. Virat Kohli, an aggressive captain, and Mominul Haque, a calm one, get the same number, but not the same infrastructure. A dressing room with an analyst on the headset converts better; boards that cannot fund that data backbone fall behind. Technology brought in for fairness is quietly hardening into a new infrastructure inequality.

Gap three: the twenty-two yards before the technology. In 2026 I analysed 83 Bundesliga matches played in empty stadiums: home win rate fell from 43.3 per cent to 33.7 per cent, and added time rose by 1.4 minutes. The whistle stopped, and the game finally spoke — crowd pressure shapes an umpire more than technology does. Most cricket research on home advantage examines the final thirty centimetres of the ball's journey; nobody keeps a ledger on the social pressure of the twenty-two yards before it.

Gap four: the dressing-room laptop and the rhythm of the field. Review calls now often belong less to the captain than to the analyst behind him. The model does not know how tired a bowler's shoulder is, how dry and cracked the pitch has become, how far the batsman has started pressing forward. The captain's internal clock and the captain's laptop do not return the same answer, and a burned review is paid for across the rest of the innings. Even a captain as seasoned as Shakib Al Hasan has spent one in the first over, because in that instant there was no middle path between emotion and data.

Now consider the popular demand. The loudest calls are to scrap Umpire's Call and add more cameras. Yet the logic behind retaining Umpire's Call is the most honest admission in the game's history — the courage to accept a margin of error. Abolishing it would not improve accuracy; it would simply move authority from the on-field umpire's hands into the servers of two private companies. And more cameras do not bring truth within reach unless the custody of that truth is publicly accounted for. The anger in the stands is legitimate — it comes from not holding the decision in your own hands — but that anger is aimed at the wrong address.

So the proposal is not about technology. It is about accounting. Every review record — over number, timestamp, tracking output, operator identity, final decision — could be written as a hash into a public, append-only ledger. Boards keep the raw data, the supplier's intellectual property stays intact, but nobody can later edit the ledger and rewrite the history of a decision. The costs are real, the boards' reluctance is real, the suppliers' IP interests are real. So start small: one ICC tournament.

The rule was never the point; the rule was the flashlight. It is time to shine it into the room where the ball's path is computed. And let the last question stand: when the ball's path is rented property, whose truth is Umpire's Call?