How to Write a Performance Improvement Plan That Works

You’re usually not reading about how to write a performance improvement plan on a calm day.

More often, a manager has already tried coaching. Deadlines are slipping. Teammates are frustrated. The employee may be anxious, defensive, or confused about how serious the situation has become. HR is trying to balance two obligations that can pull in opposite directions. Give the employee a fair chance to recover, and protect the organization with a process that is objective, consistent, and defensible.

That’s why a good PIP can’t be a generic template with vague promises to “improve communication” or “show more ownership.” A useful plan names the problem, ties it to the role, sets measurable expectations, documents support, and creates a review process that both manager and employee must follow.

The strongest plans also deal with something most PIP advice skips. Not every performance problem is purely task-based. Sometimes the missed targets are downstream of a skill gap. Sometimes they reflect a motivation problem. Sometimes the employee is working against the team’s norms, values, or acceptable behaviors in ways that keep showing up as friction, missed handoffs, and avoidable conflict. If you don’t diagnose that accurately, you’ll write the wrong plan.

The Diagnostic Phase Before You Write

A PIP should never be your first reaction. It should be the point where you’ve already observed a pattern, tried normal performance management, and decided the issue needs a formal, documented intervention.

That diagnostic work matters for both fairness and risk. Historically, PIPs became formalized after the U.S. Civil Rights Act of 1964 to mitigate bias claims, and properly documented 30/60/90-day reviews can lead to 85% fewer disputes, according to EEOC data summarized in the Arkansas State PIP guidance.

Separate symptoms from causes

Managers often describe symptoms, not causes. “She’s disengaged.” “He’s not collaborative.” “They’re dropping the ball.” None of those phrases belongs in a draft PIP until you’ve translated them into observed facts.

Most performance issues fall into one of three buckets:

• Skill gap: The employee doesn’t currently know how to perform part of the role to standard.

• Will gap: The employee can do the work but isn’t applying consistent effort, judgment, or follow-through.

• Cultural or behavioral misalignment: The employee’s approach clashes with expected behaviors, team norms, or stated values, and that clash is affecting work outcomes.

This distinction changes the remedy. A skill gap may call for training, shadowing, and narrower milestones. A will gap may require tighter accountability and clearer consequences. A culture or behavior issue needs observable conduct standards, not personality labels.

Practical rule: If you can’t explain the issue without using adjectives about attitude or character, you probably haven’t diagnosed it well enough yet.

Gather evidence you could defend in a file

The foundation of a fair PIP is dated, specific, job-related evidence. Think project logs, attendance records, quality reviews, customer complaints, error reports, missed deliverables, and documented feedback discussions.

Use evidence that answers four questions:

1. What happened

1. When it happened

1. What standard applied

1. What impact it had

A weak note says, “Needs to be more reliable.”

A defensible note says, “Missed three scheduled client update deadlines in April, despite reminder check-ins, which delayed the account team’s weekly reporting.”

That’s the level of detail you want before you write anything formal.

Use structured inputs, not memory

Managers routinely over-rely on recent events, the most frustrating incident, or their gut sense of someone’s fit. That’s where bias creeps in.

A better diagnostic file pulls from multiple inputs:

• Performance records: Deadlines, quality defects, productivity logs, service metrics.

• Manager notes: Prior coaching conversations, examples, support already offered.

• Peer or stakeholder patterns: Only if they’re documented in observable terms.

• Employee perspective: Ask what barriers they see before you conclude what the issue is.

• Engagement and feedback signals: If the issue may involve confusion, trust, or alignment, targeted listening helps. Well-designed employee engagement survey questions can surface whether unclear expectations, manager support, or team friction are contributing to the decline.

When the problem may be capability-related, a structured skills gap analysis template can help you separate “won’t do” from “can’t yet do” before escalating to a formal plan.

Know when a PIP is the wrong tool

Not every problem belongs in a PIP.

Use another route first if the issue is mainly:

• a one-off mistake

• unresolved job design problems

• unclear role expectations

• a manager who hasn’t given regular feedback

• misconduct that should be handled through disciplinary policy, not performance coaching

• a health or personal situation that may require an accommodation process rather than a performance document

A PIP is appropriate when there is sustained underperformance, the expected standard is clear, the employee has had prior notice, and you still believe improvement is possible with formal structure.

