What the Speed Gun Doesn't Count: Bangladesh's Pace Workload and the Invisible Calendar of Domestic Cricket

Inside the indoor nets at the Sher-e-Bangla National Cricket Stadium in Mirpur, it is half past nine in the morning. Outside, Dhaka is pushing thirty-six degrees; inside, there is only air conditioning and the sound of ball on concrete. A young fast bowler starts his run-up, stops, starts again, and does not release the ball. The coach standing beside him says one word: "Foot." The speed gun is off. The stopwatch is on.

During my kinesiology years in Sydney, I saw the same thing on the fields of Macquarie University, in a different body and a different code. Graham Arnold's pressing drills ran there, and I learned a plain truth that later became the foundation of my whole career: speed is never the decision, speed is the consequence of a decision. The real decision is made in the days before, in the gaps of rest, in the arithmetic of recovery.

The training ground tells the truth long before the scoreboard does.

In August and September 2026, Rawalpindi hosted one of the largest chapters in Bangladesh's Test history. In the first Test, from 21 to 25 August, Bangladesh won by ten wickets. Mushfiqur Rahim made 191, the highest Test innings by any Bangladeshi batter away from home. In the second Test, from 30 August to 3 September, Bangladesh won by six wickets. Two matches, two wins in Pakistan, where Bangladesh had never won a Test before.

Nearly every outlet in Bangladesh and the subcontinent has already written that story, and it deserved to be written. My job is different. I am a training-ground observer, so what I wanted to know was the workload ledger behind the series win. Because what dominated the conversation on that Rawalpindi pitch was not a run count or a wicket count, but a reading of pace. A young fast bowler touching the 145 to 150 kilometres per hour band, a bowler with a first-class record you could count on two hands. That kind of pace is rare in Bangladesh's cricket conversation, so the conversation naturally stopped there.

But the speed gun is an input, never an output. Over years I have watched two cricket systems side by side. From Sydney I watch the Sheffield Shield rounds; from Dhaka, or online, I open National Cricket League scorecards. In both places there are fast bowlers of the same age, the same height, the same shoulder structure, the same wrist position. The difference is not created in the number of overs, but in how those overs are spread across time.

In the Australian system, a fast bowler's work is divided into blocks. A young quick bowls in one Sheffield Shield match across five days, has limited overs in training the week before, then a defined break. Away from the ground there is GPS load monitoring, bowling-load ceilings, and most importantly an open conversation between the bowler and the coaching staff about what is being asked today. The beauty of that system is not its luxury, it is its predictability: the bowler knows what the next two weeks look like.

Bangladesh's picture is different. The first-class window of the National Cricket League is relatively compressed. Immediately after it comes the Bangladesh Premier League in December and January. Franchise T20 asks for a different pattern: four overs, near-maximum effort on every delivery, and only a handful of days for recovery. Without a bridge between those two formats, a young body takes an unnatural turn. Before it has built the tolerance for long first-class spells, it is pushed into the explosive rhythm of T20.

Bangladesh's real fast-bowling crisis is not a crisis of talent, it is a crisis of calendar. Talent has been arriving here for years. Taskin Ahmed, Hasan Mahmud, Shoriful Islam, the list keeps growing. But the structure that protects talent is not keeping time with the calendar.

This is where my second metric is simple, and it is the central observation of this piece: a fast bowler's real metric is not his top speed, it is the length of his spell in the second innings.

Because in Test cricket it is not the first innings that kills a fast bowler, it is the second. In the first innings the body has adrenaline, the tape is fresh, the rhythm is new. In the second innings the real questions arrive: how much pace survived the fifteenth over, where did the line go in the sixteenth, and in the twentieth is the ball still hitting the seam or merely being dropped onto the pitch. The speed gun does not hold those answers. Only the workload ledger does.

I have watched many times as a young quick touches 146 kilometres per hour in his first spell and drops to 136 in his second. The commentator says, "his pace has dropped." The truth is crueller: his pace has not dropped, his recovery has not happened. The difference between those two statements is enormous, because one is a question of talent and the other is a question of management. And management questions can be answered in the nets, in the workload ledger, in the rest schedule.

One scene from Sydney grade cricket is lodged in my memory. I watched a young fast bowler of Bangladeshi descent sending down overs on a grass-covered turf wicket, with bounce at shoulder height. After the match he said, "Here they stop me after four overs, then again next week." That phrase, "they stop me," is the whole point. He is not stopped for lack of talent, he is stopped as part of a decision. He is code-switching, speaking one language at home, another in the dressing room, and a third in the line and length of a ball. Movement is a language, and I learned its accent in The Cove.

A caution is necessary here. I am not claiming the Australian system is flawless. Fast bowlers break there too, young quicks are lost there too, and the schedule of formats and Sheffield Shield is punishing. I am only pointing to a structural difference, one Bangladesh can learn from, but not copy blindly.

Now to the place where the discussion usually takes a wrong turn. Two kinds of argument are heard in Bangladesh about fast bowling. The first group says, "Young bowlers should play all three formats, they need experience." The second says, "He must be protected, he should be kept for Tests only." Both are sincere. Both are incomplete.

Both bring the question down to the level of selection, when the problem sits at the level of scheduling. A fast bowler can play three formats if his overs are spread to an arithmetic. And a fast bowler can be broken in a single format if that format keeps no ledger of his load.

The outside reading always fails here: it treats pace as an inborn asset, while the training ground treats it as a stock. A stock accumulates, depletes, and accumulates again. And that cycle of accumulation and depletion is set by the calendar, not by the team sheet.

There is another outside misconception, about the BPL. Many analysts believe franchise cricket is a stage for young quicks because they bowl to big batters there. The stage is real, but the physiological demand is different. In a Test a fast bowler works in long spells, holding rhythm, without maximum effort on every delivery. In T20 he must give near-maximum effort across twelve to sixteen deliveries in four overs. Without a bridge between the two patterns, the calendar that emerges has no recovery gap, and that gap is exactly where stress fractures, side strains and shoulder problems are born.

I once wrote that a transfer is not a transaction, it is a tempo change seeking a body. Here I want the cricket version of that sentence: a format switch is a new rhythm for a body, and every rhythm change needs a preparation window.

So what should be watched from here?

Most specifically, I will watch how much breathing room the National Cricket League calendar creates, and whether that room is used as a red-ball block before an international series. If it is, the second-innings bite of Bangladesh's fast bowlers on away tours will look different.

My second watchpoint: in every Test I will log spell lengths, not top speeds. If the gap between the average pace of the sixth over of the first innings and the sixteenth over of the second innings is under five kilometres per hour, the work is being done.

And the third is a question I am still waiting to have answered. When the BPL auction ends in December and January, does anyone write a young fast bowler's previous twelve months of overs next to his name? Does the franchise that buys him know how many balls he has bowled in the last six months, and how much rest he has had?

The best analysis does not shout; it keeps time with the next question. And right now the question is not about pace. It is about the accounting of pace.