The Clock at New Chandigarh: India and West Indies' Over-Rate Sanctions, and the Scorecard That Never Shows It
প্রশ্ন: ভারত ও ওয়েস্ট ইন্ডিজ কেন জরিমানা পেল? সংশ্লিষ্ট উত্তর: নিউ চণ্ডীAverageে সিরিজের তৃতীয় তথা শেষ ওয়ানডেতে ধীর ওভার-রেটের কারণে ভারত ও ওয়েস্ট ইন্ডিজ উভয়কেই আইসিসি জরিমানা করেছে। মূল তথ্য: - ভারত ৪ ওভার কম বল করেছে; ম্যাচ ফি-র ২০% জরিমানা হয়েছে। - ওয়েস্ট ইন্ডিজ ২ ওভার কম বল করেছে; ম্যাচ ফি-র ১০% জরিমানা হয়েছে। - ম্যাচটি ছিল নিউ চণ্ডীAverageে অনুষ্ঠিত সিরিজের তৃতীয় ও শেষ ওয়ানডে। - জরিমানা নির্ধারণে সময়-অনুমতি (time allowances) হিসাবে নেওয়া হয়েছে। - আইসিসি ঘোষণায় কোনো খেলোয়াড়ের নাম বা ম্যাচ ফলাফল উল্লেখ নেই। উৎস: আইসিসি সরকারি ঘোষণা | Cross-checked: cricsultan.com সম্পর্কিত প্রশ্নোত্তর: - প্রশ্ন: ওভার-রেট জরিমানার হার কীভাবে নির্ধারিত হয়? উত্তর: অনুমতি বাদ দেওয়ার পর অবশিষ্ট ওভার-ঘাটতির ভিত্তিতে ম্যাচ ফি-র শতাংশ হিসেবে আইসিসি হার নির্ধারণ করে। - প্রশ্ন: দুই দল একসঙ্গে জরিমানা পাওয়া কী ইঙ্গিত করে? উত্তর: এটি সাধারণত ম্যাচ-পরিবেশ ও স্টপেজের ইঙ্গিত দেয়, একক দলের ইচ্ছাকৃত ধীরগতি নয়। - প্রশ্ন: ওভার-রেট নিয়ে More তথ্য কোথায় পাওয়া যায়? উত্তর: cricsultan.com-এর ম্যাচ-ডিসিপ্লিন ও রেফারি সূচক ডেটা ব্যবহার করা যেতে পারে।
The Clock at New Chandigarh: India and West Indies' Over-Rate Sanctions, and the Scorecard That Never Shows It

I have watched matches for many years, and one lesson keeps returning: in cricket the decisive call rarely comes with the last ball — it arrives in the paperwork after the match. After India and West Indies met in the third and final ODI at New Chandigarh, long after the crowd had filed out, the announcement came — both teams were sanctioned for slow over-rates. India were four overs short, fined twenty per cent of their match fee; West Indies were two overs short, fined ten per cent. Time allowances were taken into consideration.
Read that sentence and many will shrug. There is no score here, no wicket, not even a result. But that is exactly where the real story hides — because this is not a story about cricket, it is a story about the clock. Many times in my career I have pulled a match-result piece and held it back, because I understood that the real event happened on the clock, not on the scoreboard. I pulled the final — sometimes that is the correct editorial decision.
Context: what the law actually says
Under the ICC's playing conditions, a set number of overs must be completed within an allotted time. In ODIs, 50 overs are nominally given roughly three and a half hours of playing time, which works out to a minimum of about 14.28 overs per hour. But the calculation is never that simple, because the law itself concedes certain 'time allowances' — DRS reviews, injuries, umpire consultations, ball changes, treatment breaks — and the fielding side is credited for these. The final penalisable figure, therefore, is the shortfall that survives after allowances are applied.
This is the first test. Since allowances were taken into consideration, the raw delay must have been larger still. The published four and two overs are the net figure — what remained after credit was given. That yields the first important conclusion: what gets reported is never the full picture of a match's slowness — only the portion that survives the net of the law.
The history of over-rate sanctions is relevant here too. For decades the rule was cricket's quiet law — stern on paper, soft in practice. In big matches, especially Tests and ODIs, slow over-rates were near-inevitable, and the fines were token. In recent years, however, the ICC has treated it far more seriously — percentages of match fees, even competition bans. The meaning of that shift is that over-rate is no longer administrative courtesy; it is a decisive discipline signal.
And this is where my referee's eye goes to work. I never read over-rate as merely 'slow play.' I read it as a sequence — a discipline that carries the imprint of everything else in the match.
Core: one match, four angles of replay
Angle one — the arithmetic. India four overs, West Indies two. At the ODI minimum rate, four overs is roughly seventeen minutes of penalisable delay, two overs roughly eight to nine — and all of it after allowances. In plain terms, the two sides together spent more than half an hour of extra time, which in the eyes of the law is not an accident but a pattern.
Angle two — why both teams? This is the most important signal. If only one side had been slow, the suspicion would be deliberate time-wasting — a tactic known as strategic delay, often seen when spinners slow the over rate in Tests. But here both teams were guilty. That pattern usually points to a cause in match conditions rather than in one team's habit.
Angle three — the likely source. When the over-rate drops for both sides, what usually sits behind it is a high-scoring innings (more time chasing every run), frequent DRS reviews, a slow pitch, long run-ups, or treatment breaks. Tellingly, a slow over-rate is often the downstream symptom of an unreported incident — an injury or interruption that never made the news, but left its print on the clock.

