Playing Against the Clock: Two Teams in New Chandigarh, Four Overs, and Cricket's Invisible Time Economy

Nothing was written on the scoreboard. What arrived after the match was not a run or a wicket — it was an administrative notice, two names, two numbers. Yet that evening in New Chandigarh my eyes were on the clock, not the ball.

India bowled four overs short. West Indies bowled two overs short. Both teams were sanctioned — each Indian player fined twenty percent of his match fee, each West Indies player ten percent. The notice contains one line that matters most and that everyone reads past: "Time allowances were taken into consideration." That means the four overs and two overs we are seeing are the net figures left after allowances were credited. The raw delay was greater.

I am not writing this to take a side on the decision. I am writing because over recent years I have noticed that cricket's least-discussed and most influential decisions happen before the ball is bowled and after it is done — in the match referee's room, in the timekeeping ledger. And tonight one page of that ledger has been opened in front of us. Sixty-four matches taught me that one spreadsheet is never enough. Today's notice is another proof of that.

This notice gives us no result. No one is named. There is no series context. What exists is a time-management calculation. So today I will not write about cricketers. I will write about the clock.

A cricket match is really two competitions: one of runs and wickets, and one of time. The second is never shown on the scoreboard, yet it quietly shapes the first every single day.

---

The law nobody watches on the field

Under the ICC's playing conditions, each ODI innings must maintain a minimum over rate — roughly fourteen point two eight overs per hour. A fifty-over innings therefore takes about three and a half hours, plus allowances for intervals, innings breaks and unavoidable delays. That allowance is the real technical ground, because when the match referee tallies the shortfall he does not just look at the clock — he looks at which delays were sanctioned and which were the team's own responsibility.

The accounting is not as simple as it sounds. A delay can arise from many causes: DRS reviews, injuries, consultations with umpires, a batter changing gloves, a ball change, spectator stoppages, light checks. Some delays are part of the game, some are outside it. Under ICC rules certain delays are automatically excluded — innings breaks, stoppages on the umpire's instruction, medical assistance. The rest accumulate second by second, and in the end convert into overs and into sanctions.

I have long been interested in this rule. In 2026, when I watched all sixty-four matches of the Russia World Cup from a share house and logged twenty-nine penalties, every VAR intervention and every review duration into a forty-one-column spreadsheet, my deepest interest was in a two-second gap — the two seconds between the referee's hand reaching the earpiece and the arm going up. What I understand today is that the over-rate calculation is exactly the same kind of invisible gap. We watch the score; nobody shows the gap.

The penalty scale is graded too. A first offence for a minor shortfall generally brings five percent of the match fee, ten percent for a heavier one, and twenty percent plus suspension points for severe or repeat breaches. Within the ICC framework the captain carries a distinct responsibility, because the moral duty of managing time on the field ultimately rests with him. This is where the first subtle note of tonight's incident sounds: India's four overs versus West Indies' two means India were the more delayed fielding side on paper, but both captains stand under the same rule.

One thing is worth remembering — this kind of sanction is not a certificate of a team's discipline, nor the opposite. It is a procedural document. What it says is that on that day, at that ground, time broke down for both sides. Why it broke down, the notice does not say. And why is the real question, because the sanction is the outcome while the cause is the process — and I always want to see the process before the outcome.

---

Where I was standing

The first lesson of my professional life came from a knee, not from cricket. A knee reconstruction at nineteen ended my playing career, and I became a media student. But before that, on May 7, 2026, sitting at Allianz Stadium in Sydney for the A-League Grand Final, I did one thing — I coded all 118 decisions Jarred Gillett made across 120 minutes. Where he stood, how far from play, how clear the signal. That three-thousand-word blog paid me nothing. But from that day I stopped writing about whether decisions were right and started writing about how they were produced — position, sightline, angle of view.

Tonight's New Chandigarh incident lands in exactly that lens for me. We know India bowled four overs short, West Indies two. We do not know why. I want to fill that gap, not with imagination but by separating the angles through which time is lost.

First, a rough sum to seat the numbers. At the ODI minimum over rate of roughly fourteen overs an hour, four overs is about seventeen minutes, and two overs about eight to nine minutes. Remember — this is the time left after allowances. The raw delay was more than seventeen minutes for India and more than eight or nine for West Indies. In a fifty-over innings, seventeen minutes feels small. But in the rhythm of a game, seventeen minutes is nearly three or four overs of natural pace, or a full drinks break.

These numbers are not merely the measure of a fine; they are minutes the fielding side spent on its bowling rhythm, its field-placement discussions and its captain's planning — yet not a single mark of it appeared on the scoreboard.

---

Where time disappears: one evening from four angles

I do not trust a pattern until it survives three different angles. So I want to look at tonight's lost overs from four separate angles, testing at each one: is this true for both teams, or mostly for one?

First angle: DRS and the modern ODI's new clock

In the modern ODI, the biggest time-eater is the review. Every DRS call takes a few seconds to sometimes a minute and a half — ball tracking, slow-motion replays, snicko, umpire's call, then the verdict. If a match has six or seven reviews, and two or three of them fail, eight to ten minutes vanish on reviews alone. And those eight to ten minutes go straight into the over-rate ledger.

