240 Was Not the Price, It Was the Calendar Turning: Ahmedabad's Slow Pitch, the Cross-Seam Cutters and the Ledger of a Broken Anchor

Hook: Forty-two balls to spare

It was nearly half past nine on the night of 19 November 2026 at the Narendra Modi Stadium in Ahmedabad. Sitting in my Sydney flat, I opened the spreadsheet I have maintained since 2026 — every match's build-up shape, powerplay field settings, death-over line and length, spin match-ups, each in its own column. On the scoreboard two numbers were stuck together: 240 and 241.

The first took fifty overs. The second took forty-three. Same pitch, same night, same ball. India scored 4.80 an over; Australia scored 5.60. Forty-two balls were left in the chase. Looking at those two figures I understood that the story being told in the television studios — slow pitch, toss, dew — was at best incomplete. If the pitch really capped a side at 240, then 241 in 43 overs should not have been possible.

This is not a hot take from a single night. It is an arithmetic discrepancy, and I wrote it into my ledger that same evening.

Context: nine-nil against nought-two

India won all nine of their league matches at the 2026 World Cup. Rohit Sharma's side was the most complete unit of the tournament: Mohammed Shami's 24 wickets, the most by any bowler in a single World Cup, and Virat Kohli's 765 runs, the most by any batter in a single edition. Australia began the other way round — beaten by India in Chennai and by South Africa in Lucknow in their first two matches — then won nine in a row to reach the final.

Put those two records side by side and something emerges that almost nobody mentioned in the pre-match build-up. Six of India's nine wins came batting first, piling up a total and squeezing the opposition. Their middle order spent almost the whole tournament in comfortable conditions: a large target, low risk, a set batter above them. Australia walked the opposite road, repeatedly coming through pressure — batting first and recovering from collapses, or chasing 292 against Afghanistan in Mumbai on the back of Glenn Maxwell's 201 not out.

One thing about the pitch deserves to be remembered. The Ahmedabad surface was used, slow, low and black-soil. The square boundaries were long, the straight ones comparatively short. Pat Cummins chose to bowl at the toss. Rohit Sharma later said he would have batted anyway. The toss, in other words, gave nobody an edge: both captains were looking in the same direction with different explanations.

The dew story is in my ledger too, but as context, not as cause. Dew stops the ball gripping, reduces drift for spinners, makes the slog-sweep easier. But dew never fixes a batting order's sequencing. That is exactly where India's problem lay.

Core: a powerplay of fire, thirty overs of empty outfield

Rohit Sharma's 47 off 31 balls was the direct application of his own tournament model. In the powerplay he takes risk, because the arithmetic is simple: only two fielders are out, the ball is hard, and the short boundary is reachable. In Ahmedabad he did exactly that, and India raced to roughly eighty inside the first ten overs.

But here is my first observation, noted during the match: India's powerplay assault was planned; the thirty overs that followed were not. After Rohit fell, India's scoring between the 20th and 40th overs was probably insufficient on that surface — but the problem was not the volume of runs, it was their type.

What Cummins, Hazlewood and Starc did that night was the product of a specific plan built over three weeks after those first two defeats: cross-seam, cutters, and a length hammered into the pitch. On a slow surface a cross-seam ball stops suddenly; a batter going for the pull or the lofted drive top-edges or mis-hits. On that pitch the square boundary was far harder to clear than the straight one.

India's middle order had no rehearsed option against it. Kohli's 54 off 63 and KL Rahul's 66 off 107 were both serviceable innings, in no way bad. But their combined strike rate sat in the eighties, and no Indian batter found the boundary across two consecutive overs through that block. That is the real ledger entry.

Let me unpack it. In modern ODI cricket, middle-over batting follows one of two plans. One is the floor plan: a set batter stays in, guaranteeing four or five an over. The other is the ceiling plan: a batter who can take eight or ten an over, at higher risk.

India's final XI had floors — Kohli, Rahul, Jadeja. It had one ceiling, Suryakumar Yadav, and he walked out in the 47th over. India therefore played forty-eight overs in which the floor and the ceiling were never on the pitch together. Australia had Maxwell, Head and Marsh, and their middle order held both roles simultaneously.

And here is my second observation: India did not lose by batting badly; they lost by batting an incomplete sequence. If a batting order is a timeline, then India's timeline had a hole between the 35th and 45th overs.

