Auction Ledgers, Empty Injury Columns: Auditing Bangladesh Cricket's Workload

Zahur Ahmed Chowdhury Stadium, Chattogram. An evening T20. Dew is settling, fielders are busy drying the ball, spinners are trying to keep their palms dry. The bowler who was hitting 140 km/h in his first spell is now shortening his run-up in his second, his arm dropping lower. I was not looking at the scorecard; I was looking at my calendar. My spreadsheet never asked, 'how many wickets did this bowler take.' It asked, 'how many overs has he bowled in the last 90 days, how many flights has he taken, how many nights has he spent in hotels, and how many days has he gone without touching a ball.' I opened a blank spreadsheet because destiny had too many missing values. That evening it became clear: Bangladesh's fast-bowling crisis is not a crisis of talent, it is a crisis of one empty column — recovery. The entire cricket economy is standing inside a transfer window. The IPL mega auction, the BPL draft, ILT20, SA20, the Lanka Premier League — every franchise is answering the same three questions: whom do we retain, whom do we release, and at what price do we buy. In Bangladesh the arithmetic is harder, because franchises and the national team tug at the same limited resource — one fit fast bowler, one in-form batter. Talent gets a price at the auction table; recovery gets none. I have watched this ecosystem since 2026, and since 2026 I keep a simple dataset for every series. The columns are plain: player name, date, format, overs bowled, balls faced, travel days, rest days, and a workload index. The most embarrassing thing about this dataset is that one column is almost always empty — injury history. Franchise contracts, medical reports, NOCs: the detail of a breakdown rarely appears in those papers. Where data is absent, we fill the cell with assumption, and assumption is usually wrong. My workload index is not complicated. I multiply each match's overs by format intensity — a Test over weighs 1.0, an ODI over 1.3, a T20 over 1.5. Then I add travel days at 0.2 each, plus a back-to-back penalty: after three straight matches, every extra match adds 0.5. Finally I read the rolling 60-day total. The model is not exact; the confidence interval is wide, because injury history is incomplete. So I never decide on a single number — I always keep at least two alternative branches open. That empty column is the real subject of analysis. Much has been written about Indian players' workloads, but Bangladesh's numbers are harsher. Our leading fast bowlers play three formats for the national team, the BPL, and often one or two overseas leagues in the same calendar year. The demands differ. A Test bowler may deliver 15 to 18 overs a day; a T20 spell is four overs, but every ball is at maximum intensity. Walk straight from a Test into a T20 league and the body gets no recovery window at all. This is where my decision tree earns its keep. A decision tree is just a disciplined argument with branches you can audit. Say the question is whether to play this fast bowler in the next series. Branch one: age and injury history. Above 28, with a past hamstring or back injury, the risk weight rises. Branch two: overs bowled in the last 60 days. Past 250, rest becomes mandatory. Branch three: pitch and venue. On an evening surface in Chattogram or Mirpur, dew makes a fast bowler's job harder, because gripping the ball is difficult, and when a bowler loses grip he tries to bowl harder than usual — many breakdowns start there. Branch four: alternatives. If a fit bowler is on the bench, the case for risk weakens. Four branches produce a clean decision, with no need for captaincy folklore. Bangladesh's recent history supports the argument. In August and September 2026, Bangladesh beat Pakistan 2-0 in a Test series in Rawalpindi — the first Test by 10 wickets, the second by six. Before that series the squad had preparation time, and the core bowlers were rested and focused. By contrast, in series where the team has arrived directly from a franchise league, bowling intensity visibly drops on the third and fourth days. There is a real constraint here that I read as structural context, not as weakness. Bangladesh's elite fast-bowling depth is thin — many of the domestic names have not yet reached international standard. So resting a frontline bowler lowers the replacement's quality, and the coach comes under pressure. That pressure cannot be solved by data alone; it needs investment in the domestic structure, and that is not the work of one transfer window. Mustafizur Rahman's 2026 calendar is the clearest example. In the IPL he took 14 wickets for Chennai Super Kings — a strong half-season. Then came the national team's congested schedule, the travel, the different pitches, and by my count his workload index had entered the red zone. He was fit, but fit and ready are not the same thing. Put both in one cell and you make the wrong call. One familiar claim deserves a test. We often say, 'playing brings form.' If that were true, the data would show it. But when I measure the gap between a bowler's first-spell and third-spell speed in the series after a run of franchise matches, I see the gap widening. More cricket does not mean more edge; it means less edge at the far end. There is no destiny cell here — this is a recovery calculation. Batters and wicketkeepers carry a different load, and we usually skip it. A top-order batter like Najmul Hossain Shanto plays three formats in one year and carries a BPL side's weight; an all-rounder like Mehidy Hasan Miraz is used with both bat and ball, which shrinks his rest. A keeper like Litton Das squats for more than 120 balls an innings, extra strain on hamstrings and back. Workload is not only overs bowled — it is total innings time. Where does this sit in auction economics? A player's base price is set by format fit, age and recent performance. On retention, franchises weigh loyalty and brand value. Neither path admits recovery data. So the same player is either overbought or left unpicked entirely — the fine middle calculation is missing. Now the counter-intuitive part, the one nobody writes on the auction table. What the market pays most for is availability — the player willing to play every league. To a franchise, availability means low risk, because he will not miss games. But the link between availability and durability is a correlation, not a cause. The player who plays every league is playing more, yes, but his recovery time is shrinking. His peak output may fall next season, yet the auction pays him on the strength of last season's name. The market prices past availability as future durability — that is the error. Another dark corner is home advantage. We assume Mirpur means a Bangladesh fortress. Analysing empty-stadium matches in 2026 taught me that home advantage was a column I had never questioned. Separate dew, crowd and umpiring decisions and most of home advantage becomes venue-specific character, not supernatural force. This matters for Bangladesh, because our spinners who are so effective on Mirpur's slow surface may be less so elsewhere. Buy a player on an undefined column called 'home advantage' and you have bought the wrong thing. The return-from-injury question sits here too. After an ACL or hamstring injury, the body is often ready but the head is not. In his first match a fast bowler thinks twice before bowling at full pace; he pulls out of a dive. That mental block is harder than the physical one. The transfer window inflates it, because the player knows he must be seen to earn a contract. So he ignores his body's signals and pays for it next season. A club that asks only 'is he fit' does half the sum; the complete question is 'does he trust his body again.' One thing is worth holding onto: the eye test is a feature, not the whole model. An experienced coach's eye sees much, but an eye cannot count 90 days on a calendar. Data and the eye are not substitutes; each complements the other. When they agree, the decision hardens; when they diverge, ask which piece of information is empty. What is the signal for the next transfer window? On my count, the franchise or board that tracks injury and recovery data seriously will spend less and last longer. Those who auction on names and last season's runs and wickets will find that the real ledger is the bench that suddenly empties mid-season. I do not chase edges; I build a process that makes edges repeatable. So the question is simple: are you buying a player, or are you buying his calendar?