A borderline kid is sitting between two of your teams. One coach wants her up, one wants her held. The parent is going to email you either way, and whichever way you decide, you will be defending it by Thursday. So you make the call the way most placement calls get made: on instinct, in a hallway, in ninety seconds, by whichever coach happened to be in the room.
Placement calls are genuinely hard, one athlete at a time. The problem that actually hurts a multi-team program is the inconsistency underneath them: the same athlete would land on a different team depending on which coach evaluated her and what kind of week they were having.
A shared framework leaves the judgment fully intact. What it removes is the randomness. It makes the same call consistent across your staff, explainable to a family, and steady on a bad day as on a good one.
Rate the Athlete on Five Inputs, in Two Groups
The framework starts with five judgments about the athlete, and the most important move is keeping two groups of them apart. The first group describes where the athlete is right now. The second looks ahead, to where they will grow fastest. Most placement mistakes come from letting the first group decide everything on its own.
1: Skill
Where the athlete performs today against the level's demands. The most visible input, and the one most likely to be over-weighted, because it is the easiest thing to see in a tryout.
2: Confidence
How the athlete responds to pressure, mistakes, and real competition. A technically ready athlete who folds under a level's intensity may develop faster with a season of success one rung down.
3: Maturity
Physical and emotional readiness relative to peers, including the honest question of whether a late developer needs more time rather than a harder environment.
4: Role Fit
Where the athlete's strengths actually help a team, and whether the level in question has a genuine role for them or a seat at the end of the bench.
5: Development Needs
What this specific athlete needs next in order to improve, and which environment delivers it. Most programs skip this input, and it is the one that should carry the most weight.
The Sixth Input Is Not About the Athlete
6: Team Composition
Roster balance, position needs, and group chemistry are real constraints, but each one describes the team rather than the athlete. Apply them only after you have rated the athlete on the first five, as a limit on where the decision can land, never as a reason to talk yourself out of what the athlete needs. Team composition is where politics and favoritism tend to slip into placement wearing the costume of strategy.
When the Inputs Disagree, Development Wins
The framework earns its keep on the split decisions, where current skill says one thing and development needs say another. The default should lean toward the environment where the athlete develops fastest, even when that means a level below where their raw skill could survive. An athlete who plays every minute a rung down often improves faster than the same athlete absorbing spot minutes a rung up. Reps beat proximity to a better team. Placing for this weekend's roster strength is how you stall a developing athlete in the name of a lineup.
Write Down the Reason, Then Say It Out Loud
A placement decision is only half-finished when you have made it. The other half is a one-line reason, written down, that connects the call back to the framework. A reason like "she needs starter minutes at this level to build the confidence the higher team would not give her yet" does the work that "she is not ready" never can.
That written reason does two things. It keeps the standard consistent when the next borderline athlete comes through, and it becomes the exact language you use with the family, so the conversation is about the child's development instead of your judgment. Families rarely fight a decision they understand. What they fight is the decision that feels arbitrary, and "that is just how we saw it" is the most arbitrary answer there is.
With one team, this framework can live in your head. It stays consistent across a dozen teams and as many coaches only when the criteria and the recorded reasons live in one shared place every coach places from, rather than in twelve separate memories.
The Call Your Program Is Known for Getting Right
You are going to make placement calls this month no matter what. The only question is whether they come from a framework your whole staff shares or from whoever is standing in the hallway when the decision gets forced. Build the six inputs into a single sheet, make development the tiebreaker, and write the one-line reason every time. Do that, and the borderline call stops being the thing you dread and starts being the thing your program is known for getting right.
