450 Overs Against 360: The Workload Ledger Nobody Opens in Bangladesh Cricket

Second session, fourth day in Chattogram. The sixty-seventh over of the match is about to be bowled by the quick who has sent down more overs than anyone else in this Test. The scoreboard shows three wickets beside his name. My notebook shows another number beside it: an average release speed of 136 kph in his first spell, 129 in his third.

The broadcast graphic does not show that decay, because the graphic counts wickets, not fatigue.

Since 2026 I have hand-charted fifty-eight matches across domestic first-class cricket and international series. Every spell on its own page, every rest day in its own column, every over's start and finish time written out. The sample is small, collected by one pair of hands, and the speed readings come from a broadcaster's screen — the weakest joint in my method, and I will not hide it. Still, one pattern repeats too consistently to ignore: what best predicts a Bangladesh seamer's next performance is not his wicket count, it is the number of days between his matches.

Context: the match where a bowler learns is the shorter one

The National Cricket League is Bangladesh's only full first-class competition, and it runs for four days. At ninety overs a day, the scheduled range of a match is 360 overs. A Test is played over five days: 450 overs. The gap is exactly ninety overs — a full day.

The number sounds dry. In a fast bowler's life it is flesh and blood. The hardest work in pace bowling happens in the third session of a day, when the pitch stops changing, the light drops, and hope of a new ball fades. A seven-over spell in that session decides how a bowler wakes up the next morning. In a domestic four-day game that third session often never arrives — the match drifts to a draw, or the innings ends first.

This is where the calendar enters. Bangladesh's domestic season is compressed: league rounds on one side, the BPL window on the other, A-team series and home series squeezed between. Within a few weeks the same quick crosses a four-day match, a four-over match and a five-day match — three entirely different physiological demands. No single body keeps all three ledgers at once.

Core: what the notebook surfaces

Where matches break, domestic cricket does not reach. In roughly two-thirds of the domestic first-class games I watched in full, the final session of day four never required a new ball — either a follow-on had happened, or the game was heading for a draw. So the exact situation that demands the most endurance and patience from an international seamer is one he never rehearses at home. Nobody designed this gap; it is a by-product of the fixture list.

The fourth seamer's six overs. Across the eight rounds where I kept a separate over-allocation sheet, one repetition stands out. The frontline quick averages 24 to 28 overs a match; the fourth seamer gets 6 to 9. The first is already capped or already on a BPL contract. The second is the bowler who needed those overs precisely at this stage. This is not a selector's personal failure; it is an incentive problem. To stay in the points table, a coach must give the ball to the most experienced bowler. The bowler who is not being built is the one who was supposed to be.

Rest is a variable, not a luxury. Here my log is clearest. Where seven or more days separated two matches, the drop from first spell to third averaged one and a half to two and a half kph. Where the gap was three days, the drop ran five to six kph. The sample is small and the environment uncontrolled, but the difference is too wide to wave away as noise.

We are measuring with the wrong unit. A four-over T20 spell and a seven-over four-day spell are both counted in overs, though the physiological cost is nothing alike. In T20 nearly every ball is maximal effort; in a four-day spell the first three or four overs run largely on rhythm. In my log, the share of deliveries landing within a bowler's own top five speeds sits far higher in T20 and far lower in first-class cricket. Thirty overs in one week means two different thirties.

Who writes the calendar? The answer is easy and uncomfortable: nobody. The board writes the fixture list, the franchise writes the window, the captain writes the bowling change. Rest has no single owner. My second job, transfer market administration, turns out to be oddly relevant here. A transfer is not a rumour; it is a row of cells awaiting confirmation. A seamer's workload is the same — a row of cells, every one of them empty.

Contrarian: a pace drop is not an injury

My sheet shows a correlation, not a cause, and without that distinction nothing else means anything. Humidity in Chattogram in April sits near eighty percent; a good part of that third-spell drop can be explained by weather alone. My sheet holds no data on a bowler's action, his injury history, or the load of the previous six months. Concluding that workload is breaking bowlers sits outside what my evidence can support.

The second discomfort is larger. Blaming the calendar protects selection policy. If the schedule is the offender, nobody has to answer why the same three quicks start in all three formats, or why the fourth seamer cannot get a single series. The injury story is comfortable; the notebook does not accept it easily.

And third: four-day domestic cricket is not a Bangladeshi deficiency. The County Championship is four days. The Sheffield Shield is four days. The 360-versus-450 gap is universal. The difference is built in the bridge — how many A-team tours, how long the away series, how many warm-up matches. That bridge is priced in money and in calendar space, and in Bangladesh's case it has been the least-funded part of the route.

Takeaway

At the next National Cricket League round I will not watch the bowler with five wickets. I will watch who bowls the sixtieth over of the match, and how long ago his previous round finished. If the answer is 'three days', the number sitting next to the pace drop will not belong to any bowler — it will belong to our own accounting gap. The question now is narrow: if the board published an over-by-over workload ledger, would the selectors still open with the same three?