The Radar Dropped in the Fourth Over: Auditing Bangladesh's Pace Workload in a Tournament Cycle

I was watching the over from the second tier at Mirpur. The speed gun said 141, then 140, then 137, and on the fifth delivery, 132. The run-up had shortened, the delivery stride had been cut off, the arm had dropped through follow-through. No boundary, no wicket, no real comment on air. It was the fourth over of his spell and the fourth match of the tournament inside eleven days. I keep a session card every day at the training ground and draw spell charts from the stands. Put the two sets of numbers side by side and one thing becomes clear: the crack in continuity does not begin in a bowler's body. It begins between the calendar and the contract. A tournament cycle is the season of delayed decisions. The squad is announced, it fills up to fifteen or seventeen names, and then six matches in eleven days across two venues and a travel day. The T20 format is itself written against the quick: four overs out of twenty, a two-over gap in the middle, two in the powerplay and two at the death, with the worst part of it for the body at the back end. What a one-day match spreads across ten overs gets compressed into four. In 2026, when I joined Abahani Limited Dhaka for the Dhaka Premier League campaign, I built a Session Intensity Card with the club's fitness coach. Forty-six training sessions, RPE and sprint load for twenty-four players. I went to standardize a training ground and found the club — the card itself recorded who measures what and who avoids what. Winger Nabib Newaj Jibon ran 1,042 high-intensity metres in a single session, and that one number became the most-read line of my eighteen training diaries. What interested me more is that club-level metrics do not translate cleanly to match spells. Training RPE tells you session intensity. In a match, the real cost of a bowler splits three ways: the last over of an unmatchable spell, the fielding sprints in the middle overs, and the deliveries nobody counts — the wrist-turners, cutters and slower balls. I added one column to my spell chart: bowler-reported fatigue, on a scale of one to five, immediately after the match. That number never enters the fitness consultant's laptop, because it is self-disclosure. This is where the real pressure of a tournament cycle emerges. Across six straight league matches, the length of young quicks' spells swells, and the swelling happens at exactly the age when shoulder stability is unproven and the lower-body strength reserve is thin. For a twenty-two-year-old, a four-over spell in a qualifier is effectively a rehearsal in senior rhythm, and the bill for that rehearsal is paid later. A bowler sending down the death overs of a final at twenty-two is still making his body's primary long-term investment. At the 2026 World Cup in Russia I covered twenty-one matches over thirty-two days across Moscow, Saransk and Nizhny Novgorod. We built a shared sixty-four-match pressing database and modular coverage templates — a pre-match data pack, an in-game tactical log, a post-match quote sheet — so that a team could be run from a distance. The live blog drew 3.4 million pageviews and the tactical logs were syndicated by two Dhaka dailies. The lesson from that month: in a distributed operation, the weakest part is never in the system. It sits in the handover. That handover gap is now the biggest issue in Bangladesh's workload management. The ledger report is produced in Dhaka, the pitchside data sits at the venue, and the final match-day update reaches the physio through the player's own mouth. The three streams cannot be read together. In a tournament cycle you then get an outside verdict of 'the bowler looks incredible' while the inside knowledge is that the eye has been narrowing since the third match. When it comes to boards and franchises, the most valuable documents I hold are contracts and payment schedules, because they determine whether a bowler speaks about his own body. In a two-year central contract, match fees, bonuses and performance-linked components are three separate clocks. If there is any doubt about when each one lands, an injury-reporting lag appears. Players do not hide injuries; they calculate protection — what do I lose if I miss this match? This is not theory. In 2026, after the league was suspended, I spent eighty-seven days embedded with Mohammedan SC at their bio-secure camp, cross-checked contracts and payment dates, and interviewed twenty-three players and staff. The story was that players had gone five months without full wages. Within two weeks, the club paid 40 percent of what was owed. That number is the most important tactical data I own, because it proves financial leverage controls the tempo of medical reporting. The wage problem and the tendency to conceal injuries are two faces of one structure. I have watched from the stands long enough to know that a quick in his third spell can look identical and be a different bowler. Based on my years of watching matches, the radar drop rarely arrives gradually; it arrives between two overs, after a half-volley or a wide. Now to where the outside read goes wrong. To a fan the problem is simple: either the physio is bad, or the bowler is soft, or the coach is inept. All three options run downhill into emotion. One popular assumption is that rest is the fix. My ledger says the opposite. Rest does nothing unless it is paired with a reporting channel. When a quick knows that an honest injury report will not cost him his match fee, he reports early and honestly. When he knows that reporting will cost him his slot, he goes quiet. The second misreading: a young quick's one big spell means he can carry a four-over load. The session card says a twenty-six-year-old curve and a twenty-one-year-old curve are dangerously different instruments. The third misreading: a radar drop equals fatigue. My spell charts often show that in the fourth over the plan changes, the angle changes, the length changes. The radar is telling you something worked — and hiding what worked. The real question for a tournament cycle is therefore this: over the next twenty to forty days, how much skill does this team intend to spend and how much does it intend to keep? Both numbers live on the training card. What is needed is a session workload index — not published outside, but at least signalled with one number before a match. That is not a commercial demand. It is an obligation. What we get on workload so far is not the player's welfare but the boss's estimate. Whether that number survives contact with the field is the real test, and the final is close. What to watch next: whether the board's contract adds an injury-protection clause, whether a squad index appears in pre-match material, and whether the fitness coach starts publishing training data in a different vocabulary. Whatever the scoreboard says, the spell chart will reveal who is being spent — and the entire tempo of the spell changes with it.