How to use this library
Feedback is the biggest lever you have as a leader. Regular, specific feedback lifts engagement, shrinks turnover and keeps performance on track. The reason most leaders do not give enough of it is not that they do not believe in it. It is that they are not sure what to say.
This library gives you the words. Ten scripts and emails across five phases, covering the positive side as well as the hard conversations. Replace the placeholders in [square brackets] with your own specifics. Every template has a one click copy. Scripts for in person moments mark stage directions in ALL CAPS. The tip box on each template names what the wording is doing and why.
The highest leverage feedback is the kind a team member hears the same day you saw the thing. Short. Specific. One on one, within minutes or hours of the moment. If you wait until Friday, you have already lost most of the weight.
Why this wording works
The script names the moment, the action and the impact. Those three things together turn a vague "well done" into specific positive feedback the person can actually learn from. Naming it as "the kind of work I want to see" is the bit that sticks. Keep the script under 90 seconds. Longer than that and it drifts into a chat, and the recognition gets lost.
Two written templates. The first is a short end of week message for one team member who has had a great week. The second is a quarterly style email for when someone has delivered on something bigger, often after you have been asking them to lift in that area.
Why this wording works
Bullet pointed specifics are the bit that matters. One vague "great job this week" email is noise. Three named moments with customers, team members or deliverables inside the bullet are recognition. Sending it Friday afternoon also signals you were paying attention all week, not just in the last meeting.
Why this wording matters
When someone lifts after constructive feedback and you say nothing, the message they hear is that the feedback was punitive. When you name the change, the message they hear is that feedback in your business is a development tool, not a ledger. Closing the loop like this is how you build a feedback culture that people trust.
For smaller things. A one off slip. A handover that did not go well. Something you want to address cleanly without it needing to become a meeting. Keep it quick, specific, and out of earshot of the team. One follow up email captures the conversation in writing.
Why the script works
Short. Specific. COIN structured so you do not soften the concern into vagueness. The "I will send a follow up email" line is the bit that separates a coaching conversation from a disappearing one. The "listen, then hold the line" move is the part most leaders skip. Pushback is normal, and agreeing with it cancels the feedback.
Why this wording matters
Short is deliberate. A three page recap of a five minute conversation signals that you are building a case, which is not the intent here. The "anything I got wrong" line is the procedural fairness safeguard. It invites correction, which matters if the issue ever escalates. Keep it plain. File it. Move on.
When the issue is bigger, a pattern, a skills gap that is affecting the team, a communication breakdown with a client, or a team dynamic, you schedule the conversation properly. This pair covers the meeting invite (so the team member is not blindsided) and the written follow up after. For the plan you take into the meeting itself, use the COIN Feedback Planner.
Why this wording matters
Naming the topic without writing a full case in the email is the right balance. If the team member walks in cold, the feedback lands as a surprise and defensiveness spikes. If you write three paragraphs of concerns in the invite, they shut down before the meeting starts. The "bring a support person if you would like" line is best practice even for non disciplinary feedback conversations. It signals you are taking it seriously without escalating it unnecessarily.
Why this wording matters
The structure matters. "What I raised / What you said / What we agreed / What I will do" is the four part recap that documents both sides of the conversation. The "what I will do" section is the part most leaders skip. If the team member is being asked to change, naming your own commitments signals the conversation is two way. The last line inviting correction is the same procedural fairness safeguard as in the short version.
Three of these. One for when the same feedback is landing for the second or third time and you need to raise the seriousness. One for when the team member is deflecting or disputing in the moment. One for when the feedback has been received as a personal attack and the conversation is getting emotional. These are the harder ones. Keep the scripts short.
Why this wording matters
Naming the two or three earlier conversations in writing is what turns a vague feeling ("this keeps happening") into a documented pattern. Flagging the possibility of formal performance management is the move that either shifts the team member into gear or surfaces a bigger issue that needs addressing. The "I would rather sort this out here" line matters. It tells them you are still trying to resolve it informally, which keeps the relationship alive even as the seriousness lifts.
Why the script works
Every line is a way of holding the observation without arguing about it. "I hear you" is not capitulation, it is a bridge to "and this is still the thing I am raising." The "intent is not the question" move is the one most leaders miss. When a team member explains why they did something, a lot of managers retreat. You can accept the intent without withdrawing the feedback. The "sit with it overnight" close is there for the times where the conversation cannot land in one sitting. It keeps the process moving without forcing a breakdown.
Why the script works
This is the script most leaders wish they had. Two moves are doing the work. First, naming that tears do not mean the team member is a bad person, which is what they are hearing in that moment. Second, asking whether something else is going on. That question is not optional. About a third of the time, the team member will disclose something (a diagnosis, a relationship ending, a grief, financial pressure). That information does not cancel the feedback, but it absolutely changes how you support them through it. The EAP reminder and the drive home check are safety steps, not formalities.
Use these with the other feedback and performance tools
- COIN Feedback Planner : before you walk into a planned conversation (Phase 4 or 5), use the planner to draft the full COIN conversation plan and Radical Candor self check. Then pull the invite and follow up templates from this library.
- One on One Meeting Builder : most constructive feedback belongs inside a regular one on one rhythm, not a special meeting. Use the builder to set up the cadence first, so feedback has somewhere to go.
- Probation Performance Templates : if the team member is still in their probationary period, use the probation specific template set for the Week 1, Month 3 and Month 6 check ins, which replace the Phase 4 and 5 templates here.
- Performance Review Builder : feedback given in the moment during the period should come together on paper at the review. Nothing in the review should be new.
- Written Warning Generator : if the pattern has continued past Phase 5 and the next step is a formal warning, use this generator to draft a warning that meets procedural fairness requirements.