The Fast Bowler's Ledger: Where Injury Sits in the Franchise Calendar

Late one night last January, a row in my ledger turned red. The line read like this — one fast bowler, three numbers beside him: 162 balls in seven days, two days of recovery between matches, and an average pace drop of 4.3 kilometres per hour between his first spell and his third. Four days later he bowled two overs and walked off. The trainer called it a precautionary break.

In my ledger it was not a precaution. It was an invoice I had written four months earlier and nobody had read. When I opened the batting for Udity Club in the Dhaka league in 2026, I thought fast bowling was a matter of courage. At fifty-seven, sitting at a desk in Sylhet, I think it is an accounting problem. Costs can be hidden. Costs cannot be avoided. Injury is not fate; injury is a scheduled expense, and the receipt is usually cut before the match begins.

What The Ledger Actually Records

Building a standardised model across all 64 matches of the 2026 World Cup taught me that every claim needs a definition attached. In cricket, that habit is my only capital. Working on fast bowlers forces one decision at the very start: what is workload? Balls bowled? Overs bowled? Days?

My desk's ledger carries six columns, each written in man-days.

BB7 — total deliveries in seven days. A simple number, and the most misleading. SPM — spells per match. Six overs in one block is not the same as three spells of two. ASL — average spell length, in overs. RD — recovery days between matches, excluding travel days. SD3 — the gap between average pace in spell one and spell three, in kilometres per hour. TLI — travel-load index: flight hours, time-zone changes and hotel switches between matches, added together.

My thresholds run in three bands. Green: BB7 under a hundred, RD three or more, SD3 under 1.5. Amber: BB7 between a hundred and a hundred and fifty, RD two, SD3 between 1.5 and three. Red: BB7 above a hundred and sixty, RD two or fewer, SD3 above three.

This is my desk's internal standard, not a board's regulation. Here comes the first confession. I calibrated those numbers for the South Asian environment — 35 degrees, 80 per cent humidity, slow outfields. Drop the same figures into a New Zealand February and they will fail. Universal definitions and local calibration are not the same thing.

Counting Balls Is The Weakest Measure

From 2026 to 2026 I tracked 214 fast bowlers and logged 3,912 spells across nine franchise leagues and international cricket. The most uncomfortable finding in that dataset is that BB7 — counting balls — is the weakest predictor of all.

The reason is simple. A 90 kph cutter in a four-and-a-half-hour Test and a 145 kph bouncer at Mirpur at ten at night are not the same purchase. Counting balls makes them one. So I added a separate column.

HID — High Intensity Deliveries. The definition: any delivery above 92 per cent of that bowler's own match maximum, or any delivery in which the bowler produced peak sprint in the last four strides of the run-up.

In the franchise window of the 2026-25 season, 114 of the 682 spells I logged fell in the red band. Spells in the red band were followed by a match missed within 21 days in 18.6 per cent of cases, against 7.7 per cent in the green band. A ratio of 2.4.

Here is my caveat block, stated once. The sample is 682, and spell-level observations are not fully independent because many spells belong to the same bowler. I use the 2.4 figure as a headline, never as the sole basis of a board-level decision.

Spell-Decay: Pace Loss Is A Statement

SD3 is the hardest-working column in my ledger. The reason is not journalistic but human. You can tell when a bowler is tiring without asking him. The ball gets shorter. The yorker stops reaching the toes. The bouncer arrives at hip height.

Across the 1,270 spells for which I hold spell-by-spell speed arrays from 2026 to 2026:

| SD3 gap | Spells | 21-day recurrence ratio | |---|---|---| | 0 to 1.5 kph | 618 | 6.9 per cent | | 1.5 to 3.0 kph | 417 | 14.2 per cent | | Above 3.0 kph | 235 | 27.5 per cent |

A three-kilometre pace fall inside a single match is a stronger signal in my ledger than any ball count.

One thing needs stating plainly. Decay in SD3 is not always fatigue. Microphone height, ball brand, the ratio of slower balls, even a change in pitch pace will drag SD3 down. A decision that changes the conditions cannot be taken mid-match. I built a monastery out of ledgers, and the franchise window became my liturgy — but there is always a warning board nailed to the monastery door.

So I always read SD3 alongside three things: the delivery mix (percentage of slower balls and cutters), the phase in which the spell occurred, and how many rest days the bowler had before it.

The Density Of The Franchise Calendar

Here is the real story. A franchise league is 14 matches in 24 days. A bilateral series is five matches in 30. The first number looks about three and a half times more dangerous on a per-day basis.

Measure in days and you go wrong. Measure in balls and the picture inverts. A Test fast bowler can reach 140 balls in seven days; a T20 specialist tops out at 72. Anyone counting matches per day is weighing a book by its page count.

The real comparison has to be made in HID. In last January's window I separated two kinds of labour: bowlers used only in the powerplay and at the death, and bowlers grinding through the middle overs.

The first group averaged 58 HID per seven days, the second 34. But the first group's average SD3 decay was 2.8 kph; the second group's was 1.4.

In other words, the death specialist bowling fewer balls is breaking down faster in my ledger than the middle-overs workhorse bowling more.

If one franchise genuinely read that sentence, its auction table should change shape.

Travel: The Variable That Never Reaches The Table

TLI is an old idea of mine. When the stadiums emptied in 2026, I learned from 306 matches that when the environment shifts, every previous decision must be rebuilt. The empty stadiums of 2026 made every model I trusted confess its assumptions. Thinking about travel gave me the same lesson.

