Most Performance Improvement Plans are written to fail. Not intentionally — but because they are drafted when a manager has already given up, handed to HR as a formality before a dismissal process, and presented to the employee as a surprise. The employee knows it. The manager knows it. HR knows it. And yet everyone goes through the motions.
That’s the version of the PIP that has given the whole tool a bad name. Done properly, a PIP is one of the most useful things a manager has at their disposal. Done badly, it wastes weeks of everybody’s time, damages trust, and creates exactly the legal liability it was supposed to protect against.
This is a guide to doing it properly.
What a PIP is actually for
A Performance Improvement Plan is a structured, time-bound agreement between a manager and an employee that sets out specific performance standards, the support available to meet them, and the consequences if they are not met.
That word “agreement” matters. It is not a disciplinary sanction. It is not a formal warning. It is a documented plan. Many managers conflate the two — partly because PIPs are often the final step before capability proceedings, and partly because HR departments sometimes introduce them as a softer form of warning to avoid the word “disciplinary.” Neither framing is helpful to anyone.
A PIP is designed to give a struggling employee a fair, supported, documented opportunity to reach the required standard. If the employee reaches it, the problem is solved. If they don’t, the organisation has a clear, defensible record that appropriate support was offered and the standard was not met.
The key is that both outcomes — improvement and documented failure to improve — are legitimate uses of the process. A PIP that only succeeds if the employee gets better has already failed as a management tool.
Before you reach for a PIP: questions to ask first
The most common mistake is introducing a PIP too soon or too late. Too soon means the employee hasn’t yet had clear, informal feedback that their performance is below standard. Too late means the manager has been tolerating the problem for months and is now using the PIP to build a dismissal case.
Before you start drafting anything, ask yourself honestly:
Has the employee been told, clearly and directly, that their performance is not meeting the standard? Not hinted at. Not included in a general team message. Not said in a way that allowed any ambiguity. If the answer is no, a PIP is premature.
Does the employee know exactly what the standard looks like? This sounds obvious but it frequently isn’t. “Better attitude” and “more proactive” are not performance standards. “Responds to client enquiries within four working hours” is.
Is this a skill problem or a will problem? Someone who can’t do the job needs training, coaching, or a different role. Someone who can do the job but isn’t choosing to do it is a different conversation entirely. A PIP addresses both — but the support you offer looks very different.
Have you checked for external factors? A sudden drop in performance is sometimes the first sign of something happening outside work — health, bereavement, a difficult personal situation. None of these remove the need to manage performance, but they do affect how you do it. A short, private conversation before starting formal proceedings can save weeks of difficulty.
If you have done all of the above — and the performance is still below standard — a PIP is appropriate.
How to write a PIP that actually works
A PIP needs to meet the SMART criteria that apply to any well-set objective: Specific, Measurable, Agreed, Realistic, and Time-bound. This is not optional. A vague PIP is not defensible, and it doesn’t give the employee a fair chance.
A working PIP document should include:
The specific performance concern. Not a general statement of disappointment. Specific, factual examples with dates. “Client satisfaction scores in Q1 averaged 62%, against a team target of 80%” is useful. “Not meeting expectations on client service” is not.
The required standard. What does good look like? If it’s measurable, state the number. If it’s behavioural, describe the observable behaviour. “Attends team meetings and contributes at least one substantive point per session” is observable. “Shows more engagement” is not.
The timeline. PIPs typically run for four to twelve weeks. Shorter than four weeks rarely gives enough time to demonstrate genuine change. Longer than twelve weeks tends to drag without resolution. The right length depends on the nature of the performance gap: a procedural issue might be resolved in six weeks; a more complex behavioural shift might need longer.
The support offered. This is the section that turns a PIP from a paper exercise into a genuine attempt to help. What training? What coaching? More frequent one-to-ones? Access to a mentor? Whatever it is, commit to it specifically and make sure it actually happens.
Review checkpoints. Don’t wait until the end of the PIP to assess progress. Weekly or fortnightly check-ins let both parties identify early if things are getting worse, and give the employee feedback they can act on.
The consequences of not meeting the standard. This needs to be stated clearly, not buried. The employee must understand that failure to meet the PIP objectives may result in capability proceedings. This is not a threat — it is information, and they are entitled to have it.
Everything should be written down, shared with the employee before the PIP begins, and signed by both parties. Not to create legal protection — though it does — but because clarity is the foundation of a fair process.
Running the PIP period
A PIP that is written well and managed poorly is still a failed PIP. The formal document is only useful if what happens during the improvement period reflects the intent behind it.
The manager’s role during the PIP period is active, not administrative. This means:
Following through on the support you committed to. If you promised fortnightly coaching sessions, have them. If you said you’d provide access to a training resource, arrange it. If you don’t deliver the support, the employee has a legitimate grievance about the process — and they would be right.
Keeping contemporaneous notes. After each check-in, note what was discussed, what progress was observed, and what was agreed. Brief is fine. These notes matter if the situation escalates, and they also keep both parties honest.
Giving real feedback, not just updates. The check-ins should not be a progress report from the manager to the employee. They should be a genuine conversation: What’s working? What’s getting in the way? What does the employee think they need? The manager who turns a PIP check-in into a one-way status update is doing everyone a disservice.
Not saving up bad news for the end. If it becomes clear by week three of an eight-week PIP that performance is not improving, say so. The employee deserves the chance to course-correct, and the manager who stays silent until the end and then says “you didn’t meet the standard” has not run the process fairly.
When PIPs go wrong
There are a handful of predictable failure modes.
The surprise PIP. Presented without prior informal feedback, the employee hears it as a threat rather than an opportunity. They disengage immediately, often involve a union or seek legal advice, and the process becomes adversarial before it’s even begun. The fix is simple: informal feedback should always precede formal process.
The vague PIP. Objectives that cannot be measured cannot be fairly assessed. An employee who is told to “demonstrate a more positive attitude” has no idea what they’re being assessed against. Neither does the manager. The only outcome of a vague PIP is disagreement about whether the standard was met.
The unsupported PIP. The manager writes a development plan with good intentions, then does nothing to deliver on it because they’re busy, or because they’ve already emotionally moved on from the employee. The employee does the best they can with no support and fails. This is not a performance management outcome — it’s a management failure, and it will be seen as one.
The retaliatory PIP. Issued to an employee who has raised a grievance, requested flexible working, or disclosed a health condition. Even where there is a genuine underlying performance concern, timing matters enormously. Take legal advice before issuing a PIP in any of these situations.
The ghost PIP. The PIP period ends, the manager cannot bring themselves to have the consequences conversation, and nothing happens. The employee assumes they’ve passed. Six months later the conversation happens anyway — but now without the documented process that would have made it fair and defensible.
The conversation that matters most
Writing the PIP is the easy part. The conversation where you present it to the employee is where most managers struggle — and where most PIPs go wrong before they’ve started.
A few principles that help:
Be direct. Tell the employee at the outset what the conversation is about. Don’t spend ten minutes on small talk and then pivot to a formal improvement plan. The employee will feel ambushed.
Be factual, not emotional. The evidence is the evidence. Present it clearly, without editorialising about what it says about the employee as a person. “In the last three months, the error rate on your reports has averaged 12% against a team average of 3%” is a fact. “I’m disappointed with the quality of your work” is your emotional state, and it puts the employee on the defensive rather than in a position to engage with the substance.
Give the employee time to respond. They may have context you don’t. They may be surprised. They may be upset. None of these invalidate the process, but all of them are worth hearing before you finalise the document.
Be clear about what you want the outcome to be. The right message is not “I’m putting you on a PIP to give you a chance before we let you go.” It’s “I want you to succeed in this role. This plan sets out what that looks like and how I’ll support you to get there.” Mean it when you say it.
The legal and HR context
Performance management processes sit within employment law — in the UK, primarily the Employment Rights Act 1996 and the ACAS Code of Practice on Disciplinary and Grievance Procedures. The ACAS Code does not technically cover capability proceedings (as distinct from disciplinary ones), but employment tribunals do take it into account when assessing whether a process was reasonable.
This matters because “reasonable” is the standard. Not perfect, not flawless — reasonable. A manager who genuinely tried to help an employee improve, documented the support offered, gave clear feedback throughout, and followed a transparent process is very likely to be on the right side of that test. A manager who used a PIP as a paper exercise to build a dismissal case is not.
When in doubt, involve HR early. Not to outsource the management, but to make sure you’re following your organisation’s procedure and not creating unintended liability.
Related reading
If your organisation needs a structured approach to developing managers through exactly these scenarios — having difficult conversations, running performance processes, building confidence in managing underperformance — SkillsCircle offers structured CPD pathways designed for working managers rather than classroom theory.