Performance Improvement Plan

A performance improvement plan is a written document that identifies specific performance gaps, defines the standard the employee needs to reach, sets a timeframe, describes the support the employer will provide, and states what happens if the standard is not met.

It is for performance: an employee who is trying and not delivering to the requirements of the role. Conduct problems such as policy violations, dishonesty, or misconduct run through a disciplinary process instead, because the response there is a consequence rather than a development period.

How it works

A PIP should never be the first conversation. By the time one is written, the employee should already have heard the same concerns directly, more than once, with examples. The plan formalizes what has been discussed and raises the stakes explicitly.

The document names the gaps in behavioral terms, states the required standard in measurable terms, and sets a period long enough for the change to be demonstrated. Thirty, sixty, and ninety days are the common durations. The right length depends on the work: if the role has a monthly cycle, thirty days shows almost nothing.

During the period the manager meets with the employee on a set schedule, usually weekly, and documents each check-in: what improved, what did not, and what was discussed. Those notes are the substance of the plan. A PIP with no check-in record is a document with a beginning and an end and nothing in the middle.

At the end there is an explicit decision, communicated to the employee: the standard was met and the plan closes, the plan is extended because progress is real but incomplete, or employment ends. Letting a PIP lapse without a decision is the worst outcome, because it tells the employee the standard was never real.

What a usable plan contains

The test for every element is whether a reasonable person outside the situation could tell from the document what success would look like.

• The specific performance gaps, described as observable facts with dated examples rather than as characterizations.
• The standard required, stated so that meeting it is verifiable: what output, at what quality, at what frequency.
• The duration and the end date, with scheduled check-in dates listed.
• What the employer will provide: training, mentoring, adjusted workload, tooling, or manager time.
• How progress will be measured, and by whom.
• A plain statement of the consequence if the standard is not met, including that it may result in termination where that is accurate.
• Space for the employee response, and a signature line acknowledging receipt rather than agreement.
• The date, the manager name, and the HR partner involved.

Running one

The sequence matters as much as the document.

1. 1Confirm the concern is performance rather than conduct, and that the expectations were actually communicated before now.
2. 2Check for causes the plan would not fix: an unclear role, a missing tool, an unaddressed accommodation request, a workload change, or a manager transition.
3. 3Draft the plan with specific gaps, a measurable standard, a realistic period, and the support the employer will supply. Have HR review it before delivery.
4. 4Deliver it in a live conversation. Explain the gaps, the standard, the timeline, and the consequence, and give the employee room to respond.
5. 5Give the employee a copy and ask for acknowledgment of receipt. If they decline to sign, note the refusal on the document and proceed.
6. 6Hold every scheduled check-in and write a short dated note after each: what was reviewed, what improved, what did not, what was agreed.
7. 7Respond to what emerges. If the employee raises a health condition, a need for accommodation, or a complaint about treatment, route it to HR before continuing.
8. 8Make the decision at the end date and communicate it clearly, whether that is closure, an extension with a defined reason, or separation.
9. 9File the plan, the check-in notes, and the outcome in the personnel record.

Where PIPs go wrong

Most of these are recognizable from either side of the table.

• Written after the decision to terminate has already been made, which produces a document that cannot survive scrutiny and an employee who spends the period job hunting.
• Vague standards. Improve communication and be more proactive cannot be met, cannot be measured, and cannot be defended.
• A period too short for the work cycle, so the employee never gets a fair opportunity to demonstrate the change.
• No check-ins. The plan is delivered, then nothing happens until the end date.
• Using a PIP for conduct, where the message should be that the behavior stops immediately rather than improves over ninety days.
• Ignoring what surfaces during the period. A disability, a leave entitlement, an accommodation request, or a retaliation complaint changes the analysis and must be handled before the plan continues.
• Inconsistency. If two people perform comparably and only one gets a plan, the difference needs a documented, job-related explanation.
• Manager avoidance. A manager who has never given direct feedback puts the whole plan on unstable ground, because the gap between the review file and the plan is visible.
• No closure. Plans that quietly expire teach every observer that the standard is negotiable.

Why it matters operationally

A PIP done well is one of the few interventions that can genuinely turn a struggling employee around, usually because it forces a specificity the manager had been avoiding. Employees often report that the plan was the first time they understood exactly what was expected.

Done badly, it is worse than doing nothing. It consumes months of manager time, signals to the team that the standard is theater, and creates a record that undermines the separation it was meant to support. The difference is almost entirely in whether the gaps were specific, the check-ins actually happened, and the decision at the end was made and communicated.