Overview

A Performance Improvement Plan (PIP) is a document that might end up in court. If someone sues for wrongful termination, the PIP is evidence: did we give them a fair chance to improve? Did we communicate clearly about what was expected?

Most PIPs fail because they're vague or unreasonable. "Improve communication" with no specific examples. "Be more proactive" with no metrics. "Show better attitude" which is entirely subjective. When the person doesn't improve (and most don't, because they don't understand what success looks like), the company's credibility suffers: "We asked them to improve but never told them specifically what to improve."

A strong PIP is crystal clear: here's what's not working (with specific examples), here's the specific improvement needed (measurable success criteria), here are the metrics of success, here's the support we're providing, here's the timeline, and here are the consequences. A well-drafted PIP actually gives the person a genuine opportunity to improve. It also protects the company if termination follows.

This lesson teaches you how to use AI to draft PIPs that are fair, clear, and legally defensible. The stakes here are high: a PIP might lead to termination, which might lead to litigation. You need the documentation tight. You need clarity. You need to show you gave the person a fair chance.

Why This Matters for HR Professionals

A PIP is a legal document. It's evidence of your attempts to address performance before termination. It will be reviewed if someone sues for wrongful termination, discrimination, or retaliation.

A badly-written PIP:
- Creates liability (the person argues "you didn't clearly tell me what to improve")
- Demoralizes the person (they don't know what success looks like; they feel the deck is stacked)
- Often doesn't work (vague expectations = no improvement = termination)
- Creates legal risk (they sue, the PIP is weak evidence of fairness)

A well-written PIP:
- Is crystal clear on expectations (you can't argue about what was required)
- Is achievable but demanding (shows you're trying to help them succeed)
- Creates a genuine opportunity to improve (they know what to do and how to succeed)
- Is legally defensible if termination follows (we gave clear notice and a fair chance)

The difference is documentation quality. AI can help you write clear documentation. But you need to own the substance and get legal review.

The High Risk: Why Legal Review Is Mandatory

Before we talk about AI, let's be clear: every PIP should be reviewed by a lawyer before it's implemented. This is non-negotiable.

A PIP might lead to termination. Termination might lead to litigation. The PIP is evidence of whether you acted fairly.

If the PIP says "improve communication" and someone later argues it was retaliatory or discriminatory, you need strong documentation showing: you communicated clearly about what was expected, you gave them a reasonable chance to improve, you provided support, and you documented their performance (or lack thereof). A weak PIP (vague requirements, no support offered, unreasonable timeline) won't hold up in court.

Bottom line: Never ask AI to draft a PIP without planning legal review afterward. Never implement a PIP without legal approval.

This protects both the person (they get fair treatment) and the company (you have defensible documentation).

What a Strong PIP Includes

A strong PIP has these components. This structure is defensible and fair:

• Clear performance issue: Specific examples of what's not working (not general statements)
  - Business impact: Why it's a problem (how it affects the team/business)
  - Specific improvement needed: What "success" looks like (clearly defined)
  - Success metrics: How you'll know they've improved (measurable, testable)
  - Timeline: How long they have (typically 30, 60, or 90 days)
  - Support provided: Training, coaching, tools, whatever will help them succeed
  - Check-ins: When you'll meet to review progress (weekly is typical)
  - Consequences: What happens if they don't improve (termination)

A PIP with these components is thorough, fair, and defensible. It shows you gave the person a clear chance to succeed.

The Performance Issue: Specific Examples, Not Vague

This is the foundation of a strong PIP. Specificity matters legally and practically.

Bad:
"Communication has been an issue."
"Attitude has been concerning."
"Reliability has declined."

These are vague. The person can't argue with them because they don't specify anything. But they also can't improve because they don't know what the problem is.

Good:
"In the last three months, you've missed three project deadlines without communicating the status to your manager. Specifically: Q3 planning doc due Aug 15, submitted Aug 25; customer proposal due Sept 10, submitted Sept 24; Q4 roadmap due Oct 1, not submitted. You also didn't send weekly status updates despite the team asking in standup each week. This impacts the team's ability to plan and causes projects to slip."

See the difference? The good version has specific examples with dates. The bad version is vague generalization.

How to gather specifics before asking AI:

Have a conversation with the manager: "Give me specific examples of when this person didn't meet expectations."

Don't accept "they're not performing" as an answer. Dig in:
- "Give me a specific project/deadline where they didn't meet expectations."
- "What specifically did they do (or not do)?"
- "When did this happen?"
- "What was the impact?"

Write down these specifics. This is your input for AI.

Example gathering:

Manager: "James isn't pulling his weight on code quality."

You: "Give me a specific example."

Manager: "He keeps writing code with low test coverage."

You: "How many times? What projects? What was the test coverage? What's expected?"

Manager: "Last month, he submitted three PRs for the auth feature. All three had test coverage below 60%. Expected is 80%. Each one had to be reworked. He also submitted a PR with a critical bug that made it to staging."

Now you have specifics: three PRs last month, test coverage 60% vs. expected 80%, rework required, one PR had a critical bug.

How to use AI:

You have manager feedback with specifics. Ask AI:

"Drafting a PIP for a software engineer. The performance issue is: [paste the specific examples]. Write the 'Performance Issue' section of a PIP. Make it specific, factual, not judgmental. Include dates and examples where possible."

AI produces:

"Over the last month, you submitted three pull requests to the authentication feature with test coverage below 60%, compared to the team standard of 80%. Each PR required rework to meet quality standards. Additionally, you submitted a PR containing a critical bug that made it to staging. These incidents indicate your code isn't meeting the performance standards for your role."

Specific. Factual. Defensible.

The Success Criteria: Measurable, Not Subjective

This is critical. The person must know exactly what success looks like. And you must be able to measure it objectively.

Bad success criteria:
"Show better attitude and be more engaged."
"Improve communication."
"Be more proactive."

These are subjective. Different people might judge them differently. The person can argue "I did improve my attitude" and you can't prove they didn't.

Good success criteria:
"Complete the communication training by Week 2. Provide weekly status updates (email every Friday at 5pm) starting Week 1. Meet all project deadlines; next project (Q4 launch) must be delivered on schedule. Code reviews must show test coverage above 80% for all submissions."

The good version is measurable. You'll know if they succeeded.

How to develop measurable criteria:

For each performance issue, ask: "What would improved performance look like?"

Not "better attitude" but "attends all meetings on time, responds to Slack within 2 hours during business hours, volunteers to help on tasks."

Not "improve communication" but "sends daily standup updates, documents decisions in writing, asks clarifying questions in meetings instead of derailing them."

Not "be more proactive" but "identifies blockers before the manager asks, proposes solutions to problems, raises issues early (not day-before-deadline)."

How to use AI:

"The performance issue is [specific issue]. The person must improve in [area]. Generate 3-5 measurable success criteria. What would improved performance look like? How would we measure it?"

Input: "Performance issue: missed deadlines. Needs to improve in: delivering projects on schedule."

AI output:
- Criterion 1: Deliver all assigned projects by the agreed deadline (zero misses). Measured by project tracking system.
- Criterion 2: Provide weekly status updates (email Fridays at 5pm) showing progress and blockers. Starting Week 1.
- Criterion 3: Communicate delays 48 hours in advance (not day-of). Document reason for delay and recovery plan.
- Criterion 4: If a deadline is at risk, escalate to manager immediately and propose revised timeline. No surprises.
- Criterion 5: Complete a project management training course by Week 2. Apply learnings to current projects.

These are measurable. You can see if they succeeded.

The Support: What You're Providing

A fair PIP includes support. Not just "improve or you're out." But "here's how we'll help you improve."

Support demonstrates good faith. It also increases the likelihood of improvement. It shows a court (if it comes to that) that you gave the person a genuine chance.

Examples of support:
- Specific training or external coaching
- More frequent feedback/check-ins (daily or twice-weekly instead of weekly)
- Pairing with a peer mentor or strong performer
- Modified responsibilities (remove distracting tasks; focus on the core improvement area)
- Tools or resources
- External resources (books, courses, trainings)
- Clear documentation of what success looks like
- Regular feedback on progress

How to determine what support to offer:

For the improvement area, what would actually help someone get better?

Example: "Improve deadline management"
Support options:
- Project management training (external course)
- Weekly planning sessions with manager (structured forecasting)
- Daily check-ins on blockers (clear obstacles early)
- Pairing with senior engineer who's excellent at estimation
- Reduced scope (fewer concurrent projects so they focus)
- Calendar blocking for focused work time

You can offer several of these. The more support you offer, the more defensible and fair the PIP.

How to use AI:

"The improvement needed is [issue]. What support would help someone improve in this area? Generate realistic options that [company] could provide."

AI suggests options. You decide which ones you'll provide and document them.

Example:

Input: "Improvement needed: Improve code quality and test coverage. Person needs to get from 60% to 80% test coverage on all submissions."

AI output:
"Support options:
- Enroll in unit testing/TDD training (Week 1)
- Weekly code review sessions with senior engineer (1 hour)
- Pair programming on first two PRs of the new project
- Documentation: provide examples of high-test-coverage PRs to reference
- Slack channel for questions (quick feedback)
- Access to testing tools/frameworks"

You decide: "We're providing: TDD training in Week 1, weekly code reviews with [senior engineer], and pair programming on first two submissions."

Document it in the PIP: "We're providing the following support: enroll you in unit testing training (Week 1), weekly code review sessions with [name] on Fridays (1 hour), and pair programming on your first two PRs to the Q4 project."

This is fair. It shows you're invested in their success.

The Consequences: Being Crystal Clear

The person needs to understand this is serious. If they don't improve, termination is likely.

Clear language:
"If you don't meet the success criteria outlined above, your employment will be terminated."

Vague language:
"We hope you'll improve and understand the importance of this performance plan."

The vague version is too soft. The person might not realize they're on thin ice. The clear version tells them the stakes.

In the PIP, be explicit:
"This Performance Improvement Plan indicates that your job is at risk. If you do not meet the success criteria outlined above, your employment with [company] may be terminated. We are committed to helping you succeed. However, you must meet these expectations by [date]."

This is clear, direct, and fair.

The Duration: 30, 60, or 90 Days?

A PIP needs a definitive end date. The length depends on the issue:

30 days: For clear-cut, objective issues (deadlines, code quality, attendance). You can measure improvement quickly.

Example: Attendance PIP. You can measure "improved" in 30 days (showed up on time, no absences).

60 days: For skill-based issues where the person needs to develop a new competency.

Example: Code quality PIP. They need time to learn testing practices and apply them across multiple PRs.

90 days: For complex behavioral issues where sustained change is needed.

Example: Leadership/communication PIP. They need to change how they interact with the team, and that takes time to show sustained improvement.

Whatever you choose, be clear in the PIP: "This performance improvement plan is effective [date] and will be evaluated on [end date], 30/60/90 days from now."

The Check-in Schedule: Frequent Communication

The PIP should include a check-in schedule. Typically weekly during the PIP period.

Check-in structure:
Week 1: "Progress on success criteria A and B?"
Week 2: "How's the training going? What are you learning?"
Week 3: "Show me examples of improved performance."
Week 4: "Are we on track to hit the success criteria?"

At each check-in, document: what they're doing well, what needs improvement, whether they're on track.

Why this matters:
- It provides feedback so they know how they're doing
- It documents their progress (or lack thereof) for legal defensibility
- It gives you a chance to adjust support if they're struggling
- It shows good faith effort to help them succeed

Evaluating the PIP: End of Period

At the end of 30/60/90 days, you evaluate: did they meet the success criteria?

If yes: Congratulations, the PIP is over. You might document this and continue monitoring, but the PIP period is done.

If no: You have two options:
1. Extend the PIP (rare; usually happens if they were very close)
2. Terminate employment (most common if they didn't hit the criteria)

Document either outcome clearly. If extending, explain why and what changed. If terminating, you have documentation showing you gave them a fair chance.

Try This Now: Three Exercises

Exercise 1: Specificity Exercise

Take a performance issue you're aware of (or imagine one: "poor communication," "low productivity," "attitude problem").

Ask your manager/yourself: "Give me specific examples. When did this happen? What specifically did they do (or not do)? What was the impact?"

Write down 2-3 specific examples.

Ask AI: "Make this specific: [vague issue]. Provide concrete examples. [paste the specific examples you gathered]."

Review what AI produced. Is it specific enough to put in a legal document?

Exercise 2: Success Criteria

Ask AI: "The performance issue is [specific issue]. Generate 4-5 measurable success criteria. What would improved performance look like? How would you measure it?"

Review the criteria. Could you measure them objectively? Would the person understand what success looks like?

Exercise 3: Full PIP Draft

Ask AI: "Draft a Performance Improvement Plan for [role]. Performance issue: [issue with examples]. Success criteria: [measurable criteria]. Timeline: 60 days. Support: [support you'll provide]. Draft the full PIP document."

Review the draft. Is it clear? Fair? Legally defensible? Show it to a lawyer.

Practical Application - "What to Do Monday Morning"

• 
  Before you draft a PIP, consult your lawyer: Know what's legally required in your jurisdiction.
• 
  Gather specific examples: Don't start with vague complaints. Get concrete examples from the manager.
• 
  Define success clearly: Measurable criteria. You must know objectively if they improved.
• 
  Determine what support to offer: Show you're invested in their success.
• 
  Use AI to organize and clarify: AI helps you write clear, organized PIPs. But you provide the substance.
• 
  Have legal review the PIP: Before you implement. This is non-negotiable.
• 
  Communicate clearly: Have a face-to-face meeting with the person. Explain the issue, the expectations, the timeline, the support, and the consequences.
• 
  Document everything: Check-ins, feedback, progress. This is your evidence.

Key Takeaways

• PIPs are legal documents: They might be evidence if someone sues. Make them defensible.
  - Specific > vague: Examples matter. "Missed three deadlines" is specific. "Unreliable" is not.
  - Measurable success criteria: You must know if they improved. "Better attitude" isn't measurable.
  - Include real support: Training, coaching, mentoring. Show you're trying to help them succeed.
  - Legal review is mandatory: Before you implement. This protects everyone.
  - Document everything: Check-ins, feedback, outcomes. This is your evidence.
  - Clear consequences: They need to understand termination is possible if they don't improve.

FAQ

Q: What's the success rate of PIPs?
A: Statistically low. 10-20% result in improvement and the person continuing employment. 80-90% result in termination. PIPs are often a documented opportunity, often a prelude to termination. But some people do improve when given clear expectations and support.

Q: Should I tell someone they're on a PIP or just implement it?
A: Tell them. Have a clear conversation: here's the issue, here's what needs to improve, here's the timeline, here's support, and here are the consequences. Surprise PIPs are unfair and legally indefensible.

Q: Can I modify a PIP mid-way?
A: Yes, if circumstances change legitimately. But document any modifications and the reason.

Q: What if someone says the PIP is unfair?
A: Listen to their concerns. If you think they have a point, you might adjust. If you don't think they have a point, document that you heard their concern and explain why the PIP is fair. Have legal review whether the PIP is defensible.

Q: Should a PIP be public?
A: No. It's confidential. Only the person, their manager, HR, and any legal counsel know about it. Don't broadcast it to the team.

Q: Can I put someone on a PIP for being a "cultural mismatch"?
A: Legally, this is dangerous. PIPs should be for specific, measurable performance issues, not personality or culture fit. If culture fit is the issue, that's a different conversation.

Q: What if the person improves 50%?
A: If the success criteria were "meet all deadlines," and they met 50% of them, that's not meeting the criteria. The PIP period ends with an "improvement not sufficient" result and termination. Be clear about the bar. They either meet the success criteria or they don't.

What's Next

You've covered performance management: reviews, goals, feedback, and PIPs. Chapter 6 is about compensation and benefits: how to use AI to analyze and communicate total rewards effectively.