There is a subtle but important point here. Under ICC rules some review time is excluded — especially when the review arises from the umpire's own doubt, or when ball tracking suffers a technical fault. But player-requested review time is generally not excluded. So the modern ODI has produced a strange equation: the more reviews players take, the deeper in debt the team is to the clock.

And this equation is no different for either team. Both sides take reviews. So when India bowled four overs short and West Indies two, a large part of it may be the total number of reviews in the match — shared by both teams. This is where I first feel that reading this sanction as "India were slow" or "West Indies were sluggish" is wrong. It is a joint time-inflation, touching both teams, though not equally.

Second angle: pitch, ball and the quiet influence of a high score

ODI over rates are worst in two kinds of matches — very high-scoring ones and very slow pitches. In high-scoring matches boundaries come often, the ball must be retrieved, fielders shift again and again, new balls are brought, and teams confer between every over. On slow pitches batters take time, bowlers slow their run-ups, and umpires inspect the ball repeatedly.

The New Chandigarh stadium is relatively new. A new venue means less-known pitch behaviour, and less-known pitch behaviour means more hesitation, more discussion, more time. I keep this as a weak signal only — the notice gave no information on the pitch's character or the score. But since four overs survived even after allowances were credited, we can safely say the innings was not the kind to end quickly and easily.

Here the second angle supports the first: if the pitch is slow and the score high, both teams lose time — and that is exactly what happened.

Third angle: injuries, drinks and the quiet economy of intervals

Now to the part that interests me most, because I believe ninety minutes of silence can explain more than a thousand replays.

In 2026, with the A-League restarted behind closed doors, I sat in a junior producer's seat at a Sydney sports desk, listening to the empty Bankwest Stadium for the Grand Final of Sydney FC versus Melbourne City with headphones on, transcribing the on-field voice of referee Chris Beath — 412 verbal instructions in 90 minutes, from "no, no, no" to "green, green." That day I learned that a match's true rhythm sometimes escapes the camera and is caught by the microphone — intervals, breaths, repetitions.

Over rates are part of that same economy. How much the captain and bowler confer between overs, how quickly fielders move to position, how often the umpire asks for a ball change — all of it creates an invisible expenditure. Twelve to fifteen small stoppages in an innings, each ten to twelve seconds, add up to two or three minutes. Add two or three injury breaks, where the physio enters the field, and each is four to five minutes. Add it up, and suddenly you hold a four-over calculation.

This is where I want to pull the biggest warning, because interval fixation is an old ailment of mine. Treating every break as a cause is dangerous. So I say clearly: this kind of break is a plausible explanation of lost overs, not a confirmed cause. The notice mentions no injury or break. I only want to show that the whole process of losing time is not captured by the camera — it happens while the ball is being returned, while a fielder walks, while the umpire takes a note.

Fourth angle: what the gap between the two teams' accounts says

Four overs versus two. The gap is interesting, and I want to see it from two sides, because I look at position before outcome.

One explanation is that India took more time while fielding that day — perhaps rotating more bowlers, changing more fields, taking more reviews. Another is that West Indies perhaps did not bowl for a large part of that match, or their innings ended quickly. These two explanations differ, and the notice does not tell us which is true.

But one thing I can state firmly: both teams were guilty of the same offence in the same match — and this fact itself is not a story of team discipline, it is a story of match environment. If a team is institutionally slow, it repeats across a series. Here both teams were caught once, in the same match. So my reading is: the match itself was time-expensive.

My notebook has a separate column for this kind of event, which I call "time-inflation." I record the match type, the number of reviews, the likely breaks, and the allowances. Tonight is a classic example for that column — two names, two numbers, and behind them a whole invisible process.

---

The contrarian view: we blame the wrong team

Now to the place where my view of this incident separates from the crowd.

Over recent years I have noticed that whenever an over-rate sanction lands, fan reaction splits in two. One camp says the team wasted time on purpose — it is a tactic, an abuse of the rules. The other says the rule is inhuman — why put the clock on players in such heat, such effort?

I agree with neither, because both camps start from a wrong assumption — that over rate is a product of a team's will. In reality over rate is almost never a product of will. It is the sum of all the unavoidable stoppages in a match. If you want to reduce that sum, you will not do it by fining teams — you must change the structure of the game.

This is where I feel most anger at the fans who one-sidedly blame a single team. In tonight's incident both teams were sanctioned. So who is guilty? The answer is — no one, or everyone. The match itself was time-consuming. And what I find strangest is that we are discussing which team was slower, while nobody asks: is the game's rule actually ready for this delay?

Look, the modern ODI has come to stand against itself. On one hand we want more reviews, more checks, more fairness — because one wrong decision within 120 minutes can turn a series. On the other we want the game to finish in three and a half hours, because broadcasters have schedules and audiences have patience. Satisfying both at once is practically impossible. Adding reviews adds time; cutting time means cutting reviews; cutting reviews means cutting fairness. That triangle is hidden in tonight's notice, and nobody is talking about it.

