Two Matches a Week: Bangladesh's Pace Load Ledger and the Poll That Rewrote the Model

November 24, 2026, Jeddah. On the first day of the IPL mega auction, two numbers came and sat side by side in my notebook. One was a dollar figure. The other was a number of rest days. I had already guessed the dollar figure. The rest-day figure stopped me short.

That night I opened my load ledger. From 2026 through 2026, for every seamer who regularly bowled for Bangladesh, the ledger has two filled columns: how many deliveries in each spell, and how many days between two spells. I was not counting how many balls they had bowled. I was counting how many days they had rested. Across fourteen months of data, a pattern emerged that looks meaningless at first glance: the longest breaks arrived exactly when the next series was the most condensed.

To test the pattern, I ran a poll. More than eight thousand votes came in. The question was simple: what is most responsible for the injuries to Bangladesh's pace bowlers? Sixty-one percent voted for "the calendar," twenty-two percent for "training methods," eleven percent for "bowling action," six percent for "pitches."

That sixty-one percent is the real subject of this piece. Because the poll is not an output of my model — it is an input. And if I treat it as an input, I have to rewrite the model in public. If I don't, the whole exercise is incomplete.

Context: How I Built the Ledger

One thing must be said at the start. This is not medical research. This is a journalist's ledger. I have not seen a single player's scan report. The BCB medical department's files have never reached my desk. What I had is what everyone has: public ball-by-ball scorecards, the Future Tours Programme schedule, squad announcements, franchise league dates, and supporters' inboxes. From those four places I built three indices for each seamer.

First, delivery load — competitive deliveries across all formats in a calendar year. Second, recovery window — the days between two spells, excluding travel days. Third, the one I added last, gap variance — how inconsistent the lengths of the breaks were within a year.

It took me nearly six months to add the third index, because I assumed total deliveries would explain everything. It did not.

Why these three and not simply match counts? Because Bangladesh's schedule has a specific shape. The BPL sits in December and January, bilateral series fall before and after it, ICC events land in February and March, the Dhaka Premier League and National Cricket League fill the gaps, and franchise leagues run all year — the IPL, ILT20, LPL, Caribbean Premier League. A Bangladesh cricketer is no longer only a national player. He is part of an international labour market.

That is where the NOC question sits. The board grants a permission, the player signs a contract, and under that contract the decision about a fast bowler's rest is split three ways: a third to the board, a third to the franchise, a third to the player. No one owns it. No one wants to own the blame either.

The central contract numbers are brutally honest here. At the top tier, a year of central contract income is comparable to one or two months of franchise money. So when a seamer is told "sit out this series," that is not just a physical decision. It is a direct financial one. A board that does not compensate the income gap cannot enforce the rest order either.

This is why I say it plainly: fixture congestion itself is the single biggest cause of injuries to Bangladesh's fast bowlers. No medical team can save a player from a two-matches-a-week schedule. The medical department is the easy target because it has names and faces. The schedule has neither.

The Core: Reading the Ledger at Five Levels

One: The Three-Seamer Bottleneck

Start with the depth ceiling of Bangladesh's pace attack. The number of bowlers who regularly carry the ball in major series can be counted on one hand. That creates a mathematical inevitability. When two are injured, the third must bowl more spells in one innings than he normally would. More spells means accumulated muscle fatigue. Fatigued muscle means risk in the next series. Risk means another man out. Then the loop turns again, and with every turn the team leans harder on the survivor.

In my ledger this is the clearest linear relationship: of the bowlers who broke down, roughly seventy percent carried a delivery load in the ten days before the injury that was above their own annual average. That is not proof. It is a signal, and read against squad announcement dates, it repeats.

One number belongs here, because a number without a source is just a rumour. To understand the culture of Bangladesh's pace attack, Mashrafe Bin Mortaza's record is essential — 220 ODIs for Bangladesh, a large share of them played with a chronic knee condition. That number reached me while I was rereading interviews with former players for a long-form oral history. It tells me two things: a seamer can run a long career with an injury, but only if a system exists that lets him rest.

Two: Big Breaks, Big Risk

This is where my first model was wrong. I assumed risk rose with total deliveries. The data said something else.

Most of the bowlers I had flagged as the "high-risk group" had only moderate delivery loads. But their gap variance was the highest. This does not mean they played more. It means they played irregularly. Three matches in five days, then six weeks of nothing, then four matches back to back. A body can handle accumulated fatigue. It cannot handle working without any accumulation at all.

This is the lesson I first learned in 2026, working on fifty Bundesliga matches played behind closed doors. In those empty stadiums, the home win rate fell from 43.3 percent to 32.0 percent, and home teams were awarded about 1.2 fewer fouls per match. The numbers look clean, but numbers alone cannot tell the story.

I traced the ball back until the highlight forgot where it began. In cricket, that trail usually returns as slow over rates and extra spells.

Three: The Taskin Ahmed Protocol

I have kept one file open longer than any other: Taskin Ahmed's. In 2026 his bowling action was ruled illegal. He remodelled it, returned, and then in the years that followed ran into repeated side and shoulder problems, each time coming back through short, managed spells.

