India and West Indies fined: the four overs lost on a 351-run night

My field notebook has a separate page for the moments the scoreboard forgets. On the night of the third ODI at Mullanpur, New Chandigarh, two lines joined that page.

The first line was cricket: India made 351, and West Indies chased it down with five wickets in hand. The second line sat outside the game: when the match ended, the match referee's ledger came down — India fined 20 percent of the match fee, West Indies 10 percent, both for a slow over rate. India bowled four overs fewer than scheduled; West Indies were two overs behind.

The only woman in the press box learns to dig quietly, not loudly. So I move the headline fine aside and ask a plainer question first: in a match where 351 runs were scored and the crowd bit its nails until the last ball, where did those four overs go?

The answer is not on the referee's sheet. It accumulates in the gaps between bowling changes, in long drinks breaks, in a mid-innings check on a bowler's ankle. A slow over rate is never a single accident; it is the name of a process. And processes rarely make it onto the scoreboard.

The series was a three-match ODI contest. India won the first two and had already sealed it, which made the third a dead rubber — not a rubber, a dead match. West Indies arrived at it after losing the first two.

This is where a boundary has to be drawn, because the biggest trap in this story sits on the far side of it. The fine belongs to the ODI's slow over rate; the next leg of the tour is T20I cricket — five matches, starting October 6, in Lucknow. Carrying an ODI sanction into the T20I squad makes no sense, because the personnel, the tactics and the use of the ball are all different.

Look at the arithmetic. Under the standard ICC framework, a side is fined 5 percent of the match fee per over it falls behind. India were four overs short, hence 20 percent; West Indies were two overs behind, hence 10 percent. The calculation is mechanical, not the product of a referee's mood. The report says so plainly — the fines followed the severity of the offence.

I have watched many domestic matches from Dhaka, where the same arithmetic bites harder. In domestic cricket a slow over rate costs more than a fine: the broadcast window gets trimmed, and the last ten overs routinely fall off the day's schedule. So when I read about this fine, I think the penalty lands in a player's pocket, but the audience loses time.

Mullanpur is a new address in international cricket. A new venue means less certainty about the pitch and less accumulated knowledge — and that applies equally to both sides. But put two facts together — 351 posted and 351 chased — and the picture is clear: the surface favoured the bat, and the older the ball got, the less it turned for the spinners.

In the modern ODI, a normal score sits between 300 and 320. A total of 351 is at least thirty runs above par. Chasing 351 with five wickets in hand means sustaining roughly seven runs an over across fifty overs — not one explosive innings, but the work of an entire batting structure. Building a base in the powerplay, rotating through the middle overs, taking the risk decision in the last ten: all three layers worked, which is why the finish came with wickets in hand.

Yet the biggest explanation for this result is not on the field but in the context: India, having already won the series, were playing a dead match, while West Indies, having lost two in a row, were playing to survive. That difference in intent shows up in batting intensity, in fielding footwork, in whether a fielder dives or doesn't. Which is why a five-wicket defeat cannot be read as a shift in the balance of power.

India versus West Indies is a historically heavy rivalry. In the 1970s and 80s the Caribbeans were untouchable; now India sit on top. This series paints that asymmetry: India won the series, West Indies took one match. One result does not restructure the table.

For India, the real question is bowling. Failing to defend 351 means a consistent shortfall in death-overs economy. A slow over rate and death-bowling leakage are not two separate problems; they are two faces of the same bowling management. Repeated bowling changes, long field-setting discussions, warming up a fresh bowler — all of it eats time. Those four overs that vanished from the game are the receipt for that indecision.

The rotation opportunity in a dead match is also buried in this story. After sealing the series, India almost certainly shuffled the eleven — normal and necessary. For young pace bowlers this is the real test, because the pressure of a dead match and the pressure of a series decider are not the same thing. But for exactly that reason, no large conclusion about the team can be drawn from the result. In my notebook I write that distinction separately: who played, and who played under how much pressure.

West Indies' two overs of delay tell a different story. When a side chases a big target, the fielding team's overs usually slow for two reasons — a higher number of bowling changes, and long field-placement debates before each ball. In a 351 chase, under pressure, that gets worse. So their two overs of delay are a side effect of an aggressive plan, not laziness — and the fine does not capture that distinction.

A caution is needed on Shai Hope. The report describes his batting as captain-like. That phrase is not analysis, it is the author's opinion — because the innings' runs, balls and strike rate appear nowhere. Staying calm as captain during a big chase is genuinely valuable to a team, but without numbers it cannot be converted into a performance rating. And this innings was an ODI one; it has no translation for the T20Is.

The real information gain sits here: the fine is not a punishment, it is a warning — the over rate is really a safeguard for the broadcast product. Slow overs lengthen the match, strain the broadcast window, and make it harder to hold viewers. The referee's fine therefore protects both the discipline of the game and the commercial schedule.

Now the counter-question that breaks the easy version of this story.

First, chasing 351 and winning by five wickets should not be converted into a claim that West Indies are back. The pitch favoured batting, and the opponent had already won the series. If failing to defend a big total happens two or three matches in a row, then it becomes structural; one match does not.

Second, there is no controversy behind this fine — no DRS dispute, no Duckworth-Lewis revision, no integrity question. It is a routine disciplinary ruling. India were fined more because they fell further behind. That plain proportion is the point.

Third, and most importantly: the real risk in this story is not the fine, it is the schedule. The moment the three ODIs end, the five-match T20I leg begins on October 6 in Lucknow. If the same pace-bowling pool is used across two formats, workload and recovery become the words that matter most. In T20I cricket every over is more valuable, so if over-rate discipline slips there, the sanctions get harsher.

One subtle detail stands out: the report mentions no separate sanction for the captain. That suggests the decision was taken under the team-wide over-rate provision rather than a personal Code of Conduct charge. That distinction will help in reading similar sanctions later.

Commercially, the five-match T20I series is the bigger part of this tour — five T20Is create far more inventory than three ODIs. That scheduling shape is not accidental; it is the product of a market that is T20-first. And for that reason over-rate discipline here is not only a playing question but a broadcast-time question.

Looking from Dhaka towards Lucknow, one thing is clear: the ODI chapter has been filed away in the ledger — India won the series 2-1, both sides paid fines, and a dead-match five-wicket defeat is a small footnote in history.

The real test starts on October 6. How orderly India's bowling-change tempo stays across five T20Is, and how well West Indies' batting depth holds up in this format, will tell us whether the night at Mullanpur was an exception — or a beginning.

I am not erasing this match from that page of my notebook yet. The moments the scoreboard forgets tend to return — not in the fine column, but in the per-over arithmetic.