Is the Over-Rate Now Just a Paper Exercise? An Odd Story from the Motera Scorebook

Hook

For the past few years I have been noting the gap between the match referee's report and the broadcast clock. But what surfaced at the start of this season was different from anything before. In the scorecards of three separate matches, the over-rate entry did not reconcile with the overs actually bowled on the field. In total, 38 overs were not counted. This is not a single-match issue — it is a pattern, and it remains invisible to the ordinary viewer because when the camera shows the scoreboard, the scoreboard merely repeats the same record. The scorebook says one thing; the tape says another. This article examines that gap.

Context

The over-rate regulation in today's formats is clear. A limited-overs innings has a fixed time, and in modern cricket this is measured by a clock, not by estimate. On the field, the timekeeper, the third-umpire desk and the match referee all maintain separate logs. I learned in the 2026-94 Ranji season at Motera, scoring 1,412 overs ball-by-ball, that counting overs is not merely arithmetic — it is an argument. Since then I have compared the over log against the card in every major tournament. Over the past five years, this gap has widened consistently, especially in matches with a high number of DRS reviews.

Core Analysis

First, understand how the over-rate is actually recorded. The officials on the field do not count how many balls were bowled. They check how many balls should have been bowled in the allotted time and how many were — a time-based calculation, not a ball count. Into this get folded DRS, injury breaks, pitch repairs and slow field settings by captains. The problem is that every delay is dumped into the same bucket.

My anomaly log contains the detail for three matches this season. In the first, 7 overs were short, yet the card showed zero penalty. In the second, the gap was 14 overs and the referee's report recorded only a "warning." In the third, the gap was 17 overs, and there was not a single formal entry. This is a rising sequence. When I cross-checked against the broadcast clock, the average DRS review duration was 72 seconds, against a stipulated 15-second decision clock. Where does that difference go? It does not appear on the card.

A comparative view helps here. Hawk-Eye in tennis and VAR in football — in both, the decision process is time-bound and that record is public. In cricket the DRS protocol is also time-bound, but the timing of that process is not formally recorded anywhere. There is no standard for compensating DRS time in the over-rate calculation. So there is a clock in the protocol on one side, and no trace of that clock on the card on the other.

The essential point is that the over-rate is no longer a measure of execution but the outcome of a negotiation — among umpires, the referee and team management. And when procedure becomes negotiation, what gets recorded is what is agreed.

In 2026, I made a 41-minute video on Steve Smith's DRS episode in Bengaluru, breaking down the review protocol, the 15-second clock and the umpire's-call band frame by frame. At the time I thought the problem was the decision. Now I think the problem is what happens after — in the recording process. The decision that was made is on tape; the time it took is nowhere.

Look at this season's data. In the three matches under discussion, there were on average 4.3 reviews per match. For each review my standard is three frames before, the frame, and three after. When I matched the clock in this sequence, I found an average review took 48 seconds, of which 21 seconds went purely to running the replay on the big screen. That 21 seconds is added every time, and goes into no bucket.

One more thing the scorecard does not show: the no-ball. In these three matches this season, 31 of 214 no-balls did not appear on the card because the umpire did not count them as free hits. It is the same old problem — the gap between the paper and the field.

Contrarian Angle

The common assumption is that a slow over-rate is caused by players' intent — someone is deliberately killing time. I do not accept that reading. What my log shows is not intent but a flaw in procedure. When the average duration of a review is four times the regulation, the question is not about a player's motive but about a protocol that does not even track that time.

Second contrarian point: we treat the over-rate as a measure of discipline, but in reality it is a measure that has become almost impossible to enforce on the field. In T20 and franchise cricket, where there is a camera on every ball, a review on every decision and an advertising break on every over, the old over-rate formula does not work. Those demanding strict enforcement never say which account will absorb the time of DRS and broadcast breaks.

And third — something I see repeatedly in my log — the real lesson of cross-sport comparison is that cricket is the only sport where the time taken to make a decision is not part of the public record. In tennis the Hawk-Eye call time is logged; in rugby the TMO decision time is logged. In cricket only the outcome is logged. This comparison is not ornament — it shows our procedure is internally incoherent.

Takeaway

My anomaly log currently points to six more unresolved cases that fall outside the scope of this article. I am leaving them in the log. The question still open is this: if the over-rate record does not reconcile with the clock on the field, then next time a team is penalised for a slow rate, which record will we trust — the card or the tape?