Cricket's Review Log: Where Every Ruling Becomes an Immutable Block

I keep a spreadsheet on my laptop. I have named it the "Referee Ledger." One line on the first tab is still underlined: 2026, twenty-seven incidents, each timed in seconds, each carrying a clause number beside it. Even now, when a cricket controversy breaks — a catch, a no-ball, an over-rate fine — I open the ledger. Because the ledger tells you who actually made the call: the umpire on the field, or the law book. For the past few weeks I have been turning one idea over. Cricket's biggest decisions are not made in a single moment; they are built in a chain — every review a block, every timestamp a hash, every clause citation linked to the block before it. That is why, to my eye, cricket's most immutable blockchain does not live on the field. It lives in the match-referee's report, in the review log, in the code-of-conduct file. And unfortunately, it is the least-read document of all. Understand this: the first question in any legitimate analysis of a cricket controversy is format — Test, ODI, T20, or The Hundred? The same bowler's economy rate is two different organisms in a Test and a T20. In a Test, a bowler can sustain ten overs of pressure; in a T20, the account settles within four. Add the venue and the picture sharpens — spin in Kandy, bounce in Perth, dew in Dhaka. The Russia review log taught me that a tournament is a legal document written in over-by-over chapters. In cricket, the paragraph numbers of that document are the ICC playing conditions, the DLS table, the reserve-day rule, and the clauses of the code of conduct. Take the 2026 World Cup final. England and New Zealand, Lord's. Both sides finished their 50 overs on 241; the Super Over finished 15-15. Then the result came down to boundary count — England had struck more boundaries. Nobody on the field made that call; it was made by a clause printed before the tournament began. Eoin Morgan and Kane Williamson walked into two different fates that day, yet the difference was created by a line item, not by a cricket ball. I understood that afternoon that the final was played between two teams, but the verdict was handed down by a document. DRS's "umpire's call" tells the same story. When ball-tracking shows the ball clipping more than half the stump, the original decision still stands — because the law says the benefit of doubt belongs to the umpire in the middle. That is not a weakness; it is design. Since DRS arrived in 2026, the arithmetic of two reviews, the penalty for losing one, and the margin built into the technology have formed a chain of decisions where every block depends on the one before it. A player like Ben Stokes lives on the boundary line, and that line is drawn by a team of technology operators and a step of clause text. Over-rate gives an even cleaner example. The match referee counts the clock, docks points for slow overs, and can suspend a captain for a match. There is no room for emotion here; this is a ledger entry. I have watched the same law applied in two different cricket economies — Bangladesh's domestic and political circuit, and England's county and international regulatory culture. Same MCC Law, same code of conduct, different tone. When a star like Shakib Al Hasan faces sanction, the question is not only about him — the question is whether the ledger counts everyone the same way. This is why I read a tournament as a constitution — the schedule, DLS, over-rate penalties and reserve-day rule are its real plot. When rain fell in the 2026 World Cup semi-final, how the reserve day would operate had already been written; the players were merely following the law as drafted on the field. To the spectator it was weather drama; to the file it was the application of clause 2.4. Player data demands the same discipline. A batter's average, strike rate and situational splits answer three separate questions — how many runs per ball, how fast per ball, and how they behave under pressure. Fuse the three together and the analysis becomes cheap. For bowlers the logic inverts: a low economy rate is not automatically good unless you know how much wicket threat was generated and in which format the batter was playing. Raw numbers never speak for themselves; they speak only when seated beside context. A team's context must be read the same way. The ICC ranking is an average over time, the home-away profile is another picture, and the squad's age structure is a third layer. The same side behaves differently under dew at home and under bounce abroad. So the honest answer to "how good is this team" never arrives in one word; it arrives in information divided across layers. Read the review log, the match-referee's report and the broadcast data together after a match and a truth surfaces: cricket's commercial side runs on story, while its governance side runs on documents. Franchise contracts, broadcast rights, star salaries — all priced in the spectator's memory. But a result is overturned by the strength of a clause, not the strength of a feeling. That gap between the two sets of books is cricket's biggest untold story. The whole system also runs like a supply chain. Upstream sits youth development and talent supply; midstream, national teams and franchise leagues; downstream, broadcast, fantasy play and data markets. A shock at any one layer ripples downward — a selection controversy, a sanction, an abandoned series. An analyst who watches only the bottom layer hears the sound of the wave but never sees its source. Risk attaches here too. On one side, the long-term risk in the talent pipeline and coaching systems; on the other, the cyclical shock of the broadcast market; and above that, the non-playing risks — weak match management, judgment rendered in the wrong format, and the patience of the audience. Looked at separately these risks seem small; seen together they reveal that cricket's stability depends on how honest its paperwork stays. Now to my real objection. The conventional reading is easy — "New Zealand were robbed," or "that umpire was poor." Open the ledger and you find the result was set in advance, lawfully, inside the law itself. What is genuinely weak is not any single ruling; the weakness lies in our habit of analysis. We want the verdict before the evidence. We judge Test batting by a T20 strike rate, and a sixteen-year career by five overs of one match. Just as distance covered and sprint counts get passed off as "effort," though pointless running also produces pretty numbers, so too does pointless hitting produce a pretty strike rate in cricket. A number becomes meaningful only when a clause number and a context sit beside it. So my advice is quiet but plain. Before you pass judgment, demand the ledger — which clause, which format, which venue, which timestamp. As semi-automated and officiating technology advances, decisions will rest less in the hands of emotion; the controversies will not disappear, but their quality will rise. I keep a review log for esports rulings too, because pixels can foul as well. What the next block of cricket's blockchain reads will depend on how we read the next review. — Root: Referee