How to build a rugby coaching cue library

The language a coaching team uses during training shapes what players pay attention to and what they retain. A coaching cue is not just a phrase you say when you stop a drill. It is an instruction that directs a player's attention to one specific thing at the moment they need to act on it. The difference between a useful cue and a useless one is almost always specificity.

This guide covers what makes a coaching cue effective, how to write cues that players can act on, and how to build a shared library that keeps language consistent across your entire coaching staff throughout a season.

What a coaching cue is and what it is not

A coaching cue is a short, specific phrase that tells a player what to do with one part of their body or one decision in the next repetition. It is not an evaluation ("that was poor"), a general instruction ("work harder"), or an explanation ("the reason we are doing this is..."). Explanations belong before a drill starts. Cues belong during it.

The distinction matters because of what is happening in a player's brain during a physical repetition. Their attention is on executing the skill. A long explanation mid-drill competes with the execution for cognitive resources and usually loses. A short, specific cue can be processed and applied in the same breath as the physical action.

Every effective cue in that list names a body part or a specific action. Every ineffective one names a quality without specifying how to produce it. A player who hears "better body position" has no new information about what to change in the next repetition. A player who hears "hips below his hips before contact" knows exactly what to do differently.

Writing cues that are specific enough to act on

The test for a coaching cue is simple: can a player do something different in the next repetition based on what you just said? If the answer is no, the cue needs to be more specific.

Start with the body part or the decision point. "Hands" tells a player where to focus. "Hands inside the ball on the tackle" tells them what to do with them. "Hands inside the ball on the tackle before your shoulder makes contact" tells them when. The more specific you are, the more directly the cue connects to the physical action.

Cues that use imagery can also be effective when players respond to them. "Sink into the ground before you hit" is less precise than "bend your knees to thigh depth before contact" but for some players the image is more accessible. The test is whether the player can reproduce the action, not whether the phrasing is technically precise. Trial the cue, observe whether it produces the change, and keep it if it does.

Why consistent language across a coaching staff matters

When a head coach, an assistant coach, and a specialist coach all use different language for the same technique, players receive three versions of the same instruction and form an average of the three in their heads, which is usually none of them precisely. The inconsistency is rarely deliberate. Coaches develop their own language over years of coaching, and without a shared framework they default to it.

The effect accumulates over a season. A player working with the forwards coach on scrummaging body position hears one cue. The same player working with the head coach on the same technique in a team session hears a different one. Over time, the player's execution drifts between the two and neither coach understands why the correction is not sticking.

A shared coaching language, agreed and written down at the start of the season, prevents this. It does not need to be exhaustive. Twenty to thirty agreed cues covering the core techniques relevant to your system is enough to produce meaningful consistency. The key is that every coach on the staff knows the list and uses it.

How to build the library

Start by listing the ten to fifteen techniques your team most frequently coaches in training. For each one, write the cue you would use if you could only say one thing during a drill. That becomes the agreed cue for that technique.

Bring the coaching staff together and review the list. Each coach may have a different preferred phrase for the same technique. The discussion itself is valuable: it forces agreement about what the technique actually looks like when it is being done correctly, which is a conversation many coaching teams have never explicitly had. Once the list is agreed, write it down and distribute it to every coach.

The library grows naturally over the season. When a new technique becomes a training focus, add the agreed cue before you start working on it. When a cue consistently produces the wrong result, review the phrasing. When a cue stops being relevant, remove it. The library is a living document, not a fixed list.

Introducing cues to players

Players learn faster when they know the cue before the drill starts. A fifteen-second explanation of the cue and what it means at the top of a drill removes the need for mid-drill interruption: "When I say 'hips below his hips', I want you to focus on getting lower than the ball carrier before you make contact. That is the only thing I am looking at in this drill." Players then enter the repetition already primed for the cue, and when they hear it mid-drill it reinforces rather than interrupts.

Sharing cues with players outside of training reinforces this further. A player who can read the cue attached to a drill in the session plan before they arrive at training is already thinking about it. CoachCraft's coaching cue database lets you attach cues to session phases and drills so that every coach on the staff uses the same language, and players can access them through their player portal before training.