Gather facts before conclusions. Once a PIP starts, every sentence in it will be read as both a management tool and a legal record.

How to Construct an Effective PIP Document

Once the diagnosis is solid, the document itself should feel plain, direct, and hard to misunderstand. Employees shouldn’t have to decode HR language to figure out what they need to do on Monday morning.

The common failure point is ambiguity. A rigorous PIP methodology starts with measurable examples, a 30 to 90 day timeframe, and SMART goals. It also works better when the employee is involved in goal-setting. Gallup data cited in this Primalogik guide to performance improvement plans shows that involving employees in goal-setting boosts engagement for goal achievement by 3.6 times, while vague goals are a leading cause of the 70% failure rate for unstructured PIPs.

Start with the performance discrepancy

The opening section of the PIP should do one job. State what isn’t meeting expectations, tied directly to the role.

Include:

• the required standard

• the observed gap

• a short statement of business or team impact

For example:

This section should read like a factual summary, not a character assessment.

Build the goals around SMART language

This is the core of the document. If the goals aren’t specific and measurable, the rest of the plan won’t hold.

Use SMART in the strict sense:

• Specific

• Measurable

• Achievable

• Relevant

• Time-bound

Compare these examples:

• Vague: Be more organized.

• Better: Submit all weekly reports by Friday at 5 PM for the duration of the plan, with no missing fields or calculation errors.

• Vague: Improve teamwork.

• Better: Attend scheduled cross-functional meetings prepared, complete assigned follow-ups by deadline, and confirm action owners in meeting notes within one business day.

• Vague: Show more ownership.

• Better: Escalate identified project risks to the manager within one business day and propose at least one mitigation step for each risk during the plan period.

A good test is simple. Could another manager review the goal later and reach the same conclusion about whether it was met? If not, rewrite it.

Document what the company will provide

A PIP shouldn’t read like all burden, no support. The employee is responsible for improvement, but the organization is responsible for providing the resources it says it will provide.

Support can include:

• Training: Refresher sessions, process instruction, product knowledge review.

• Coaching: Weekly manager meetings focused on planning, prioritization, or communication habits.

• Tools: Checklists, workflow systems, templates, or job aids.

• Clarification: Reconfirming role expectations, priorities, or decision rights.

This section matters because it proves the plan is constructive. It also disciplines the manager. If you promise training and never arrange it, you’ve weakened both the outcome and the record.

A PIP is stronger when it creates obligations for both sides. Employees improve performance. Managers provide the support, access, and feedback the plan promises.

Set timeline, check-ins, and consequences

The document should state the plan length, milestone dates, and how progress will be reviewed. Keep the cadence predictable. Employees shouldn’t have to wonder when they’ll hear whether they’re improving.

A strong structure includes:

1. Plan duration: State the start and end date.

1. Check-in rhythm: Weekly or bi-weekly meetings, already scheduled.

1. Evidence reviewed: What data, work samples, observations, or logs will be used.

1. Outcome language: What happens if expectations are met, partly met, or unmet.

Be careful with consequence language. It should be clear, not theatrical. “Failure to meet the expectations outlined in this plan may result in further corrective action, up to and including termination of employment” is standard because it’s transparent without becoming threatening.

If you want a starting structure, a performance improvement plan template library can help managers avoid blank-page drafting and keep core fields consistent across teams.

Include the basics people forget

The strongest PIP documents are usually boring in the right way. They include basic operational details that reduce confusion later.

Use this checklist:

• Employee details: Name, role, department, manager

• Plan dates: Start, milestone reviews, final review

• Performance areas: Specific categories under review

• Evidence summary: Concrete examples tied to dates

• Improvement expectations: SMART goals only

• Support commitments: Training, coaching, tools

• Documentation method: Notes, system reports, work review, attendance logs

• Sign-off section: Acknowledgment that the plan was reviewed, not necessarily agreed with

A PIP doesn’t have to sound warm to be humane. It has to sound clear.

Addressing Culture and Behavioral Gaps in a PIP

Some of the hardest PIPs involve problems managers describe as “not a fit,” “difficult to work with,” or “low emotional intelligence.” Those phrases are risky because they sound subjective, and usually are.

Still, behavioral issues are real. People can damage trust, ignore norms, create friction in meetings, resist collaboration, or repeatedly act against how the team is supposed to work. If that conduct affects outcomes, it belongs in performance management. It just has to be translated into observable behavior.

