This article explains what that review rating usually means, how to diagnose the real cause of underperformance, how to write feedback that is specific rather than blunt, and how to turn the conversation into a workable improvement plan. I’m keeping the focus practical, because that is where performance management either helps or fails.
The most useful outcome is a clear path back to expected performance
- The rating should point to specific gaps in output, quality, behaviour, or reliability, not vague disappointment.
- ACAS recommends regular performance reviews for employees, with written records shared afterwards and at least one formal review a year.
- Strong feedback names the standard, the evidence, the impact, and the next step.
- Most underperformance has a cause worth checking before escalation: unclear goals, skill gaps, workload, tools, or wellbeing.
- A credible improvement plan needs targets, support, milestones, and a review date.
What a low rating is really telling you
A poor review rating is usually a signal that current performance is below the agreed standard in one or more measurable areas. I try not to read it as a verdict on the person. In practice, the issue is almost always narrower than that: missed deadlines, weak quality, poor handovers, inconsistent communication, or a pattern of behaviour that is affecting the team.
When I look at underperformance, I separate it into four buckets. That keeps the conversation honest and stops it drifting into personality comments.
- Output - the volume of work, the pace, and whether agreed targets are being met.
- Quality - accuracy, completeness, attention to detail, and the amount of rework needed.
- Behaviour - collaboration, responsiveness, professionalism, and whether the person is following team norms.
- Reliability - attendance, punctuality, follow-through, and consistency over time.
That distinction matters because a one-off dip should not be treated like a long-term capability problem. If performance has only slipped for a short period, the right response may be support, clarification, or a temporary adjustment. If the same issues keep repeating over multiple review cycles, you are dealing with a pattern, not a bad week. Once that is clear, the next question is what is driving it.
Why performance drops and what to check before you write the review
Before I write a harsh note into a review, I want to know what has changed. ACAS is right to push managers to understand why performance is slipping before they jump to labels, because the cause changes the solution. The same missed target can come from very different problems.The most common causes I see are straightforward, even if they are frustrating:
- The standard was never explained clearly enough.
- Priorities changed, but the employee was still working to the old brief.
- The role has outgrown the person’s current skills, and no training was provided.
- The person does not have the right tools, access, or support to do the job well.
- Workload has become unrealistic, so everything is being done in a rush.
- Health, stress, family pressure, disability, or neurodivergence is affecting performance.
- The relationship with the manager has become too vague or too tense for useful feedback.
This is where managers often make a mistake. They assume the issue is effort when it is actually structure, capability, or environment. If a health condition or neurodivergence may be involved, the conversation needs more care and, where relevant, reasonable adjustments. In other words, do not start with blame when a better diagnosis is still available. That takes us to the wording itself, because the way you describe the gap shapes whether the person can act on it.
How to write feedback that is firm, fair, and usable
The clearest review comments usually follow a simple pattern: standard, evidence, impact, next step. That gives the employee enough detail to understand what needs to change without turning the review into a speech.
CIPD’s view that performance management is a continuous cycle, not a one-off event, matches what works in practice. Feedback is strongest when it is regular, timely, and focused on improvement, not surprise. I would rather see a blunt but specific comment than a polite sentence that tells the employee nothing.
| Weak wording | Better wording | Why the second version works |
|---|---|---|
| You need to communicate better. | Two client updates were sent after the agreed deadline this month, which delayed follow-up work. From now on, updates need to go out by 3 p.m. on Fridays. | It names the behaviour, the effect, and the expected standard. |
| Your quality is not good enough. | Three of the last five reports needed rework because key figures were missing. The standard is a complete first draft with checked numbers and source links. | It replaces a vague judgement with evidence the employee can act on. |
| You are not proactive. | I need you to raise blockers within 24 hours instead of waiting until the deadline has already slipped. | It turns a personality complaint into a specific expectation. |
| You are letting the team down. | When the handover was missed on 12 June, the team had to reassign calls at short notice. The next step is a 10-minute end-of-shift handover note. | It explains impact without making the employee guess what “letting people down” means. |
| You need to improve attendance. | You were late on four of the last eight shifts. If travel or another issue is affecting this, tell me now so we can look at options. | It is firm, but it also leaves room for a real cause to surface. |
If I had to reduce the whole process to one rule, it would be this: describe the gap in a way that the employee could repeat back accurately. If they cannot tell you what the problem is after reading the review, the review is not yet useful. Once the wording is clear, the conversation itself matters just as much.
How to deliver the conversation without turning it defensive
A difficult review does not need to become a confrontation. The best managers keep the tone steady, the evidence visible, and the next step concrete. I usually structure the meeting in five moves.
- State the purpose plainly: this is about closing the gap to the expected standard.
- Share the evidence calmly and in sequence, not as a pile of complaints.
- Ask what is getting in the way, and listen long enough to hear the real answer.
- Agree the support, the standard, and the deadline for visible change.
- Close with written actions so nobody leaves with a different memory of the meeting.
What I avoid is just as important. I do not compare the employee with someone else, because that usually triggers defensiveness instead of insight. I do not present every problem at once, because people stop hearing the detail after the third criticism. And I do not treat the review like a debate to be won. The goal is improvement, not victory. Once the conversation is handled well, the next step is to turn it into a plan with real weight.
What a credible improvement plan looks like
A serious improvement plan is not a motivational poster with dates on it. It is a working document that tells the employee what success looks like, how it will be measured, and what support they will receive. I prefer a 30, 60, 90-day structure because it gives enough time for change without letting the issue drift.
The plan should cover five things:
- One or two priority targets - not eight. Too many goals make the plan impossible to follow.
- Specific measures - numbers, dates, quality checks, or observable behaviours.
- Support - coaching, shadowing, training, clearer briefs, tools, or a temporary workload reset.
- Check-in cadence - weekly or fortnightly at the start, depending on the severity of the issue.
- Review point and consequence - what happens if the standard is met, and what happens if it is not.
There is also a judgment call on timing. For a small, specific issue, two to four weeks may be enough to prove change. For a broader skills gap, eight to twelve weeks is more realistic. I would not make the plan so long that urgency disappears, but I would also not pretend complex behaviour changes happen in three days. If the plan is built properly, the next question becomes whether the issue has crossed into a formal capability route.
When the issue should move into a formal capability route
A formal capability process makes sense when the same performance gap keeps showing up despite clear feedback, support, and a fair chance to improve. At that point, the problem is no longer just a conversation issue. It is a management issue that needs structure, records, and consistency.
Before moving there, I would check three things:
- Has the employee been told exactly what is expected?
- Has the organisation actually given the support it said it would provide?
- Has the employee had enough time and follow-up to show change?
It is also important not to mix up capability and conduct. If the main issue is lateness, refusal to follow instructions, or disrespectful behaviour, that may belong in a different process. On the other hand, if a disability, health issue, or neurodiversity is involved, the process should be adjusted rather than rushed. The practical rule is simple: be firm about the standard, but fair about the route you use to enforce it. That leads naturally to the part people often overlook - what happens after the meeting.
The next 30 days matter more than the label
What turns a weak review into a useful one is not the rating itself. It is the follow-through. If the conversation ends and nothing is scheduled, the employee has no real chance to recover, and the manager has no basis for judging change.
- Send the written notes within 24 hours, while the discussion is still fresh.
- Book the first follow-up within 7 days, not a month later.
- Track just a few measures so the evidence stays clear.
- Check whether the support offered is actually being used.
- Review whether the target is realistic or needs to be adjusted.
For employees, the smartest response is equally direct: ask for examples, restate the expected standard in your own words, and confirm the next review date before leaving the meeting. For managers, the real test is whether the process is specific enough to produce change. If both sides leave with a shared plan, the review becomes a reset. If they leave with only a label, the same problem will return.
