The New Chandigarh Over-Rate Fine: The Ledger the Scorecard Never Writes

"The pass log began with a turn I almost missed." This time the turn was not on a touchline but in an administrative notice after an ODI at New Chandigarh. Following the third ODI of the India–West Indies series, word came that both teams had been fined for a slow over-rate. India finished four overs short; West Indies two. That is all there is — no scorecard, no result, no player named. Two teams, two numbers, one venue.

I collect these post-match notices year after year. A sheet taped to a dressing-room door, a board email, a match referee's short statement — nobody reads them, nobody saves them. Yet the history of cricket's time management is written on exactly these sheets. In a match carrying broadcast interests worth crores, the least-read document is the one keeping the time ledger. This piece tries to read that ledger.

Context first. The ODI is a 50-over format: two new balls, defined powerplay phases, roughly three and a half hours per innings. It does not compare with a 20-over T20I, because over-rate management gets structurally harder as the format lengthens. The longer the innings, the more breaks, the more DRS reviews, injury stoppages, bowling changes, and the fuss of managing evening dew. Every stopped second adds up into an over shortfall.

The ICC's Minimum Over-Rate Offence provision is the framework under which a fielding side is sanctioned for failing to complete its overs in the allotted time. The structure is not simple: the sanction scales with each over short, and the captain bears the largest share while the rest of the side is fined collectively. How much the exact percentage was in this match, and whether the in-match fielding penalty — an extra fielder brought inside the circle when the final over does not start on time — was applied, remains pending verification in the original source. Where there is no information, there is no inference; that is the first rule of my log method.

How over-rates are measured matters too. A side must hold a required rate within the allotted time; time allowances are granted for defined reasons (reviews, injury, dew breaks), and what remains after those allowances is what counts. So an over-rate is not only a question of speed but a question of documented allowances.

The venue is part of the context. New Chandigarh (Mullanpur) is a relatively new Indian international venue, and its pitch character is not stated in the notice. Because the match was played at India's home ground, dew management naturally enters the over-rate conversation — but that is inference, not evidence. India–West Indies is a long bilateral rivalry; a third ODI means a series of at least three matches, though the notice does not say whether it was a decider.

Now the real arithmetic.

Four and two — these two numbers are not a performance signal; they are a time-management ledger. The fine scales with the number of overs short, so there is one simple reason India's sanction is heavier than West Indies': India were two overs further behind. Anything beyond that, without a scorecard, is inference.

That both sides were sanctioned is the most telling fact. Had only one team's bowling innings run late, the sanction would have been one-sided. Both fined means the match as a whole was running behind time. The cause list holds DRS reviews, injury stoppages, dew management, repeated ball changes and long field-setting consultations.

My thirteen years of watching from the ground say the main driver of a slow over-rate is usually not slow bowling but stoppage. In 2026, the Modrić pass log taught me a habit: verifying every sequence against video. That habit travels. In the ISL bio-bubble in Goa I logged 37 set-piece routines for one side and saw that a team disciplined in process is disciplined in time. Across 21 days with the Indian men's hockey team in Paris, logging 47 penalty-corner routines, the same rule held. In cricket, that process is field-setting, the rhythm of bowling changes and review management. The over-rate is the mirror of those three.

The real teeth of the sanction are not in the fine. Under the modern ICC framework, over-rate breaches accumulate demerit or suspension points that can edge a captain toward a ban. The notice mentions only the fine, so whether points accrued is unknown. This is where the storyteller and the log-keeper part ways; one writes a hint of heavier punishment, the other writes pending verification.

That the host nation was fined too is the biggest governance signal. India as host and West Indies as visitors, both sanctioned in the same match, means over-rate enforcement is venue-blind. The oldest complaint against cricket's regulators was favouritism toward the marquee side; this notice is a counter-example.

One limitation deserves honesty. This notice contains no result, no scorecard, no toss and no DLS information. Who won, how the powerplay or death overs went, or whether a particular bowler's rhythm caused the shortfall — none of that can be drawn from this source. What exists here is only the arithmetic of governance.

Outside readings usually go wrong in a few ways. Many treat the fine as a lack of practice or a symptom of bowling workload stress. Without a scorecard, toss or DLS data, an over shortfall cannot be called evidence of bowling stress; it is a single administrative event, not a trend. Others assume a slow over-rate means slow bowling. In practice it is often stoppage-driven — reviews, injuries, dew. A side that bowls quickly but stops repeatedly posts a poor over-rate; a side that bowls slowly but without interruption holds roughly to schedule. The biggest error is treating the fine as the whole punishment. The fine is a sponsor-friendly, low-intensity message; the real pressure sits in accumulated points that nobody displays.

Assuming a sanction notice without a scorecard is an accident is easy, but it is the design of the source. These documents do not come from match reportage; they come from the match referee's office — the official empowered to lay over-rate charges, though this notice does not name him. The item's incompleteness is, in effect, the signature of its source.

There is a format-side counter-intuition too. In T20Is, being four overs short is not rare; in ODIs, where the tolerance is larger, the same shortfall is far more serious. Analysts who blend formats stumble here. The over-rate provision is format-specific, and so is its tolerance.

One debate usually stays in the background. Cricket's time discipline is, in effect, a mechanism to protect the product's time-boundedness for broadcasters. An over that runs long eats into the next programme and pushes out advertising slots. In that sense over-rate governance is not only a rule of the game but a guardrail on the product's schedule. Those who call the fine trivial miss this fine arithmetic of the sport's economy.

Looking forward, I am logging three signals. The demerit-point ledger for both captains — whether anyone is nearing the suspension threshold. Whether the same side breaches again in the rest of the series — once is an isolated event, repeatedly is a pattern, and a pattern is a story. And whether the in-match fielding penalty was actually applied, to be checked against the ICC Playing Conditions.

The original notice does not even carry a date. The question stays: who actually keeps this ledger? The scorecard counts runs, but who counts time?