Tryouts · Updated May 2026

Most youth soccer tryouts do not evaluate anyone. They sort.

A few dozen kids show up, run through some drills and scrimmages, and at the end the coaches gather around and form teams based on a mix of what they saw that day, what they remember from last season, who the parents are, and who looked athletic in the warmup. The decisions get made. The teams get posted. And almost none of it is written down in a way that anyone could defend a week later, let alone explain to a parent who asks why their child was put where they were put.

This is what running tryouts looks like at most clubs. A director with a clipboard, a roster printout, and the same memory everyone else relies on. By the end of a week of weeknight sessions, the Monday U10 group has blurred into the Wednesday U11 group, and roster decisions about eight-year-olds get made on impressions no one could reconstruct the next morning. It works, in the sense that teams get formed. It does not work in the sense that the tryout actually told anyone anything about the players, or gave the players anything in return.

This guide is about how to run a tryout that does both jobs. Not just selection, which every tryout manages somehow, but evaluation, which most tryouts skip entirely. It is written for directors and coaches running tryouts at the community and competitive club level, the people doing this with volunteers and limited time, not professional academies with full-time scouting departments.

A tryout has two jobs, and most clubs only do one

The first job of a tryout is selection. You have more players than roster spots, or you have multiple teams to form across a skill range, and you need to decide who goes where. This is the job every tryout does, because it has to. The teams get formed whether or not the process was any good.

The second job is evaluation. For each individual player, what did you actually observe, against what standard, and what does it tell you about where they are and what they need next. This is the job almost no tryout does, because selection is urgent and evaluation is not. Once the teams are posted, the pressure is off, and the evaluation that would have justified the selection never gets written down.

The two jobs are related but not the same, and conflating them is the source of most of what goes wrong at tryouts. Selection is comparative and zero-sum: this player over that one. Evaluation is absolute and developmental: this player, against what is appropriate for their age, in each part of the game. A good tryout does the evaluation first and lets the selection fall out of it. A bad tryout does the selection by feel and never produces the evaluation at all.

The reason this matters beyond tidiness is that the evaluation is the thing of lasting value. The selection decision is consumed the day it is made. The evaluation, if it exists, is something the player and their family can use for the next six months, and something you can compare against at the next tryout to see whether the player actually developed. A tryout that produces only selection produces nothing that outlives the afternoon.

Before the day: the setup determines whether evaluation is even possible

Whether a tryout evaluates players or just sorts them is mostly decided before anyone touches a ball. Four things have to be in place.

Decide what you are evaluating, and write it down. The single most common failure is that the coaches running the tryout never agreed on what they were looking for. One coach is watching first touch, another is watching effort, a third is watching who scores. They are running the same session and evaluating different games. Before the day, decide the specific characteristics you will assess and make every coach use the same list. It does not need to be elaborate. It needs to be shared.

Sort your age bands honestly, including the combined ones. Real clubs do not run clean single-age tryouts. You run U10 and U11 boys together on a Tuesday evening at the rec complex because that is the field slot you could get. That is fine, but it changes the evaluation, because a strong U10 and an average U11 are not the same player even if they look similar on the day. Decide in advance how you are handling combined-age sessions, and make sure whatever standard you evaluate against is calibrated to each player's actual age, not to the group average.

Brief and calibrate your coaches before the whistle. Hand them the criteria, walk through what each level looks like, and if you can, look at one or two players together at the start so everyone is anchored to the same scale. Ten minutes of calibration before the session is worth more than any amount of careful watching by coaches who are each using a private scale in their own head.

Handle the logistics that wreck evaluation if you ignore them. Bibs or pinnies with numbers, so coaches can record observations against a specific player rather than "the fast kid in the blue shirt." A plan for goalkeepers, who are chronically under-evaluated at tryouts because they do not fit the field-player stations and there are never enough of them. A check on registration so you are not building rosters around players whose paperwork is not done. None of this is glamorous, and all of it determines whether your notes at the end of the day are usable.

The problem at the center of every tryout: calibration

Here is the thing nobody tells you when you start running tryouts. The same coach will evaluate the same player twice and produce two different ratings. Two coaches evaluating the same player will produce ratings that do not even agree on what they were rating. This is not a knock on the coaches. It is what happens when evaluation runs on memory and private judgment with no shared scale.

The phenomenon is easy to watch happen. A coach finishes a tryout convinced they have a clear read on a player, and a colleague who watched the same session describes a completely different player. The two are not disagreeing about the player. They are using different words to mean different things, with no common reference for any of them.

