Performance Improvement Plan (PIP): What It Is, How to Write One, and How to Make It Work

A performance improvement plan (PIP) is a formal document that defines a specific performance gap, sets measurable goals for closing it, and establishes a structured timeline — typically 30 to 90 days — with defined manager support and consequences if targets are not met. PIPs apply to employees whose output or behavior has fallen below a documented standard.

What Is a Performance Improvement Plan (PIP) and When Should You Use One?

A PIP is not a firing notice drafted in HR language. It is a formal performance contract between a manager and an employee — one that commits both parties to a defined outcome over a defined period. When written correctly, a PIP protects the organization legally, gives the employee a fair shot at recovery, and creates a paper trail that either validates success or supports a final decision.

The problem is that most PIPs are issued too late, written too vaguely, or treated as a formality before an exit. That is how the tool earned its reputation as a termination precursor rather than a development mechanism.

Use a PIP when an employee’s performance gap is:

• Specific and documented — the gap can be named with examples, not summarized with impressions
• Persistent — informal feedback has already been given and has not produced change
• Measurable — progress can be tracked over the PIP period, not just judged at the end
• Recoverable — the employee has the capability to meet the standard; the gap is performance, not fit

If all four conditions are true, a PIP is the right tool. If the performance gap is a values or culture mismatch rather than a skills or output issue, a PIP is the wrong document — and applying it creates legal exposure rather than reducing it.

HR teams that connect PIPs to continuous performance management software with real-time goal tracking reduce the risk of issuing a PIP that fails on legal review — because every step is logged and visible.

What Should a PIP Performance Improvement Plan Template Include?

A PIP template that fails to produce results typically omits one of three things: specificity in the goal, structure in the timeline, or clarity in the consequences. Most templates found online cover the first field and skip the other two.

A complete PIP performance improvement plan template contains six sections:

How Do You Choose Between a PIP and Informal Coaching?

One of the most common errors HR teams make is applying a formal PIP when informal coaching was the correct first step. The reverse error — continuing informal coaching when a PIP was warranted — is equally costly, particularly when a legal challenge follows.

The decision point is this: if informal feedback has been given, documented, and the gap persists, move to a formal PIP. If no documented feedback exists yet, informal coaching is both the ethical and legally safer first move.

Organizations using performance management platforms that log check-in notes, feedback exchanges, and goal progress never have to reconstruct this history from memory — the record is already built.

Why Do Most Performance Improvement Plans Fail?

PIPs fail at a high rate — not because the employee cannot improve, but because the plan itself creates the conditions for failure. Three structural problems account for the majority of PIP breakdowns.

Problem 1: Goals Are Disconnected from Real Work

When PIP goals exist in a separate document from the employee’s actual role objectives, the employee cannot see how hitting the PIP target connects to their job. This is not a motivation problem — it is a systems design problem. Goals that are not anchored to the employee’s OKRs or project assignments feel arbitrary, which erodes buy-in within the first two weeks.

The fix: PIP goals should map directly to the employee’s existing OKRs. If a salesperson is on a PIP for missing pipeline targets, the PIP goal should be expressed in the same units as their sales OKRs — not invented in HR language that no one on the sales floor uses.

Problem 2: Check-Ins Are Scheduled but Never Happen

The structured check-in is the most important feature of any PIP — and the one most frequently skipped. When managers get busy, the biweekly one-on-one moves to the bottom of the calendar. By week six of a 90-day PIP, many employees have had one documented conversation. A PIP without executed check-ins is legally fragile and practically useless.

The fix: check-ins should be calendar-locked, agenda-driven, and output-documented. The meeting notes, not just the meeting, are the evidence trail.

Problem 3: Progress Is Assessed Subjectively at the End

Many PIPs define goals but not measurement methods. The manager reviews the employee at day 60 or day 90 and relies on an overall impression rather than tracked data points. This creates two risks: the impression may be wrong, and it is nearly indefensible if the employee challenges the outcome.