Now Australia's innings, which is where the ledger becomes uncomfortable.

Travis Head's 137 off 120 balls is one of the great final innings, no doubt. But when I went ball by ball, I found it was not explosive; it was rhythmic. He took few risks in the first ten overs. He read Shami, Siraj and Kuldeep, and only then attacked.

That is where Marnus Labuschagne comes in. 58 not out off 110 balls is, in the language of modern analytics, almost a crime. But on that night, on that pitch, in that match, Labuschagne was the floor that made Head's ceiling possible. Their 192-run stand for the fourth wicket was the true turning point of the final, and its run rate never climbed above six — because it did not need to.

Australia were 47 for 3 with 240 to get and 47 overs to get them. Required rate under five. Two batters in that position can quietly knock off six or seven overs. Australia did exactly that. Then, when the spinners came on, Head found boundaries through the sweep and the cut.

I pulled one number out of that stand: Australia's run rate was in the fours for the first fifteen overs of the chase and above seven in the last ten. They did not create pressure; they held it, then released it. Nobody will call that aggressive cricket, or temperament. I call it sequencing.

Back to the discrepancy: why 240 was never a ceiling.

Because on that pitch boundaries were hard for new batters, not for set ones. A used surface gets slower still, but once you have read the pace, both the cutter and the holding ball can be scored off. Head and Labuschagne were at the crease for twenty-four overs, so they completed that reading. Nobody in India's order lasted that long — Kohli faced 71 balls, Rahul 108, but both fell late largely through their own lack of tempo.

Contrarian: the death of the anchor is a letter sent to the wrong address

For several years now one sentence has hardened into doctrine in ODI cricket: the anchor is dead. Analytics departments write it on their sheets. Strike rate is all that matters. Show them Labuschagne's 58 off 110 and they shake their heads.

I disagree, and my objection is not to the numbers but to their application.

The anchor has not died; the anchor is being placed in the wrong slot. The Ahmedabad final proves it. Australia's Labuschagne was an anchor, and he was one of the biggest reasons his side won. India's Kohli and Rahul were anchors too, and they were not the reason India lost — the reason was that nobody beside them was taking the ceiling role.

The lesson of my whole working life sits here: when analysis walks into a dressing room, it tends to look at a batter in isolation. But batting is never isolated — it is always a pair, a sequence, a handover. Saying 'anchors are good' or 'anchors are bad' is a denial of the rhythm of the match. Just as a fielding plan is only a hypothesis until the tape disagrees, a batting card is only a theory until the rhythm of the ground disagrees with it.

One addition here. If I had watched that same match as a women's ODI — same pitch, same cutters, same sequencing problem — where would the board and the broadcaster be? I raise it because I keep a separate column in the ledger that I have named 'who gets analysis, who only gets broadcast'. Year after year the same figures appear in it.

There is one more uncomfortable truth. Cummins, Hazlewood, Starc and Zampa built a specific pitch map over three weeks. From the defeat in Chennai they practised the cross-seam cutter, because they assumed the knockout pitches would be slow. That is not match preparation; it is preparation for the matches after the match — and in modern cricket that is where the real competition now sits.

India did the opposite. They ran one set pattern all tournament because it was working. Nine wins from nine — no coach wants to break that formula. But the gap between league and knockout is this: in the league you play what you can, in the knockout you play what you have learned. India learned nothing new for the knockouts, because nothing ever forced them to.

Takeaway: what to watch in the next cycle

That night in Sydney I added a new column to the spreadsheet: 'paired sequence' — how many floor batters and how many ceiling batters a side carries, and which over-block each of them walks out in. That column is my work for the months ahead.

The reason is simple. Ahmedabad proved that the real contest in ODI cricket now lives in the design of the batting order, not in individual talent. A side that can keep an anchor and an exploder on the pitch together will not merely defend 240 on a 300 pitch — it will chase 241 on a 240 pitch.

Next season I will watch two things closely. First, who a side sends out in the ten overs after the powerplay: two floor batters in a row means that side slows down even on a big-target day. Second, which bowling unit prepares in advance for knockout pitches rather than settling for league-phase success.

The last question I asked myself that night, before closing the laptop, was this: if the toss, the dew and the pitch were all neutral, then who exactly lost with forty-two balls to spare?

The answer is in my ledger. What is in yours is now worth checking.