The fix is a shared framework: a defined set of characteristics, a defined scale, and a definition of what each level looks like at each age. When two coaches both rate a U12 player's first touch as "On Track," that only means something if both of them are pointing at the same definition of what an On Track first touch looks like for a twelve-year-old. Without that shared definition, the rating is just two people's moods wearing the same number.

This is the problem the SportFormIQ Player Development Model was built to solve. The framework defines 23 characteristics across six categories, evaluated on a five-level scale (Beginner, Developing, On Track, Advanced, Top Class), with each level calibrated to age-appropriate expectations rather than to how the player compares to the others in the session. It is grounded in published player-development guidance from nine national soccer federations, so the standard is not one club's opinion. You can read the full framework at sportformiq.com/methodology.

You do not need SportFormIQ to apply the principle. You need a defined list of what you are evaluating, a defined scale, and a shared understanding of what each level means. The national federations publish exactly this kind of age-appropriate guidance, and it is worth reading regardless of what tool you use. England's FA Foundation Phase lays out what to develop in players aged 5 to 11, and US Youth Soccer's Player Development Model breaks the preteen age groups into separate developmental stages. The point is to evaluate each player against what is appropriate for their age, not against the kid standing next to them.

Running the day: get enough looks, and capture them as they happen

The structure of the day should be built around one goal: getting enough quality looks at each player to evaluate them, and capturing what you see while you still remember it.

Small-sided games beat drills for this. A drill tells you whether a player can execute a technique in isolation. A four-versus-four game tells you whether they can execute it under pressure, whether they scan before they receive, whether they make decisions, and whether they compete. Most of what you actually want to evaluate only shows up in game-like situations, so weight the session toward small-sided play and use drills sparingly to confirm specific technical questions.

Rotate deliberately so every player gets evaluated in comparable situations. The kid who happened to be on the strong team in every scrimmage will look better than the kid who was on the weak team, and that is an artifact of your rotation, not the players. Mix the teams across the session so your read on each player is not an accident of who they played with.

Capture observations in real time, not from memory afterward. This is the discipline that separates a tryout that evaluates from one that sorts. If you wait until the end of the day to write anything down, you are writing fiction, because the U9 session has blurred into the U11 session and you are reconstructing impressions rather than recording observations. Whether you use an app, a paper form, or a clipboard with a structured grid, the point is that the evaluation gets recorded against each player while you are watching them, not three sessions later.

And plan for the players who are not on your list. Walk-ups are a reality at every community tryout: the kid whose parent did not register, the family that heard about it that day, the player who shows up in the wrong age band. You cannot turn them away, and you should not let them blow up your process. Decide in advance how you add an unregistered player to the session and how you evaluate them against the same standard as everyone else, so a walk-up becomes a row in your evaluation rather than a scribble in the margin.

Field conditions matter more than people expect, and weeknight tryouts have their own. A session in fading evening light or under patchy floodlights, in the rain, in the cold, with coaches trying to record notes one-handed while managing the group, is a different exercise from a tryout in perfect conditions. If your evaluation method falls apart the moment conditions get difficult, it was never robust. Whatever you use to capture observations has to work on a wet Tuesday night in October, because some of your tryouts will be wet Tuesday nights in October.

Making the decision: let the evaluation drive the selection

Once you have evaluated the players, the selection should be most of the way made already. This is the payoff of doing evaluation first. Instead of a coaches' huddle full of competing memories, you have a set of players assessed against a common standard, and the team formation becomes a structured decision rather than an argument.

A clean decision structure separates players into a small number of outcomes. Invite, for players who have a place. Hold, for players whose decision depends on how other pieces fall, or who you want to keep in consideration without committing yet. Cut, for players who do not have a place this cycle. Some clubs add a development-team or second-team outcome between Invite and Cut. The exact labels matter less than having a defined set of decisions and applying them consistently.

Two specifics that save you grief. First, decide what happens to players you did not get a clear look at. The right default is Hold, not Cut. A player who slipped through the rotation, or who you genuinely could not assess, should not be cut by accident, and defaulting unevaluated players to Hold rather than Cut prevents the worst kind of mistake. Second, handle goalkeeper scarcity explicitly. If you have four teams and three goalkeepers showed up, your selection math is different for keepers than for field players, and pretending otherwise leaves a team without a goalkeeper in August.

