The Fourth-Innings Crack: What the Pacer Workload Ledger Records, and What It Leaves Out

The Fourth-Innings Crack: What the Pacer Workload Ledger Records, and What It Leaves Out

Hook

In the third session of the fourth day at Mirpur, one thing caught my eye that the scorecard never records. In the seventh over of a spell, the pacer's release point dropped, his speed fell by four to five kilometres an hour, and his line drifted away from off stump towards slip. The scoreboard wrote, “one over, six runs.” My ledger wrote, “three dots from six balls, two deliveries at no-ball distance, one released.” At the striker's end the batsman was, at that exact moment, working out which ball to leave. In the fourth innings, Bangladesh's pacers concede roughly one and a half runs more per over than in the first, and their balls-per-wicket worsens by eleven or twelve. The number is not shouting. But the timeline was shouting loudly, so I opened the spreadsheet, ran the regression, and let the noise fall away.

Context

My ledger starts with overs, not runs. Runs are an outcome; overs are a cost. Explain an outcome without reconciling the cost and you get a story, not an analysis.

I keep four columns. One: competitive overs — Tests, ODIs, T20Is, domestic first-class, A-team tours, franchise leagues. Two: hidden overs — nets, match simulation, warm-up spells, throwdowns. I weight these at 0.6, because there is no batsman in the nets but the physical load is nearly identical. Three: the internal structure of a spell — how many balls in each spell, how many minutes between two spells. Four: the recovery window — how many days between matches, how much travel, how much of it went into acclimatisation.

My sample threshold is explicit. Before I write a claim about a pacer, I need at least ten matches of rolling data, and those ten must include at least three different venues. Otherwise I do not publish. Sixty-six years taught me patience; the data taught me why it pays.

One more element has to be added in the Bangladesh context, and outside analysts routinely miss it. In Asian conditions spinners absorb sixty to seventy per cent of total overs. That means pacers bowl short spells, but the intensity per ball is far higher — because they are used either to break the new ball or to hunt reverse with the old one. Fewer balls, more intensity; for recovery purposes that is worse than a long spell.

I learned another lesson in 2026, from a different sport. At the Under-17 World Cup in India, England scored 28 goals against an xG of 22.4 — an overperformance of 5.6. I wrote to clients that this scoring was not sustainable. By exactly the same logic, at the 2026 World Cup in Russia I took under 2.5 and Russia +1.5 in the Spain match — Spain's 1,029 passes, 74 per cent possession and 2.4 xG ended in a 1-1 draw, and Russia won on penalties. A pacer's speed obeys the same rule as those goals: an abnormally good run tells you only one thing, that the run will drift back towards normal.

Core Analysis

Let us begin with the annual overs burden. A frontline Bangladesh pacer, across domestic first-class cricket, A-team tours, franchise leagues and national duty, bowls a certain number of competitive overs in a calendar year — and to that you must add roughly thirty to forty per cent in hidden overs. The ledger total is therefore far larger than the scorebook total. What we discuss as a “bowler's workload” is in fact half an account. For a bowler like Mustafizur Rahman the gap is even wider, because franchise demand and national duty pull from both directions.

Next comes the question of window compression. Over recent seasons the gap between Bangladesh's home season and the franchise window has narrowed. Two series used to sit three or four weeks apart; now they are often ten to twelve days apart. In my ledger, pacers who received fewer than ten days of recovery between matches saw both their average speed and their line-and-length accuracy drop over the following three matches. That is not a guess; it is a pattern that keeps returning in my rolling splits.

Go inside a spell and another pattern appears. I log ball-by-ball speed and a pitch map for every spell. The picture is almost identical each time: after ball eighteen to twenty-four of a spell, the release point begins to drop and the line progressively slides towards leg stump. That does not mean the bowler is exhausted — it means his body is announcing its limit. If the coaching staff do not break the spell at that ball-band, the overs that follow become pure expenditure. In the spell maps of Taskin Ahmed or Shoriful Islam that bend is clearly visible.

The least discussed element is defensive accounting. A Test pacer's real value lies not in wickets but in dot balls and the keeper's work. A pacer who lands four dots an over is not the hero on the scoreboard, but he is the one controlling the tempo of the innings. I did exactly this exercise once with Alisson Becker — to measure what Liverpool were actually buying for £66.8 million, you had to look at save positions and distribution rather than a highlight reel. For Alisson I counted the saves that never made the thumbnail. The same principle holds in cricket: we count what is easy to count; what changes matches is what is hard to count. Taijul Islam's spell economy is rarely written about, because nobody wants to sell the story of dot balls.

The final link concerns rotation. Bangladesh's bowling unit has historically swung between two extremes — either bowled at full intensity, or suddenly rested. My ledger shows that a break in rhythm is itself a load. A pacer who plays continuously has a smooth decay curve; a pacer who plays two matches and sits out one takes time to find his speed in the first spell back. If rotation is not planned, it too is a cost. For a young pacer like Hasan Mahmud the question is even more pressing, because one good season is still a hypothesis; a whole career is its peer review.

Contrarian Angle

Now let me stand against my own conclusion.

Pacers perform worse in the fourth innings — that is true, but this data does not prove that fatigue is the cause. Sample selection is a trap here. When does a match reach the fourth innings? When the pitch is broken, the air is dry, the ball is soft, and both sides are tired. When the fourth-innings target is small, pacers bowl fewer overs. In other words, the sample we are looking at has already been manufactured under the hardest possible conditions.

The second trap is survivorship. A pacer who breaks down under load is not there for the next match. So the sample retains only those who survived — and looking at their number we conclude, “load is not a problem.” The reverse is equally true: those who broke down are absent from the sample, which is precisely why the statistic looks so clean.

The third trap is the age of the pitch and the ball. A new ball is taken after 80 overs; in a fourth innings that often does not happen, or the ball becomes so old that nothing works except reverse. So is the pacer bowling badly, or is the ball no longer working in a pacer's hand? The difference is enormous, and ordinary statistics cannot separate the two.

The biggest trap of all concerns causation. If a team rotates more, does it win more matches? My ledger shows no such relationship. There is, if anything, evidence in the other direction — more rotation means less rhythm, and less rhythm means a slower return to speed in the first spell. “Reduce the load” and “improve the performance” are not the same sentence. I once put my ear to the ground to hear where home advantage disappears once the stadiums empty; by the same token, the idea that performance will rise once load falls is merely an assumption.

Takeaway

In the coming season my eyes will be on three places. The recovery window between two series — if that number again falls below ten days, a red mark goes into the ledger. The timing of the spell break — if any pacer's average spell starts exceeding 24 balls, that is a gamble against his own limit. And dot-ball percentage with keeper interventions, because the wicket column is weekly while the dot column runs the whole season.

I keep a separate ledger for legends, because memory edits its own columns. The spell someone writes a story about today may sit in the ledger tomorrow as an expenditure. So the question is not “who is best.” The question is who survives the next six months — and who has already reconciled the arithmetic in advance.