This is not legal advice. If the situation involves discrimination, retaliation, medical leave, accommodation, wage issues, whistleblowing, harassment, or protected complaints, consider speaking with an employment attorney before sending strong written accusations or signing exit paperwork.
A standard PIP check-in with a manager and possibly HR present. You want to participate in good faith, clarify expectations, preserve the record, and avoid overexplaining.
Strategy before the meeting
Your goal is not to win the whole PIP in the meeting. Your goal is to leave with:
- The exact expectations for the next review period
- The evidence that will be used to judge progress
- Any blockers, dependencies, or support needs documented
- A calm record that shows you are participating without admitting every allegation
Bring three things
- The PIP document or written warning
- A short list of completed work since the last check-in
- A short list of questions that force clarity
Do not bring
- A long speech about unfairness
- A full history of every prior conflict
- Speculation about motives
- A threat to go to HR, legal, social media, or leadership
The complete script, line by line
Opening
Say
Thanks for meeting. I want to make sure I understand the expectations clearly and that I am tracking progress in the same way you are. My goal today is to confirm what is expected before the next check-in, what evidence will be used to evaluate progress, and whether there are any blockers we need to resolve.
Why it worksThis opening does three things. It shows good-faith participation, moves the meeting toward measurable facts, and frames the conversation around shared tracking instead of emotional disagreement.
Don’t sayI still think this PIP is unfair and I want to go through everything wrong with it.
That may be true, but it invites a broad debate. Broad debates create messy records. Start with clarity, then preserve disputes in a controlled way.
Confirm the standard
Say
Can we go through each PIP expectation and confirm what successful performance looks like for the next period? For each item, I would like to confirm the deliverable, deadline, review owner, and how completion will be measured.
Why it worksThis forces vague categories into operational terms. "Better communication" becomes response time, meeting notes, stakeholder updates, or escalation rules. "More ownership" becomes named deliverables and dates.
Don’t sayWhat do you even mean by communication? That is completely subjective.
It may be subjective, but the phrasing sounds combative. Ask the same question in a way that makes the manager define the standard.
Address a disputed point without sounding defensive
Say
I understand this concern is part of the record. I want to add one clarification so the record is complete. On [date], I delivered [specific item], and the related document is [document/link/name]. If there is a different gap you are referring to, can you point me to the example so I can address it directly?
Why it worksThis is the right shape for a dispute: acknowledge, clarify, provide proof, ask for the specific example. It avoids the trap of saying "that never happened" when the manager may have a different example in mind.
Don’t sayThat is false. I have always done my job, and you know it.
Absolute denials are easy to challenge. Specific corrections are harder to dismiss.
Document blockers and dependencies
Say
For [goal], my ability to complete it depends on [person/team/system/approval] by [date]. I can own [your part]. I cannot control [dependency]. Can we document the dependency and agree on how it will be treated if the response or approval is delayed?
Why it worksThis is HR-insider important. PIPs often contain goals that depend on other people while still holding the employee solely responsible. You want the dependency named before the deadline fails.
Don’t sayI cannot do this because everyone else is blocking me.
That sounds like blame. The better version separates what you control from what you do not control.
Ask for examples behind vague feedback
Say
For the feedback about [communication/ownership/quality/judgment], can you give me two recent examples you want me to use as the reference point? I want to make sure I am correcting the specific behavior you are concerned about, not guessing.
Why it worksThis is a clean way to challenge vague language. It makes the manager either provide examples or admit the feedback is not yet specific.
Don’t sayThis is just vague corporate language.
It may be vague, but saying that does not improve your file. Asking for examples does.
Respond to new criticism raised during the meeting
Say
I hear that this is an additional concern. Since it was not listed in the written PIP, can we confirm whether it is now part of the PIP expectations? If so, I would like the specific standard, example, and deadline in writing so I can address it properly.
Why it worksThis protects against moving goalposts. New feedback may be legitimate, but if it becomes part of the PIP, it should be documented clearly.
Don’t sayNow you are just adding things because you want me gone.
Motive language is risky unless you are prepared to support it. Focus on the process change.
If HR is in the meeting
Say
Since HR is here, I want to confirm the process. Will HR be maintaining the official record of these check-ins, or should I send a written summary after each meeting? I want to make sure the record reflects expectations, progress, and any dependencies accurately.
Why it worksThis reminds HR that the record should be complete, not just employer-favorable. It also gives you a reason to send your own follow-up summary.
Don’t sayI hope HR is here to make sure my manager stops targeting me.
That may be a real concern in some cases, but it is too broad for a standard check-in. If targeting, retaliation, discrimination, or protected activity is involved, get individualized advice before making accusations.
If they ask whether you agree with the PIP
Say
I understand the expectations in the document and I am participating in the process. I may have clarifications or context on some points, and I will keep those tied to specific examples and documents. For today, I want to focus on what successful performance looks like by the next check-in.
Why it worksThis avoids the forced-choice trap. You do not have to say "I agree with everything" to show you are participating. You also do not have to turn the meeting into a refusal.
Don’t sayYes, I agree.
If you do not actually agree, that sentence can hurt you later.
Don’t sayNo, I reject this entire process.
That can be framed as nonparticipation.
If they ask for a response on the spot
Say
I want to respond accurately, so I would like to review the notes and send a short written follow-up by [date/time]. I do not want to answer from memory and create confusion.
Why it worksThis buys time without sounding evasive. It also signals that you care about accuracy and the written record.
Don’t sayI cannot talk about this without a lawyer.
In some situations legal advice may be appropriate, but dropping that line in a standard check-in can escalate the meeting fast. If you do need legal advice, get it before the meeting or ask for time in a neutral way.
Close the meeting
Say
To confirm my next steps: I will complete [deliverable] by [date], send [update/report] to [person] by [date], and flag any blocker by [date/time]. Please let me know if I missed anything or if any of those expectations are different from your understanding.
Why it worksThis creates a clean end-of-meeting record. It also gives the manager a chance to correct the summary. If they do not correct it, your follow-up becomes more useful.
Don’t sayFine. I will do whatever you want.
That sounds frustrated and vague. The record needs named actions, dates, and owners.
Follow-up email after the meeting
Thank you for meeting today. I am sending this summary to make sure I am tracking the expectations accurately.
My understanding is:
- [Expectation 1]: [deliverable], due [date], measured by [standard]
- [Expectation 2]: [deliverable], due [date], measured by [standard]
- [Dependency/blocker]: [who/what is needed], needed by [date]
- Next check-in: [date/time]
I will proceed on that basis. Please let me know if anything above is different from your understanding.
Why it worksThis is one of the most useful records you can create. It is neutral, specific, and hard to characterize as uncooperative. It also gives you proof of what you understood the standard to be.
What never to say, and what to say instead
Don’tThis is illegal.
BetterI want to make sure the process and expectations are documented clearly.
Legal conclusions can escalate the record before you have the facts sorted.
Don’tYou are trying to fire me.
BetterCan you confirm what successful completion of the PIP would look like and who makes that decision?
The better question forces them to describe the path and decision-maker.
Don’tEveryone knows my manager is the problem.
BetterFor the record, I want to separate the specific performance expectations from any process issues that may affect my ability to complete them.
Group opinion is weak. Process facts are stronger.
Don’tI have been perfect.
BetterI am prepared to address the stated concerns. I also want the record to include the completed work and context that relate to those concerns.
Perfect is not credible. Specific is credible.
Don’tI will sign whatever you need.
BetterI would like time to review before signing. If a signature only confirms receipt, please note that it does not mean I agree with every statement.
Some signatures are harmless acknowledgments. Some are broader. Read before signing.
Don’tI am going to HR about this.
BetterI may ask HR to clarify the process so I understand how the PIP is being administered.
This keeps the conversation process-focused instead of sounding like a threat.
Get a script built for your specific situation
If your next check-in is routine and you need a clean structure, use PIP Shield ($50) before the meeting.
If HR is active, the deadline is close, new accusations are being added, or this could become an exit conversation, use PIP Defense ($450) or book a 1:1 Strategy Call before sending your next written response.