Blog post

How to Write an Effective Performance Improvement Plan (PIP) That Actually Works

Learn how to create a fair, legally defensible performance improvement plan that drives real behavior change. Includes template, legal considerations, and how data removes bias from PIP decisions.

How to Write an Effective Performance Improvement Plan (PIP) That Actually Works
Last updated: March 2026

Meta description: Learn how to create a fair, legally defensible performance improvement plan that drives real behavior change. Includes template, legal considerations, and how data removes bias from PIP decisions.


What This Post Covers

A Performance Improvement Plan (PIP) isn't a punishment. It's a structured agreement that tells an employee exactly what needs to change, how you'll measure it, and what support they get. Done right, it either gets the employee back on track or documents why they're not a fit. Done wrong, it becomes a lawsuit waiting to happen.

This guide covers what actually works, based on talking to HR leaders who've been through the process hundreds of times. You'll learn when PIPs help (and when they don't), how to structure them legally, and the specific mistake that makes them backfire most often.


What Is a Performance Improvement Plan?

A performance improvement plan (PIP) is a formal, documented agreement between an employer and an employee that:

  • Defines the problem clearly. Specific performance gaps, not vague complaints
  • Sets measurable expectations. What success looks like in concrete terms
  • Provides support and resources. What the company will do to help
  • Establishes a timeline. Usually 30-90 days, sometimes 6 months
  • Makes consequences clear. What happens if expectations aren't met

Think of it as a contract. Both parties agree on what's expected, how it will be measured, and what happens next.

The key phrase: "We want to help you succeed. Here's what we need to see."


When Should You Use a PIP?

Not every performance problem needs a PIP. In fact, most don't.

A PIP is appropriate when:

  • The problem is specific and fixable. Not a fundamental skills mismatch or culture fit issue
  • Documentation already exists. You've had conversations, sent emails, given feedback. This isn't a surprise
  • The employee has the capacity to improve. They understand the issue and theoretically could fix it
  • There's genuine business value in improvement. The role still matters, and the employee still has a chance

Don't use a PIP when:

  • You've already decided to fire the person (it becomes obvious, creates legal risk)
  • The problem is attitude/culture fit rather than performance (PIPs don't fix cultural issues)
  • The employee is new and just needs training (use onboarding plans instead)
  • You're avoiding a difficult conversation (PIPs won't help here either)
  • The employee is protected by disability law (you may have legal obligations to accommodate instead)

If you're genuinely trying to help an employee improve, a PIP works. If you're just documenting your way to a termination, skip the PIP and have an honest conversation. If the PIP fails, see our guide on how to fire an employee legally and respectfully.


The Three Critical Components of a PIP

Every effective PIP has these three pieces. Miss one, and it falls apart.

1. Specific Performance Gaps

Bad: "Your work quality needs to improve."

Good: "You've missed 3 of the last 5 deadlines. Code reviews show 12+ open comments per pull request on average. We need daily deliverables completed by 5 PM PT and code reviews addressed within 24 hours."

Be so specific that an objective third party would agree whether the gap exists or not.

The mistake most managers make: staying vague to avoid hurting feelings. Vagueness is what gets you sued. An employee can't improve what they don't understand.

2. Measurable Success Criteria

What does "fixed" look like? Define it in numbers, not feelings.

Example:

  • All project deadlines met for 60 days
  • Customer satisfaction scores above 85% for two consecutive months
  • Attendance 100% (no unexcused absences) for the duration of the plan
  • Zero compliance violations in the next quarter

You need an objective way to measure success. Your gut feeling doesn't count, and neither does "improvement." Define the bar. Make it achievable but not trivial.

3. Support and Resources

This is where most PIPs fail. Managers skip this part.

You can't just say "improve or else." You have to actually help.

What support looks like:

  • Coaching or mentoring. Weekly check-ins with you or an experienced peer
  • Training. Specific courses or skill-building
  • Adjusted expectations temporarily. Maybe they get smaller projects during the improvement period
  • Clear communication. Regular feedback on progress
  • Removal of obstacles. If they're failing because of bad tools or unclear process, fix that

Example: "You'll have a weekly 30-minute check-in with your team lead every Monday. We're enrolling you in the 'Advanced Excel' course. I'm removing the weekly status report from your plate so you can focus on deadline delivery. We'll review progress together every two weeks."


How Bias Sneaks Into PIPs

Here's what most guides skip: PIPs are perfect vehicles for bias if you're not careful.

A manager can write a PIP that looks objective but is actually targeting someone unfairly. And it will hold up in writing. Which is why data matters.

Where bias enters:

  • Selective documentation. You document one person's missed deadlines but not another's
  • Vague standards. "Not a team player" means different things for different people
  • Inconsistent application. You gave someone else a warning for the same issue, but this person gets a PIP
  • Different measurement bars. You accept 80% completion from one employee but require 95% from another
  • Timing. PIPs that appear right after an employee asks for a raise, reports a complaint, or becomes pregnant look suspicious (and are)

The antidote: Use data, not judgment.

Don't say "You're not performing well." Say "Here's your output versus the team average. Here's your error rate. Here are your deadline metrics." Let the numbers make the case.

Compare the PIP against:

  • How you've treated similar issues with other employees
  • What the actual job requirements are
  • Industry standards for the role
  • Whether you're measuring everyone the same way

If you can't make the case with data, the PIP is probably unfair.


Legal Considerations: The Stuff That Actually Matters

Lawyers care about four things:

1. Reasonable Accommodation (If Applicable)

If the performance issue might be related to a disability, mental health condition, or other protected status, you may be required to try accommodation before a PIP.

Example: If someone's missing deadlines because of anxiety or ADHD, the legal path might be accommodation (flexible hours, different tools, adjusted workload) before a PIP.

Action: If there's any possibility a medical condition is involved, consult HR and legal before proceeding. This is not optional.

2. Retaliation Concerns

If the employee:

  • Recently filed a complaint (harassment, discrimination, wage violation, safety hazard)
  • Asked for a raise or promotion
  • Complained about working conditions
  • Reported something to a government agency (OSHA, EEOC, Department of Labor)

Then a PIP can look like retaliation. The appearance matters as much as intent.

Action: If timing looks suspicious, wait 6-12 months or document that the performance issue existed before the protected activity.

3. At-Will Employment Doesn't Mean No Documentation

Even in at-will employment states, companies lose lawsuits because they didn't follow their own procedures.

If your handbook says "Employees receive a warning before termination," but you skip straight to a PIP and then fire someone, you've created evidence of unfairness.

Action: Follow your own policies. If you don't have clear policies, create them before you're in crisis.

4. Consistency

Are you treating everyone the same way?

Did someone else get a warning instead of a PIP for the same issue? Did you let someone miss deadlines without consequences? Did you give one person three chances but this person one?

Inconsistency is what turns a reasonable termination into a lawsuit.

Action: Before writing a PIP, ask: "Have I handled similar issues consistently in the past?" If no, acknowledge that in writing or adjust accordingly.


The PIP Process: Step by Step

Step 1: Have the Conversation First (Not Written)

Before the PIP exists in writing, have a conversation. Tell the employee:

"Your performance in [area] hasn't met expectations. Here's what I'm seeing. [Share specific examples.] This needs to change. I want to help you improve. Let's put together a formal plan so we're both clear on what's expected."

If they're blindsided by the PIP, something went wrong earlier. There should have been feedback, conversations, and warnings.

Step 2: Write the PIP Document

Use this structure:

PERFORMANCE IMPROVEMENT PLAN

Employee: [Name]
Position: [Title]
Department: [Department]
Effective Date: [Date]
Review Period: [X days/weeks]

PERFORMANCE ISSUES
[Describe specific gaps with data/examples]

EXPECTED PERFORMANCE
[Define exactly what success looks like]

SUPPORT & RESOURCES
[What you'll provide]

MEASUREMENT & REVIEW
[How progress will be tracked and when]

NEXT STEPS
[What happens if expectations are or aren't met]

Employee Signature: ________    Date: ________
Manager Signature: ________     Date: ________

Keep it factual. No editorializing. Let the data do the talking.

Step 3: Get HR Approval

Before you give this to the employee, HR and legal review it. They'll catch:

  • Language that could be interpreted as discriminatory
  • Policies you're not following
  • Timing concerns
  • Alternative approaches you haven't considered

Don't skip this step. A lawyer's review takes 20 minutes. A lawsuit takes years.

Step 4: Present the Plan in Writing and In Person

Meet with the employee. Go through the PIP together:

  • Explain why it's happening (connect to previous conversations)
  • Be clear it's not a punishment, it's a structured path
  • Explain what success looks like and what happens if expectations are met
  • Explain consequences if they're not met
  • Answer questions
  • Get their signature

Make a copy for them. This is theirs to keep.

Step 5: Check In Regularly

This is not a "we'll talk in 90 days" situation. Check in weekly or biweekly:

  • How are they doing on the metrics?
  • What obstacles came up?
  • What additional support do they need?
  • Are they on track?

Document these conversations. Write a quick note: "Reviewed progress on [date]. Status: [on track / falling behind]. Areas of improvement: [X]. Areas of concern: [Y]."

If they're failing, you'll have documentation. If they're succeeding, they'll have evidence to point to.

Step 6: Make the Call

At the end of the PIP period:

If they met expectations. Congratulations. Remove the PIP. Let them know they're back on solid ground. Don't hold it against them forever.

If they partially improved. You have options. Extend the PIP, adjust expectations, or let them go. Choose based on business needs, not feelings.

If they didn't improve. You have documentation. The termination is defensible because you gave them clear expectations, support, and a fair shot.


Common PIP Mistakes (And How to Avoid Them)

Mistake 1: The Surprise PIP

You haven't given feedback before. The employee opens their email and finds a formal plan. They feel ambushed.

Fix: Have conversations first. The PIP should never be a surprise.

Mistake 2: Vague Expectations

"Be a better team player." "Improve your attitude." "Step up your performance."

These are feelings, not metrics. An employee can't aim at a moving target.

Fix: Use data and numbers. "Attend 100% of meetings" vs. "Be more engaged." "Reduce bug rate from 8% to under 3%" vs. "Write better code."

Mistake 3: No Support Offered

"Here's what you need to do. Figure it out."

This isn't a plan, it's a setup.

Fix: Actually allocate resources. Weekly coaching. Training budget. Adjusted projects. Make it real.

Mistake 4: Moving the Goalpost

Halfway through, you change what success looks like. Or you keep adding new requirements. Or you accept 80% completion but then say it's not enough.

Fix: Write the expectations down. Don't change them unless there's a genuine business reason, and if you do, update the PIP in writing.

Mistake 5: Treating It as a Punishment

The employee feels like they're in trouble. They become defensive or demoralized.

Fix: Frame it as support: "I see you're struggling in [area]. I want to help you get back on track. This plan is how we do that together."

Mistake 6: Using It as a Backdoor to Termination

You've already decided to fire them. The PIP is just documentation.

Employees can feel this. They become less likely to improve. And if they improve anyway, you look petty firing them.

Fix: Only use a PIP if you genuinely want them to improve and have a business reason for them to stay.


How Data Removes Bias From PIPs

This is the Confirm angle: Data-driven performance management removes the human bias that makes PIPs feel unfair.

Traditional PIP: A manager looks at Sally's work and thinks "She's not keeping up." Subjective. Biased. Sally feels targeted.

Data-driven PIP: Here's Sally's output: 78 tickets completed this quarter vs. team average of 112. Here's her quality: 4% error rate vs. 2% team average. Here's her deadline adherence: 76% vs. 88% team average.

Now you're not arguing. You're just stating facts.

Bias still exists, but it's much harder to hide. When everyone can see the same data, it's obvious if you're applying different standards to different people.

Tools like Confirm give you:

  • Objective performance tracking across the team
  • Consistent measurement standards
  • Historical data (so you can't suddenly decide someone's underperforming when the data shows they've been consistent)
  • Visibility into whether you're treating people fairly

A manager says "Jenny doesn't pull her weight." The data says Jenny's in the top 15% of output. Now the conversation changes.


Your PIP Template: Get It Free

We've built a PIP template that covers:

  • Performance gap documentation (with space for data/examples)
  • Success criteria framework
  • Support and resources checklist
  • Review and measurement schedule
  • Legal review notes

Download the template now. Use it as your starting point. (Customize it for your role, your company, your situation.)

[CTA: Get the free PIP template + legal checklist]


FAQ

How long should a PIP last?

Most PIPs are 30-90 days. Some are shorter (30 days for clear, fixable issues), some longer (6 months for complex performance problems). The length depends on how long it reasonably takes to show improvement in that area.

What if an employee refuses to sign the PIP?

They don't have to sign it to be bound by it. If they refuse, document that they refused. "Employee declined to sign PIP. Plan was presented on [date]. Employee stated: [reason]. PIP is in effect regardless."

Can you fire someone who's on a PIP?

Yes, but the appearance matters. If they're improving but you fire them anyway, that looks discriminatory. If they're not improving and you gave them support, that's defensible.

What happens to the PIP if an employee goes on leave (vacation, medical, parental)?

You pause the clock. If someone goes on medical leave for 6 weeks, you don't count those weeks against their 90-day window. Restart the PIP when they return.

Can an employee appeal or contest the PIP?

Depending on your policy, yes. Many companies allow employees to appeal through HR. Let them. It's not a bad thing. It shows fairness in process.

Should everyone on the team know about a PIP?

No. It's private between the employee, their manager, and HR. If the whole team knows, it becomes a gossip situation and the employee feels humiliated, which hurts improvement chances.

What if the employee improves partway?

You have options: End the PIP (if they've met criteria), extend it (if progress is there but not complete), or adjust expectations (if the original goals were too ambitious). Don't yank it away capriciously or move the goalpost.

Is a PIP considered a "write-up"?

It's more formal than a write-up. It's a structured improvement plan. In employment law, it's evidence that you gave someone a chance to improve before any termination. That's valuable.


Key Takeaways

  • A PIP is not punishment. It's a structured agreement to help someone improve or document why they can't.
  • Specificity beats kindness. Being vague to spare feelings actually hurts the employee more. Be clear about the problem.
  • Data removes bias. Use numbers and facts, not judgment calls. This makes PIPs fairer and legally stronger.
  • Support is non-negotiable. If you're not genuinely helping them improve, don't write a PIP.
  • Consistency matters. How you treat one person shapes how you can legally treat others.
  • Get HR involved. A 20-minute legal review prevents a two-year lawsuit.

A well-executed PIP either fixes a real problem or documents why it couldn't be fixed. Either way, it protects the company, respects the employee, and serves the business.


Internal links included:

  • [Link to Confirm performance management product page: how data drives fair PIPs]
  • [Link to HR compliance resources: legal considerations guide]
  • [Link to performance management playbook: ongoing feedback strategies to avoid PIPs]

Schema markup ready: Article schema + FAQ schema included in rendering.


Next Steps

Your move:

  1. Download the free PIP template above
  2. Customize it for your company's policies
  3. Get HR review before using it
  4. Use it as a tool for improvement, not punishment

[CTA Button: "Get the Free PIP Template + Legal Checklist"]

See Confirm in action

See why forward-thinking enterprises use Confirm to make fairer, faster talent decisions and build high-performing teams.

G2 High Performer Enterprise G2 High Performer G2 Easiest To Do Business With G2 Highest User Adoption Fast Company World Changing Ideas 2023 SHRM partnership badge — Confirm backed by Society for Human Resource Management

Ready to see Confirm in action?