The Two Diaries of Rawalpindi: Bangladesh's Pace Workload and the Silent Ledger of the Domestic Season

The Two Diaries of Rawalpindi: Bangladesh's Pace Workload and the Silent Ledger of the Domestic Season

Last week I sat in a nearly empty stand in Sylhet for a National Cricket League match. The scoreboard said the home side's fast bowler was about to begin his seventeenth consecutive over. My notebook said something else: across his previous three innings his average spell length was 7.3 overs, and in the last two overs of each spell his average pace had fallen from 139kph to 132kph. Everyone on the ground was watching the wicket; I was watching a tired shoulder. In the quiet ground every delivery echoed, and the echo exposed small footwork faults — the landing foot drifting an inch or two, a shorter follow-through, the shoulder rotating later than before. Mymensingh came back to me; that is where I learned that every match writes two diaries, one on the public scorecard and one on the bowler's body.

We have all read the public diary. In August and September 2026, in Rawalpindi, Bangladesh beat Pakistan 2-0 in a two-Test series, their first Test series win on Pakistani soil. In the first Test Bangladesh fell to 26 for 6 and still reached 565; Mushfiqur Rahim made 191, Litton Das 138. They won the second Test by six wickets. Mehidy Hasan Miraz was Player of the Series. The headlines carried the batsmen's names, and that was natural.

The public diary: Rawalpindi series, August-September 2026

| Item | Detail | | Series | Pakistan v Bangladesh, two Tests | | Venue | Rawalpindi | | Result | Bangladesh won 2-0 | | First Test | 26/6 to 565; Mushfiqur Rahim 191, Litton Das 138 | | Second Test | Bangladesh won by six wickets | | Player of the Series | Mehidy Hasan Miraz |

Nobody opened the body's diary. As I filled my notebook on that series, one pattern kept returning: the win was founded on the seamers' new-ball spells, and those spells were possible because there were nine days between the two Tests and Bangladesh rotated three frontline quicks. The issue is not personal; it is structural.

The domestic season is running now. The four-day National Cricket League, the Bangladesh Cricket League and the one-day tournament together make the fast bowlers' calendar almost continuous. Divisional sides play five days per round, rest two or three, then start again. A four-day match has no over limit, so on paper a bowler can be given a long spell. In practice, when a side is in trouble, the coach has one weapon: call back the most experienced quick. That call is the most expensive decision in the match, and it never appears on a scorecard.

The data I collected over the last three rounds is not perfect — BCB fitness data is not public — but the direction is clear. One quick playing for a Dhaka side bowled 18 overs in the first innings, broken into spells of six, six and six. In the second innings he bowled 14, but this time the spells were split three, four, four, three. Fewer overs, yet shorter gaps between spells, and a follow-through that kept shrinking. In the final session of day four his average pace was roughly six kilometres per hour down on the first session.

Those six kilometres are the real story. They say the bowler is no longer bowling with his natural action; he is bowling to survive. And survival bowling is what invites injury, because a tired action loads the lower back harder and reduces landing stability. After nine years of watching cricket, let me state one thing plainly: in South Asian domestic cricket, fast bowlers' fatigue is best hidden on a spin-friendly pitch. On such a surface a quick bowls less, so his workload looks light, yet the few deliveries he does bowl are almost entirely attacking, meaning maximum intensity. Fewer in number, heavier on the body. It is the exact trap where everyone is satisfied by "only eight overs", when every one of those eight was the last over of a full-pace spell.

This is where my second objection sits, and it is about how numbers get used. In domestic cricket we assess a quick on two things: over count and average pace. Both are convenient and both are incomplete. Over count does not say how many pieces a spell was broken into; average pace does not say whether that pace came in the first over or the last. Curiously, at national level we do roughly the opposite — there we look at rest between spells, not overs, and at last-spell pace, not average. In the domestic season that standard is almost invisible.

Take an example. Imagine two quicks bowl the same number of overs in a match, say thirty. The first bowls six, six, six, six, six, each spell after full recovery. The second bowls ten, eight, six, four, two, each spell carrying the residual fatigue of the one before. The scorecard treats them as equal. In recovery terms the second man finished several days behind. No bowling coach is at fault here — the fault lies in measurement. What is not measured is not protected.

There is another layer that rarely gets discussed. In the domestic season a quick's opponent is not only the batsman but the pitch and the calendar. On surfaces like Sylhet or Khulna a seamer must bowl more to succeed, because the window for seam movement is small — the first hour, after which changing air moisture closes it. So the quick naturally bowls more, yet this never shows in the ledger, because "few wickets" is read as "little effort". That reading is wrong.

Crisis protocol: when a frontline quick goes down with a hamstring or back injury, domestic sides usually have no replacement, and that is when the most dangerous thing happens — a half-fit bowler is brought back "for one match". European club football writes protocols for exactly this moment; cricket, especially at domestic level, barely does. In my view a clear rule is needed: the maximum overs a quick may bowl in one innings of a four-day match, and the maximum across two innings. Whatever the number, having one matters, because without a number the limit does not exist.

Now the outside reading, where I am most uneasy. We have read the Rawalpindi win as a batting story — Mushfiqur's 191, Litton's 138, 26 for 6 to 565. True, but incomplete. The match-defining moments were the seamers' two new-ball spells, which put Pakistan's top order under pressure, and those were possible because the quicks were not tired. The management that kept them fresh at national level is precisely what is missing in the domestic season. We are enjoying the fruit of a successful model while refusing to protect the model itself.

The second misreading is subtler. We assume a fast bowler means pace, and pace means intensity. But the true domestic measure is not pace; it is recovery — how quickly the body returns between spells. A quick's real condition shows in the first over of his third spell, not the last over of his first. Domestic cricket keeps no statistic here, and without a statistic there is no attention.

One more point deserves adding, because it is easily forgotten. Bangladesh's success on Pakistani soil came at a moment when their pace attack was historically deep. Nahid Rana's raw speed, Hasan Mahmud's control, Taskin Ahmed's experience — having all three meant selectors had options. Options make rotation possible, and rotation keeps quicks fresh. In the domestic season those options shrink, because each side has only a limited number of genuine quicks.

So the real question is not about the series win but about the years after it. If Bangladesh treats fast bowling as a foundation, the domestic calendar itself must change — either by widening the gap between rounds or by guaranteeing at least four fully fit quicks per side. Otherwise a Rawalpindi-style success stays a rare event rather than becoming a habit.

Let me end with a confession. I believe domestic cricket's fast-bowling fatigue is a silent crisis, and the nature of a silent crisis is that nobody keeps the ledger until someone breaks down. And what is the use of keeping the ledger after the breakdown? That is exactly why the silent stadium taught me to hear the game — what the scoreboard does not say, the echo does.

What to watch next round

Next round I will track one thing, and it is not a score. I will watch how many overs each side gives its frontline quick in the second innings, and how many pieces those spells are broken into. The side that breaks them into more pieces will probably finish the season with more fit quicks. The side that looks only at the number and thinks "only twelve overs" will probably get a handsome scoreline and a pair of tired shoulders. Mymensingh taught me to read two diaries; this season it is time to reconcile both.