The fix: define how progress will be measured at the time the PIP is written. For a sales PIP, that is pipeline activity tracked weekly in the CRM. For a project management PIP, it is on-time delivery per sprint. For a communication PIP, it is attendance and completion of structured feedback sessions.

The underlying pattern across all three failures is the same: PIPs fail when they are treated as HR documents rather than performance systems. A PIP that integrates with live goal data, logged check-ins, and automated progress tracking operates as a real performance mechanism — not a paper trail assembled after the fact.

How Do OKRs Strengthen a Performance Improvement Plan?

The traditional PIP and the OKR framework appear to serve opposite purposes — one is corrective, one is developmental. In practice, they are structurally identical. Both define a goal, set a timeline, and measure progress at regular intervals. The difference is intent, not mechanics.

Organizations that run OKRs already have the infrastructure to run better PIPs:

This is not theoretical. When performance goals, project deliverables, and check-in history exist in the same platform, the PIP is not a separate process — it is a mode within the normal management rhythm. That integration is what separates organizations that recover employees on PIPs from those that lose them.

For a deeper look at how goal frameworks connect individual performance to strategy, the OKR University covers cascading and alignment models in full. For role-specific examples of measurable key results that can be adapted for PIP goal-writing, see OKR examples by department. Teams building the business case for connecting PIPs to OKR software can also use the OKR ROI Calculator.

How Long Should a Performance Improvement Plan Last?

PIP duration should match the complexity of the performance gap — not a fixed HR policy number. The most common durations are 30, 60, and 90 days, and each applies to a different type of gap.

• 30-day PIP — appropriate for a single, isolated behavioral gap that can be observed and corrected quickly. Most appropriate for process compliance issues: late reporting, missed deadlines in a high-frequency task environment, attendance policy violations.
• 60-day PIP — the most common duration. Appropriate for output or skill gaps that require multiple cycles of feedback and iteration to observe genuine change.
• 90-day PIP — appropriate for complex performance gaps in high-complexity roles where the output cycle is longer than two weeks. Applying a 30-day PIP to a role where significant deliverables take six to eight weeks to produce creates a structurally unfair evaluation.

Regardless of duration, the check-in cadence should be weekly in the first half of the PIP and biweekly in the second half once a clear trend is established. An employee who shows consistent improvement at week 4 of a 90-day PIP should receive that signal explicitly — not wait until day 90 to learn they are on track.

PIPs that incorporate weekly check-ins rather than a single endpoint review operate differently at a structural level — the employee receives real-time signals about whether they are on track, rather than learning their outcome on the final day. That signal closes the feedback loop that most PIPs leave open.

For a full view of how check-in cadences work within a continuous feedback model, see the guide on OKR check-in best practices.

Why Are Most PIPs Written for Legal Protection Rather Than Performance Recovery?

Here is a belief most HR teams hold privately but rarely say out loud: the PIP exists to document the path to termination, not to recover performance. That assumption shapes how PIPs are written, how they are communicated, and how managers engage with the process.

When a PIP is written as a termination precursor, the goals are deliberately vague — vague enough to fail. The check-ins happen on paper but not in practice. The outcome is predetermined before day one.

This approach is not just ethically problematic — it is increasingly legally vulnerable. Employment tribunals in multiple jurisdictions now scrutinize whether PIP goals were genuinely achievable and whether the required support was actually provided. A PIP with three vague goals and no documented check-ins looks exactly like what it is.

The organizations that run effective PIPs treat them as a last-opportunity coaching engagement — not as a six-week countdown. They connect the PIP goals to real role objectives, log every check-in, track progress with the same tools used for OKRs, and give the employee a fair chance at hitting the mark. This approach recovers a higher percentage of employees and protects the organization in every outcome scenario.

For organizations building a scalable performance review and continuous feedback system, the PIP is simply the most intensive expression of a process that should already be running quarterly for every employee.