What you'll learn
- What a PIP Is Actually For — and the Two Purposes That Pull Against Each Other
- Before the PIP: Why Surprise Is the Single Biggest Risk Factor
- Writing Success Criteria That Can Actually Be Evaluated
- Timeline, Support, and Check-Ins: What the Plan Actually Needs to Include
- Common Legal and Practical Mistakes
A performance improvement plan is one of the most consequential documents a manager writes, and most managers write their first one with no training and no template beyond whatever HR hands them. The result is predictable: vague success criteria nobody can objectively evaluate, a timeline that reads as designed to fail, and a document that — if the employee is later terminated and challenges it — does more to expose the company than protect it. A well-run PIP does two things at once: it gives an employee a genuine, supported opportunity to close a specific performance gap, and it creates a fair, consistent record if they don't. This guide covers what needs to happen before a PIP is ever issued, how to write success criteria that can actually be evaluated, what the plan needs to include beyond a list of demands, and the legal and practical mistakes that turn a PIP into a liability instead of a protection.
What a PIP Is Actually For — and the Two Purposes That Pull Against Each Other
Quick answer
A performance improvement plan serves two purposes simultaneously, and most of what goes wrong with PIPs comes from an organization or a manager quietly prioritizing one over the other without admitting it. The first purpose is genuine: give an underperforming employee a clear, structured, time-bound opportunity to close a specific gap, with real support and a real chance of success. The second purpose is protective: create a documented record that the company gave the employee fair notice and a fair opportunity before any termination decision, which matters enormously if that termination is later challenged.
These purposes are not inherently in conflict, but they pull against each other in practice. A manager who has already mentally decided to terminate someone writes a PIP designed to be unwinnable — vague standards, an unreasonably short timeline, success criteria that shift once the employee starts hitting the original ones. That PIP still creates a paper trail, but it's a bad one: a plaintiff's attorney can identify a pretextual PIP fairly easily by looking at whether the standards were achievable and whether the company genuinely engaged with the employee's progress, and a plan that was designed to fail generally looks designed to fail under scrutiny.
The organizations that get real value out of PIPs are the ones that commit fully to the genuine-opportunity purpose, on the theory that a well-run, honest PIP process serves the protective purpose better as a byproduct than a plan explicitly engineered around litigation risk ever could. If the employee improves, the company keeps a productive employee it would have otherwise lost, at a fraction of the cost of a new hire ramping up. If the employee doesn't improve despite a fair, well-supported process, the resulting termination is both more defensible and more clearly the right call, because everyone involved — including the employee — can see that the process was real.
Before the PIP: Why Surprise Is the Single Biggest Risk Factor
Quick answer
A PIP should never be the first time an employee hears that their performance is a serious concern. If it is, that's a management failure that predates the PIP, and it puts the plan on shaky ground from day one — both because the employee is often too blindsided to engage productively, and because a paper trail showing no prior feedback on the specific issue undermines the company's position if the PIP leads to termination and gets challenged. Regular one-on-ones and mid-cycle check-ins should surface performance concerns as they happen, with informal verbal feedback first, then a documented written warning or coaching conversation if the pattern continues.
The transition point — when a manager moves from ongoing coaching to a formal PIP — should be a deliberate decision, typically made in consultation with HR, not something a manager does unilaterally the first time they're frustrated. The threshold is usually: has this specific issue been raised directly with the employee at least once already, has the employee had a reasonable window to respond, and has the gap persisted or worsened despite that. A PIP issued after a single missed deadline, with no prior conversation about a pattern, reads as reactive and disproportionate, and employees who receive one under those circumstances often disengage rather than genuinely try to improve.
HR should review every PIP before it's delivered, not after. This isn't bureaucratic gatekeeping — it's the point where an inconsistent standard, a legally risky phrase, or an unreasonably compressed timeline gets caught before it becomes a document the company has to defend. Managers writing their first PIP without a review step reliably make the same mistakes: vague success criteria, timelines that don't match the complexity of the gap, and a tone that reads as adversarial rather than genuinely supportive.
A PIP that shows up as a surprise is already a failed PIP — if the specific performance gap wasn't raised clearly at least once before the plan lands, the document reads less like a genuine improvement path and more like the first page of a termination file, which is exactly how it will be read in a wrongful termination claim.
Writing Success Criteria That Can Actually Be Evaluated
Quick answer
The single most common PIP failure is success criteria that can't be objectively evaluated at the end of the plan. 'Improve communication with stakeholders' or 'demonstrate stronger ownership' sound like reasonable goals, but they give the manager, the employee, and HR no shared basis for agreeing, 30 or 60 days later, whether the standard was met. Every success criterion needs a specific, observable behavior or output tied to it: not 'improve communication' but 'send a written status update to the project stakeholder group every Friday, and respond to direct messages from the manager within one business day.'
Where possible, anchor criteria to existing performance data rather than inventing a new standard specifically for the PIP. If the underlying issue is missed deadlines, use the team's actual deadline-tracking data — 'complete at least 90% of assigned tickets within their committed due date over the next 45 days' — rather than a subjective standard that different observers might read differently. Objective, data-anchored criteria protect the employee as much as the company: they can track their own progress against the same numbers the manager is using, rather than wondering whether they're meeting a moving target.
Limit the plan to two or three core issues, ranked by severity. A PIP that tries to address every minor gap simultaneously — communication, technical quality, meeting attendance, proactivity — overwhelms the employee and dilutes focus on the issue that actually matters most. If there are genuinely many separate problems, that's often a signal the role or the fit itself needs to be reconsidered rather than addressed through a single improvement plan; a PIP works best when it's solving one or two specific, well-defined gaps, not serving as a catch-all for general dissatisfaction with the employee.
Timeline, Support, and Check-Ins: What the Plan Actually Needs to Include
Quick answer
Standard PIP timelines run 30, 60, or 90 days depending on the complexity of the gap and the seniority of the role — a 30-day plan is reasonable for a discrete, measurable behavior change, while a 90-day plan makes sense for a more complex skill gap that takes longer to demonstrably close. Whatever the length, build in scheduled check-ins at regular intervals within the plan, not just a single conversation at the end. Weekly or biweekly check-ins give the employee real-time feedback on whether they're tracking toward the standard, and they give the manager an opportunity to adjust support if something isn't working, rather than discovering failure only at the final review.
Specify the support the company is providing, not just the standard the employee needs to hit. This might include additional training, a temporarily reduced workload to focus on the specific gap, pairing with a mentor, or more frequent manager availability for questions. A PIP that lists demands without any corresponding support reads — and often functions — as a formality on the way to termination rather than a genuine improvement opportunity, and employees can tell the difference immediately.
State clearly, in writing, what happens at the end of the plan depending on the outcome: successful completion typically means the employee returns to standard performance management with no further PIP-specific tracking; partial progress may result in an extension, at the company's discretion, with revised criteria; failure to meet the standard typically results in termination. Employees should not have to guess what's actually at stake, and ambiguity here tends to produce more anxiety and less productive focus on the actual improvement work.
Related reading
Common Legal and Practical Mistakes
Quick answer
Inconsistent application across similarly situated employees is the most common source of legal exposure in PIP processes. If one employee with a documented performance gap gets a 60-day PIP with weekly coaching support, and another employee with a comparable gap gets a 15-day PIP with no support and an unstated expectation of failure, that inconsistency is exactly what a discrimination claim looks for — particularly if the two employees differ by a protected characteristic. Track PIP issuance, timelines, and outcomes across the organization the same way you'd track any other people-process metric, specifically to catch this pattern before it becomes a claim.
Changing the goalposts mid-plan is the second major failure. If an employee is tracking well against the original success criteria and the manager introduces new or revised standards partway through, that's a strong signal — to the employee, and later to a court or arbitrator, if it comes to that — that the real goal was never a fair evaluation against a fixed standard. If circumstances genuinely require adjusting criteria, document why explicitly and communicate it directly to the employee in writing, rather than letting the standard drift informally.
Terminating immediately upon PIP completion, even when the employee has genuinely met the criteria, on the theory that 'we'd already decided to let them go anyway,' is both an ethical failure and a legal one. If the documentation shows the employee met the stated standard and was terminated regardless, that undermines the credibility of every PIP the company issues afterward, and it exposes the specific termination to a much stronger challenge, since the company's own documentation contradicts its stated reason for the decision.
Most PIPs fail not because the employee couldn't improve, but because the manager never defined what 'improved' actually looks like in measurable terms — vague language like 'improve communication' gives everyone, including the manager, no way to agree at the 30-day mark whether the standard was actually met.
Frequently asked questions
Common questions about hr strategy and how InCruiter helps teams solve them.
InCruiter Editorial Team
AI Hiring Research · Interview Intelligence · Enterprise Talent Strategy
The InCruiter editorial team covers AI-driven hiring, interview intelligence, and modern talent acquisition strategy. Our guides draw on platform data from 2,000+ hiring teams, conversations with talent leaders, and published research in industrial-organizational psychology.
