What Remains After the Auction Lights Go Out: A 90-Day Notebook on Squad-Building, Workload and the Bench

One morning last December. I was standing beside the nets at the Khulna club ground, an old notebook in hand. A young pacer was bowling his fourteenth over — in training, not in a match. The physio beside me gave a small nod after each delivery, as if counting something. When I asked, he said, "Not overs, brother. I'm counting recovery." That one sentence wrote the day's real story. Much of what television shows is built outside the ground — and that part never reaches the camera. I keep the beat of the training ground before I name the story. That habit has taught me that squad-building decisions are not made on the auction stage; they are made beside the bench, in the physio's notebook, in the analyst's spreadsheet, and in the conversations where the role of the fifth bowler and the seventh batter is settled. Right now the cricket market is hot. Player moves, retentions, release clauses, agents' phone calls — it all fills the ear. But picking the real signal out of the noise is the actual job of a reporter today. A Bangladesh Premier League auction and squad-building window looks a lot like a football transfer window. At first you notice the big names and big money. But the real arithmetic of squad-building runs through three invisible layers — the structure of the wage bill, the release clause in a contract, and the continuity of support staff. When a franchise buys a pacer, it is not just buying wickets; it is buying the entire supply chain behind that bowler — the physio, the load manager, the pitch report, and a plan for sharing overs within a match. Fans see the squad list. Outside the list sit the questions — who bowls with the new ball, who bowls at the death, who is returning from injury, whose workload needs cutting. The answers to these are prepared off the field, and they decide how the team looks on it. In Bangladesh the picture is sharper. We have a limited number of pacers, and their load is heavy. So one pacer's injury is not just one player lost; the entire bowling plan is redrawn. This is where the support staff steps forward. The physio's notes, the analyst's data, the trainer's load chart — together they decide who plays and who rests. A team is not a machine; it is a system, where each part has a defined job. I call this team-function cartography: who sits where, how far each player is from the other, and who fills which gap. Draw that map and you can predict a team's behaviour in advance. Take the pace attack. Taskin Ahmed, Mustafizur Rahman, Nahid Rana, Shoriful Islam — each has a different role. One hunts swing with the new ball, one fires yorkers at the death, another adds pace through the middle. When a coach builds a squad, he is not only looking at names; he is checking whether these roles balance. Two similar bowlers leave no room for a third, and one phase of the match stays empty. Ninety days in one notebook taught me to trust the drills. In 2026, at the Sheikh Russel KC camp, I watched 68 sessions and collected 120 voice notes. I learned then that a pacer who is simply told to bowl will break; he needs a rhythm — how many overs a week, how many recovery sessions, what kind of spell on which day. The same logic holds in the spin department. An all-rounder like Mehidy Hasan Miraz fills two slots in the team structure — control with the ball and lower-order responsibility with the bat. So an all-rounder makes team management more flexible and reduces the load on a specialist. Another layer of the cartography is the bench. Those who do not play the eleven are still part of the system. Reading Iceland's role mapping, I spoke with three backup players; each knew when the team would need them. With that clarity, a bench player who suddenly enters the side does not look lost. When Khulna comes to mind while I read squad-building, one thing keeps returning — continuity. A franchise that changes its entire squad every season loses the invisible connection of the training ground. Players need time to understand each other's rhythm, and that time is lost in matches. During COVID I was in Khulna with the Sheikh Russel KC players. Fourteen players went five months without full pay. That is when I understood that the wage bill and squad-building decisions are not separate things — one is tied to the other. A team that can give a player financial security also earns his focus. Now, watching the market rush, the outside reading is usually different. Headlines say, "Star joins", "Big deal". But those who work inside the ground know the real difference is made by continuity, the structure of the release clause, and workload arithmetic. I watch for the second beat, because the first one is always public. "Small team beats giant" — behind this romantic story hide questions of financial inequality and sustainability. A small franchise winning one good match and surviving a whole season are two different things. Differences in the wage bill, the size of the support staff, and the capacity for player development — these gaps get buried under result-driven news. For me, the biggest signal comes from training, not headlines. One pacer's over count, one spinner's rhythm of deliveries, the pattern of a retention — together they build an early picture of how the team will look next season. In the next window I will watch exactly that: who brings a plan to cut their pace load, who retains their support staff, and who treats the bench as part of the system. Those who can answer these questions may not be in the auction headlines — but they will stand on the field as the most organised side. In Gelendzhik, Iceland taught me that team-first starts before kickoff. In cricket, that pre-kickoff moment is the night after the auction, when the lights go out and the real accounting begins.