TEAM

file TM-01 · filed September 2026 · standing

Building a roster that survives four games in two days

Compressed events reward depth and punish specialisation, which is the opposite of what a long season rewards.

A roster built for a twenty-game school season and a roster built for a compressed weekend event are not the same roster, and the difference is not talent. It is the number of players who can be used without the quality of play collapsing.

Across a long season, a tight rotation is usually an advantage. Games are spaced, the best players can absorb heavy minutes, and continuity between the players on the floor is worth more than freshness. Across a weekend of four games in forty-eight hours the calculation inverts. The fourth game is played by whoever still has legs, and a team carrying seven usable players against a team carrying ten is at a structural disadvantage before the tip, regardless of which team has the better starting five.

That has a straightforward consequence for how a compressed roster is put together. What matters is not the ceiling of the top players but the floor of the eighth, ninth and tenth. A ninth player who defends his position, catches and shoots without hesitating, and does not turn the ball over is worth more over a weekend than a more talented ninth player who needs the offence run through him to be effective.

Positional labels are a weaker guide than they used to be, but the underlying jobs are stable enough to plan around. Somebody has to bring the ball up against pressure and make the first decision. Somebody has to guard the opponent's most dangerous perimeter player without help. Somebody has to rebound the defensive glass, because a team that does not finish possessions gives away extra ones. Somebody has to be a reliable catch-and-shoot threat, because spacing collapses without one. A roster is best checked against those jobs rather than against a list of positions: if only one player on the roster can do a given job, the team has a single point of failure that foul trouble will find.

Foul trouble deserves its own consideration in a compressed event, because the schedule offers no way to recover from it. A player who fouls out of the second game is not merely absent for the rest of that game; he has usually played fewer minutes than planned, which changes the rotation in the third. Teams that plan an explicit answer for the loss of each of their two or three most important players handle Sunday better than teams that improvise it.

Rotation planning is mostly a matter of deciding in advance which units are allowed on the floor together, rather than substituting one player at a time by feel. Three or four pre-decided units, each with a ball-handler, a shooter and a defender in it, survive contact with a chaotic schedule far better than a substitution pattern invented at the scorer's table.

The last consideration is the least tactical. Over a weekend, a roster spends far more time together not playing than playing: in a gym corridor, in a car, in a hotel lobby. Whether that time is tolerable has a direct effect on the fourth game, and it is not a soft consideration. A roster that is too big for anyone to get meaningful minutes creates its own problems in exactly that time.