Coaches watch the same session and write down different things. One writes a page, one writes a name and a smiley, and the selection meeting runs on memory. I would rather every evaluator use the same questions.
The player and the session. Name, date and what you watched: tryout, practice, match or camp. Scores only make sense when you know the setting.
The scores. Technique, game sense, fitness, teamwork and effort, each from 1 to 5. Five short scores are quick to give on the side of a field and easy to average later.
Your call. The biggest strength, one thing to work on, a suggested level and a box to invite the player back. These lines tell the next coach what to do.
Who fills it and who reads it
Your evaluators fill it, often on a phone. You read the CSV. An evaluator's AI might ask "Who did you watch today?" Then "How would you score their effort?" Then "Which level would you suggest?" It shows every answer and sends only after a yes. See agent-fillable forms.
A tip for selection day
Average the scores per player, then read the notes of the players near the cut line. Tools for the whole season sit under forms for sports clubs and teams. Link each evaluation to a player registration form, and keep a short player profile template for the final squad.
Questions
How do I compare players from different evaluators?
Download the CSV, then average each score column per player. The evaluator_name column shows who scored, so you can spot a harsh or a generous marker.
Does the player see the scores?
No. The form goes to your evaluators and the answers come only to you. If you want to share feedback with a player or parent, do it yourself after you read the rows.
Can I change the skills that are scored?
Yes. Edit the labels of the five rating questions to match your sport, for example swap fitness for stamina or add a goalkeeping score.