Performance Improvement Plan (PIP) Template and Guide
A PIP structure with real, measurable goals, why most PIPs fail as a documentation exercise, and a template that gives someone a genuine chance to improve.
A performance improvement plan sits in an uncomfortable spot: it's supposed to be a genuine chance to fix a problem, but it's often written mainly to protect the business ahead of a termination that's already effectively decided. Both things can be true of the same document, and pretending otherwise doesn't help either side.
The way to make a PIP actually useful — for the employee if they can turn it around, and for the business either way — is specificity. A vague PIP is a bad outcome twice over: it doesn't give someone a real path to improve, and it doesn't hold up well if the outcome is termination.
What makes a PIP real versus performative
Real PIPs have measurable goals, not impressions. "Respond to client emails within 24 hours, verified by email timestamps, for the next 45 days" is measurable. "Improve responsiveness" is not — nobody can prove or disprove it on day 44.
Real PIPs reference prior conversations. If a PIP is the first time a performance issue has ever been named directly, that's a sign the process skipped a step — informal feedback and, often, a documented write-up should generally come first, except for serious or safety-related issues.
Real PIPs include support, not just requirements. Additional training, more frequent check-ins, or a temporarily adjusted workload where relevant. A PIP that only lists what the employee must do, with nothing about what the manager or company will do differently, reads as one-sided because it is.
Real PIPs have a genuinely achievable timeline. Thirty days for a goal that takes a full sales cycle to demonstrate sets someone up to fail on a technicality rather than a fair measure of whether they actually improved.
A PIP template
Employee name and role:
Performance gap identified: [Specific, observable — not a trait]
Prior discussion of this issue: [Date(s) and brief summary]
Specific, measurable goals for this period:
- [Goal with a clear, objective way to verify it]
- [Goal with a clear, objective way to verify it]
- [Goal with a clear, objective way to verify it]
Support provided during this period: [Training, resources, adjusted check-in cadence]
Check-in schedule: [Weekly or biweekly, with specific dates]
Plan duration: [Start date] to [end date]
Outcome if goals are met: [Plan concludes successfully, documented]
Outcome if goals are not met: [Stated plainly — typically further discipline up to termination]
Employee signature: [Acknowledges receipt, not necessarily agreement]
Running the check-ins
A PIP with no real check-ins during the period is just a document that gets revisited once, at the end, to decide pass or fail. Weekly or biweekly check-ins during the plan give the employee genuine feedback on where they stand — not a surprise at the end — and give the manager an honest, ongoing record of what's actually happening, not a reconstruction after the fact.
Each check-in is worth a short written note: what's been observed since the last one, whether it's trending toward the goal, and what (if anything) needs to adjust. This is also where a PIP that was set up with an unrealistic timeline or an unmeasurable goal becomes obvious early enough to fix, rather than discovered only at the final review.
When a PIP is the wrong tool
Not every performance issue calls for a PIP. Serious misconduct — safety violations, harassment, dishonesty — generally doesn't belong on an improvement timeline; it calls for immediate action through your standard discipline or termination process instead. A PIP is built for genuine, correctable performance gaps: missed targets, quality issues, inconsistent output — not for conduct that shouldn't be tolerated while a 60-day clock runs.
It's also the wrong tool when the real issue is a mismatch between the role and the person's actual skills, rather than an effort or execution problem. A PIP built around "become dramatically better at a core skill you've shown limited aptitude for in eight months" rarely produces a genuine turnaround — that's often a hiring or role-fit conversation, not a performance-plan one.
The honest tension, named directly
Employees who've seen PIPs used purely as termination paperwork are often skeptical the moment one lands on their desk, even at a company using it in good faith. There's no wording trick that fully resolves this — the plan's substance is what signals intent, not its tone. A PIP with vague goals, no support offered, and an unrealistic timeline reads exactly like a formality regardless of how it's framed. A PIP with specific, achievable goals, real support, and a genuine review at the end reads as what it claims to be — and holds up far better either way it concludes.
Documenting the outcome either way
Whichever way a PIP concludes, the outcome deserves its own short, specific documentation — not just an implicit understanding of what happened. If goals were met, a brief written confirmation closes the plan formally and gives the employee something concrete acknowledging the improvement, which matters for morale as much as for the record. If goals weren't met and the outcome is termination, the PIP's own documented check-ins become the core evidence for that decision, which is exactly why vague or skipped check-ins during the plan itself create real risk regardless of which direction the plan concludes.
Telling the difference between a skill gap and a fit problem
A PIP works best for a genuine, correctable execution gap — someone has the underlying capability but isn't yet meeting the bar consistently. It works far less well when the real issue is a mismatch between what the role requires and what the person is fundamentally suited for or interested in. Before writing a PIP, it's worth honestly asking whether the goals being set are things this person has shown they're capable of under different circumstances, or whether the plan is effectively asking them to become a different kind of employee than they are. The former is a fair use of a PIP; the latter usually isn't, and setting it up as one anyway tends to produce a plan that fails regardless of effort.
The short version
A performance improvement plan earns its name only when its goals are specific and measurable, its timeline is genuinely achievable, and it includes real support alongside its requirements. Written that way, it gives someone an actual chance to turn things around — and if that doesn't happen, it's also the clearest, most defensible record a business can have for what came next.
Frequently asked questions
What is a performance improvement plan?
A formal, time-boxed document — typically 30 to 90 days — that names specific performance gaps, sets measurable goals to close them, and states what happens if the goals aren't met. It sits between informal feedback and termination.
Do PIPs actually help employees improve?
Sometimes, but plenty are written after the decision to terminate has already effectively been made, purely to build a documentation trail. Employees often sense this, which undermines the plan's stated purpose from the start.
How long should a PIP last?
30 to 90 days is typical, scaled to how long the specific goals genuinely take to demonstrate. A 30-day plan for a goal that takes a full quarter to show results sets someone up to fail on a timeline that was never realistic.
What happens if someone doesn't improve during a PIP?
Termination is the most common outcome, and the PIP itself — with its specific goals and documented check-ins — becomes the core evidence supporting that decision. That's exactly why vague goals hurt the business as much as the employee if it comes to that.