Performance Improvement Plan: An Employer's Guide

A performance improvement plan, usually shortened to a PIP, is a written document an employer issues when an employee's output falls below the standard for the role. It names the gap, the measurable standard, the period, the check-ins, and the support you'll provide. It has a second use almost nobody takes: it's the clearest advance notice you'll get that a seat may open, and the most accurate written description of what the role demands.

What is a performance improvement plan?

A performance improvement plan, or PIP, is a written document an employer issues when an employee's output falls below the standard for the role, naming the gap, the standard, the period, the check-in schedule, and the support provided. Three questions settle the rest: what the acronym means, what a PIP isn't, and who owns the document. It becomes a paperwork exercise before a decision already made only when you treat it as one.

What PIP stands for in HR

PIP stands for performance improvement plan. Both forms describe the same document, and your managers will say "PIP" whatever your policy calls it.

PIP means something else entirely outside HR, notably in finance and insurance. A founder hearing it for the first time often reads it as a termination notice with a delay built in. It isn't, and drafting it that way is what produces plans that fail review.

What a PIP is and isn't

A PIP addresses performance against a standard, not misconduct. EEOC guidance analyzes performance and conduct standards separately, and states that where a disability doesn't cause the misconduct, the employer may hold that person to the same conduct standards it applies to everyone else.

Some policies classify a PIP as a formal disciplinary step, which is a choice you should confirm before issuing anything. Take an employee who is repeatedly late and also missing quality targets. The lateness belongs in the conduct process and the targets belong in the plan, because one document means a dispute about one contaminates the other.

Who owns the plan

The manager owns the content and the check-ins, and HR owns consistency, the template, and the record. Counsel comes in when protected activity, an accommodation request, or employer-sponsored work authorization is in the picture.

EEOC's guidance on performance and conduct standards states that systems built on explicit expectations, clear standards, accurate measures, reliable feedback, and consistent application help reduce the chances of discriminatory ratings. Consistency is an organization-level property, which is why one manager can't produce it alone.

In a company with no HR function the founder holds both roles, and that's where the consistency check gets skipped. A VP of Engineering who plans one of two struggling engineers, with nobody asking how the other was handled, has created the exposure. The substitute for HR is a written comparison against the last comparable case.

When to use a performance improvement plan

Three conditions have to hold before you draft: the problem is performance rather than conduct, the gap is closable with time and support, and the role as written is still the role you want filled. This section covers that test, performance versus conduct, skill versus will versus fit, and how a plan weighs against opening a requisition in the 2026 market for that role.

The three-part test before you draft

The third condition is the one employers skip, and the one that connects the plan to the hiring decision. If the role has drifted and you'd write a different job description today, the plan is fixing a person against a spec you no longer believe in.

If any condition fails, you're in a different process: conduct discipline, role redesign, or a separation conversation with counsel involved. Consider an account executive missing quota in a territory rebuilt six months ago, where the quota was never reset. Fixing the spec comes first.

Performance problems versus conduct problems

Performance is output against a standard, and conduct is behavior against a rule. EEOC's guidance on performance and conduct standards treats them as separate analyses, stating that where a disability doesn't cause the misconduct, the employer may hold that person to the same conduct standards it applies to all other employees.

Some problems are genuinely both, and the answer is two documents on two tracks rather than one hybrid. Slow code review turnaround is performance. Twice ignoring a direct instruction about deployment process is conduct.

Skill, will, or fit

Diagnose which of the three is failing before choosing the instrument. A plan can close a skill gap, rarely closes a will gap, and never closes a fit gap.

The diagnosis drives the support column, since a skill gap needs training, pairing, or reduced scope. Writing training into the plan to be seen as fair makes the record less coherent rather than more.

Fit failures often look like skill failures because the employee is capable but in the wrong seat, and internal transfer belongs in this decision. A strong individual contributor promoted into management who misses every people-management standard has a fit problem with an internal answer.

The plan versus replace decision

Put the requisition on the other side of the ledger explicitly. The honest comparison is the plan's elapsed time and the manager hours it consumes, set against the real time to source, interview, and onboard a replacement into the same seat.

The choice isn't plan versus nothing. Both cost time, and what differs is what you hold at the end.

The comparison can't be made on numbers, because nothing defensible exists for what a replacement costs you or how long your search runs. A niche infrastructure role where the last search took months makes a plan look cheap, while a role with a deep local pool changes the arithmetic. Most employers making this call haven't looked at that market in a year.

