What is a performance improvement plan, formally?

A documented process setting out specific objectives, a timeline to meet them, and the support the employer will provide — Acas guidance describes PIPs in exactly those terms, typically following informal steps that have not resolved a capability concern. It is formal: its records persist, its outcomes have consequences, and it should be engaged with at that level of seriousness from the first meeting.

Can you survive a PIP and keep your job?

Yes — plans are passed, and the route back is real when the process is run in good faith. The pattern among people who come through: they engaged from day one, made every objective measurable, used all the offered support and chased the missing pieces, kept their own dated records, and corrected the file in writing where it was wrong. None of that promises an outcome; all of it improves the odds and the record simultaneously.

Should I sign a performance improvement plan I disagree with?

Check what the signature means — usually it confirms receipt and discussion, not agreement, and it is fair to ask that out loud. The stronger protection is a written response attached to the plan: accept what is accurate, dispute what is not with dated evidence, and confirm you will work the objectives regardless. Refusing to engage at all reads as the problem the plan alleges; precise, documented disagreement reads as credible.

Can a PIP lead to dismissal?

An unmet plan can lead into a capability procedure that can end in dismissal — that is the honest shape of the process, and it is why engagement and records matter from week one. The process must be fair to be lawful: genuine opportunity to improve, proper procedure, warnings at the formal stages. GOV.UK's guidance on dismissal sets out your rights, and Acas can advise on whether a process is being run properly.

Do I have the right to bring someone to a PIP meeting?

The statutory right to be accompanied attaches to formal disciplinary and grievance hearings; for performance meetings it depends on the meeting's nature and your employer's policy, and many policies allow a colleague or union rep at formal stages regardless. Read the capability policy, ask HR which meetings in your process carry the right, and involve a union rep early if you have one — Acas guidance covers the detail.

How long does a performance improvement plan last?

Commonly somewhere between four weeks and three months, with review points along the way — long enough to demonstrate genuine change on the objectives set. Be wary in both directions: a plan too short to realistically show improvement is worth querying in writing at the start, and an endlessly extended one with shifting goalposts is a pattern worth recording and, if needed, taking advice on.

Review

The performance improvement plan meeting: steady lines for a hard process

Updated 12 August 2026

Being told you are going on a performance improvement plan is one of the most frightening sentences working life produces, and the fright itself is the first thing to manage — because the meetings that follow reward exactly the qualities fear suppresses: steadiness, precision, and the ability to ask good questions while your pulse argues for either surrender or war. This page is the steady version, written for the reader who is in it or can see it coming.

Two honest framings, held at once, because either alone misleads. A PIP is what its name says: a structured route back to good standing, with objectives, support, and a timeline — Acas guidance describes it in exactly those terms, and people do come off plans successfully and go on to fine years. And a PIP is also a formal process with consequences at the end of it, whose paperwork will be read later by people who were not in the room. Treating it as a death sentence wastes the genuine route back; treating it as a formality wastes the protection that engaging seriously provides. The posture that serves you in every meeting: engaged, on the record, and taking the plan more seriously than anyone else in the room.

What follows works through the process in order — the meeting where the plan lands, the reading of the document itself, the disagreement done properly, the check-ins, and the endgame questions people are afraid to ask out loud. One boundary, stated plainly: this page teaches the conversations. It is not legal advice, and where rights and procedure matter — companions, capability procedures, dismissal — it points at Acas and GOV.UK, which is where those answers properly live. And if the process is reaching into your sleep and your health, the wellbeing note at the end of this page is not decoration; it is part of the plan.

Your career — see how Review closes the loop and informs what comes next.

What your reviewer is weighing

