Spell Count, Not Wicket Count: Bangladesh's Pace Workload Ledger and the Quiet Collapse of the Fourth Innings

Fourth day at Mirpur, second session. At sixty-six my eyes still swing between two places — the scoreboard and the speed gun. In that session something caught my attention that will never reach a thumbnail. The seamer was hitting 141 kph in his first spell; by his third it had slipped to 134, and the left arm was arriving a beat late before release. The very next over he shelved the out-swinger and went flat. The body had rewritten the script on its own.

The scoreboard said: three spells, 3 for 27. My notebook said: six overs, five overs, four overs — fifteen in total; nine minutes of rest between spells; fourteen days since the previous Test. The first set of numbers goes to the press conference; the second set goes to the physio.

I opened the spreadsheet and let the tournament lower its voice. The timeline was loud, so I regressed it until the noise fell away — because that wicket, replayed three times on television, was really the interest paid on the previous twenty-eight overs of fatigue.

Context: what I count, and why

My ledger has been running since 2026. That year, as new media was rising in Mumbai, I launched a paid data newsletter. The first lesson came from England Under-17's World Cup win in India: 28 goals against an xG of 22.4. I told clients the scoring was unsustainable. The following year, in Russia, Spain against Russia produced 1,029 passes, 74 percent possession and 2.4 xG — and a 1-1 scoreline. That taught me one thing: the number shouting loudest usually carries the least information.

In cricket that lesson has to be translated differently. In football I talk PPDA and xG; in cricket those seats are taken by spell length, recovery minutes, release-speed decay, dot-ball audits and catch-drop accounting. I do not measure a bowler's career in wickets. I measure how often and how quickly his body has been forced back into service.

The method is simple but ruthlessly patient. I keep six columns: overs per match, overs per spell, rest time between spells, gap between matches, total travel days, and innings-wise average release speed. Read them separately and you reach the wrong conclusion. Count only overs and you will never understand why a bowler goes limp in the fourth innings.

I do not compromise on sample size. Six bright matches are a notice, not a report. I generally publish after twelve to fifteen consecutive matches, and by then the headlines have already formed — but my numbers survive.

Core: the fourth-innings story is really the third-spell story

One pattern keeps returning in my ledger of Bangladesh's seamers. In the first innings they hold their speed well. Enter the second innings and spell lengths start stretching — not six overs but ten. The cause is situational, not tactical: when the first innings yields no quick wickets, captains lean harder on their quickest bowler, and that pressure compounds at the end of spells.

In my calculation, average release speed in the fourth innings falls below the first, and the decline is not one single spell — it is a staircase descending from the first spell to the fourth. A bowler who clocks 139 kph in spell one sits near 132 in spell four. Seven kilometres is nearly half a second of extra reaction time for the batsman — enormous in Test cricket.

Yet the two bowlers end with similar wicket counts. Here is my core grievance: we judge bowlers by output, never by depletion.

I do not treat the fourth-innings collapse as a separate event. I treat it as the refund on the second spell of the second innings. Fatigue accrues in the ledger and is withdrawn on the final day. That is why my previews say the next innings is really the harvest of this innings' rest.

Let me spread the data out.

When I plot overs against recovery minutes together, the decline is not linear — it comes in lurches. Speed holds almost flat from spell one to spell two; the lurch arrives at spell three, if the interval drops below eight minutes. In Test cricket the tea break and lunch create safe windows. On days when sessions are extended, or light delays push the start later, that window narrows.

In Bangladesh's case another variable enters: the character of the pitch. On a fresh Mirpur surface a seamer is obliged to bowl twelve to fourteen overs across the first two days. That loan returns with interest on days three and four. I log that interest model explicitly.

The most painful data comes from bouncer counts. In matches where a seamer sends down more than twenty-five bouncers, his average release speed in the following match almost always dips. I now use it as a warning signal. On a thumbnail a bouncer means aggression; in my ledger a bouncer is an instalment on future fatigue.

The illusion of economy, and the dot-ball audit

In T20 cricket we judge bowlers by economy rate. I say the measure is half true. A figure of six an over looks tidy, but it can be built two ways — many dot balls plus the odd boundary, or a completely empty run flow with no pressure at all.

So I separate dot-ball rate from quick-scoring ratio. A bowler who delivers two dots and fourteen singles across four overs will show a good economy, but he is not creating any squeeze.