Signals drawn from EEOC's guidance on performance and conduct standards, applied to the drafting decision.

The row you can't fill from inside the building is the state of the role, which depends on what the outside market holds.

How to write a performance improvement plan

Six components carry every plan, in order: the specific gap, the measurable standard, the period, the check-in schedule, the support you provide, and the range of outcomes.

The components every plan needs

EEOC's performance standards guidance states that performance systems built on explicit expectations, clear standards, accurate measures, reliable feedback, and consistent application help reduce the chances of discriminatory ratings. Each of those five maps onto a component.

The support column is the one most often left blank or filled with a generic offer of help. A plan that says "improve stakeholder communication" leaves nobody able to say on the end date whether it happened, which makes the decision either way look arbitrary.

Writing standards that can be measured

Every item converts to an observable output with a number, a frequency, or a named deliverable, plus a date. If you can't say on the end date whether it happened, it isn't a standard.

The conversion is harder for qualitative roles, and the answer isn't to write an adjective instead. Name the artifact: a design review attended and documented, a spec delivered by a date, a defect rate on shipped work. "Be more responsive" becomes "acknowledge inbound client requests within one business day, measured across the plan period."

What you can't do is lower the standard to make it reachable. EEOC states that an employee with a disability must meet the same production standards, whether quantitative or qualitative, as a non-disabled employee in the same job.

How long the plan should run

Length is your choice, with no legal minimum, and the work cycle should set it rather than calendar convention. The one duration figure with a citable source is EEOC's illustrative example, which describes a federal employee placed on a 60-day plan. That's an example inside guidance, not a default for a private employer.

If the standard can't be fairly measured inside the period, the period is wrong. A role whose output is one major deliverable per quarter can't be fairly assessed on a one-month plan, however convenient one month is for the calendar.

What the employer commits to

The plan names what you'll do: the check-in cadence, who runs them, what training or resources you provide, and by when. Missed check-ins are the most common way an employer damages its own record, because the document shows a commitment the calendar shows was never kept.

Hold the check-ins even when the news is good. If a plan promises weekly reviews and three of six happen, your own document becomes the evidence that the employee didn't get what they were promised.

Building in the accommodation branch

Decide in advance what happens if the employee responds to the plan with a reasonable accommodation request, and write that branch into the template. The interactive process is the back-and-forth discussion between employer and employee to identify a workable reasonable accommodation.

EEOC's worked example describes a supervisor who postpones the start of a 60-day plan when the employee responds with a reasonable accommodation request, discusses it immediately, and brings in the disability program manager. Postponing the start isn't withdrawing the plan.

EEOC is equally clear that an employer doesn't have to rescind discipline, including a termination, or an evaluation warranted by poor performance, because an accommodation request arrived afterward. Both facts belong in your template. An employee who gets the plan on Monday and discloses a condition on Tuesday meets a prepared manager or an improvising one.

The drafting checklist, with the failure mode beside each line:

Components and the same-standards constraint come from EEOC's guidance on performance and conduct standards.

Rewrite every adjective in your draft as an observable output with a date, then add the accommodation branch so the next manager doesn't have to invent one.

Performance improvement plan examples and structure

The same six components carry every plan, and the only thing that changes between roles is the standard.

A missed-quota example

State the gap as the specific shortfall against the specific target over the specific period, with the measure named. The shape runs four lines: the target missed, the figure to close inside the period, the start and end dates, and the coaching cadence with its owner.

The support column is where this example earns its keep, through pipeline review cadence, named deals to be worked, and a named coach. Without it the plan is an instruction to try harder. If the territory or quota changed inside the measurement window, the plan has to account for that or the standard isn't fair.

A quality and rework example

For output-quality problems the standard is a defect or rework rate against a named baseline, not an impression of sloppiness. The same four lines apply, with the support line naming the review or pairing arrangement.

If the team has never stated an acceptable rework rate, the plan is where you state it first, and it has to be a rate the rest of the team meets. EEOC's prohibited-practices guidance is explicit that an employer may not discipline two employees differently for a similar offense on the basis of a protected characteristic, so a standard invented for one person is the inconsistency that guidance points at.

A collaboration example, and why it's the hardest to write

Behavioral standards convert to attendance, artifacts, and response times rather than to adjectives about attitude. The standard line names the meeting to attend, the artifact to produce, and the response window to hold.