Whether you engage or bristle. From the first meeting, the record being built says one of two things: 'took it seriously, worked the plan' or 'fought the process'. Every later reader of the file — HR, an appeal, a panel — sees which, and the first is protective in every direction the process can go.
Whether your disagreement is specific or global. Disputing everything reads as denial; agreeing with what is fair and contesting precisely what is not, in writing, reads as credible — and makes the contested points harder to wave away.
Whether you use the support or only cite it. A plan's support clauses — training, supervision, adjusted workload — are also a test: the person who books the training and attends the check-ins prepared is visibly working the route back; the one who mentions support only at the end, as a complaint, has let it become evidence for the other side of the file.
Whether your evidence habit matches theirs. From the day a plan opens, the process runs on records. The person who confirms meetings in writing, keeps their own copies, and brings dated examples to check-ins is operating at the process's own standard — and is far harder to mis-describe.

'We're placing you on a performance improvement plan.' — the meeting where it lands.

Why it's asked: The hardest ninety seconds of the process, and the moment most likely to produce the two classic errors: the argument (contesting everything on the spot, unprepared) and the collapse (agreeing to everything, including things that are not accurate). The strong response does neither — it stays composed, gathers the process facts, and buys time to respond properly.

Model answerFormal meeting with manager and HR, claims handler, insurance company

"Okay. I won't pretend that's easy to hear — but I'd rather respond to it properly than react to it now, so let me make sure I leave this meeting understanding it fully.

Can I take the practical questions in order? First, I'd like a copy of the plan document today, and the performance data behind it — the quality scores and the file reviews you've mentioned — so I can look at the same evidence you're looking at. Second, the process itself: how long does the plan run, who reviews it, and what are the possible outcomes at the end — including the one nobody enjoys saying out loud? I'd rather know the whole shape of it than half. Third, what's the meeting rhythm — weekly, fortnightly — and is the capability policy this sits under on the intranet? I'll read it tonight.

On the substance: some of what you've described I recognise, and I'll say so properly when I respond. Some of it I see differently, and I'll put that in writing rather than argue it across a table today.

Last thing — I'd like to send a short note after this meeting confirming what was said and handed over, just so we start with one shared record. I'm going to take this seriously, and I want the process to see that from day one."

Everything here is doing double duty: the questions are genuinely needed, and asking them calmly, on the record, is the first entry in the file that says 'engaged professionally' — the most valuable sentence that file can contain.

Reading the plan document — what to check, and what to ask for before you sign anything.

Why it's asked: The plan document is the whole game: its objectives define success, its measures define evidence, and its support clauses define what you can hold the employer to. Vague objectives are the classic trap — 'improve communication' cannot be met, because it cannot be measured — and the reading below is the checklist that catches them while they can still be fixed.

Model answerFollow-up meeting, warehouse shift supervisor, distribution company

"I've read the plan twice, and I want to go through it while we can still adjust wording — because I intend to meet it, which means it has to be meetable.

Objective one — pick accuracy above the site standard for eight consecutive weeks — that one's fair and clear. It's measured by a system neither of us can argue with, and I've no changes.

Objective two says 'improve leadership visibility on shift'. I genuinely don't know how either of us would prove that met or not met at week twelve — it's a description of an impression. Could we replace it with the behaviours you actually want: the pre-shift briefing delivered every shift, the handover log completed daily, and the two floor walks logged per shift? If I do those for the full period and the impression still hasn't moved, we'll at least be arguing about facts.

Objective three — the stock discrepancy follow-ups — the target's fine, but it depends on the inventory team answering my queries inside two days, which is outside my control. Can the plan record that dependency? Not as an excuse in advance — as an honest description of how the number gets made.

And the support section currently says 'coaching as appropriate'. I'd like it to say what, when, and from whom — because I'll use it, and 'as appropriate' has a way of meaning 'never' once diaries get busy.

I'll confirm all of this by email once we've agreed the wording."

The pattern to copy: every push is toward measurability — and every request makes the plan more binding on both sides, which is precisely what a person intending to pass it should want.

'Do you accept this assessment?' — disagreeing on the record without torching the process.

Why it's asked: Most plans contain a mix: some fair findings, some contestable ones, occasionally something factually wrong. Global agreement signs you up to inaccuracies; global war marks you as in denial. The credible position — the one that survives later reading — agrees precisely, disputes precisely, and puts the disputes in writing while still engaging with the plan.