In the last window, one legal bowler's 11-day schedule ran like this: a match in Dubai, Karachi the next day, Dhaka two days later, Chattogram three days after that, then back to Dubai. Twenty-two flight hours, three time-zone changes, four hotel switches.

His BB7 was 96 — green. His SD3 was 3.1. Red.

I have written a rule into the ledger: once TLI crosses sixteen, the green colour on BB7 stops working. Travel sits outside workload; travel is workload's shadow.

I also admit this: I have not yet weighted TLI properly. The number sixteen comes from my desk's experience, not from a regression coefficient. I will change that line in future, and I am writing that down now.

Role Switching: The Hidden Line Item

This is the least discussed cost. A fast bowler who takes the new ball in the second over and returns at the death in the sixteenth carries two different demands in one body. The powerplay wants a full run-up and an upright follow-through. The death wants yorkers, explosive bracing and a bent back.

In the 2026 franchise season, across 227 spells in which a bowler operated in both the powerplay and the death within the same match, average SD3 was 2.9. Across 511 spells in which a bowler stayed in one phase, average SD3 was 1.6.

Trainers usually record over counts in their post-match reports. Overs do not lie, but overs do not describe a role.

This is why I tag every over with a role — powerplay, middle, death, extra. Without the tag, workload data is incomplete: useful to selectors, useless to physios.

Valuation: Who Prices The Risk

Part of my work as a transfer market administrator has been keeping valuation logs for transfers and auctions. In January I saw an old habit return. Franchises want workload data. They do not price the probability of a missed match.

I learned that a transfer fee is not a number; it is a sentence with a term sheet behind it. That sentence still has no clause for injury.

By my ledger's arithmetic, if a franchise priced SD3-based risk, the valuation band of a bowler with a red-band history would widen by roughly nine per cent — a discount on one side, conditions on big-match usage on the other.

A boundary must be stated. The idea of pricing SD3 works inside my model; demand for it in the market is unproven. A 214-bowler dataset can explain one auction season, but an auction is never settled by data alone — quota arithmetic, visa limits and board no-objection certificates sit at the same table.

Sport-Specific Caution

I have built models in both football and cricket over two decades. Dragging football's PPDA, defensive-line height or sprint counts into this argument would be a mistake. Cricket distributes load unevenly — decisions change inside a two-, four- or six-ball over — while football spreads it more evenly. Every number in this piece is cricket-specific. A load threshold from one format cannot be transplanted into another. A Test's 140 balls and a T20's 72 differ in delivery type, in the shape of session breaks, even in shoe-changing habits.

The Bangladesh Context

When I moved from cricket writing into the BCB media set-up in 2026 — The Daily Star called me the fine cricket writer turned media manager — I learned that high-performance data and media data are not the same thing.

In 2026, during England's tour of Bangladesh, I bowled to Kevin Pietersen in the nets as an amateur left-arm spinner. That day I understood that a batsman's patience is also a load metric. It simply never gets sold in the sales office.

In the BPL my frustration with fast-bowler management is one thing: we discuss injuries after they happen, never before. When domestic schedules are drawn, nobody prices travel load or SD3, because the tournament department draws the schedule and the medical department handles the injuries, and there is a wall between the two desks.

Mustafizur Rahman's franchise load, Taskin Ahmed's workload breaks under a central contract, Jasprit Bumrah's return at the 2026 World Cup after his 2026 back injury, Shaheen Shah Afridi's knee trouble in 2026, Cricket South Africa's load control for Kagiso Rabada — different events, but they sit on the same row of my ledger.

One thing must be said. This workload ledger is my own desk-level dataset. It is not a board's official injury record or an ICC record. No specific player's injury can be attributed from it.

The Contrarian Turn: Reading The Account Backwards

Here is my objection to my own model. I have shown a relationship between the red band and injury. Correlation is not causation. And the most uncomfortable thing I found was inside my own data.

I isolated my red-band cases. In many of them, BB7 had fallen in the two weeks before the injury, not risen. The reason is straightforward — the bowler already felt it, and the coaching staff had already started managing him.

BB7 is not a signal of injury; BB7 is often a consequence of it. The man was already breaking, and the first response was to reduce his work.

This is reverse causality. Counting balls is a rear-view mirror for a fast bowler. It shows where the car has been, not what is coming.

SD3 is different, because SD3 is measured inside the match and cannot be influenced by outside decisions. A coach cannot arrange SD3 by fiat. SD3 testifies on its own.

The second correction is more uncomfortable still. For six years I assumed that reducing load reduces risk. In a 2026 subset, bowlers rested for two matches mid-tournament for selection reasons showed an average SD3 one point two kilometres per hour higher in their first match back. A sudden rest is itself a cost, because rhythm breaks.

I record that as an amendment. My old rule was not wrong. It was incomplete.

The Signal For The Next Window

For a reader looking for one metric, this is enough: the gap between average pace in overs 17 to 20 and average pace in the first two overs of the match.

If a fast bowler crosses a three-kilometre gap twice in one franchise season, the green paper should come out of his valuation band.

For boards with congested bilateral calendars, such as England and Bangladesh, seven-day HID and travel load belong on their own websites — in a data file, not a newspaper. A bowler's body is a balance sheet. In 2026 I learned that no metric can ever replace the crowd. In injury accounting too, a man's silence is never zero. It is a variable.

The question goes to the desk that draws the schedule: this season, will you bowl your most expensive fast bowler in the seventeenth over because your league table needs points — or will you take him off in the sixteenth, because his spell-three figure in your ledger has already turned red?