The evaluation also gives you something to stand behind when a parent asks why. And a parent will ask why. A selection made by feel cannot be explained without sounding arbitrary or personal. A selection grounded in a recorded evaluation against an age-appropriate standard can be explained as exactly what it is: here is what we observed, here is the standard, here is where your child is, here is what comes next.

The part most clubs get wrong: telling families

The tryout is not over when the teams are formed. It is over when the families have been told, and this is the part that most often turns a well-run tryout into an angry one.

There are three messages to send, and they are not equally hard. The Invite message is easy; everyone is happy. The Hold message needs to be clear about what "hold" means and when the family will have a real answer, because a vague hold that drags on is its own kind of cruelty. Set a hold decision deadline, communicate it, and honor it. Two weeks is a reasonable default. A family in limbo deserves a date.

The Cut message is the one you will be judged on, and the one worth the most care. You are telling a family their child did not make it, and how you say it shapes how they remember your club for years. The message should acknowledge the disappointment without dwelling on it, avoid generic praise that reads as a brush-off, and always give a real next step: other teams that are still forming, the next tryout window, a development path, a recommendation. A cut handled with specificity and respect keeps a family in your community. A cut handled badly loses them, and they tell other families why.

This is also where the operational reality of running a club bites. After a tryout, there is a sequence that has to happen and is easy to botch in the post-tryout chaos: resolve the walk-ups and any duplicate or merged player records, finalize the decisions, send the family messages, and export the roster to wherever your registration lives. Each step missed is a family who did not hear, a player who fell off the roster, or a registrar doing manual cleanup. The registration handoff in particular is a known time sink. One director measured their registration system at roughly a dozen clicks per invited player, which across several age bands of invites is hours of repetitive work and a real error rate. Plan the handoff as part of the tryout, not as an afterthought, because the afterthought is where rosters get lost.

What the player should walk away with

The last question, and the one that separates a developmental club from a sorting machine, is what the player gets out of the tryout.

For most clubs the answer is a result. Made it, or did not. The evaluation that was done, if any, stays with the coaches. The player learns their outcome and nothing about themselves.

A club that takes development seriously gives every player, including the ones it cut, something about where they are and what to work on. This does not have to be elaborate. It has to be honest, specific, and grounded in the same standard you used to evaluate. A player who is told "you are developing well technically for your age, and the thing to work on before the next tryout is making decisions faster under pressure" has been given something useful. A player who is told only "you did not make it" has been given nothing, and will arrive at the next tryout no better informed than they were at this one.

This is the strategic case for treating evaluation as the real product of a tryout rather than a byproduct. The evaluation, turned into a development report a family can actually read, is what turns a tryout from a gate into a step in the player's development. It is also, not incidentally, what families remember and talk about. A club that hands every player a clear, credible read on their development is doing something almost no club does, and it compounds into the kind of reputation that fills tryouts in the first place. This is what the SportFormIQ parent report is built to produce, evaluation grounded in the Player Development Model and turned into a development story for each player. You can see how the pieces fit together, and what it costs, at sportformiq.com/pricing.

Putting it together

Compressed into a single page, the advice runs like this. Decide what you are evaluating before the day and make every coach use the same standard. Build the session around small-sided games and rotate so every player gets a fair look. Capture observations against each player in real time, not from memory at the end. Let the evaluation drive the selection rather than the other way around, default unevaluated players to Hold, and handle your goalkeepers and walk-ups as part of the plan rather than as surprises. Tell families promptly, give held families a real deadline, and put your care into the cut message because that is the one you will be judged on. And give every player something about where they are and what to work on next.

None of this requires special software. It requires deciding that the tryout's job is to evaluate players, not just to sort them, and then building the day around that decision. The clubs that do this produce better teams, defensible decisions, and families who stay. The clubs that do not produce teams that are roughly right, decisions they cannot explain, and a fresh round of the same guesswork every season.

If you want the tool built specifically for running a tryout this way, structured evaluation against an age-calibrated framework, clean Invite/Hold/Cut decisions, and a development report for every player, that is what SportFormIQ is for. You can read more at sportformiq.com/pricing.

Running a tryout this season? Our free tryout day operations checklist covers the setup, the coach briefing, the decision workflow, and the family communication sequence, so nothing gets missed in the post-tryout rush.

This guide is part of an ongoing series on youth soccer development. The framework underlying it is the SportFormIQ Player Development Model, a methodology built on published guidance from nine national soccer federations. More at sportformiq.com/methodology.