The Review Ledger: DRS, Match-Referee Reports and Over-Rates — How Cricket's Results Are Actually Written on Paper

At 6:47 on Sunday evening, in the 47th over of a domestic one-day match, the field umpire raised his arm and said “not out.” Three seconds later four words appeared on the big screen — “Umpire’s Call, stumps clipping.” The batter walked back. A section of the crowd still did not understand: if the ball hit the stumps, why was it not out?

The answer is not in cricket’s main Law book. It lives in an annex of the protocol. If less than half of the ball strikes the stumps — if the ball merely brushes them — the field umpire’s decision stands, however convincing the ball-tracking proof may be. Nobody keeps a count of how many matches turn on that single line.

I do. That night I opened my review ledger — every DRS call, timestamp, clause number, review duration in seconds. I opened the 2026 VAR Protocol Ledger again, and the same clause was staring back. The method of that 12,000-word spreadsheet, built while I was a student in London, has not changed: clause first, then tape, then decision. Because results in cricket are not made by bat and ball alone — they are made by a log entry.

Context: one technology, three pillars

DRS first took the field in July 2026, in the India–Sri Lanka Test in Colombo. Since then the system has stood on three pillars — ball-tracking (Hawk-Eye or Virtual Eye), edge detection (UltraEdge or Snicko), and the third umpire’s real-time replay. The more advanced the technology, the more complex the question. Technology does not state truth; it states probability.

Under the ICC playing conditions the number of reviews differs by format. In Tests, two unsuccessful reviews per innings, topped up to two again once 80 overs are bowled. In ODIs and T20Is, a single review per innings. So a captain holds exactly one wrong bet for an entire match.

That number is the real story. A review does not only change an umpire’s decision — it changes strategy. Who challenges when, which batter is “saved,” which over the review is saved for: all of this is now part of innings planning. Before a match a coach sets a “review budget” from ball-tracking forecasts, pitch behaviour and an umpire’s history, exactly as he plans bowling changes.

And off the field there is a second layer of paperwork: the match-referee report. The ICC-appointed match referee does not merely watch. He is the adjudicator of the Code of Conduct. Sledging, slow over-rates, ball-tampering, improper conduct toward an umpire — all are classified in his report from Level 1 to Level 4. Level 1 brings a fine; Levels 3 and 4 bring match bans. A match ends on a scoreboard, but it is settled in a document.

I grew up in Bangladesh and work in London. The same ICC conditions apply in both places, but the culture of enforcement differs. In Dhaka’s domestic league, over-rates are rarely discussed, because time pressure is lower; in England’s County Championship, over-rate is almost a religion, because play must close at fixed hours and tickets, spectators and broadcast are all tied to that clock. One clause, two temperaments.

Core: what the ledger says

The first fact my ledger yields is uncomfortable: DRS review success rates vary less by umpire than by the type of decision. LBW calls produce the most overturns, because three steps — pitching, impact, wicket — are each a ball-tracking prediction. On caught-behind and edges, review is nearly certain, because UltraEdge either shows a sound or it does not.

A review, in other words, is a bet placed on three different chessboards at once.

The second observation concerns “Umpire’s Call.” The idea is a constitutional compromise. If technology took full power, the on-field umpire would become a ceremonial figure. Real cricket has not accepted that. So the rule says: if the ball strikes less than half the stump, or impact sits on the boundary line of the on-field decision, the umpire’s ruling survives. This is not surrender to technology; it is a treaty between technology and authority.

The third observation is time. In my log, the third umpire’s average decision time has crept up. Early on a decision took 30 to 40 seconds; now complex ball-tracking cases pass 90 seconds. The reason is more camera angles, spin tracking, and the calculation of how much the ball turned after pitching. That delay is not only technical, it is psychological. Bowler, batter, 30,000 spectators — all stare at a screen. The rhythm of the game breaks.

The fourth layer is the over-rate. Under ICC conditions, the minimum in Tests is 15 overs per hour. Drop below and you are fined; repeat the offence and the captain is banned. These sanctions shape results directly — a banned captain means re-set fields and a re-set bowling rotation. A bowler who gets no rest in a slow over-rate match breaks in the next session. The over-rate is not merely a time account; it is a hidden fitness control.

