The Scan Is One Frame, the Sequence Is the Film: Fast-Bowling Load in the January–March League Stack

19 November 2026, Ahmedabad. The number printed beside Mohammed Shami's name at the end of that World Cup final reads 24 wickets in seven matches — the most by any Indian bowler in a single edition. The next officially recorded date arrives in February 2026: right ankle surgery in London, followed by an open-ended rehabilitation window. Between those two entries, India play no international cricket. The ankle carried no competitive load for roughly three months, and it still went to an operating table. I spent that period at a sports desk in Istanbul, reconciling Shami's match-by-match spell sheet — total overs per fixture, average spell length, rest between spells, travel days, and how many consecutive days he had been on the field. When the announcement came, someone on the desk asked whose fault all the cricket was. The answer was not simple, because his previous three months had been load-zero. The question was aimed at the wrong place. Before the ankle became a headline, it was a line in a workload log. The scan is one frame; to see the film you need the sequence. Over the past five years the cricket calendar has grown a new stack, and it sits between January and March. December and January belong to the Big Bash League in Australia. January opens the ILT20 in the United Arab Emirates and the SA20 in South Africa, both launched in 2026. The same month brings the Bangladesh Premier League. February belongs to the Pakistan Super League, running into March. The IPL starts in late March and ends in late May. International fixtures resume in June. For a fast bowler, the important fact is not how many leagues exist but what the stack has removed. What has been removed is the gradual load-building period from September to November — the off-season in coaching language, but a training block in physiological language. You may call it a holiday; tendons and bone do not. They call it the adaptation window. Baseball has standardised this idea for decades. Cricket still treats it as a luxury. From the Gulf, where I am based, the stack is easiest to see. Dubai is its geographic centre. Dubai to Karachi is a two-hour flight, Dhaka five, Johannesburg eight, Melbourne fourteen. A route that runs Big Bash to Dubai to Karachi to Mumbai in January is not eccentric; it is the cheapest itinerary available. Travel days do not appear in a bowler's load sheet as overs, but on the recovery ledger they cost exactly as much. My years of watching matches from this side of the world tell me something the broadcast rarely captures. In the middle overs of a Gulf league, nobody notices the difference between a first spell and a third spell, because the commentary box is looking elsewhere. What becomes visible is a length ball where a yorker should be. An ankle does not announce itself. It first appears as a difference in height. There is another layer to Gulf leagues that we routinely skip. ILT20 squads are built on invitations and contracts, and UAE domestic bowlers fill the gaps. Their match count is modest; their preparation time is arbitrary. Consider one Emirates quick: a franchise deal in January, a PSL replacement list in February, a domestic one-day tournament in March. Three medical teams, three strength-and-conditioning philosophies, one body. The version of his ankle history that a franchise holds is not the version his board holds. This is where the accounting breaks down. "Players are playing too much cricket" sounds reasonable and is scientifically incomplete, because it carries no definition. Too much of what — matches, deliveries, match hours, or the absence of days between fixtures? Load accounting requires three decisions before any number means anything: who is the population, how long is the window, and what is the counting rule. Change any one and the result changes. A Test match and a T20 are not the same load, and any average computed without admitting that is badly wrong. I keep a database of my own, and it is football, not cricket. In 2026 the Turkish Süper Lig returned after a 102-day hiatus. I was watching Radamel Falcao's comeback for Galatasaray; his first match lasted 34 minutes before his hamstring went. I pulled injury reports from 18 clubs and found hamstring episodes up 42 per cent across the first three rounds after the break. I then built a searchable database of 120 soft-tissue injuries, coding return-to-play days by age and position. The hamstring database did not predict the pandemic; it recorded what the pandemic did to hamstrings. The distinction matters. A database does not ask what happens next; it asks what actually happened. The hiatus did not weaken muscle. It created de-training, and the return to competitive intensity out of that de-trained state was the injury window. In cricket we saw the same logic in September 2026, when a lumbar stress fracture was identified in Jasprit Bumrah, who was pulled from the West Indies tour and returned the following January. In 2026 the same region failed again, and that year's T20 World Cup became something he watched rather than played, with the return arriving in early 2026. Drawing a straight line between the two episodes is easy, but doing it properly requires a dated chain: how many overs, in which format, with how many days of rest. That chain is not consistently in my hands. In July 2026, Shaheen Shah Afridi's knee gave way mid-Test at Galle. He missed the 2026 Asia Cup and the bulk of the T20 World Cup group stage, then returned for the November final. That return reads as a story to the media. To a medical team it was the output of a calculation that was never published. This is my central observation: return-to-play decisions are made where contract length, tournament deadlines and franchise need intersect, and we receive no transparent record of that intersection. Placed side by side, the three cases show a pattern that is about load distribution rather than injury type. In each, the rehabilitation window was contestably short, and in each, the route back ran through competitive matches rather than a graded block of overs. That is why I argue the loss of the off-season block is larger than any loss in match count. Adding matches raises load. Removing the block erases adaptation itself. The workload literature that shaped us most is the acute-versus-chronic ratio. It became enormously popular in the 2010s, then ran into statistical criticism, because the internal averages behind the ratio are methodologically fragile. I still use it, with a caveat: a ratio is a language, not evidence. A good language sharpens the question. It never supplies the answer by itself. Here I have to be plain, because no-speculation is not a gag order; it is a reporting standard. I do not hold a cricket soft-tissue series coded by league window. I hold a football database and match reports. They cannot be welded into one line. So the documented ledger stops here. The next sentence is inference, and I will state its confidence: the January stack has widened the return window for fast bowlers — medium confidence, because we have testimony for the start of the window and none for its end. Back to the ankle. An ankle does not collapse suddenly. It is a structure that absorbs several times body weight on every release, and the bill accumulates in sinus data nobody looks at. In Shami's case, seven consecutive matches preceded the final, every spell woven into the pressure of having to win. That load was measured all tournament. The bill arrived afterwards. Three months of rest did not forgive it, because rest does not repair damage; rest only builds the base from which new load can be added. When the joint is already broken, the question of the base is academic. Now the counter-question, because the popular explanation may be the weaker one. The common view is that injuries are rising because cricket is rising. Count matches, though, and we are not comparing like with like: a T20 played on four days' rest, a five-day Test, a night in transit and a match carrying drinks all get counted in the same column. An undefined average is as useless as an explanation for injury as it is as a forecast for next season. The real change is not matches added but blocks removed. A bowler who once built load slowly from September to November now finishes in November, flies in December and plays the second week of a tournament in January. That schedule contains rest. It does not contain rehabilitation. Rest is zero load; rehabilitation is controlled, rising load. Confusing the two means hunting for injury risk in the wrong place. Passing a fitness test and being ready for match load are different states, and that is the thread running through everything I write: a body can be fit while a sinus is not ready. The rush-back narrative also points at the wrong address in franchise cricket. No club forces a player; everyone's incentives simply point the same way. The contract is three weeks long, medical clearance is a checkbox, and the replacement list is already drawn up. Club arithmetic and player arithmetic become identical: return quickly. There is no villain here, only a structure in which a short window pushes everyone one way. Until recently nobody published domestic figures from inside that structure, and that absence is the real gap. So what should be watched in the next window? Three signals hold my attention. First, release speed dropping in the second and third spells. Second, the disappearance of the yorker at the death, the earliest expression of an unstable ankle. Third, the spell bowled the day after a flight. If any of the three appears in two consecutive matches, the question should be asked — and the answer sought from the training log, not the press conference. I do not ask what happened next; I ask what was documented first. When February's bulletin about Shami arrived, the spell sheet from three months earlier was still open on my desk, and that was the actual story. An ankle that had carried no load for a quarter of a year did not reach an operating table through haste. It most likely reached it through an accounting that began in September, and that nobody wrote down. Next season I will be watching the first three rounds of January, because that is where the return window is narrowest. And one question will stay open: will the Gulf leagues, which built this window from nothing, become the first in the world to require a mandatory pre-contract load block? If they do, a new line enters the injury ledger — and it will not be a fitness certificate. It will be a date.