Performance Improvement Plans: How to Run a Fair PIP

Key Takeaway / TL;DR: A fair performance improvement plan (PIP) names a specific, evidenced performance gap, defines measurable success criteria the employee can actually control, runs on a clear 30/60/90-day timeline with scheduled check-ins, and commits the manager to concrete support — coaching, resources, clarified priorities. A PIP is appropriate only after expectations were clear and informal feedback failed; used as a surprise or a paperwork ritual before a predetermined exit, it's neither fair nor effective. Document everything, involve HR early, and consult counsel on anything legally ambiguous.

What Is a Performance Improvement Plan?

A performance improvement plan is a formal, written, time-bound agreement between a manager and an employee that does four things: names a specific performance gap, defines what acceptable performance looks like in measurable terms, commits both sides to a support plan, and sets a timeline with scheduled checkpoints for evaluating progress.

The key word is formal. A PIP is what you reach for when informal feedback — delivered clearly, more than once, with time to respond — hasn't closed the gap. It escalates the seriousness explicitly: this is now a structured process with defined outcomes, including the possibility that the role doesn't work out.

Done honestly, a PIP serves both parties. The employee gets something they often haven't had: total clarity about what's wrong, what "fixed" looks like, and real help getting there. The company gets either a recovered employee — the genuinely best outcome, since they keep the institutional knowledge you already paid for — or a fair, documented basis for parting ways.

Done dishonestly — as theater before a decision already made — a PIP poisons trust well beyond the person on it. Teams can tell the difference, and they remember.

When Is a PIP Appropriate — and When Isn't It?

A PIP is appropriate when all four of these are true:

1. The gap is about performance, not fit or preference. Missed deliverables, quality problems, unmet role expectations — things that can be described in observable terms.
2. Expectations were actually clear beforehand. This one fails more often than managers admit. Gallup has found that only about half of employees strongly agree they know what's expected of them at work. If expectations were never explicit, the first fix is a clear expectations conversation — not a PIP. You can't formally fail someone against a standard they were never given.
3. Informal feedback has already been tried. The employee has heard the concern specifically, at least twice, with time to respond. A PIP should confirm a known problem, never announce one.
4. Improvement is genuinely possible and genuinely wanted. You can articulate what success looks like, and you'd be pleased — not inconvenienced — if they achieved it.

A PIP is the wrong tool when:

• It's a surprise. If the employee's last review was fine and no serious conversation preceded it, the process failure is yours.
• The real issue is conduct. Policy violations, harassment, and ethics breaches are disciplinary matters with their own procedures — not "improvement" opportunities.
• The role changed, not the person. If the job outgrew the employee or the goalposts moved, that's a re-scoping or redeployment conversation.
• The decision is already made. If no realistic performance would change the outcome, a PIP is dishonest to the employee and legally riskier, not safer — a pretextual process looks like exactly what it is.
• The gap traces to something a PIP can't fix — chronic under-resourcing, an impossible dual-reporting setup, or circumstances that call for an accommodations or leave conversation instead. Fix the system before formalizing blame on the person inside it.

What Should a PIP Actually Contain?

Five components, none optional:

1. The specific gap, with evidence. Not "communication needs improvement" but: "In Q2, four of six client deliverables missed committed dates by a week or more (April 12, May 3, May 24, June 9), and two required rework after client escalations." Dates, artifacts, numbers. If you can't evidence the gap concretely, you're not ready to write the PIP.