Stop writing personality judgments

The cleanest way to write a PIP for behavior is to ban yourself from personality labels.

Don’t write:

• resistant

• negative

• arrogant

• not team-oriented

• poor culture fit

Write what the person did, where it happened, and what standard it missed.

Examples:

• interrupted peers during team meetings and spoke over assigned presenters

• failed to share needed information before cross-functional handoffs

• dismissed agreed feedback channels and escalated concerns inappropriately

• did not follow documented norms for client communication

That shift is what makes the plan fairer and more defensible.

Translate values into observable standards

Many organizations have values, but very few turn them into behavior standards managers can use in a PIP. That gap matters. A 2023 Gallup study found only 23% of employees feel their values align with their company’s, correlating with 2.5x higher disengagement. The same AIHR article notes that a 2026 Deloitte survey reported 68% of firms using AI for PIPs saw 40% faster resolutions by quantifying soft issues with assessment data. Those figures are summarized in this AIHR discussion of PIP templates and values alignment.

Here’s the practical translation:

Use behavioral data when you have it

Structured assessment data can help. If your organization uses values, culture, or acceptable-behavior assessments, those results can guide diagnosis and goal design without turning the PIP into a personality test.

A manager might see a recurring mismatch between team expectations and employee behavior around feedback, conflict style, or collaboration norms. Used correctly, that data helps define what to coach and what to measure. Resources on behavioral assessment tests can help managers understand how to anchor soft-skill conversations in observed patterns rather than instinct.

Behavioral PIPs should measure conduct, not identity. You’re not trying to prove what kind of person someone is. You’re documenting what they need to do differently at work.

What works better than “culture fit”

“Culture fit” is too vague to stand on its own. In practice, what managers usually mean is one of three things:

• the employee isn’t following accepted team behaviors

• the employee’s work style is clashing with the role’s demands

• the employee is undermining values the company has chosen to operationalize

All three can be addressed. None should be written as a personal verdict.

A strong behavioral PIP keeps returning to this question: what would an outside reviewer need to see to confirm improvement happened? If you can answer that clearly, you can manage the issue without drifting into bias.

Implementing the Plan and Measuring Progress

The handoff from document to conversation is where many PIPs go off course. A plan can be well written and still fail if the delivery is rushed, defensive, or vague.

The first meeting should feel serious, but not punitive. The employee should leave understanding three things. What problem is being addressed, what improvement looks like, and what support they will receive during the plan.

What to say in the initial meeting

Managers often talk too much in the opening conversation. Keep it direct.

A useful script sounds like this:

We’re formalizing a performance improvement plan because the concerns we’ve discussed haven’t improved enough through regular coaching. This plan outlines the specific gaps, the expectations for improvement, the support we’ll provide, and the dates when we’ll review progress together.

Then pause and let the employee react. Expect emotion. Some employees will argue the facts. Some will go quiet. Some will ask whether this means they’re being fired. Don’t improvise around the seriousness of it.

Use follow-up language like:

• “This is a formal process, and it’s also a real opportunity to improve.”

• “I want to walk through the expectations carefully so there’s no confusion.”

• “If you see barriers to meeting these goals, this is the time to raise them.”

What the check-ins are actually for

Check-ins aren’t ceremonial. They are the working engine of the PIP.

HR Acuity analytics show that employees who meet at least 80% of measurable milestones within the first 30 days are 65% more likely to achieve full improvement, according to this HR Acuity analysis of PIP outcomes. That finding is one reason structured early milestones matter so much.

Each check-in should answer four questions:

Don’t let these meetings drift into general encouragement. Review evidence. Confirm what’s improved and what hasn’t.

Keep the record as if someone else will read it later

Because someone might. HR may review it. Senior leadership may review it. Legal counsel may review it. Another manager may inherit the employee.

That means documentation should be:

• Objective: Describe work and behavior, not motives.

• Current: Record notes right after the meeting.

• Balanced: Note improvement as clearly as you note failure.

• Consistent: Use the same standards throughout the plan.

A note like “Seems to care more now” isn’t useful. A note like “Submitted both assigned reports on time this week and requested clarification in advance on one data field” is useful.

For managers who need a more disciplined cadence around goals, feedback, and documentation, practical guidance on performance management best practices can help standardize follow-up habits.

Know the three likely endpoints

