How to Write a Performance Improvement Plan: Step-by-Step with Examples

A performance improvement plan written correctly is a structured support mechanism. Written incorrectly, it is a legal liability. The difference is almost always in the specificity of the language and the completeness of the documentation at every stage.

This guide walks through the five components every PIP must include, explains the most common writing mistakes that create legal vulnerabilities, and provides a blank template you can adapt for any role or performance gap.

Practitioner Insight: A frequent mistake is writing the expected standard after the fact, after the manager has already decided the employee is not meeting it. The expected standard section must be written at the start of the PIP, specific enough that both parties agree on it before the process begins. If the standard can only be defined in retrospect, it is not specific enough.

What a Performance Improvement Plan Must Include

A complete performance improvement plan has five core components. Missing any one of them does not just weaken the document—it creates a specific legal vulnerability.

Performance gap description

Name the specific behaviors or outcomes that are not meeting expectations, with concrete examples, dates, and observable evidence. This is not a general statement about attitude or effort; it is a documented account of specific, verifiable events.

Expected standard

Defines what meeting expectations looks like in this role, written specifically enough that both parties would agree on whether it has been achieved. The most common PIP writing failure is a standard vague enough to be interpreted differently by the manager and the employee.

Support structure

Documents what coaching sessions are scheduled, what training resources are being provided, who the employee can contact for support, and what access to tools or expertise is being provided. This section carries legal weight—if support documented here was not provided, an employee has a credible challenge.

Milestone review dates

Sets specific review points with defined criteria for what will be assessed at each one. Milestone criteria should depend on observable outcomes, not the manager's general impression.

Consequences

States clearly and specifically what happens if improvement is not demonstrated by the final review date. Vague consequences ("further action may be taken") undermine the enforceability of the entire plan.

Step 1: Define the Performance Gap Specifically

The most common PIP writing mistake is describing the performance gap in general terms. "Communication issues" is not a performance gap.

Weak version: Communication issues.

Strong version: In three separate project handoffs between June and August, deliverables were transferred to the receiving team without the supporting documentation required by the handoff protocol, resulting in rework delays averaging four days per incident.

For each performance gap, include: the specific behavior or outcome, the date or date range when it occurred, the measurable impact on the team or business, and any prior feedback given about this issue before the PIP was initiated.

That last point is critical. A PIP that appears without any prior documented feedback creates the impression that the employee was not warned, which is both legally problematic and usually factually incorrect.

Step 2: Write the Expected Standard

The expected standard answers the question "what does success look like?" in terms specific enough that both parties would agree on the answer without debate.

Weak standard: Improve communication with the team.

Strong standard: Complete all project handoff documentation using the approved handoff template before transferring work to a receiving team, with no missing fields. The receiving team lead confirms receipt and completeness in writing within 24 hours of each handoff.

The strong version is accessible. The weak version is not. At each milestone review, you are asking: Was this standard met? You need a standard that produces a yes or no answer, not a debate about interpretation.

Step 3: Document the Support Structure

This section is often written as a formality. It should not be. Document specifically: what coaching sessions are scheduled and how frequently, what training resources or courses are being provided, who the employee should contact for support, and what access to tools or information is being provided.

An employee who can demonstrate that the support documented in the PIP was not actually provided has a credible challenge to the outcome decision. A manager who can show that every documented support commitment was fulfilled is in a significantly stronger legal and ethical position.

PIP Template You Can Adapt Immediately

Copy and replace the bracketed sections with your specific content. Every field is required.

EMPLOYEE:  [Full name, role, department]

PIP INITIATION DATE:  [Date]

PIP REVIEW PERIOD:  [Start date to end date]

PERFORMANCE GAP:  [Specific description with dates, observable examples, and measurable impact. Reference any prior feedback given before the PIP was initiated.]

EXPECTED STANDARD:  [Specific, measurable definition of what meeting expectations looks like for each performance gap area documented above.]

SUPPORT PROVIDED:  [Coaching sessions scheduled and frequency. Training resources provided. Key contacts for support.]

MILESTONES:  [Date 1: What will be assessed and how. Date 2: What will be assessed and how. Final review date: Full assessment criteria.]

CONSEQUENCES:  [Clear statement of what happens if improvement is not demonstrated by the final review date.]

ACKNOWLEDGMENT:  [Employee signature and date. Manager signature and date. HR witness signature and date.]