2. Measurable success criteria. What does "fixed" look like, in terms both parties can verify without arguing? (More on this below — it's where most PIPs fail.)

3. A timeline with structure — 30/60/90 days is the standard shape. Ninety days total, with distinct expectations at each gate:

• Day 30: Early signal. The employee has engaged with the plan, quick-fix items show movement, support is in place and being used.
• Day 60: Substantial progress. Most criteria trending clearly toward the bar; course-correct the plan if something reasonable has changed.
• Day 90: Full evaluation against the written criteria, and a decision.

Shorter can be fair for narrow, fast-feedback gaps (a 30- or 45-day plan for punctuality of deliverables); complex skill gaps may need the full 90. The timeline should match how long improvement genuinely takes to demonstrate — not how long HR paperwork usually runs.

4. The support the company commits to. A PIP without support is a countdown clock. Real support is specific: weekly coaching time with the manager, a named mentor for the skill in question, a training course with work time allocated to complete it, reprioritized workload so the improvement areas are actually practicable, clearer specs, pairing sessions. Write the support into the document with the same precision as the expectations — the company is on the plan too.

5. A check-in schedule and the stakes, stated plainly. Weekly check-ins, on the calendar now, plus the formal 30/60/90 reviews. And an honest sentence about consequences: that failure to meet the plan may result in reassignment or termination. Omitting this to soften the conversation is a false kindness that reads later as a trap.

How Do You Write Success Criteria That Are Actually Measurable?

Bad criteria doom a PIP from the first paragraph, in one of two directions: so vague that the day-90 conversation is an argument about interpretation, or so harsh that no strong performer could meet them — which tells everyone what the PIP really is.

Tests for every criterion:

• Verifiable by both parties independently. "Submit the weekly report by Friday 5pm, complete per the attached template, for 10 of the 12 weeks" — either it happened or it didn't. "Show more initiative" fails this test permanently.
• Within the employee's control. Criteria that depend on other teams, market luck, or approvals the employee can't obtain aren't performance measures — they're dice.
• Set at "meets expectations" — not "heroic." The bar is the standard you hold the rest of the team to. If the criteria demand more than your solid performers deliver, the plan is punitive, and it will read that way to anyone who later reviews it.
• Few enough to matter. Three to five criteria. A twelve-item PIP guarantees partial failure and signals that the goal was coverage, not improvement.

How Should Check-Ins Work During a PIP?

Weekly, short, and structured — this is where the plan actually happens.

Each check-in covers three things: progress against the specific criteria since last week, obstacles (including whether the promised support is materializing — from the manager's side too), and priorities for the coming week. Fifteen to thirty minutes.

Two disciplines make check-ins fair. First, no drift: feedback in check-ins must track the written criteria. Introducing new complaints mid-plan — "also, your meeting presence…" — turns a defined process into a moving target. If something new and serious emerges, amend the plan explicitly and adjust the timeline. Second, no silence: skipping check-ins because they're uncomfortable, then delivering a day-90 failure verdict, is the single most common way managers make a defensible PIP indefensible.

Write a short summary after every check-in and share it with the employee: what was reviewed, status, next steps. No surprises, ever — the employee should be able to predict the day-90 outcome weeks in advance because the weekly record has told them exactly where they stand.

What Should You Document — and Why?

Everything, contemporaneously, factually.

• The pre-PIP history: the informal feedback conversations, when they happened, what was said (this is why writing feedback down before things get formal matters so much)
• The PIP document itself, acknowledged in writing by the employee — noting that acknowledgment means receipt, not necessarily agreement
• Every check-in summary, shared with the employee at the time
• Evidence attached to each criterion at day 30, 60, and 90 — the actual reports, dates, and outputs, not just verdicts
• The support delivered, with dates — if the company failed to hold up its end, that fact belongs in the record too, and it should change the outcome

Documentation isn't (only) about protecting the company. A well-documented PIP protects the employee from shifting standards, protects the manager from memory disputes, and forces the whole process to run on evidence instead of impressions. Keep the tone factual throughout: describe behaviors and outcomes, never character.

What About the Legal Side?

A note of general caution rather than legal advice: employment law varies significantly by jurisdiction, and PIPs intersect with it in ways that aren't always obvious — protected-status considerations, disability accommodations, medical leave, retaliation claims if the employee recently raised concerns, and documented-practice consistency (a PIP for one person over conduct others do freely is a problem). Involve HR before the PIP is presented, not after it goes wrong, and consult employment counsel whenever anything about the situation is ambiguous — recent complaints, accommodation requests, leaves, or anything else that gives you pause. The consistent themes that serve everyone: clear prior notice, honest evidenced criteria, consistent application across the team, and a genuine opportunity to succeed.

What Happens at the End — and How Does Tooling Help?

Day 90 has three honest outcomes. Success: say so unambiguously, close the plan in writing, and treat the person as recovered — a permanently probationary employee will leave anyway. Partial progress: a single, bounded extension can be fair if the trajectory is genuinely positive; serial extensions help no one. Not met: proceed with the transition respectfully — the documented process is what lets that conversation be brief and dignified rather than contested.

The thread running through every section above is records: expectations set in writing, feedback logged when it happened, goals with visible progress, check-ins with shared notes. That's infrastructure, and it's much easier when it's your everyday system rather than an emergency binder — platforms like LVL Up Performance keep goals, feedback history, review records, and 1:1 notes in one place, which means that by the time a PIP is warranted, the fair version of it is mostly already written.

The best PIP outcome is the one where the plan worked. Run it like you mean that.