How to Give Constructive Feedback: Templates & Examples for UK Managers

Why Feedback Matters More Than Most Managers Think

Feedback is the single most powerful tool a manager has for improving performance, and yet most managers avoid giving it or do it badly. A CIPD survey found that only 36% of UK employees feel they receive useful feedback from their manager. The rest either get no feedback at all or receive feedback so vague that it changes nothing.

The cost of poor feedback is real. Employees who do not receive regular feedback are twice as likely to be actively disengaged at work. They are also more likely to leave: research consistently shows that "my manager does not give me feedback" is among the top five reasons people resign.

This guide gives you a proven feedback model, ready-to-use templates, and worked examples that you can adapt for your own conversations and performance reviews.

---

The SBI Feedback Model

The SBI model (Situation, Behaviour, Impact) is the most widely used feedback framework in UK management training. It works because it removes opinion and focuses on observable facts.

How SBI Works

Situation: Describe the specific context — when and where the behaviour happened.

Behaviour: Describe the observable behaviour — what the person actually did or said. Avoid interpretations or judgements.

Impact: Describe the impact of that behaviour — on you, the team, the customer, or the outcome.

Why SBI Is Effective

• It separates the person from the behaviour
• It removes subjective language ("you are lazy" becomes "you submitted the report two days late")
• It gives the recipient something concrete to act on
• It works equally well for positive and corrective feedback

---

Positive Feedback: Templates and Examples

Positive feedback is not just "well done" or "good job." Effective positive feedback is specific, timely, and explains why the behaviour mattered.

Template: Positive Feedback Using SBI

Situation: "In yesterday's client meeting..." Behaviour: "...you anticipated the client's objection about the timeline and prepared a revised schedule before they raised it..." Impact: "...which meant we resolved their concern immediately and kept the project on track. The client specifically mentioned how well-prepared we were."

Worked Example 1: Positive Feedback on Initiative

Context: A team member noticed a recurring error in the weekly data export and fixed it without being asked.

The feedback:

"I wanted to flag something you did last week that really stood out. When you noticed the formula error in the weekly export, you investigated it, identified the root cause, and implemented a fix — all before I was even aware of the problem. That saved us from sending incorrect data to the finance team and potentially causing issues with the month-end close. That kind of initiative is exactly what makes you so valuable to this team. Thank you."

Why it works: It is specific (the formula error), describes what they did (investigated, identified, fixed), and explains the impact (saved from incorrect data, prevented month-end issues). It also names the quality being recognised (initiative).

Worked Example 2: Positive Feedback on Collaboration

Context: A team member helped a colleague from another department who was struggling with a system migration.

The feedback:

"I heard from James in IT that you spent an hour walking him through how we use the leave management system before the migration last Thursday. He said your explanation of our custom approval workflow saved his team a full day of configuration work. That kind of cross-team collaboration makes a real difference, and I want to make sure you know it has been noticed."

Why it works: It references a specific event (last Thursday), a specific action (spent an hour explaining), and a measurable impact (saved a full day). It also shows the manager is aware of contributions beyond the immediate team.

Worked Example 3: Positive Feedback on Handling Pressure

Context: A team member managed a difficult customer complaint calmly and professionally during a busy period.

The feedback:

"I sat in on that call with the customer on Monday afternoon — the one who was upset about the delayed order. You stayed calm, acknowledged their frustration without becoming defensive, and offered a clear resolution within ten minutes. The customer went from threatening to escalate to thanking you by the end of the call. That is genuinely difficult to do under pressure, and you handled it brilliantly."

---

Corrective Feedback: Templates and Examples

Corrective feedback is where most managers struggle. The instinct is either to soften it so much that the message is lost, or to deliver it so bluntly that it damages the relationship.

Template: Corrective Feedback Using SBI

Situation: "In this morning's team stand-up..." Behaviour: "...I noticed you were on your phone for most of the meeting and did not contribute when asked about your project updates..." Impact: "...which meant the team did not get the information they needed to plan their work this week, and it gave the impression that you were not engaged."

Follow with: "Can you help me understand what was going on?" — This invites their perspective before moving to a solution.

Template: Corrective Feedback on Missed Deadlines

"I want to talk about the Henderson report that was due last Friday. It came in on Tuesday, which meant the client did not have the information for their board meeting on Monday. I understand things come up, but I need to know in advance if a deadline is at risk so we can manage the client's expectations. Can we talk about what happened and how we can prevent it next time?"

Template: Corrective Feedback on Quality

"I have been reviewing the last three proposals you sent out, and I have noticed a pattern I want to discuss. Each one contained formatting inconsistencies and two of them had incorrect client names in the header. These documents go directly to potential clients, and errors like these affect how professionally we come across. I would like us to put a review step in place before anything goes out. What do you think would work?"

Key Principles for Corrective Feedback

Be timely. Give feedback within 48 hours of the event. Saving it for a quarterly review makes it feel like an ambush and robs the person of the chance to improve sooner.

Be private. Corrective feedback should always be delivered one-to-one, never in front of colleagues. Public criticism destroys psychological safety.

Be specific. "Your work has been slipping" is useless. "The last three reports contained data errors that required corrections" is actionable.

Separate intent from impact. The person probably did not intend to cause a problem. Acknowledge that: "I do not think you intended this, but the impact was..." This keeps the conversation constructive.