In my ledger the most valuable bowler is not the one with the lowest economy — it is the one with a high dot-ball rate and a high ratio of false strokes. The first is aesthetics; the second is pressure.

I have counted the dot balls that never make the thumbnail.

That is why I keep a separate ledger for Test spinners. If someone like Taijul bowls more than twenty-five overs in a day his pace barely changes, but his drift does — how straight the ball is arriving. A spinner's fatigue never shows in speed; it shows in the patience of his length. In Mehidy Hasan's case that patience is his fortune, and it is what keeps him fit to bowl long spells.

Defensive accounting: labour nobody records

I also count cricket's defensive labour, because it is the most ignored. A keeper's footwork per innings, low catches, improbable one-handed takes — none of it reaches a highlight reel. Yet a single missed stumping can turn a series.

I have kept that ledger on Mushfiqur Rahim for fifteen years. We talk about his batting because his double century at Galle in 2026 — Bangladesh's first — is written into history. The hundreds of runs his gloves quietly save are written nowhere.

That is the heart of my complaint: thumbnails decide worth, while consistency statistics — which are always silent — decide merit.

Run-outs, saved singles and the fielding map

I keep an innings-wise fielding map: which fielder covered which zone, and how often. It shows plainly that a good fielding side saves two to three runs an innings. Across a series that is twenty to thirty runs — often the margin.

Those runs enter no record book and no memoir. I keep a separate page for them. I keep a ledger for legends, because memory edits its own columns.

Auctions, valuations and the light of miscalculation

Franchise auctions price seamers on last season's wickets and raw pace. My ledger says the price should be set by over-bank, age-adjusted recovery time and back history.

A large fee is a hypothesis; the season is the peer review.

I never write a bowler valuation without ten matches of rolling data, however large the fee.

Contrarian: correlation is not causation

Now I have to stand against myself, because a pure workload theory is its own trap. Not every decline is fatigue. Three separate causes often paint the same picture. First, a change in action — someone returning from injury on a shorter run-up looks tired. Second, the pitch; on a slow fourth-day surface bounce drops, not speed. Third, the opposition's deliberate approach — when a batsman starts slog-sweeping, a safer, slower spell is a plan, not a crime.

So I never publish a fatigue estimate until I have run the action filter, the pitch filter and the opposition filter. With a small sample I hold the conclusion back, and that is my professional edge — even if it looks slow to the reader.

One more thing must be added, which few have the courage to say plainly. The roar of a big stadium and the aura of stardom leave marks on decisions — especially on marginal DRS calls and umpire hesitation. I do not call it conspiracy; I call it a measurable effect. The courage to review against a big name is not the same as the courage to review against a smaller side. That is not a secret formula; it is the sound of the ground.

Injury and comeback: the account nobody keeps

My fatigue ledger drives me to another reluctant conclusion. When a returning bowler takes no wicket in his first match back, we raise questions, as if the return were an examination. I find that demand cruel. A comeback is a recalibration of the body; the first match is not supposed to deliver perfection.

So in the first three matches after a return my ledger does not measure speed — it measures how stable the release point is. When that returns, time handles the rest.

The religion of aggression and its missing arithmetic

In modern limited-overs cricket aggression has become almost a faith. Attack from ball one, the same language from openers to the lower order. In that ethos bowling is reduced to raw physical contest — who bowls faster, who runs harder. Craft shrinks; athletics expands. In my calculation this template has become imitable even for mid-tier sides, because it demands fitness rather than talent.

I am not calling it morally wrong. I am saying it compresses tactical variety, and nobody keeps the account of that loss.

The metric I trust most

One last thing. I never lead with possession as a penetration measure. I start with the defensive one-percenters — dots, blocks, quietly saved runs. Because attack wins matches, but defence wins championships.

This outlook makes me a dry, slow and often boring analyst. I have accepted it.

Takeaway: what I will watch in the next round

Over the next four to six weeks my eyes will be on spell length rather than wicket columns. Two things especially: first, whether a seamer given under fourteen days between Tests produces a third spell in the second innings that looks exactly like his fourth spell in the previous match. Second, whether teams bowling first after the toss are selecting bowlers on dot-ball rate rather than economy.

Sixty-six years taught me patience; the data taught me why it pays.

And one question remains, unanswered in my ledger: if we keep an account of wickets, who keeps the account of rest — the captain, the physio, or the scorecard?