Fixture Load, 132 km/h, and the Poll That Rewrote the Model

Hook: The Last Ball on the Speed Gun

At a quarter to three last Friday night I was sitting in front of a laptop in my Manchester flat, watching a T20 franchise knockout. In the sixteenth over a right-arm quick came on to bowl — I am keeping his name out of this, because the story is not about him, it is about the number. His first ball read 141.2 km/h. The twenty-fourth ball of the same spell read 132.4. A six-to-seven km/h drop across one over is invisible on television; nobody in the comments notices it. On the spreadsheet it shouts.

I traced the ball back. Every delivery, every reverse-swinging seam, every slower ball, laid out until the highlight forgot where it began. That 132.4 was not the story of one over. It was the balance sheet of twelve days, two leagues, four flights and three sleepless nights.

Context: The Calendar Is the Real Venue

Over the past decade the biggest change in franchise cricket did not happen on the pitch; it happened in the calendar. UAE in January, Pakistan in February and March, India in April and May, the Caribbean in June, England in August, Bangladesh in December — a top-tier quick now plays four or five separate tournaments a year, with the flights, hotel rooms, conditions and the pressure to win every single night.

Look at the injuries. In October 2026, just before the T20 World Cup, Shaheen Afridi's knee ligament came under strain and both his pace and rhythm shifted during the tournament. That same year one of India's leading quicks was ruled out long-term with a back stress fracture and missed the World Cup entirely. In Bangladesh, the board's workload management of Taskin Ahmed has been debated for years — how much he plays, which series he skips, who decides.

I joined the sports desk of The Daily Star in 2026, first as a scorer, then a reporter. In 2026 I turned a hobby page into a professional cricket portal. Then came ScoutLab and the Football Analytics Lab in Manchester, and the work stayed the same: I read a player's body as a time series, not a colour reel. From that experience my position is simple — fixture congestion itself is the biggest injury culprit, and no medical team can save a player from two games a week.

The method is deliberately plain. Over three years I logged ball-by-ball data on 48 fast bowlers across six leagues — roughly 11,000 overs — recording dates, days since the previous match, travel days, overs per innings, slower-ball ratio and any post-match medical update. I do not have physio data and never want it. I want the outside record to be sharp enough that insiders' decisions can be questioned from the outside.

Core: A Column Called Load Debt

In my model there is a column called load debt: load debt = overs bowled in the last 14 days ÷ rest days taken in the last 14 days. Why 14? Because nine overs on four days' rest and nine overs on two days' rest are not the same thing, even though the scorebook writes "nine overs" for both.

In my dataset, once load debt passes 4.2, the probability of a soft-tissue problem that disrupts play within the next thirty days rises clearly. That is also where honesty is due: 48 bowlers is a small sample. Bowlers are not interchangeable — action, knee anatomy, age and even flight load change the arithmetic. The threshold is not a final limit, it is an early warning. I wrote that into version one on the day I published it, so that pressure later would not let me quietly build a different version. Every number has a first touch, and every first touch has a witness; without the witness, a number is not evidence, it is only a probability.

After the match I ran a poll: was the pace drop mainly workload, or a changed action? Eight thousand four hundred votes came in. Sixty-one per cent said workload, thirty-nine per cent said a remodelled action from rehabilitation. I do not treat the poll as a verdict, I treat it as an input. It showed me that fans read a pace drop as technique and hear the echo of fatigue less often. The model did not change because of the speed; it changed because you voted.

So two variables went in. One, back-to-back spell interval — the hourly gap between two consecutive spells. Two, slower-ball ratio drift — how much slower-ball usage appears in the first four overs versus the last four. A tired bowler tends to cling to the slower ball, because when pace is gone, variation is the last weapon.

The second variable paid off immediately. Across the last 34 innings in the sample, where slower-ball drift exceeded 22 per cent, boundary and six rates in the final two overs were markedly higher than in other spells. Falling pace and leaking runs are two symptoms of the same body. The speed gun shows the first; the second loses the match.

One more thing became obvious. For a bowler returning from injury, load debt cannot be applied in the first two matches, because the body is relearning and the old baseline is dead. They need a separate curve, written from scratch rather than patched onto old data.

Contrarian: The Speed Gun Is an Edit, Not a Witness

Before believing a "his pace has dropped" highlight, ask who measured it. A speed gun reading depends on radar placement, camera angle and which point of the delivery is timed. Two broadcast feeds of the same match routinely differ by several km/h. The 141.2 and 132.4 above came from the same feed, so the comparison holds. But "he used to bowl 145 and now he bowls 138" usually places two different platforms, two different spells and two different angles side by side.

The second trap is statistical. Workload correlates with injury; that is what my model says. Correlation is not causation. A bowler loses form, asks for a defensive field, and the captain gives him fewer overs — the overs fall, but the injury still arrives. Sometimes the over count is a consequence, not a cause. I stay careful there, and I do not worship the dashboard; I ask who is missing from it.

Takeaway: What to Watch Next Window

If you genuinely care about player health in the next franchise window, watch three things. First, the medical and injury-replacement language in contracts — that reveals how much a club really values the body. Second, which league a bowler skips — the rest gap is the true price, and nobody writes it into a contract. Third, your own model: have you actually tested it, or merely rearranged last season's numbers?

Highlights are made in the edit; healing happens in the rest. The gap between those two truths is the most important cricket story of the next two seasons.