Read that file with the locks off and one thing stands out: every comeback does not redefine its own protocol — it adds weight to the previous one. In a return pathway the deliveries increase, but the rate of that increase is set by the team's need, not by the medical department. In a two-innings Test a bowler might send down eighteen overs; in a Sri Lanka series the same man bowls twenty-four, because he is the healthiest option. No individual is at fault. The fault is built into the system.

I am not claiming in this piece that a specific injury was caused by a specific innings. I am claiming that tissue history is one thing and schedule pressure is another, and when the two arrive together they make a third thing, whose name is recurrence.

Four: Money Hides, Honesty Dies

The most uncomfortable question in cricket journalism never reaches a microphone: who pays for rest?

One case shows how international the problem is. Mustafizur Rahman played the 2026 IPL for Sunrisers Hyderabad and won that season's Emerging Player award. In the years after, he became one of Bangladesh's heaviest-worked fast bowlers. For a seamer, load management is not only a health question. It is a contract renewal question, a visa question, a relationship question with a franchise.

When a board says "skip this franchise league," a compensation calculation becomes necessary. Australia can do this for one reason: central contract values are high enough that resting is a professional decision rather than financial self-harm. Cricket Australia can drop Pat Cummins, Mitchell Starc and Josh Hazlewood from an entire format's series and bring them back for the next one. England has made rotation routine. India now builds internal structures around Jasprit Bumrah's workload.

Bangladesh does not have that financial room. So the decision is not taken by the board. It is taken by the team's immediate need. And immediate need never utters the word rest.

Five: What If the Ledger Were Public

Here is a proposal that is not hard to implement. The board could keep a public load record for every centrally contracted player, updated monthly: how many deliveries, how many rest days, in which format, at which venue. Target data would carry a version number and an update date, and previous versions would not be deleted.

This is not surveillance; it is a ledger. The difference: surveillance asks the player questions, a ledger asks the system questions. Supporters would know why their favourite seamer is missing from a Bengaluru tour. Journalists would not be forced to guess. What is currently a whispered allegation against selectors would become verifiable information.

Six: Where Women Carry More Risk

In women's cricket the risk is more uneven. Bangladesh's women's side plays far fewer matches than the men's team, but the medical and fitness support around it is far thinner. Bowlers like Nahida Akter or Jahanara Alam end up bowling the heaviest overs of a series because alternatives are scarce.

The counter-intuitive fact is this: playing fewer matches is not safer. Fewer matches means less match fitness, and a body unaccustomed to sustained cricket absorbs the biggest shock the first time it faces three matches in three days of heat. I have watched this team's data for seven or eight years, and the sharpest performance drops have come in the matches immediately after a long gap.

Seven: The Poll and Version Two of the Model

Back to the poll.

Sixty-one percent voted for the calendar. But three days after the votes closed I realised the question itself was at fault. I had asked "what is the biggest cause" — that framing forces a supporter to pick a single cause. In reality the causes are layered.

So I changed the question. The new one: "If you could set the number, which piece of information would you want first?" This time the leading answer was rest days, and the whole character of the response changed.

But changing the poll result was never my job. My job was to change the model's weights. I moved gap variance to the top of the model and dropped delivery load to the second tier. The model did not change because of the speed; it changed because you voted.

Every number has a first touch, and every first touch has a witness. The witnesses to this ledger were eight thousand voters — some of them, perhaps, a player's younger brother, forwarding injury news at midnight.

The Contrarian Angle: Maybe Congestion Is Not the Real Culprit

Now let me attack my own story.

Sixty-one percent of poll respondents blamed the calendar. But supporters see scorecards, not training loads. They see back-to-back matches; they do not see the weights room, the recovery sessions, the sleep data.

In my ledger, a small group carried high loads and did not break down. They played regularly, but their recovery windows were wide and consistent. That is an uncomfortable hint: the relationship between congestion and injury is not simply linear. Correlation and causation are not brothers here.

There is a second, more uncomfortable objection. Why don't Bangladesh's selectors rest a high-load seamer? Because the replacement either lacks international quality or is untested in big matches. That is not a schedule problem. That is a pipeline problem — and a pipeline is a structural problem for which no physio is accountable. The board often avoids accountability too, because a home series needs bums on seats, and a rested seamer's place in the XI does not sell tickets.

And a third objection, aimed at me. I built the ledger from ball-by-ball data, which is public. What is not public is weekly training load, grip strength, sleep data. My model sees only one part of the structure, and I am using it to claim the whole truth. That is a confession, not a defence.

I do not worship the dashboard; I ask who is missing from it. Missing from this ledger is the domestic cricketer who bowled three matches in four days in the BPL without a physio, and whose name appears in nobody's model.

Takeaway

The biggest cause of injury is not any single thing. It is a system that knows the number of balls but forgets to count the days of recovery. In the next cycle I will watch one signal: whether the new Future Tours Programme shows any appetite for widening the recovery window between consecutive series, and whether the board puts a rest clause into the payment structure of its central contracts.

A cricket traveller who sits at Mirpur and watches only where the ball pitches loses one number — the number of the day after the ball. If a team plays two matches every week, even the best medical staff in the world cannot take that place.

The question, then, is not about any doctor's skill. It is about the courage of the people who write the schedule.