Model answerWritten response attached to the plan, finance assistant, academy trust

"Formal response to the performance improvement plan dated 4 March — I'd like this attached to the plan document.

I want to be straightforward about what I accept. The reconciliation errors in November and January happened, they were mine, and the plan is right to address accuracy — I've no quarrel with objective one and I've already restarted the checking routine I should never have dropped.

Two findings I dispute, with evidence. The plan states the month-end pack was late three times in the autumn term. My records — the submission emails, attached — show one late submission, in October, by one day, during the week the finance system migration locked us out for two days; the November and December packs went in on schedule. I ask that the plan be corrected to reflect the documented dates. Second, the plan describes the supplier statement backlog as unaddressed. The backlog was raised by me, in writing, in September, with a proposed fix — the attached email refers — and I was asked to hold the fix until after the migration. It is fair to say the backlog exists; it is not accurate to describe it as unaddressed, and the distinction matters for what happens next.

None of this changes my engagement with the plan: I'll work every objective in it, including the ones attached to findings I dispute. But the record should be accurate, because this record gets read later — by both of us."

Dated evidence, surgical scope, continued engagement: this is what credible disagreement looks like in a formal process, and it is the version that makes both corrections and cooperation easy to grant.

The check-in meetings — turning them from inspections into your evidence trail.

Why it's asked: The weekly or fortnightly reviews are where plans are actually passed or failed, and the difference is preparation: the person who arrives with their own dated record of progress runs the meeting; the one who arrives to be assessed gets assessed. The habit worth building from week one — bring the numbers, name the misses before they are found, and confirm every meeting in writing afterwards.

Model answerWeek-four check-in, customer service adviser, utilities provider

"I've brought my own tracker so we're looking at the same picture — I'll email it after, as usual.

Against objective one: call quality's been marked at green for three of the four weeks. Week two was amber, and I want to talk about that one rather than hope it isn't mentioned — it was the week of the billing system outage, my average handling time went long because I was doing manual lookups, and the amber was for call length, not accuracy. I'd like that context in the notes.

Objective two, the complaint escalations: four weeks, zero missed callbacks — the log's attached. That's the one the plan was really about, and I want it on the record every single fortnight it stays clean.

On support: the coaching session with Marcus happened in week two and genuinely helped — the callback scripting we built is why the log is clean. The refresher training the plan promised hasn't been booked yet; I've chased it once with the training team, copy attached. Can you push it from your side? I want to have done everything the plan offers, and right now the gap in the support column is not on my side of the table.

Same as always — I'll send the summary note this afternoon; tell me if anything in it reads differently from your notes."

The support chase is the underrated move: delivered without heat, it keeps the plan honest in both directions — and if the process ever reaches a panel, the person who used every offered support and chased the missing piece is standing on very different ground.

'Can I bring someone with me to these meetings?'

Why it's asked: Worth asking out loud at the start, because the answer depends on what kind of meeting each one is. The statutory right to be accompanied applies to formal disciplinary and grievance hearings; whether a given PIP or capability meeting attracts it depends on the meeting's nature and your employer's own policy — many policies allow a colleague or union representative at formal performance meetings regardless. The practical move: read the capability policy's wording on accompaniment, ask HR directly which meetings in this process carry the right, and if you are a union member, involve your rep early — Acas's guidance covers how the right works and where its edges are.

'Is this just managing me out?' — the question underneath every PIP, answered honestly.

Why it's asked: Sometimes no — plans genuinely succeed, and a manager who wanted you gone tomorrow has cheaper options than a twelve-week documented process. Sometimes yes — a plan can be the paperwork of a decision already leaning. The honest answer is that you usually cannot know from inside week one, and the strategy is identical either way: work the plan visibly, keep your own records, use every support clause, and correct the file where it is wrong. If the plan is genuine, that is how it is passed; if it is not, that is what makes the endgame contestable — and quietly updating your CV in parallel is not defeatism, it is the same prudence the process is showing you.

Asking for what the plan forgot — training, workload, and health adjustments.

