The staff file can be twenty pages. The player message should fit on one. FIBA's coaching manual recommends giving players as little information as possible while still defining what the team will do. Hudl's film-session guidance reaches the same conclusion from another direction: keep the purpose clear, use focused playlists, invite the right group, and ask questions that prove understanding.
The presentation is not a summary of everything the staff learned. It is a teaching sequence for the decisions players will make.
The One-Page Player Scout
Build the handout in this order:
1. Three team rules. One sentence each, written as actions. 2. Starting matchups. Name, role, and one tendency, not a biography. 3. Primary action and first counter. Show the decision chain. 4. Our offensive opportunity. The matchup or rotation you will attack. 5. One contingency. What changes if the opening plan loses. 6. One success metric. Something players can see during the game.
Do not shrink a full report to eight-point type. Cutting is the work. If a detail does not change a player's decision, it belongs in the staff file.
The Eight-Clip Playlist
Every clip should have a job.
Clips 1 and 2: establish the opponent's identity
Show the primary action once at normal speed. Ask players what they notice before explaining it. Then show a second example where the same action begins from a different entry or side.
The goal is recognition: players should see the alignment and trigger before the action develops.
Clips 3 and 4: teach rule one and its counter
Show what happens when the defense follows your preferred rule. Then show the opponent's first response. Pause at the decision point, not after the result.
Ask: What do you see? What is the call? What happens next?
Clips 5 and 6: teach the matchup opportunity
Use one clip of the defender or lineup behavior you plan to attack and one of a similar action from your own offense. The bridge matters. Players should leave knowing not only that a weakness exists, but how your normal offense reaches it.
Clips 7 and 8: silent recall
Remove the voiceover. Stop each clip before the decision and call on a player who has not spoken. If the player can identify the cue and next action, the room is learning. If not, return to the rule, not to a longer explanation.
A 15-Minute Meeting Script
Minutes 0-2: say the plan first
Open with the three rules and the success metric. Players need a frame before details.
"Tonight we win the paint by keeping ball screens on the sideline, tagging the roller early, and never helping off number 12 in the right corner. We will know it is working if they have fewer than six paint touches in the first quarter."
Minutes 2-8: show proof and counter
Use the first four clips. Ask a question before giving an answer. Keep the language consistent with the calls used in practice.
Minutes 8-11: show the offensive opportunity
Use clips five and six. Name who will initiate, who sets the action, and what the second read is if the defense takes away the first.
Minutes 11-13: explain one contingency
"If they beat our opening coverage twice, we change to this." One contingency calms the room because players know the staff has anticipated resistance. Five contingencies create hesitation.
Minutes 13-15: test recall
Show the silent clips, ask two players to explain the next action, and finish by having a third restate the three rules.
Split Detail by Audience
The full team gets the common plan. Then use short position meetings for detail that does not belong in the main room.
- Guards: screen angles, rejection cues, pressure releases.
- Wings: tag responsibility, shooter relocation, closeout direction.
- Bigs: coverage depth, screener behavior, rebound matchup.
This protects the shared message while respecting that each position needs different information.
What Not to Do
- Do not read the document aloud. FIBA's manual explicitly warns against simply reading a report players can read themselves.
- Do not lead with percentages. Start with the decision, then use a number or clip as proof.
- Do not show ten versions of the same tendency. Two clear examples are enough for the main room.
- Do not use three names for one coverage. Match the words players hear in practice.
- Do not end with "Any questions?" End with a recall test.
- Do not scare the team with the opponent's strengths. Frame each tendency as a solvable assignment.
Make the Report Memorable
Use contrast and rhythm. "No middle. Early tag. Stay home on 12." Short phrases survive game speed. Pair each with a visible cue: screen angle, roller release, corner location.
The report becomes memorable when the same three rules appear in the meeting, walkthrough, scout-team possessions, bench sheet, and timeout language. Consistency across those surfaces matters more than a polished template.
Generate the first draft with the free Scout, validate the high-leverage claims, and then cut the answer until every line changes something a player will see, say, or do.