Asia's Pace Load Ledger: The Notebook Nobody Keeps

Asia's Pace Load Ledger: The Notebook Nobody Keeps

Ahmedabad, 19 November 2026. On the eve of the World Cup final, an Indian pace-bowling coach walked the length of the pitch at the Narendra Modi Stadium. I sat in an empty stand with my notebook open. The next day, Mohammed Shami finished the tournament with 24 wickets — the most by any Indian pacer in a single World Cup, and it is there in the ICC's record book. Seven matches, 48.5 overs, an average of 10.70.

The number that actually mattered was not on the scoreboard. Ten weeks after the final, Shami had ankle surgery. No IPL 2026, no T20 World Cup. He returned in early 2026, but those eight months of absence never appeared in an official workload report. I had them in my notebook, because nobody else was writing them down.

The stadium was empty, so the notebook got loud. Shami's problem was never the total overs — it was the interval between two spells. Behind the 24 wickets lay 10 overs in a day at the Wankhede, then 9 overs in Lucknow 72 hours later. Nobody put a comma between those two lines.

Context: Three tiers of calendar, not one shared ledger

Asian cricket now runs on three tiers. One, ICC events — the World Cup, the Champions Trophy, the Asia Cup. Two, bilateral series, scheduled years in advance in the Future Tours Programme. Three, franchise leagues — the IPL, PSL, ILT20, BPL, LPL and now MLC.

None of the three owners keeps the others' data. The IPL physio knows how many overs his bowler sent down from March to May. The BCCI's NCA knows what he did from June to September. Nobody knows what state his back was in on 26 May, when he conceded 38 off four at Eden Gardens. Franchises treat that data as a commercial asset; national boards do not ask, because asking means accepting liability.

So the two things most often said about Asian pace bowling — "Asian fast bowlers are made of glass" and "Asia plays too much T20" — are both side issues. The real question is structural. Who bowled, how many overs, with what recovery interval: nobody in Asia keeps that account.

Core analysis: what the ledger would look like

After nine years of watching matches, my experience says injuries do not arrive on the day of peak load. They arrive in the week after the load drops. The muscle stays under sustained tension, then is suddenly released, then is suddenly loaded again — and that sawtooth is where the crack opens.

In 2026, with Mumbai City's under-18 side, I logged RPE, sprint counts and sleep hours for 23 players across 42 sessions. The coach threw away my first report. I re-watched every session tape and built a one-page table — and found that one specific build-up shape had produced 17 turnovers across two matches. From that day my rule was fixed: a match report opens with a verified training-ground number, and only then with opinion.

Apply the same method to cricket and this is what falls out. Across a franchise season, a frontline pacer plays 14 to 17 league matches. At four overs each, that is 56 to 68 overs in seven to eight weeks. Then a two-to-three-week break, then a bilateral series. In Test cricket, 20 overs in an innings is not unusual — 40 across two.

That total is not new. Wasim Akram, Zaheer Khan and Chaminda Vaas carried similar loads. What is new is the density of the overs and the travel. In Akram's time a pacer might visit six countries in a year. Now an Indian pacer gets two continents, six cities, four airports and three types of pitch in one calendar year — with a recovery window under four days between them.

The data nobody stores

Look at Jasprit Bumrah's file. A lumbar stress fracture in 2026, another back problem ruling him out of the 2026 T20 World Cup, Player of the Tournament at the 2026 T20 World Cup, then another back injury keeping him out of the 2026 Champions Trophy. The data between those four dates sits with three separate organisations — the NCA, an IPL franchise, and the ICC's match officials system.

Pakistan's picture is clearer still. Shaheen Shah Afridi's knee, Naseem Shah's shoulder — the injury picked up during the 2026 Asia Cup kept him out of that year's World Cup. The PCB announced a workload policy, but the policy lived on paper, not in franchise contracts.

Sri Lanka is the most familiar case of all. Dushmantha Chameera, Lahiru Kumara — stress fractures keep returning to both files. Since the LPL launched, Sri Lankan pacers play two domestic tournaments and a franchise league a year, yet the national physio has no central record of those overs.

Bangladesh has different names, the same story. Taskin Ahmed's back, Mustafizur Rahman's shoulder — both careers show a pattern in which national duty lands immediately after a franchise season. Not one of these three boards publishes over-by-over load data.

Contrarian angle: the problem is sequence, not volume

The outside reading usually goes one of two ways: "Asia has too many T20 leagues, hence the injuries," or "this generation of pacers is less fit." Both send the letter to the wrong address.

By match count, Asia is not far ahead of the rest of the world. An English county seamer plays 14 first-class matches a year, each carrying a strong chance of 40-plus overs. Australia's Sheffield Shield runs back-to-back rounds four days apart. In raw numbers they are not under less strain.

The difference is sequence. In England and Australia the season runs inside one structure — a beginning, a middle, an end. The workload curve can be drawn in advance because the calendar is known in advance. In Asia the calendar is now in fragments: two weeks of Tests, a five-day gap, two weeks of T20, a three-day gap, then a flight. Inside that fragmented structure the body never builds a baseline, so every series starts from a fresh peak.

The second problem is monitoring inequality. For Bumrah, Shami and Shaheen, rest decisions come out of a coach-selector meeting and reach the media. But the second-tier pacer who bowls 14 overs in the Ranji Trophy and then flies out for the ILT20 has no monitoring at all. The NCA's eyes are on centrally contracted players. The boy between Ranji and the BPL is in nobody's notebook.

Then there is age. In Asian domestic cricket a 19-year-old pacer is asked for 22 overs in an innings — because he matured early physically and the team leans on him. But maturing early is not the same as being physically complete. The bowling load booked in adolescence returns at 27.

Read the medical before the highlight reel

I once heard a sentence in a physio room that I still carry. A senior physio said: "I don't watch his bowling video, I watch the first three strides of his run-up."

That is the whole point of a load ledger. The first three strides tell you how much work the legs have banked and how much is running on habit. In an empty ground those three strides are the clearest sound in the world — metal studs on concrete have a distinct click, and when the foot starts dragging, the sound shifts. That sound never reaches a scorecard. It reaches the injury list.

The rhythm broke before the scoreline did. If a pacer cannot release four balls in an over from the same point, it means he is working but his body is not. That signal requires being in the ground; a scorecard will not show it.

Looking forward

The signals worth watching now will not appear on any scoreboard.

One: the first two weeks after a franchise season ends. Asia's frontline pacers are at their most exposed in that window, because there is no bridge between rest and build-up.

Two: which board publishes over-by-over load data first. The day an Asian board does, the logic of selection changes — and journalists start asking, after every match, how many overs today, how many last week, how long the break.

Three: the Ranji Trophy format. Overs bowled in domestic cricket are still nobody's account, even though that is exactly where national pacers are made.

I started writing down loads because nobody else was. The same reason still applies. The question is simple: for a player whose body is his entire capital, whose notebook holds the account — the franchise's, the national board's, or nobody's?