This is where most real plans fail, because the manager's complaint is about how someone makes the team feel, and that doesn't convert cleanly. If nothing in the complaint converts to an observable, you have a fit problem, and the three-part test sends you somewhere else.

On templates

A template standardizes the components and the branches, and it can't standardize the standards, which are role-specific by definition. Reuse is where inconsistency creeps in, because a manager copies the previous plan and inherits standards written for a different role.

Two engineers in different specialties on plans with identical wording, neither standard matching the work, is the common version. The fix is that the template carries the components and the accommodation branch, while the standard gets written fresh each time. Run the weakest item in your draft through the rewrite table.

Rewrites apply EEOC's measurable-standards framing from its guidance on performance and conduct standards.

Performance improvement plan employee rights and legal exposure

EEOC's published guidance points at consistency rather than at the plan document, which is why a well-drafted plan issued against an inconsistent history is still exposure. This section covers consistency, timing after protected activity, disability and the same-standard rule, and record retention. Three triggers should route a plan past counsel, and each is named below.

Consistency is the exposure, not the plan

EEOC prohibited practices guidance states that an employer may not take into account a person's race, color, religion, sex (including transgender status, sexual orientation, and pregnancy), national origin, age (40 or older), disability, or genetic information when making decisions about discipline or discharge. It gives the example that where two employees commit a similar offense, an employer may not discipline them differently on that basis.

That comparison is the first thing an investigator constructs, and it gets built from your own history rather than from the plan in front of them. The quality of the document doesn't repair the pattern.

Differences between cases can be legitimate, and the basis has to be documented and role-based at the time rather than reconstructed afterward. Two employees in the same role miss the same target, one gets a plan and one gets a conversation. That difference has to be explainable from the record that existed when the decision was made.

Timing after protected activity

Protected activity means conduct such as filing a discrimination complaint or opposing discrimination, which anti-retaliation rules cover. EEOC retaliation guidance states that engaging in EEO activity doesn't shield an employee from all discipline or discharge, and that employers are free to discipline or terminate workers if motivated by non-retaliatory and non-discriminatory reasons that would otherwise result in such consequences.

EEOC enforcement guidance on retaliation notes that the causal link is often established by evidence that the adverse action occurred shortly after the protected activity. It adds that temporal proximity isn't necessary, and that other evidence of retaliatory motive may establish the link even when the gap is lengthy.

EEOC's retaliation guidance also states that an employer may not do anything in response to EEO activity that would discourage someone from complaining about future discrimination. A plan issued eight days after an internal complaint, with no written performance record predating it, is a weak position regardless of how accurate the concerns are. The record that predates the complaint carries the decision.

Disability, accommodation, and the same-standard rule

EEOC's guidance on performance and conduct standards states that an employee with a disability must meet the same production standards, whether quantitative or qualitative, as a non-disabled employee in the same job.

Accommodation operates on method rather than on the standard. EEOC's own worked example shows a supervisor postponing the start of a plan when the employee responds with an accommodation request, and opening the interactive process immediately. You can pause in order to assess accurately without withdrawing the requirement that performance improve.

At the same time, an employer doesn't have to rescind discipline, including a termination, or an evaluation warranted by poor performance, because a request arrived afterward. Present that alongside the pause guidance rather than instead of it, since either half alone misstates the rule.

Documentation and record retention

EEOC recordkeeping requirements state that employers must keep all personnel or employment records for one year, and that where an employee is involuntarily terminated, the personnel records must be retained for one year from the date of termination. Under ADEA recordkeeping requirements, employers must also keep all payroll records for three years.

Set the clock at issue rather than at exit, because a plan that ends in success still carries the obligation. Under FLSA recordkeeping as it applies to the Equal Pay Act, employers must keep for at least two years all records that explain the basis for paying different wages to employees of opposite sexes in the same establishment.

The common failure is a plan closed successfully in March and deleted in May during a drive cleanup, while the obligation was still running.

All four periods come from EEOC's recordkeeping requirements and apply to the plan file like any other personnel record.

What happens at the end of a performance improvement plan

Four outcomes are possible: the standard is met, the plan is extended, the employment ends in separation, or the employee resigns mid-plan. Each has a hiring action attached, and calendaring that action on the plan's end date is what stops the plan lapsing without a decision.

Outcome one, the standard is met

