What Is a Performance Improvement Plan?
A performance improvement plan is a structured, time-bound document that names specific performance gaps, sets measurable targets, and commits the company to support. Done well, it is a recovery tool. Done badly, it is paperwork before an exit. This guide covers how to do it well.
Few documents in management carry as much weight as a performance improvement plan. For the employee, it is often the first formal signal that their job is at risk. For the manager, it is a test of whether a performance problem was ever described clearly enough to fix. A good PIP does three things at once: it defines the gap in specific, observable terms, it sets measurable targets with a realistic timeline, and it commits the company to concrete support. This guide explains when a PIP is the right tool, how to write one that can actually be passed, how to run the check-ins, and how to keep the whole process fair and defensible.
What a performance improvement plan is
A performance improvement plan, usually shortened to PIP, is a formal written document that describes a specific gap between an employee's current performance and the standard their role requires, then lays out exactly what improvement looks like, by when, and with what help. It typically runs 30, 60, or 90 days and ends with a documented outcome: the plan is passed, extended, or the employment relationship ends.
The word formal matters. A PIP is different from routine coaching or an offhand comment in a one-on-one. It is written down, signed by both sides, and kept on file, which is why it tends to arrive only after informal feedback has not produced a change. If the first time an employee hears about a problem is inside a PIP, the process upstream of the document has already failed.
A PIP is also different from a disciplinary warning. A warning looks backward at conduct: a policy was broken, and here is the consequence. A PIP looks forward at performance: output, quality, or reliability is below standard, and here is the path back. Keeping those two instruments separate keeps expectations clear on both sides of the table.
When a PIP is the right tool
A PIP fits a specific situation: a capable employee whose performance has genuinely slipped below standard, where the gap is describable in observable terms and the company honestly wants recovery rather than a paper trail. Missed delivery targets over a sustained period, a measurable decline in output quality, or unreliable follow-through on commitments are the classic triggers.
It is the wrong tool for several situations that get forced into it anyway. A conduct problem such as harassment belongs in a disciplinary process, not a PIP. A role that has outgrown the person, or a person hired into the wrong role, is a job-fit conversation. And a performance dip with an obvious external cause, such as a health event or a doubled workload after a departure, deserves support first and evaluation later.
The honest test before starting one is simple: if this person hit every target in the plan, would you genuinely want to keep them? If the answer is no, a PIP is theater, and both sides usually sense it. Managers who use the document as a legal formality before a predetermined exit corrode trust in the process for everyone who watches it happen.
How to write a performance improvement plan
Start with the gap, described in evidence rather than adjectives. Not attitude problems or lack of ownership, but observable facts: four of the last six weekly deliverables were late, ticket resolution time has been double the team median for two consecutive months, or error rates on processed claims exceeded the standard in each of the last eight weeks. Every claim in the document should be something both parties can verify.
Then define success in measurable targets, one per gap. Each target needs a number or an unambiguous condition, a deadline, and a source of truth for how it will be measured. Resolve tickets within the team's 24-hour standard for six consecutive weeks is a target someone can pass. Show more commitment is not, because nobody can prove it happened.
Finally, write down the support the company commits to: training, a reduced queue while skills rebuild, weekly coaching sessions, or clearer specifications for incoming work. This section is what separates an improvement plan from an ultimatum, and its absence is the most common reason PIPs feel like, and legally resemble, constructive dismissal. A plan with obligations on only one side is not a plan.
Progress Against Plan
Weekly target progress
Support delivered
▲ Four of five improvement targets trending to pass by week five, with all check-ins documented.
Illustrative eMonitor dashboard.
Running the plan: check-ins and honest tracking
A PIP without scheduled check-ins is a countdown timer, not a plan. Weekly or biweekly meetings should review progress against each target using the agreed source of truth, note what improved, and adjust support where it is not working. Each check-in gets a short written summary that both people see, so the final decision rests on a record rather than a memory.
The manager's job during the plan is to remove ambiguity. If a target is being missed, say so at the next check-in rather than at the end. If a target turns out to be badly designed, fix the target and note why. Employees fail recoverable PIPs most often not because they cannot do the work but because they discover at day 60 what they should have heard at day 14.
Momentum matters more than perfection. An employee who moves from missing most targets to hitting most of them is demonstrating exactly the trajectory the document asked for, and the review should weigh that direction honestly. Treating a single stumble in week five as decisive, after four weeks of improvement, tells the team the plan was never real.
Grounding a PIP in objective data
The weakest PIPs rest on impressions, and impressions are exactly what a stressed employee will dispute. Objective work data changes the footing of the whole process. Activity and time records from a monitoring platform can show, neutrally, whether focus hours collapsed, whether workload actually doubled, or whether output genuinely trails the team's range, before anyone drafts a document.
That evidence protects both sides. It protects the employee whose apparent slump turns out to be a workload spike or a queue full of mis-scoped work, a discovery that should end the PIP conversation and start a workload balancing one. And it protects the company, because a plan grounded in verifiable records is far more defensible than one grounded in a manager's recollection, a point our guide to monitoring data in performance reviews covers in detail.
The discipline is to use the data as a measuring instrument, not a weapon. Share the same reports with the employee that the manager sees, measure only work-relevant patterns during work hours, and pair every number with context from conversation. Data answers what changed; only the person can answer why, and a fair process asks both questions in that order.
Make performance conversations factual
eMonitor gives managers and employees the same neutral record of hours, focus, and workload, so improvement plans start from shared facts instead of contested impressions.
How PIPs end: success, extension, or exit
A passed PIP should end loudly, not quietly. Close it in writing, say plainly that the standard has been met, and stop treating the person as provisional. The most common post-PIP failure is a manager who keeps the employee mentally on probation for a year, which guarantees the recovery never sticks and the person eventually leaves anyway.
An extension is legitimate when progress is real but incomplete, especially if support arrived late or a target proved unrealistic. It should come with the same specificity as the original plan: what remains, how long, and what changes. Serial extensions with no trajectory, though, are usually an exit decision being deferred, and they are harder on the employee than honesty would be.
When the plan is not met, the documented record makes the exit conversation clear rather than cruel: the gap was named, the targets were explicit, the support was delivered, and the standard was still not reached. Companies that run PIPs this way find the process is respected even by people who did not pass it, because everyone could see the same facts.
Best practices
Rules that keep a performance improvement plan fair and passable:
- Never surprise anyone: a PIP should formalize feedback already given, not deliver it for the first time.
- One measurable target per gap: if success cannot be verified, the target is not finished.
- Set a realistic window: 30 days suits narrow gaps; skill rebuilds need 60 to 90.
- Write the support down: training, coaching, and workload changes are the company's side of the contract.
- Hold every check-in: a skipped review tells the employee the plan is theater.
- Use a shared source of truth: both sides should see the same numbers throughout.
- Check for external causes first: workload spikes and health events are not performance gaps.
- Close passed plans in writing: and genuinely end the probation, or the recovery will not hold.
The pattern behind every rule is symmetry. The employee owes measurable improvement; the company owes clarity, support, and an honest reading of the results. PIPs earn a grim reputation in workplaces where only one side of that contract is enforced.
Run with symmetry, the same document becomes something rarer: proof to the whole team that a rough patch is survivable, that standards are real, and that the process for enforcing them is one they could stand inside without fear.
How eMonitor supports fair improvement plans
eMonitor gives a PIP the neutral measuring instrument it needs. Managers see hours, focus time, application usage, and workload trends over the exact plan period, so targets like restore consistent delivery or rebalance time toward core work can be verified against records rather than recollection. The same dashboards reveal when the real problem was a doubled queue, which is a finding that should end a PIP, not extend one.
Because reports can be shared, the employee watches the same evidence the manager sees, week by week, which removes the ambush quality that makes improvement plans corrosive. Work-hours-only tracking and role-based access keep the measurement proportionate. Trusted by 1,000+ companies worldwide and rated 4.8/5 on Capterra, eMonitor costs $3.90 to $13.90 per user with a 7-day free trial.
If a performance conversation is approaching in your team, start measuring first. Two weeks of objective baseline data makes every later step fairer: the gap is real or it is not, and everyone can see which. Start a free trial and give your next difficult conversation a foundation of shared facts.