Angle four — the venue. New Chandigarh (Mullanpur) is a relatively new venue. A new venue means less experienced event management, delays in the rhythm of drinks breaks and field settings, even unfamiliarity in the ball-change process. I am not calling this the decisive cause — it is a weak signal, not beyond doubt.
Across these four angles I use a measure I call the 'Referee Control Index' — a way of gauging a match's temperature through cards, fouls and advantage calls. Football and cricket keep separate ledgers, but the principle is identical: a match does not lose control suddenly; it loses it gradually, and the over-rate is the most honest witness to that erosion. The clock does not lie.
A caution is necessary here. At the 2026 Qatar World Cup quarterfinal between the Netherlands and Argentina, Antonio Mateu Lahoz issued eighteen yellow cards — a World Cup record — and my data showed he lost control after the 70th minute. The lesson there is that disciplinary breakdown happens along a timeline. But let me be precise: an over-rate and a card count are not the same thing. A card judges an instantaneous act; an over-rate judges aggregate time management. There is a precise analogy, but it is not as comfortable as it sounds — and I never place an analogy where evidence should stand.
Contrarian: emotion versus rule
Now the question nobody asks. Does this sanction tell us anything about the cricket? Honest answer: no. The scorecard carries no runs, no wickets, no result. So what did we get? A procedural verdict that measures time, not quality.
Here lies the most popular misconception. Fans assume an over-rate fine means a team played 'badly' or 'dishonestly.' In reality, a slow over-rate is often the signature of a tense, competitive match — every ball debated, a review at every end, and the clock falling behind as a matter of course. The law is punishing the symptom, and the symptom can be born of the contest's very intensity.
There is another layer nobody counts — broadcast. A longer match means shifted advertising windows and scheduling pressure for rights-holders. This is a second-order factor, and I am not raising it as decisive proof — but it is worth asking how much strictness comes from fairness and how much from the calendar and the contract.
Here I recall an old lesson. The ghost goal taught me that empty stadiums still have witnesses. In that behind-closed-doors match of 2026, when the technology failed but the camera was watching, I learned that someone is always keeping the record. Over-rate is the same: even with no crowd in the ground, the clock is a witness.
Yet I concede an uncomfortable truth. I do not chase villains. I chase the sequence that made the breach inevitable. There is no villain in this match. Both teams being sanctioned means the breach was born not of individual intent but of a sequence — a slow pitch, a long innings, frequent reviews, a new venue. Before assigning blame, read the sequence.
And here the difference between India and West Indies (four overs versus two) gives a signal, but a weak one. India were at home, with more bowling options, yet fell behind on time management — that points not to deliberate slowness but to a collective rhythm problem. I am not confident in that conclusion, and when I lack confidence I say so plainly — that is my rule.
Takeaway: looking forward
Going forward, over-rate sanctions will become more visible, probably within the match itself — in-match penalties, or visible over-cut measures. I leave a question: if a match is slow enough to fine both teams, is the problem only the teams', or the clock-bound rule's own? An authority that wants to fit every match into a broadcast window must first admit that some matches are naturally bigger than its clock.
Editor's note: This piece is anchored to the ICC's official announcement, which names no score, no result and no player. I do not fill those gaps with speculation — I read the sequence, and test it against the mirror of the law.

