Offence Reads · Guide

Reading Elite Playbooks as a Junior Coach

Published playbooks are written for teams that train all week against opponents who have studied the plays. Much of what is in them won't survive a junior game. This guide is a way to read one as a volunteer coach: what to keep, what to rewrite as a read, and what to leave in the book.

Why a playbook needs translating

A playbook assumes players who have rehearsed every step, a coach who has hours to teach it, and a defence that will play the way the diagram says. A weekend coach has none of those. The job isn't to copy the play. It's to find the idea underneath it, the thing a defender does that the play is built to punish, and teach that instead.

Five tests before a play goes in

Hold any play up against these. If it fails one, rewrite it or leave it out.

  1. It's a read, not a reaction. Someone has to see something, usually what their defender just did, and choose. If the play only works when everyone remembers their step, it's a script.
  2. It has few moving parts. One screen, or one cut, or one handoff. When a play needs several things to happen in the right order, it's a script too.
  3. It fits five-out spacing. Players spread around the arc, so cuts and drives have room to work.
  4. It transfers as a concept. A cut behind a defender who is overplaying works from any spot and against any team. A play built around one opponent doesn't.
  5. It falls back into normal play. If the read isn't there, nothing is broken. Players keep their spacing, move the ball and look again.

Teach roles, not positions

Screener, cutter, passer, attacker, filler. These are jobs, and anyone can do any of them from any spot. A player who understands the role can do it wherever they end up standing. A player who has only been told "you're the four" knows one spot on one diagram.

Read the defender, not the play

Every cue in a good playbook answers one question: what did he just do? The play only tells you where to stand. The defender tells you what to do next.

Each of the Offence Reads carries a coach question, so you can ask instead of tell: "What did your defender do?" Use cues players can see, and judge the decision, not whether the shot went in.

Spacing first, then fill

Hold the spacing. After any drive, cut or screen, everyone fills the nearest open spot, and nobody cuts until the drive has reached the lane line extended. A pass is a trigger: the passer goes somewhere useful, someone fills the spot they left, and nobody stands and watches. Two reads teach this without a single set play: Drive-and-kick with fill rules and Pass-triggered fill.

A touch rule, with a caveat

One rule of thumb to try: every player touches the ball before we try to score. It doesn't always apply, so drop it when the defence overplays the ball.

Some actions already build it in. In drive-and-kick, the cutter becomes the next driver. Against a zone, the ball moves from gap to gap. Other things conflict with it: isolation plays and endings that feed one post player, and a plain ball screen, which gives the guard a touch but the screener none until the roll.

A simple way to practise it in a scrimmage: the ball must cross half-court and be reversed once before any screen or drive. Drop the constraint when the defence overplays.

What to leave in the book

Most of a playbook is things a junior coach should skip. Each of these has a replacement:

Practise a read against a live defender

A read stops being block practice the moment someone is allowed to overplay it. Some ways to set that up:

The Game-Based Practice guide and the Session Plans go further on building a session around a decision.

The one idea above all

Don't ask "which play should we run?" Ask "what did he just do?" Teach your players to answer that question, and a handful of reads will take them further than a binder of plays.

Unofficial resource. The ideas here are distilled from published coaching playbooks, curated and reviewed by Ravi Sundram. No playbook is reproduced. Not affiliated with any team, coach or league. See Sources & attribution.