The Pace Workload Ledger: From Khulna's Training Ground to the National Fixture List

On a December afternoon I stood behind the northern nets at the Sheikh Abu Naser Stadium in Khulna. Dust in the air, the shadow barely reaching the pitch. The thermometer read 29 degrees, but the concrete felt hotter than that. A teenage left-arm pacer was running in for his sixth straight over. In my notebook I was writing one thing only, the number of overs. Not pace, not wickets, not praise. Just overs.

That evening I did the sum. Four pacers had bowled in that session, and two of them had bowled the previous day as well. Nobody adds those two numbers together. The scoreboard does not, the broadcast camera does not. Truth shows up at the training ground before it shows up on the scoreboard, and that has been my habit for years. The notebook travelled from Khulna to the World Cup; I just kept writing.

The domestic season and the international window now run almost fused together. A domestic T20 league in early winter, then a limited-overs series, then Tests, and between those three stages the rest gap for fast bowlers is close to zero. If anyone turns back the pages from late November to early March, they will see the same few names returning again and again, and the same few names vanishing without notice.

Look at the calendar arithmetic. If a pacer plays ten league matches at four overs each, that is forty overs. A three-match international series adds thirty more. Training sessions in between average twelve to fifteen overs a day. At the end of the week you are near ninety overs. That is one week, not one month, and nobody is ever handed the bill for those ninety overs.

I keep this count because nobody else does. Match reports say superb spell, they say pace with control. They never say that on the night before that spell the bowler was sitting in an ice bath, with three missed calls from home still sitting on his phone. Workload management is a phrase that is often used mainly for photographs.

I keep a separate page in the notebook for travel, because travel is itself a load. Dhaka to Sylhet, Sylhet to Chattogram, then Khulna. Playing that route back to back eats into sleep. For a fast bowler, a seven-hour bus ride is not two overs less the next day, and the scorecard never records it.

There is a real constraint in scheduling and I do not deny it. Broadcast contracts, stadium availability, security, weather, all of it shapes the fixture list. But even inside that constraint there is room to keep rest gaps, if someone chooses to make it a priority.

This is where my three-match threshold applies. I do not write about a bowler's consistency on fewer than three matches. And unless I have stood at the training ground for three weeks, I cannot tell who is genuinely tired and who merely looks tired.

Take the three-week session log. In week one the pacer bowls off his natural run-up, hunts reverse swing, asks the coach questions. In week two the run-up shortens slightly and he does not notice it himself. By week three the front-leg landing is heavier, the follow-through is shorter, and what the camera reads as maturity is actually the language of fatigue.

Every match has a pulse; my job is to keep the count. For pace bowling that pulse is measured in recovery runs and in the interval between deliveries. One example. If the same bowler starts his tenth over from the same run-up distance across three straight matches, his load is being managed. But if by the third match the run-up shortens and the yorker attempt drops away, then whatever the scoreboard says, the body is giving a different account.

I have a simple rule for recovery runs. I note how far behind the pitch a bowler walks after each delivery. A tired bowler walks back less, because he is saving that energy for the next ball. It is not a complicated measure, only an eye and a watch. And yet this simple thing never appears on a broadcast graphic.

I log workload three ways: weekly overs, consecutive bowling days, and the gap between rest periods. If any one of the three turns red, the other two follow quickly. Across recent seasons I have seen it repeatedly: injury lands exactly where those three press together.

A bowler's best spell and the day of his injury are often in the same week. For one reason. The week a man bowls the best spell of his career is the week his over count is highest. Performance and load are two sides of the same coin, but the report prints only one side.

There is a separate pressure in domestic cricket that gets less attention. National-team matches are recorded, but domestic league bowling loads are not stored centrally anywhere. So the number of overs a young pacer bowled in the league, and the number he bowled immediately after a national call-up, are never reconciled.

The Khulna pipeline is one example. Every season a few pacers come up from here, some from divisional sides, some from age-group sides. Their biggest problem is not a shortage of talent but a shortage of planning. Who bowls how much, who rests when, there is no written design. On match day the decision is made: who bowls today.

When a young pacer like Nahid Rana or Shoriful Islam enters the national side, nobody carries his domestic load sheet with him. The same is true for experienced bowlers like Taskin Ahmed or Mustafizur Rahman. Everyone knows their names, nobody knows their fatigue map.

Preparation for a World Cup or a major tournament starts two years out, but our domestic league load sheet starts the moment before the toss. That gap is the real gap, not a gap in personal fitness.

I also log ice baths. Last season at one team's training session I saw six pacers sit in ice baths on the same day. That is a sign of good management, because previously nobody sat in them at all. That small change is the big change, because it means the club at least admits fatigue exists.

The age-group account is more dangerous still. At under-19 or under-16 level a pacer is often bowled in every single match, because the pressure to win is direct. So before he turns twenty, his knee has already seen four years of workload. Nobody keeps that account, because nobody preserves the scorecards of that age.

There is one more thing I notice that gets little discussion. Live stats feeds are now often piped straight to betting companies. Every delivery's speed, every line and length from a young bowler, drops into that feed within seconds. We celebrate this side of datafication, while avoiding its darkest edge.

The bowler himself does not know that a map of his fatigue is being deposited somewhere every day. The training-ground coach may use it to fix rest, or may not. Either way, the decision is not in the bowler's hands.

The outside reading is usually different. When a pacer breaks down, people say a lack of fitness, they say the board failed at workload management. Or the reverse: the player does not look after his body, there is a flaw in his action. Between those two narratives one thing disappears, and that is the design of the fixture list.

An injury is not one bowler's failure; it is the output of a schedule in which the rest gaps were left empty. Nobody creates that gap deliberately. The gap appears when the calendar is built around broadcast and ticket revenue, and a player's knee becomes a line item on that ledger.

I deliberately do not blame one coach or one selector. The problem is not a person, it is a system. Run the same schedule for five years and whoever holds the selector's chair will arrive at the same decision. Change the names without changing the design and nothing is gained.

I trust the notebook more than the noise. The noise says this kid has gone soft. The notebook says this kid has bowled on twenty-eight days in the last month and rested on four. Which sentence is truer, the body will tell us next season.

The three-match threshold has another use, and it is forward-looking. I am already watching which pacer returns to the same rhythm after two straight matches. Those who do are worth trusting in the coming series. Those who do not, however big the name, should have their account set aside right now.

The scoreboard, in the end, records only runs and wickets. The training-ground diary records the rest. When someone suddenly loses rhythm in the next series, the question should be how many overs, not why so many.