Here an old obsession of mine returns: effort metrics like distance covered and sprints. In cricket a fast bowler’s workload is measured by spells and bouncers. But a 30-minute spell in which the ball barely reaches him in the field looks pretty on a spreadsheet and not on the pitch. An effort metric is not proof of effort. The over-rate falls into exactly the same trap — a side can bowl quickly and still be passive, while a side can bowl slowly and fight for every ball.

The fifth layer is the match-referee report. Here lies cricket’s legal elegance. After the Cape Town ball-tampering affair in 2026, Steve Smith and David Warner were banned for a year, Cameron Bancroft for nine months. That decision was not made by an on-field umpire but by the match referee and a hearing panel. A “scandal” was finally settled in clauses, evidence and a schedule of penalties.

Two economies, one Law book

The cricket economies of Bangladesh and the UK are not the same, so the same rules breathe differently. In the Bangladesh Cricket Board’s domestic structure (BPL, Dhaka Premier League) the match-referee system is less hearing-centric, more administrative. A Code of Conduct incident is often listed at season’s end rather than headlined mid-season. In England it is the reverse — a dissent signal or a suspicion of ball-changing becomes news the next day, because journalists, board observers and broadcast staff sit in the same network.

The consequence is visible. In London I can usually get a hearing document within a predictable time. In Dhaka the same document takes weeks, sometimes months. So one ICC clause creates two different “case histories.” And case history decides how heavy the next sanction will be, because each hearing stands on the last.

A subtle politics operates here. Banning a star of a small board means disrupting preparation for a major tournament; banning a star of a big board means challenging the international broadcast market. The law is equal, the risk calculation is not. Nobody writes that calculation down, because writing it down would expose the gap between law and commerce.

The Russia review log taught me that a tournament is a legal document written in 90-minute chapters. In cricket those chapters are written in overs — each over a paragraph, each review a note, each referee report an amendment.

Contrarian: emotion versus clause

After a match last week I read the fans’ reaction. “The umpire is biased,” “DRS is broken,” “the game is ruined.” I understand the emotion, because I have shouted from the stands myself. But I know the real problem is not the umpire.

The problem is that cricket uses two languages for one event — one on the field, one on paper. On the field: “the ball was hitting the stumps, but I am not giving it out.” On paper: “Umpire’s Call.” The spectator is stuck between the two sentences. He sees the technology’s picture but does not read the protocol’s annex. So he believes the decision is wrong when, in fact, it is entirely correct under the clause.

The real weakness lies elsewhere. “Umpire’s Call” creates a grey zone, and a grey zone is applied differently match to match. The same amount of clipping survives in one match and does not in another, because what the on-field decision was first is the deciding factor. Technology supplies the proof, but the final ruling depends on one human’s judgement a moment earlier. This is a valid design, but it is an uncomfortable truth — justice here is relative, not absolute.

When the stadiums emptied in 2026, Law 12 became the only crowd still shouting. That year I realised a crowd’s noise is not just atmosphere; it is pressure. Without noise an umpire is not less alert, but less emotional. And less emotion means fewer split-second errors. Now the crowds are back, and so is the pressure.

So my advice is simple: the fans’ anger points in the right direction, but uses the wrong language. Instead of “the umpire is bad,” it is more useful to say “the protocol is unclear in this situation,” because a protocol can be changed and an umpire cannot.

Takeaway

Cricket is moving toward a hybrid legal system — automated ball-tracking and Snicko on one side, human discretion on the other. The question is no longer “how accurate is the technology.” The question is: when technology supplies proof, whose hand holds the decision — the field umpire’s, the third umpire’s, or a written clause’s?

If next season the number of reviews does not rise, but instead the boundary of “Umpire’s Call” is clarified, we may see fewer controversies — and less theatre. That is the real test of cricket administration: whether it can keep the life of the game intact while adding fairness.

I have left my ledger open. The next match will add another timestamp. The question remains: are we seeking the truth of a decision, or simply a decision that favours us?

— Root: Referee