Close the plan in writing, confirm the standard as the ongoing expectation, and keep the file. The failure mode is silence, because a plan that quietly stops leaves the standard ambiguous, which makes any future plan on the same employee look pretextual.

If the standard was met only under a support arrangement that can't continue, that's a role-design conversation rather than a successful close. An engineer who hits the defect rate only because a colleague reviewed every commit hasn't closed anything once that ends. No requisition opens here, and the draft you prepared closes unopened at no cost.

Outcome two, the plan is extended

Extend only when there's a specific reason the period wasn't a fair measure, and state that reason in writing. Extension without a stated reason damages the record most, because it signals you aren't willing to decide.

A paused or postponed start, for example where an accommodation request triggered the interactive process, isn't an extension and should be documented as a different thing. A plan extended because the employee was on approved leave for two of the four weeks is the defensible version. The requisition draft stays open, and the decision date moves with the plan.

Outcome three: separation

The decision should follow from the record the plan created, on the date the plan named. If the record doesn't support it, the problem is the record rather than the date.

This is where retention becomes concrete. EEOC's retention rule requires personnel records of an involuntarily terminated employee to be kept for one year from the date of termination, so the plan file doesn't close when the employment does.

If the employee held employer-sponsored work authorization, the separation carries obligations the plan document doesn't cover, and an employer who sponsored an H-1B needs to understand those before the end date rather than after it. Separating a sponsored employee on the end date without having looked at what sponsorship withdrawal involves is the common error.

The fourth outcome, resignation mid-plan

The plan ends, the vacancy is real, and the requisition should open that day rather than after the notice period. Most employers treat a mid-plan resignation as a relief and lose the week, when the plan document is still the most accurate written account of what the role demands.

Keep the plan file regardless of how the employment ended, since the retention obligation doesn't depend on who ended it. The version to avoid is a resignation in week three of a six-week plan, the file closed, and the requisition opening four weeks later against a two-year-old job description.

Each outcome has a hiring action attached

Calendar the hiring decision on the same date as the plan's end date, so the plan can't lapse without a decision attached. A role scorecard is a written list of the specific outputs a role must produce, used to build a job description and evaluate candidates against it. The plan you just wrote is one.

The plan window is advance notice of a possible vacancy, and it's the only such notice you get. Used properly, the sourcing work is underway before the decision and the scorecard is already written.

Sourcing in parallel isn't a signal that the decision is made, and it stays that way by keeping hiring activity out of the plan record and out of the check-ins. A plan issued on the first of the month with a six-week period has a decision date and a matching requisition-readiness date. If the employee succeeds, the requisition closes unopened at no cost.

Each ending, with the decision and the hiring action beside it:

Retention obligations behind the separation and resignation rows come from EEOC's published recordkeeping requirements.

With the decision date on the calendar, the open question is whether the pool of people who could fill that seat is something you know or something you'll find out in a hurry.

Planning the backfill before the plan ends

Convert the plan's measurable standards into the requirements section of the job description, because they're the only requirements in the company written down with evidence behind them. What's unresolved at this point is what to do with the weeks in between, and whether preparing for an outcome you haven't decided on is legitimate. Two moves settle it.

Reading the plan as a role scorecard

The plan's measurable standards become the requirements section of the next job description. Most job descriptions are inherited, copied forward from a posting nobody has examined in years. The plan is the one document written specifically about what this role demands, under pressure, with a real gap in front of the author.

Anything in the plan that was a fit issue rather than a role requirement doesn't belong in the scorecard, so separate the two before reusing the text. A plan naming a one-business-day client response standard has just told you the line that matters most in the next posting.

Sourcing in parallel without prejudging the plan

Build the candidate pool during the plan window, keep it out of the plan record, and keep it out of the manager's check-ins. Two separate files, two separate conversations.

The separation is what makes this defensible. Market research about a role isn't an adverse action against an employee. Mixing hiring activity into the performance record is what makes a plan look decided in advance.

If the employee holds employer-sponsored work authorization, both the replacement timeline and the pool change, and some candidates will need sponsorship themselves, including anyone who would come in on an E-3 visa. A six-week plan and a six-week sourcing runway can end on the same day, so if the plan succeeds nothing was lost, and if it doesn't, the seat isn't empty for a quarter.

The plan window is the only advance notice of a vacancy you get, so stop treating the plan and the requisition as sequential steps. Seeing the real replacement pool for that role, during the plan window and separate from the performance record, is what turns a countdown into a runway.