One more thing I want to say, the most important to me. Who does this sanction actually hit? Twenty or ten percent of a match fee is small to players. But the accountability sits where the captain is. Because in the framework the captain is the owner of time on the field. And if a captain repeatedly falls into this trap, the shadow of suspension descends on him — even though the captain is precisely the person with the least power to control time. He cannot stop a review, cannot stop a physio entering, cannot stop an umpire inspecting the ball. He is punished for an offence he did not commit alone.

Here is the rule's greatest weakness: the punishment lands on the individual, but the cause lives inside the structure.

---

Time and money: the connection nobody wants to see

I did not want to write about cricket's economy here, but one connection cannot be avoided. An ODI is supposed to finish in three and a half hours. The broadcaster builds its ads, its analysis shows, its next fixture around that three and a half hours. If the match runs twenty to twenty-five minutes long, the schedule breaks.

So the over rate is really a broadcast-linked problem, expressed in the language of the game. I know many will dislike this — some will say cricket is played for the game, not for time. I agree. But the truth is that the person calculating this sanction holds a dual role: he is the guardian of the game's fairness, and at the same time the guardian of the game's time limit. These two duties cannot always run together.

I do not know exactly how late tonight's match finished, because the notice does not say. But I know that four overs and two overs means the match was longer than normal. And that is not only the players' hardship — it is the whole arithmetic of a broadcast cycle.

Here I want to be careful, because I do not want to claim without evidence that this sanction is imposed under broadcast pressure. I only signal this: the strictness of the rule and commercial interest walk in the same direction, and that walk puts pressure on teams. I keep this as an assumption, not a conclusion.

---

My own ledger against time

I am writing this from a desk in Sydney, not sitting at the New Chandigarh stadium. I was not at the ground that evening. But I have a habit — I keep a notebook per series, where I record over rates, reviews, breaks and likely time-inflation. Many things go wrong in that notebook. The numbers do not match. Assumed breaks are later proven false.

Once in a series I calculated and declared a team institutionally slow. It later turned out the pitches in that series were abnormally slow, and both teams' accounts were nearly identical. That mistake is etched in my mind. Because it taught me — numbers look beautiful, but numbers are not proof.

So tonight I caution myself too. India four overs, West Indies two — from these numbers I cannot say India played slowly or West Indies quickly. I can only say that on that day at that ground the two teams together lost six overs of time, and it was nobody's plan.

And it is from such events that I took my real lesson: cricket's most important decisions are often the quietest. A review decision everyone sees, discusses, argues over. But the decision that comes from the timekeeping ledger — where nobody places a camera, where nobody watches a replay — changes the game just as much, and nobody speaks of it.

---

Through the referee's eye: process versus outcome

I once wrote that I counted 118 decisions before I understood my own knee. It is a metaphor, but there is a truth behind it. The knee taught me that blaming what I cannot control is futile. Likewise, blaming a captain who cannot control reviews or injuries is a weakness of the process, not the fairness of the outcome.

Here I want to place two vantage points side by side.

From the on-field umpire's angle, the delay fragments into every small moment — a wait for the ball to return, time to strap a pad, a discussion to explain a signal. He does not see it as a delay; he sees it as a natural flow.

From the match referee's room, those same moments accumulate, are counted, are credited, and in the end become a single number — four overs.

These two angles are two faces of the same reality. And here I want to be clear: the referee who sanctions is not inhuman; the umpire on the field is not inattentive. Both see different parts of the same truth. We spectators often see only the outcome — four overs, twenty percent — and judge both men on that outcome.

I do not stand for any decision until I have seen it from at least two positions — because one angle never shows the whole truth, and ninety minutes of silence can explain more than a thousand replays.

---

Toward the end: can the clock be made the game's friend?

Now to the question most important to me. Is there anything to learn from this?

In my view the sanction system is fine but incomplete. It treats a symptom, not a cause. If we truly want to solve the over-rate problem, we must change the process inside the game.

First, I want a visible clock on the field. Just as a football match shows time, an over-clock should be visible to all — players, spectators, broadcasters. My experience says visibility creates accountability. If a captain sees every over that he is behind, he will speed up himself — without the fear of a fine.

Second, review time should be deducted from the over-rate calculation at a fixed ratio. Because reviews are vital to fairness, and if players are punished for them they will start cutting reviews — which harms the game.

Third, the structure of the captain's individual liability should be reconsidered. If the liability is the team's, let it be carried collectively. Because most of the power to control time on the field is not in the captain's hands.

And finally, the most important proposal: over-rate statistics should be published series-wide. Today we know one match's sanction, but not how each team managed time across a series. Publishing a series-long timekeeping ledger would let us separate a single match's accident from an institutional trend.

I know these proposals will not be easily implemented. But I can say with certainty — as long as cricket hides its clock, notices like this will be our only source. And a notice never tells a whole story; it gives only a number.

That evening in New Chandigarh the scoreboard said nothing. But the clock said a great deal. The question is — did anyone listen?

— Root: Referee