Losing to the Clock: The New Chandigarh Fines and Cricket's Politics of Time

The fine arrived late in the night. No scorecard, no result—just a two-line notice: in the third ODI at New Chandigarh, India bowled four overs short, West Indies two. Both teams were fined. That is all. And yet inside that sliver sits cricket's oldest question—who actually controls the clock of this game? I have spent years counting cricket's time across Bangladesh's grounds. In 2026, at the Rajshahi District Stadium, the stadium microphone died in the 63rd minute, and I called the final twenty-seven minutes into a borrowed phone. That evening taught me that time is not merely something to count—it is the vessel inside which a match finds its character. The New Chandigarh fine is therefore not administrative trivia to me; it is the story of a loss to a clock, where both teams lost, but the judge was not an umpire—it was a schedule. Context: ODI cricket has a different body. Fifty overs, two new balls, two-and-a-half to three-and-a-half hours per innings. Over-rate management is structurally harder than in T20. Under the ICC Minimum Over-Rate Offence provision, the fielding side is fined per over it falls short, with the captain bearing the largest share. Here the penalties were not equal—India's four-over shortfall exposed it to a larger sanction than West Indies' two. The match was played in India, at the relatively new New Chandigarh (Mullanpur) venue; dew in a night ODI is a familiar delay driver. Core analysis: The most important point is that this fine is no performance signal. Winning and losing sides alike get penalised for over-rate breaches. The scorecard has no relationship to the sanction. But the differential is the real information: the penalty scales with the shortfall, and a four-over gap is substantial in an ODI. My long-held observation is that cricket's least-discussed yet most powerful regulator is time. Overs are lost in three places—a bowler repeatedly resetting his mark, long field-setting discussions, and reviews. On the third I keep a special watch, because the review system has not reduced controversy; it has moved it from the pitch into the review room and the grey zones of the rulebook, quietly eating the match's minutes. Contrarian angle: The popular reading is that a fine means a team is undisciplined. I think the fine proves the opposite—that the sanction is not working. If the same side is fined repeatedly with no real change in time management, the penalty becomes a toll rather than a deterrent. The ICC wants to bind the game to time; the player wants to play to his own rhythm. The fine is a tax on that tension, not a resolution. And notably, both sides were penalised—including host India. That is the silent signal: the sanction does not see home advantage, it only sees the clock. Takeaway: I read cricket as a large clock, where every over is a tick and every delay a timer. The New Chandigarh notice is one small sound of that clock—but small sounds accumulate across a series, and in the ICC system demerit points can edge a captain toward suspension. The notice does not say whether that happened here. But whoever counts time knows the clock never stops. In the next ODI I will watch the overs, not just the scorecard. If that two-line notice returns, then cricket still has not answered its oldest question—who controls the clock of this game?