What to Say in a PIP Meeting: Word-for-Word Scripts for Every Stage

Which habit is behind this for you? The free 3-minute assessment names it and links the playbooks that fix it. Take the assessment →

The invite says "catch-up" and has someone from HR on it. Twenty minutes later you are holding a document with your name on it, a list of things you have apparently been failing at, and a date sixty days away. Your manager is reading from notes. HR is watching you. And the thing nobody tells you is that what you say in the next quarter of an hour will be summarised in an email you never see, and that summary will matter more than anything in the plan itself.

This page is only about the words. How to survive a PIP covers the strategy - the two parallel tracks of complying in writing while preparing your exit in private. Here you get the scripts for each of the four conversations a plan contains: the meeting where you receive it, your written response, the weekly check-ins, and the final review.

Stage 1: the meeting where you receive the PIP

You will be in shock, which is fine; shock reads as composure if you keep your sentences short. Your goals are to get the document, get the answers to the questions below, and get out without committing to anything.

When they have finished reading it to you:

"Thank you for being direct with me. I'd like to read the document properly before I respond to any of it. Can I have the written plan today, and can we schedule a follow-up in the next two or three days to go through it once I've had time to think?"

The questions to ask before you leave. You are not challenging the plan - you are asking what it means. Most plans are vaguer than the people who wrote them realise, and asking these questions calmly is the single most useful thing you can do in the room.

• "For each item, what specifically does 'meets expectations' look like? Can that be written into the plan?"
• "How will each one be measured, and who makes the judgement - you, or someone else as well?"
• "What are the dates - the check-ins and the end date?"
• "What support is available during the plan - time, pairing, a clearer brief, anything?"
• "What happens at the end if the criteria are met? And if they're not?"
• "Is this a formal step under the company's performance policy? Can I have a copy of that policy?"

When you are asked to sign:

"I'm happy to sign to confirm I've received this. I'd like the signature line to say received rather than agreed, and I'll respond to the content in writing after I've reviewed it."

What not to say. Each of these feels natural and each one costs you.

• "I disagree with this." You may. Say it in writing, with evidence, in three days. Not now.
• "Is this because of [the incident / the other manager / my leave]?" Even if true, raising it in the room without preparation turns a performance process into a dispute you have not yet decided to have.
• "Am I being fired?" They will say no, and the "no" is meaningless. Ask instead what happens at the end in both outcomes.
• "I'm so sorry, I know I've been struggling." One acknowledgement is fine. A string of apologies becomes "employee accepted the assessment" in the summary.
• Anything about a lawyer. You may want advice; get it privately. Mentioning it in the room changes everyone's tone and gains you nothing.

If you need a single line to fall back on whenever you are pushed to react: "I hear that. I want to understand it fully before I respond."

Stage 2: your written response

Within two or three days, send a short email. Its purpose is to pin down the criteria, correct anything factually wrong, and put your requests for support on the record. Keep it under a page and keep every sentence something you would be comfortable having read aloud in a meeting you are not in.

"Hi [Manager], thank you for going through the plan with me on [date]. I've read it carefully and want to make sure I've understood what's expected.

As I read it, the criteria are: (1) [criterion, measure, date]; (2) [...]; (3) [...]. Please correct me if I've misread any of them.

Two points of fact: the [project] delay in October followed the dependency on [team] that I flagged on [date] - I've attached the thread. And [item] isn't currently measurable as written; could we agree a concrete definition at Tuesday's check-in?

To give this the best chance of working I'd ask for [specific support: a written scope for X, a weekly 30-minute review, access to Y].

I'm committed to meeting the plan and I'll send a short summary against each criterion after every check-in."

Attach the evidence; do not describe it. A link to a merged pull request or a dated message is worth more than a paragraph explaining what you did.

Stage 3: the weekly check-ins

Each check-in is the same meeting. You report facts against each criterion, you ask one question that forces a judgement in the room, and you recap it in writing afterwards. The question is the part people miss, and it is the part that protects you: a manager who says "on track" on week three cannot comfortably write "consistently below expectations" on week eight.

"Against criterion 1, the migration PR merged on Tuesday - here's the link. Against 2, I sent the design doc Monday and got sign-off from [name] Thursday. Against 3, I'm blocked on the staging credentials I asked for last week; who should I chase?

Based on this week, is there anything I've done that you'd count against the plan? I'd rather hear it now than at the end."

Then the recap, within the hour:

"Thanks for today. Summary against the plan: (1) done - [link]; (2) done - [link]; (3) blocked on [item], you'll chase [name]. You confirmed nothing this week counts against the plan. Next check-in [date]."

If the answer to your question is "well, there was the [new thing]", that is good news: you have just discovered a moving goalpost on week three instead of week eight. Respond with: "That's not in the plan as written - can we add it with a measure and a date, or confirm it's outside the plan?"

Stage 4: the final review

There are three ways this meeting goes, and you should walk in with a sentence ready for each.

If the criteria were met:

"Thank you. I'd like that confirmed in writing - that the plan is closed and the criteria were met - and I'd like to talk about what the next three months look like, because I don't want to be here again."

If they say the criteria were not met:

"I'd like to see that against the weekly summaries, because the record for each check-in says otherwise. If the decision is already made, then I'd rather discuss how we handle the exit - notice, reference, and a transition package - than argue the assessment."

If you have decided you want out regardless:

"Given where this has ended up, I think a structured transition is better for both of us than running the process to the end. What would that look like from your side?"

The strategy behind that last option - when to take the exit, what to ask for, and how to keep the record clean while you interview - is in the PIP survival playbook.

This page describes a conversation, not the law. Employment rules on performance processes, companions at meetings and dismissal vary by country and by contract; if money or notice is on the table, get advice from someone qualified where you work.