PIP Plan Guide - Write Effective Performance Improvement Plans

Managing underperformance is easier when the process is structured, documented, and fair. This guide explains how to write a PIP plan in a way that gives someone a real chance to improve, without blurring the line between support and discipline. I’m focusing on what actually works in UK workplaces, especially where public-sector standards, accountability, and employee development all matter at once.

Start by deciding whether a PIP is the right tool

A performance improvement plan, or PIP, is not a shortcut to discipline. I would use it only when someone’s performance is clearly below the required standard, the issue has been observed more than once, and there is a genuine path to improvement. ACAS is clear that employers should try to help someone improve before starting formal disciplinary action, and that support should be documented.

That means a PIP usually fits situations like missed deadlines, repeated errors, weak case handling, poor quality of written work, or unreliable stakeholder communication. It is less suitable for a one-off mistake, a personality clash, or a conduct issue that should be handled through a disciplinary route instead. If the real problem is attendance, behaviour, or attitude, do not disguise it as a performance issue just because a PIP feels softer.

In a public-sector setting, I would also ask whether the role expectations are actually clear. If the standard is fuzzy, the plan will be fuzzy too. Once you know the problem belongs in a PIP, the next step is to gather facts that can stand up to scrutiny.

Build the case on facts, not frustration

The strongest PIPs start with a clean evidence trail. Before I draft anything, I want to know what happened, when it happened, what the expected standard was, and what support has already been tried. That usually means reviewing recent work samples, emails, customer or service-user feedback, deadlines missed, error rates, and any notes from one-to-ones or coaching conversations.

When the evidence is clear, the conversation becomes easier and less emotional. I also find that a simple record protects everyone: the manager is not relying on memory, and the employee can see that the issue is real rather than personal. ACAS also recommends keeping a written record of performance conversations and sharing it afterwards, which is a sensible baseline for any formal process.

Evidence type	What it should show	Why it matters
Work samples	Specific mistakes, omissions, or quality gaps	Shows the issue in concrete terms, not opinion
Deadlines and KPIs	Missed dates, backlog size, response times, accuracy levels	Connects the concern to measurable standards
Feedback records	What was raised, when, and how the employee responded	Shows whether the problem was already discussed informally
Training or support history	What help was offered and whether it was used	Helps show the plan is supportive, not abrupt

I would also check whether the issue is spread across one area or across the whole role. That distinction matters, because a narrow gap often needs one or two targeted actions, while a broad failure in core duties may require a deeper review of fit, training, or workload. With the evidence in hand, you can build a plan that says something useful instead of something generic.

Draft the plan around clear outcomes

The actual document should be simple enough to read in one sitting. I usually aim for one to two pages for the active plan, with any supporting evidence kept in an appendix or case file. If the PIP is so long that nobody can use it during a check-in, it has already become too complicated.

At minimum, I want the plan to answer six questions: what is not working, what good looks like, how progress will be measured, what support will be provided, when reviews will happen, and what happens if improvement does not materialise. That structure keeps the document practical and avoids the common trap of writing a vague warning dressed up as a plan.

Section	What to write	What to avoid
Performance concern	Describe the specific gap and the evidence behind it	General complaints like “needs to be better”
Expected standard	State the role requirement or service standard	Assuming the employee already knows the target
Improvement goals	Use 3 to 5 measurable objectives	A long wish list of unrelated issues
Support	List coaching, training, observation, or tools	Leaving the employee to figure it out alone
Review schedule	Set weekly or fortnightly check-ins with dates	“We’ll see how it goes”
Outcome if no improvement	Explain the possible next step in neutral language	Threatening dismissal in the first draft

If I were writing this for a public-sector manager, I would keep the language direct and professional. Service quality, accuracy, timeliness, and compliance usually matter more than style, so the plan should reflect those realities. Once the structure is clear, the real work is turning broad concerns into goals the employee can actually hit.

Make the goals measurable and realistic

This is where most PIPs either become useful or collapse. A goal like “communicate better” sounds neat, but it is too vague to manage. A better goal says what communication should look like in practice: respond to internal emails within one working day, update case notes before close of business, or give stakeholders a progress summary every Friday by 3 p.m.

I usually prefer no more than 3 to 5 objectives. Any more than that, and the plan starts to feel like a catch-all critique rather than a focused improvement effort. The timeframe should also match the role and the severity of the issue. In many workplaces, a 4 to 12 week review period is workable, provided there are regular check-ins and the employee is not being asked to change too many habits at once.

Vague target	Measurable target	Why the second version works
Improve report quality	Submit reports with no more than two factual errors per month	Defines the standard and how success will be counted
Be more responsive	Reply to internal messages within one working day unless the matter is escalated	Sets a time-based expectation
Manage workload better	Keep the case backlog below the agreed threshold for four consecutive weeks	Turns a broad concern into a trackable measure
Work more collaboratively	Attend weekly team meetings and provide a 2-minute progress update on assigned actions	Makes the behaviour visible and reviewable