Why it's asked: A plan that demands improvement while leaving every condition unchanged is asking the same person to produce different results by willpower, and it is legitimate to say so constructively: 'objective one needs the advanced systems training to be realistic — can it be in the plan with a date?' Two asks carry particular weight. If your workload materially exceeds the time the objectives assume, ask for the arithmetic to be done in the room. And if a health condition or disability is part of the picture, raise it formally — employers have a duty to consider reasonable adjustments, and a plan that was set without knowing about a relevant condition usually needs resetting once they do. Put both kinds of ask in writing; both belong in the file.

'What happens if I don't meet the plan?' — asking the endgame question out loud.

Why it's asked: The question everyone carries and almost nobody asks, which is exactly why it should be asked in the first meeting: 'if the plan isn't met, what does the process say happens next?' A capability process that can end in dismissal is required to be fair — proper procedure, genuine opportunity to improve, warnings along the way — and GOV.UK's dismissal guidance sets out the ground rules, with Acas covering the procedural detail. Knowing the whole shape does two things: it removes the vague dread that makes every check-in feel terminal, and it tells you precisely which stages carry appeal rights if you ever need them. Asking is not fatalism; it is the same professionalism the rest of this page runs on.

'Should I just resign and skip the whole thing?'

Why it's asked: The 2am question, and it deserves arithmetic rather than mood. Resigning mid-process trades the plan's real outcomes — including passing it, which happens — for certainty, and it usually costs the reference period, notice pay clarity, and any possibility that the file ends well; it can also complicate what you can claim or contest afterwards. There are situations where leaving on your own terms is the right call — a parallel offer in hand, a process being run in visible bad faith you have documented, a health cost that outweighs the job. But make the decision with advice rather than adrenaline: Acas's helpline exists for exactly this conversation, a union rep if you have one, and a night's sleep before anything is signed. The plan gives you weeks; use one of them to decide, not one evening.

FAQ

What is a performance improvement plan, formally?: A documented process setting out specific objectives, a timeline to meet them, and the support the employer will provide — Acas guidance describes PIPs in exactly those terms, typically following informal steps that have not resolved a capability concern. It is formal: its records persist, its outcomes have consequences, and it should be engaged with at that level of seriousness from the first meeting.
Can you survive a PIP and keep your job?: Yes — plans are passed, and the route back is real when the process is run in good faith. The pattern among people who come through: they engaged from day one, made every objective measurable, used all the offered support and chased the missing pieces, kept their own dated records, and corrected the file in writing where it was wrong. None of that promises an outcome; all of it improves the odds and the record simultaneously.
Should I sign a performance improvement plan I disagree with?: Check what the signature means — usually it confirms receipt and discussion, not agreement, and it is fair to ask that out loud. The stronger protection is a written response attached to the plan: accept what is accurate, dispute what is not with dated evidence, and confirm you will work the objectives regardless. Refusing to engage at all reads as the problem the plan alleges; precise, documented disagreement reads as credible.
Can a PIP lead to dismissal?: An unmet plan can lead into a capability procedure that can end in dismissal — that is the honest shape of the process, and it is why engagement and records matter from week one. The process must be fair to be lawful: genuine opportunity to improve, proper procedure, warnings at the formal stages. GOV.UK's guidance on dismissal sets out your rights, and Acas can advise on whether a process is being run properly.
Do I have the right to bring someone to a PIP meeting?: The statutory right to be accompanied attaches to formal disciplinary and grievance hearings; for performance meetings it depends on the meeting's nature and your employer's policy, and many policies allow a colleague or union rep at formal stages regardless. Read the capability policy, ask HR which meetings in your process carry the right, and involve a union rep early if you have one — Acas guidance covers the detail.
How long does a performance improvement plan last?: Commonly somewhere between four weeks and three months, with review points along the way — long enough to demonstrate genuine change on the objectives set. Be wary in both directions: a plan too short to realistically show improvement is worth querying in writing at the start, and an endlessly extended one with shifting goalposts is a pattern worth recording and, if needed, taking advice on.