The Franchise Workload Audit: When a Fast Bowler's Pace Shows Up in the Dataset

Last season, during a franchise T20 match, I was not looking at the scorecard but at the ball-tracking feed. A fast bowler was averaging 141 km/h in his first over. By his fourth, that average had dropped to 134. The scorecard said 4-0-28-2, a fine spell. But the release-speed series, the line-and-length variance and the delivery-to-delivery recovery time told a different story. A bowler operating seven kilometres slower than his own baseline in the final two overs, with two wickets that came from the batter's error rather than his skill, is not a success story — it is a warning row. I ran my first workload audit for exactly this reason: the eye test has no receipts. Context first, because numbers without context are merely decorative. Take the 2026 franchise calendar. Big Bash and ILT20 in January, SA20 and PSL in February, the IPL from March to May, then The Hundred and MLC in July and August, plus two or three bilateral series on top. Fourteen to sixteen T20 matches a year is now normal for a top fast bowler. The problem is not the total count but the density of back-to-back spells. A four-over spell means roughly twenty-four deliveries, preceded by travel, warm-up and pitch inspection, and followed by another match the next day. The body does not merely bowl; every delivery accumulates a measurable mechanical load. When I was on the print desk, I wrote figures — four overs, twenty-eight runs, two wickets. After leaving the desk in 2026, the day I learned to query the match, the question changed. I now ask: what state was the bowler in before each of those wickets? What was the speed decay inside his spell? And most importantly, where does this spell sit in his recent workload history? The core analysis belongs on three levels. First, intra-spell speed decay. Ball-tracking data shows that for most fast bowlers, the gap between the average release speed of the first two overs and the last two sits between four and eight km/h. That decay is the real indicator. A bowler who keeps it under three is not just fit — he is managing recovery. In my own tracking notes I call this gap the Speed Decay. It is more honest than the figure. Second, the revaluation of the powerplay. In franchise cricket the powerplay is no longer just a window for scoring; it is the most expensive asset for a wicket-taking bowler. Powerplay economy data from the 2026 and 2026 seasons shows that sides keeping their new-ball fast bowlers below seven an over gain a net run-rate advantage of roughly ten to twelve runs per match in the first six overs. But the hidden cost sits here: whoever attacks in the powerplay must be given one more over next match. That extra over is what gets added to the workload ledger. Third, the back-to-back spell. In a personal sample I found that fast bowlers playing three or more T20 matches in seven days roughly double their Speed Decay in the next spell — from four kilometres to seven or eight. This is not caught by total deliveries. It is caught by the interval between rest days. The spacing of rest is the true regulator, and this is where a quiet conflict has emerged between the ICC and the franchise boards. A league acquires a bowler at his auction price; the national team gets him for the rest of the year. Who bowls him how much is set not by total deliveries but by the gap in the calendar between the two parties. June 2026 is not irrelevant here. Across ninety-two matches behind closed doors I first understood that any major environmental change can be treated as a control group. June 2026 was the month the crowd became a control group. Fill the calendar the same way and the bowlers' bodies become a control group too — and we read the results in the injury list. Here is my central observation. The real metric of fast-bowling workload is not total deliveries but the ratio of Speed Decay to rest intervals. Total deliveries indicts everyone; the ratio reveals which spell was a planned attack and which was a tired body forcing itself. I have built a habit: in every match thread I log three rows per fast bowler — first-over average speed, last-over average speed, and days of rest since the previous match. Placed side by side, the forecast becomes checkable. For instance, five matches in fourteen days with two or fewer rest days should push Speed Decay past six km/h in the next spell. I write that claim with a date and grade it later. Turning speculation into a row with a primary key is the discipline — a transfer rumour is just a row waiting for its primary key; workload is no different. Now the contrarian part, because this is where I stand against my own model. Speed Decay correlates with injury, but correlation is not causation. The causes of decay include more than fatigue — pitch behaviour, ball age, action type, wind and humidity, even scoreboard pressure. A bowler may deliberately slow down in the final over to favour cutters, because on a dead pitch that is the right call. Then Speed Decay is strategy, not failure. And the reverse happens: a bowler who holds his pace may use an action that is worse for the lower back, yet this never shows up in the speed feed. So I refuse to treat any single number as a final verdict. I tier the sources: ball-tracking (high tier, machine-based), physio reports (middle tier, shaped by team interest), and the journalist's eye (low tier, admissible only as a hypothesis). Analysis built only on the low tier ends up blaming an individual for a systemic outcome, when the real driver is usually institutional — scheduling talks between boards and leagues, auction prices, and the guaranteed portion of contracts. Someone's injury is not a story of personal weakness but an accounting of rest days not shared between two institutions. There is a subtler trap I keep avoiding. The South Asian and English calendars are not the same, nor are the sources. Comparing workload management in a Bangladesh or Pakistan franchise league directly against England's county system ignores both sample size and context. Any comparison must state the board, the market and the sample size — otherwise the number can be true while the conclusion is wrong. So what should the reader take away? A usable habit. Next time you are impressed by a fast bowler's figures, log at least two numbers beside the scorecard — his first-over speed and his last-over speed. If the gap exceeds six km/h and the rest in between is under two days, read that figure as a warning rather than praise. If selectors see the same numbers, they will probably rest him next match. The question now belongs not to the audience but to the schedulers. If a franchise league wants to protect its most expensive asset — a fast bowler's pace — it must sell not just the number of matches but the accounting of rest between them. The board that does this first will write the shortest injury list over the next three seasons. The board that does not will watch its stars slowly settle into the dataset — just like that 141 drifting down to 134.