Invite their perspective. There may be context you are not aware of. Ask before prescribing a solution.

Agree next steps. Every corrective feedback conversation should end with a clear agreement about what will change and when you will follow up.

---

Written Feedback for Performance Reviews

Performance review comments require a different register from verbal feedback. They become part of the employee's permanent record and may be referenced in future discussions about promotions, pay, or capability.

Positive Performance Review Phrases

Exceeds expectations:

• "Consistently delivers work ahead of schedule and to a high standard. Has taken on additional responsibilities this quarter without prompting, including ownership of the monthly client reporting process."
• "Demonstrates strong problem-solving ability. Identified and resolved three process inefficiencies that collectively saved the team approximately 8 hours per week."

Meets expectations:

• "Reliably completes all assigned tasks to the required standard and within agreed deadlines. Is a dependable team member who colleagues can count on."
• "Has shown steady improvement in presentation skills this quarter, volunteering to lead two client calls after completing the internal training programme."

Corrective Performance Review Phrases

Below expectations:

• "Has missed four of six project deadlines this quarter. While the quality of completed work is acceptable, the consistent lateness has impacted downstream deliverables and client satisfaction."
• "Attendance has been a concern this period, with seven unplanned absences in three months. A formal absence review meeting was held on [date] and an improvement plan was agreed."

Development areas:

• "Would benefit from developing delegation skills. Currently retains too many tasks personally, which limits the team's growth and creates bottleneck risks when workload peaks."
• "Communication with stakeholders needs improvement. Two client escalations this quarter were caused by delayed updates rather than actual delivery problems."

Tips for Written Feedback

• Use evidence, not opinion. "Submitted 12 of 12 reports on time" is stronger than "is generally reliable."
• Be balanced. Even in a corrective review, acknowledge what is going well.
• Avoid vague superlatives. "Outstanding" and "exceptional" are meaningless without examples.
• Reference agreed objectives. Link feedback to the goals set at the start of the review period.
• Be forward-looking. Include specific development actions for the next period.

---

Timing Your Feedback

When you give feedback matters almost as much as what you say.

Real-Time Feedback

Best for: Quick positive recognition, minor corrections, coaching moments.

Example: Immediately after a meeting: "That was a really clear summary you gave at the end — it pulled together everyone's points well."

Same-Day or Next-Day Feedback

Best for: More significant positive or corrective feedback that needs a private conversation.

Example: Scheduling a 15-minute chat the day after a missed deadline to discuss what happened and agree on a prevention plan.

Scheduled Feedback

Best for: Development conversations, performance reviews, progress check-ins.

Example: Monthly 1:1 meetings where you review objectives, discuss development, and give structured feedback on the past month.

Feedback to Avoid Delaying

Never save these for a scheduled review:

• Safety concerns
• Behaviour that affects other team members
• Repeated patterns you have already discussed
• Positive feedback that will lose its impact with delay

---

Cultural Sensitivity in Feedback

The UK workplace is increasingly diverse, and cultural context affects how feedback is received and interpreted.

Points to Consider

Directness: Some cultures value indirect communication. What feels straightforward to you may feel confrontational to someone from a culture where feedback is typically delivered more obliquely. Watch for signs of discomfort and adjust your approach.

Hierarchy: In some cultures, receiving corrective feedback from a manager — particularly in anything other than a completely private setting — carries significant weight. Be mindful of power dynamics.

Face: The concept of "saving face" is important in many cultures. Frame corrective feedback as problem-solving rather than fault-finding.

Written vs verbal: Some employees process feedback better in writing, particularly if English is not their first language. Consider following up verbal feedback with a brief written summary.

Ask, do not assume. The best approach is to ask each team member how they prefer to receive feedback. Some want it direct and immediate; others prefer time to reflect. Personalising your approach shows respect and improves outcomes.

---

Linking Feedback to Development Plans

Feedback that leads nowhere is demotivating. The most effective managers link feedback to concrete development actions.

The Feedback-to-Development Cycle

1. Give specific feedback using the SBI model
2. Identify the development need — what skill or behaviour needs to grow?
3. Agree an action — training, mentoring, stretch assignment, or coaching
4. Set a timeframe — when will you review progress?
5. Follow up — revisit the feedback in your next 1:1

Example

Feedback: "Your project updates to the client have been late three times this quarter, which created unnecessary anxiety on their side."

Development action: "Let us set up a shared calendar reminder for client update days. I will also pair you with Alex for the next two updates so you can see how she manages her client communication workflow."

Follow-up: "We will review this in our 1:1 in four weeks to see how the new process is working."

---

Building a Feedback Culture

Individual feedback skills matter, but they are most effective when embedded in a team culture that normalises giving and receiving feedback.

Practical Steps

• Model it. Ask your team for feedback on your own management. "What is one thing I could do differently to support you better?" If you receive feedback gracefully, your team will be more willing to receive it from you.
• Make it regular. Weekly or fortnightly 1:1 meetings with a standing feedback item prevent the buildup of issues.
• Celebrate learning, not just outcomes. When someone acts on feedback and improves, acknowledge the effort publicly.
• Use Grove HR's performance tools. Record objectives, track progress, and document feedback conversations so nothing falls through the cracks. Structured tools remove the burden of remembering everything and ensure fairness across the team.

Explore Grove HR's performance management features