For public-sector work, I would often anchor the targets to service outcomes: response times, file accuracy, meeting deadlines, policy compliance, or stakeholder updates. That keeps the plan relevant to the role, not to a manager’s personal preference. After that, the question becomes whether the employee has the right support to meet the target in the first place.

Include support and adjustments the right way

A PIP without support is just a warning in document form. The employee should know what help is being offered, who is responsible for it, and how often that support will be reviewed. Useful options often include coaching, job shadowing, refresher training, clearer written instructions, workload reprioritisation, and closer supervision for a short period.

This is also the point where fairness matters most. If disability or a health condition may be affecting performance, the plan should not rush past that issue. ACAS and GOV.UK both emphasise reasonable adjustments where a worker is placed at a disadvantage, and in practice that means checking whether the barrier is the person’s performance or the way the work is currently arranged. I would not finalise a PIP until I had considered whether a temporary adjustment, different communication format, assistive software, or altered deadlines could remove the problem.

• Coaching for judgement, prioritisation, or confidence issues.
• Training for technical skills, procedures, or systems knowledge.
• Shadowing where the person needs to see the standard in action.
• Workload changes if the current volume makes success unrealistic.
• Reasonable adjustments if health, disability, or neurodiversity is part of the picture.

The principle is simple: support should be specific, not symbolic. If the plan says “training will be provided”, that is too weak. It should say what training, by whom, by when, and what improvement it is expected to produce. Once support is visible on the page, the review meetings become much easier to run properly.

Run the review meetings like a process, not a verdict

I would always treat the review meeting as a working session, not a courtroom. The aim is to check progress, remove blockers, and reset expectations if needed. A short weekly or fortnightly meeting usually works better than a long monthly one, because the employee gets timely feedback and the manager can correct small problems before they become habits.

Each meeting should end with a written note of what was discussed, what progress has been made, what still needs work, and what happens before the next review. That written record matters. It creates continuity, helps the employee track improvement, and stops the conversation from drifting into “he said, she said” territory later on.

1. Open with the original objective and the current measurement.
2. Check whether the employee has completed the agreed support actions.
3. Review the evidence since the last meeting, not just impressions.
4. Identify blockers that need manager or HR action.
5. Agree the next step, the next deadline, and the next review date.

If the employee improves partially, say so clearly. Partial improvement matters, but it should still be measured against the standard. If progress stalls, do not improvise new targets midstream unless the original plan was plainly unrealistic. Keep the process consistent, and keep the tone calm. That discipline prevents the plan from feeling arbitrary, which is one of the fastest ways to lose trust.

Avoid the mistakes that make a PIP feel unfair

The most common failure is vagueness. The second is overload. A PIP that tries to solve everything at once usually solves nothing. I also see plans fail because they are written as if the employee is already guilty, rather than as if improvement is still possible. That creates resistance before the first check-in has even happened.

Avoid	Use instead
“Needs to show more commitment”	“Submit weekly case summaries by Friday 4 p.m. for the next six weeks”
“Poor attitude”	“Interrupts team briefings and does not confirm agreed actions in writing”
“Improve speed”	“Reduce average turnaround time on allocated tasks from five days to three days”
“Fix everything”	“Focus on these three priorities only”

Another mistake is skipping the support conversation and moving straight to consequences. That may satisfy a manager in the short term, but it weakens the process and makes the plan look pre-decided. I would also avoid mixing conduct and capability in the same section unless the case truly involves both, because that makes the employee’s route through the process much harder to understand.

Finally, do not let the wording become passive-aggressive. A PIP is more credible when it sounds calm, specific, and professional. If the tone is harsh, the employee will focus on defending themselves instead of improving their performance.

What I would do if the plan still does not move performance

If the employee meets the standard, close the plan in writing and note what success looked like. If the result is mixed, decide whether the issue needs another short review period, a revised support package, or a different role conversation. What I would not do is leave the file sitting open indefinitely; that helps nobody and only blurs expectations.

If there is no meaningful improvement, the next step depends on the organisation’s policy and the evidence available. In many UK workplaces that means moving into a formal capability or disciplinary route, but only after the review process has been fair, documented, and genuinely supportive. In public-sector teams, that usually means involving HR early, checking consistency with policy, and keeping the decision tied to evidence rather than frustration.

The best PIPs are practical, modest, and honest. They give the employee a fair chance to succeed, they protect the manager from inconsistency, and they make it obvious whether the problem is performance, support, or role fit. If you keep those three things in view, the document becomes a management tool rather than a paper exercise.