How to give player feedback in rugby

Most rugby coaches give feedback frequently. Few give feedback that actually changes behaviour. The difference is not personality or enthusiasm. It is structure. Feedback without a clear structure tends to be too general to act on, too delayed to connect to the behaviour it is addressing, or delivered in a context where the player cannot process it effectively.

This guide covers what makes feedback effective in a rugby coaching context, how to structure individual development conversations that players follow through on, and the common delivery patterns that feel useful to the coach but produce no change in the player.

Why most player feedback does not work

Coaches tend to give feedback that describes what they saw rather than what the player needs to do differently. "Your body position in contact was too upright" tells the player what was observed. It does not tell them what to do instead, in what context, or why the change would make a difference to their game. The player nods, agrees, and returns to the same body position in the next contact because they have no replacement behaviour to draw on.

A second common failure is timing. Feedback delivered at full-team address after training is absorbed by almost no one. The player may be fatigued, distracted by a conversation happening nearby, or simply not aware that the feedback is directed at them rather than someone else. Feedback that needs to change behaviour has to be delivered individually, in a setting where the player knows it is specifically about them, and ideally within 24 hours of the session or match where the behaviour occurred.

A third problem is volume. When a coach identifies eight things a player could improve and delivers all of them in one conversation, the player leaves knowing they have a lot to work on but unable to prioritise any of it. One focused development point per conversation, with a clear action attached, produces more change than a comprehensive inventory of weaknesses.

The structure of useful feedback

Effective player feedback has four components: the observation, the impact, the alternative, and the ask. They do not need to be delivered as a rigid formula, but every useful feedback conversation will include all four.

1. The observation

Describe the specific behaviour you observed, in a specific context, without evaluating it. "In the second half, when we were defending our own 22, I noticed you were moving into the line before the ball carrier had committed to a direction" is an observation. "Your defensive reads were poor" is an evaluation. Observations are easier to receive, easier to remember, and harder to dispute. Evaluations create defensiveness and argument.

2. The impact

Explain what consequence the observed behaviour is having on the player's effectiveness or the team's performance. "When you commit early, it creates a channel for a ball carrier running a hard line inside you." This connects the behaviour to an outcome the player cares about. Players who understand the impact of a behaviour are more motivated to change it than players who are told to change because the coach said so.

3. The alternative

Give the player a specific replacement behaviour to practise. "Hold your position until the ball carrier's outside shoulder commits, then accelerate into the tackle." This is the component most coaches omit. Without a specific alternative, the player knows the current behaviour is wrong but has no replacement to use. They will either continue the same pattern or experiment with something new that may also be wrong.

4. The ask

Close the conversation by checking that the player understands and agrees with the focus. "Does that make sense? Is that something you are happy to work on in Tuesday's session?" This does two things. It confirms the player has understood the feedback correctly, and it creates a low-level commitment to work on it. Players who have verbally agreed to a development focus are more likely to attend to it in training than players who have been told what to fix.

Feedback that reinforces versus feedback that corrects

Coaches tend to give most of their feedback when something goes wrong. This is understandable but creates an environment where players associate individual feedback with criticism. A player who receives one-on-one attention almost exclusively after errors will begin to dread individual conversations rather than welcome them.

Reinforcing feedback, delivered with the same specificity as corrective feedback, serves two purposes. It helps players understand exactly which behaviours to repeat, and it creates a relationship in which development conversations are normal rather than something that happens only when the coach is dissatisfied. "When you held your channel for an extra two seconds before committing on that last defensive set, you forced the ball carrier back inside and we made the tackle. That is exactly the read we want" is reinforcing feedback with a specific observation and a clear link to what made it effective.

A practical target is two reinforcing feedback conversations for every one corrective conversation per player per week during the season. This is not about being positive for its own sake. It is about building the kind of relationship where a player can receive corrective feedback without shutting down.

Individual development conversations versus in-session feedback

Not all feedback happens in a formal conversation. Coaches also give feedback during training sessions, in the moment a drill is happening. These two contexts require different approaches.

In-session feedback should be short, immediate, and specific to the current action. "Step earlier. Step before the contact." Long explanations during a drill break concentration and slow down the session. Save the reasoning for the development conversation. During the drill, give the player enough to adjust and try again.

Individual development conversations, scheduled outside of training, are the right context for feedback on patterns that have developed over multiple sessions, feedback on development goals, and feedback that requires the player to reflect and respond rather than simply adjust and continue.

Giving feedback on selection decisions

The hardest feedback conversation in rugby is telling a player why they have not been selected. Most coaches either avoid the conversation entirely, leaving the player to find out from the team sheet, or deliver it as a brief explanation without enough detail for the player to understand what to change.

Selection feedback should follow the same structure as development feedback. Describe the specific thing that influenced the decision ("Over the last three weeks, the player who came in ahead of you has been more reliable at completing the carry in contact in our 22, and that has been a priority area for us"). Explain the impact ("When we lose the ball at the breakdown in that zone, we are under sustained pressure for the next four phases"). Give the alternative ("The focus for your training over the next two weeks is working on your carry height and leg drive through contact"). And ask for the commitment.

A player who understands exactly what they need to demonstrate to earn selection is engaged and motivated. A player who feels they were dropped without explanation is either resigned or resentful, and neither produces the kind of training performance that would earn them back into the squad. CoachCraft's player development tools let you record development goals for each player and track progress against them, so your selection decisions are grounded in observable evidence rather than general impression.

Keeping records of development conversations

Without records, development conversations become disconnected events. A player receives feedback on their breakdown technique in March, the coach does not record it, and the same feedback is given again in May. The player begins to feel that training is not progressing and the coach does not notice improvement. The coach loses credibility.

A simple record of each development conversation should capture the date, the specific behaviour discussed, the agreed action, and a note of whether the player demonstrated improvement at the next opportunity. Reviewing these records before each player development conversation ensures continuity, shows players that you pay attention to their progress, and gives you the evidence to track whether your feedback is producing any change.