The Gap Between Spells: Why Bangladesh's Pace Workload Ledger Cannot Be Counted in Overs

The Gap Between Spells: Why Bangladesh's Pace Workload Ledger Cannot Be Counted in Overs

0.74. That single number slipped past everyone at my desk. September 2026, Rawalpindi, the third day of a Test. I was logging ball by ball off the stream — which spell, which over, how much the body gave away. A Bangladesh quick's final spell carried 0.74 of the intensity of his first. The scorecard said something far more comfortable: 3 for 58, economy 3.2. "Outstanding spell" was written everywhere. Yet in the fourth over of that spell, the ball stopped travelling to slip and the batter defended with the pad alone — the real story of the match was being written in a different ledger.

My dataset is old. In 2026, on a twelve-person desk at a Dhaka sports outlet, I took the only data seat and hand-logged 1,140 balls from 96 Bangladesh Premier League matches. The desk's senior columnist called it "a girl counting pictures." Two BPL head coaches asked for the spreadsheet anyway. I logged every shot by hand before the market learned to price it — and the lesson from Belgium in 2026 has not changed: source or silence, and every number carries its expiry date.

Context: A Calendar That Manufactures Its Own Injuries

Bangladesh's cricket calendar is not smooth. It is in pieces. A dense BPL window in December and January, international series jammed into the gaps, a long-format National Cricket League in between, and six to eight weeks of silence across the rest of the year. That shape is the problem. A fast bowler's body does not know which mode it is in.

From years in the Mirpur stands I have learned a pattern the cameras never show. Inside the league window a quick bowls four overs flat out and returns the next day, eighteen to twenty-four hours later. A week on, he bowls eighteen overs in a Test innings. Then nothing for six weeks — no balls, no match intensity. What the physio room calls workload management is mostly overs added up in a spreadsheet. Nobody asks in what rhythm, at what intensity, against whom.

I do not chase edges. I audit the assumptions that create them. Every assumption in this piece carries a date; change the calendar and the numbers expire. When the schedule moves, my model moves.

Why "Overs Bowled" Is The Wrong Denominator

Overs are an output, not an input. Two quicks can each bowl 140 overs, but one does it across four months and seven matches, at eight or nine overs a week, while the other does it across six weeks and five matches at twenty-three overs a week. Landing forces, ground impact, the action's load — none of that is captured by addition. It is captured by density in time.

So I changed the metric. My ledger now holds two variables.

Spell-Gap Index (SGI) — hours between a quick's two high-intensity spells, defined as spells bowled above roughly 78% intensity.

Intensity Decay (ID) — the first spell's average intensity divided by the third or later spell's average intensity. Release speed, run-up tempo and follow-through length combine into a broadcast-derived proxy. It is not a perfect measure. It is my old result.

Core: What 1,140 Hand-Logged Balls Say

In my hand-logged BPL ledger, intensity decay fell with spell order. Against a first-spell baseline, the second spell averaged 0.91, the third 0.82 and the fourth 0.74. In Rawalpindi I saw exactly that 0.74, shrunk behind a cover drive. The fall is not linear — it drops far faster into the fourth and fifth spells than across the first two.

Here is the real finding. Intensity decay depends less on spell count than on the gap.

Where a quick returned inside forty hours, the next spell's intensity index averaged 0.86. Where the break was seventy-two hours or more, it averaged 0.96 — near-complete recovery. That broke my first assumption. I had assumed total overs were decisive. The sample said the gap was more decisive.

In the BPL's congested window it turns brutal. Dhaka's December winter puts three matches inside five days. Turnarounds fall to eighteen or twenty hours. In that scenario my log shows decay at 0.79. The scorecard difference is tiny — economy of 7.4 against 7.9. What surfaces next season is an injury or a form slump, and everyone calls it sudden. Injuries are not sudden. The window opens earlier.

I tried to measure that window. Quicks in my log who bowled three matches in a fortnight showed roughly 1.5 times the base rate of a workload-related break within the following four to six weeks. The sample is small, so this is a thesis, not a final line. Limits: six league seasons, thirty-four cases, error around ten percent.

One more thing I counted by hand, which no feed captures. The hidden overs. The day before a match, the first warm-up of the day, run-up reps, two overs of intensity on the pitch. On a Test day a quick bowls ten real overs and the equivalent of ten to twelve more. No club or franchise records them. The spreadsheet is my monastery; every formula is a vow of clarity — so when in doubt I keep them in a separate column rather than folding them into the total.

Adding those hidden overs does not change the picture; it clarifies it. Where SGI is above two days, the hidden overs are absorbed. Where SGI drops under thirty-five hours, match overs plus hidden overs almost certainly damage the next spell.

Contrarian: Injuries Arrive By Gap, Not By Overs

The popular reading is simple: Bangladesh's quicks break because they bowl too much. The data does not fully support that. The correlation between total overs and the injury list is weak. Correlation is not causation, and on overs alone my small sample shows a statistically fragile difference. Switch to gap and the picture sharpens.

The objection is obvious — perhaps the problem is age, action or pitch. I do not dismiss it. My ledger finds no independent age effect, but it cannot separate action types; broadcast angles make that impossible. So I hold the 2026 rule: I keep a position only while evidence and price justify it, then I close the book.

That brings Belgium back. Belgium against Brazil, Kazan, July 6, 2026. Brazil took twenty-one shots to Belgium's nine; expected goals were 2.4 to 1.1. Dhaka's front pages called it a robbery. I filed at 3 a.m. arguing that Belgium's 41% possession was a deliberate low block built on eighteen recoveries inside their own third. People were reading the result, not the process. Pace workload repeats that error: everyone reads the injury, nobody reads the gap. Belgium. Root: 2026 defending Belgium.

There is another layer the cricket market under-prices. Space exists between a fitness clearance and actual readiness. Franchises and agents price a bowler's availability, but that price is set before the medical. A transfer rumour is an unhedged position until the medical clears — and a "week-to-week" clearance is unhedged too, until the bowler is back at full spell intensity. In my log, quicks returning on week-to-week clearances never exceeded an intensity decay of 0.83 across their first two spells. Where the clearance ends, the truth begins.

One trap I want to avoid: workload alarmism. It is easy to forecast injury from gap data and irresponsible to do so. So I calibrate against base rates. In this ledger, most quicks flagged as at-risk actually finished the season without a break. Injury is not certain. It is elevated probability.

Takeaway: The Number To Watch Next Window

In the next series or the next league window, do not count overs. Count the gap between spells. Broadcast will not show it — the scorecard reports economy, and nobody outside the physio room logs the gap. When Dhaka's winter squeezes three matches into five days, count the hours of rest after match one. If it drops under forty, the next two spells will almost certainly lose intensity. The result may not change. But the headline two months later — "sudden injury" — will be hiding inside those thirty-eight hours.

When the stadiums emptied, the model had to learn a new kind of silence. My ledger is learning the name of that silence now: the gap.