Most PIPs end in one of three ways.

Full improvement. The employee meets the required standard and returns to normal performance management.

Partial improvement. Some goals are met, but consistency or sustainability is still missing. In that case, decide whether a short extension is justified and document why.

Insufficient improvement. The employee doesn’t meet the required standard despite support and clear notice. That result should not come as a surprise if the check-ins were handled correctly.

The employee should never learn the outcome before they’ve heard the evidence behind it.

Common PIP Pitfalls and Legal Guardrails

A lot of managers assume PIPs fail because employees “don’t take them seriously.” That’s not the whole story. Many PIPs are poorly designed, inconsistently managed, or written so vaguely that no one could fairly judge success.

SHRM reports that global PIP success rates hover at 25% to 40%, with manager bias present in 60% of failures and 65% of PIPs failing because the goals were unmeasurable. The same analysis notes that mutual accountability, where managers are responsible for guidance as well as employees for improvement, can double retention odds. That data appears in SHRM’s piece on effective performance improvement plan steps and pitfalls.

The assumption to challenge

The common assumption is that a PIP is mainly an employee test.

It isn’t. It’s also a management test.

If the manager can’t define expectations, can’t document examples, skips check-ins, changes standards midstream, or withholds support, the process becomes unreliable fast. In practice, many failed PIPs are really failed management processes.

The quickest way to poison a PIP is to say it’s supportive, then manage it like a countdown.

The errors that create the most risk

Some mistakes are obvious. Others are subtle and more dangerous because they look normal inside a busy workplace.

• Using subjective language: Terms like “bad attitude” and “not a fit” invite argument unless you convert them into observable conduct.

• Overloading the plan: If you list every weakness the employee has shown over the last year, you dilute focus and make success unrealistic.

• Ignoring comparators: If one employee gets a formal PIP for conduct that others were only coached on informally, consistency becomes an issue.

• Treating sign-off as agreement: An employee’s signature usually confirms receipt, not endorsement. Make that clear.

• Skipping support: If the plan promises coaching or training and none is delivered, you’ve weakened the process.

The legal guardrails that matter most

PIPs are not legal shields by themselves. They help when the underlying process is fair, documented, and consistently applied.

That means:

1. Tie expectations to the job. Don’t invent standards on the fly.

1. Use evidence, not impressions. Dates, work product, logs, examples.

1. Apply process consistently. Similar issues should trigger similar responses.

1. Coordinate with policy and local law. Employment law varies by location, especially around notice, termination, and documentation.

1. Watch the overlap with protected issues. If medical, disability, leave, complaint, or retaliation issues may be in play, slow down and involve the right advisors.

For teams operating in Canada or managing exits there, it helps to understand what constitutes wrongful dismissal before treating a PIP outcome as a routine termination step. The legal concepts vary, but the practical lesson is universal. Process quality matters.

A better standard for fairness

A defensible PIP answers a simple question. If a neutral reviewer looked at the record, would they understand what the employee had to do, what support they received, how progress was measured, and why the final decision was made?

If the answer is yes, you likely ran a sound process. If the answer depends on manager interpretation, you probably didn’t.

Frequently Asked Questions About PIPs

The hardest parts of a PIP usually show up in the moments managers can’t script in advance. That’s why the practical questions matter so much.

A well-run PIP isn’t successful only when the employee stays. It’s successful when the process produces a fair, evidence-based resolution that everyone can understand afterward.

Common questions managers ask

The judgment call behind every plan

Managers often ask whether a PIP is “worth it” when the odds feel uncertain. That’s the wrong frame.

The better question is whether the employee has a realistic path to meeting the role’s expectations if you define the gap clearly, provide support, and measure progress accurately. If the answer is yes, a PIP is appropriate. If the answer is no, don’t use the document to delay a decision you’ve already made.

A strong PIP creates clarity. Sometimes that clarity leads to recovery. Sometimes it leads to separation. Either way, the value is in removing ambiguity, reducing bias, and giving the process enough structure to be fair.

If you want a more consistent way to diagnose performance issues before they become formal plans, MyCulture.ai offers assessment tools and a Manager Toolbox that can help HR teams and managers evaluate skills, behaviors, values alignment, and role expectations in a more structured way. That kind of data is especially useful when performance problems involve collaboration, work style, or culture-related friction that standard PIP templates often miss.