Performance Improvement Plan Template | ADA & FMLA Ready

A PIP is a written, time-bound management instrument that does four things at once. It identifies performance deficiencies with dated examples, sets measurable targets, records the support the employer commits to provide, and states what happens if the targets are missed. Most plans run 30, 60 or 90 days, with formal checkpoints every two weeks. No federal or state labor code defines the format, which is why the drafting carries so much weight: the plan gets judged later on whether it reads like a real attempt at correction or a manufactured exit ramp.

Experienced HR counsel keep the PIP separate from three neighboring documents. A warning letter is disciplinary and backward-looking, aimed at conduct rather than output. A write-up form records a single incident. A last chance agreement is a bargained contract, common in unionized workplaces, where the employee gives up rights for one final opportunity. A PIP is not an employment contract, though careless wording can make it look like one. In states recognizing implied contract exceptions to at-will employment, a plan promising the employee "will remain employed through the full ninety-day period" hands the other side an argument built on Foley v. Interactive Data Corp., 47 Cal.3d 654 (1988).

No US statute obliges an employer to issue a plan before terminating an at-will employee. The obligations attach to how it is written and administered. Employment in forty-nine states is at will by default; Montana is the exception, where the Wrongful Discharge from Employment Act, Mont. Code Ann. §39-2-901 and following, requires good cause once the probationary period ends. Everywhere else the plan works as evidence. Under McDonnell Douglas Corp. v. Green, 411 U.S. 792 (1973), an employer defending a discrimination claim must produce a legitimate, non-discriminatory reason for the termination, and a specific, contemporaneous, consistently applied plan is the strongest form of that proof. A vague one invites a pretext argument.

The exposure has widened. In Muldrow v. City of St. Louis, 601 U.S. 346 (2024), the Supreme Court dropped the requirement that a plaintiff show significant harm to establish an adverse action under Title VII, leaving a threshold of some harm that leaves the employee worse off. The First Circuit rejected the argument that every plan clears that bar, holding in Walsh v. HNTB Corp., 169 F.4th 330 (1st Cir. 2026), that the inquiry is fact-specific. The line is worth memorizing: a plan that warns or develops is not an adverse action, while one that assigns new duties, alters pay or closes off advancement may be.

Three federal rules shape the drafting. The Americans with Disabilities Act opens the interactive process once an employer learns a disability may be driving the gap, and the EEOC enforcement guidance on applying performance and conduct standards to employees with disabilities is the working reference, which is why a plan belongs in the same file as an ADA reasonable accommodation request form. 29 C.F.R. §825.220(c) bars using FMLA leave as a negative factor, so protected absences never feed the metrics. And under Stericycle, Inc., 372 NLRB No. 113 (2023), telling an employee not to discuss the plan with coworkers can violate section 7 of the National Labor Relations Act.

The standard trigger is a sustained shortfall that has survived informal coaching. A sales representative misses quota two quarters running, an engineer's defect rate stays above the team baseline, a support agent's resolution times drift and stay drifted. Once verbal feedback has changed nothing, the next conversation needs a written frame, and a written employee warning letter is the wrong instrument when the issue is output rather than misconduct. The second scenario is a promotion that has not worked: someone effective as an individual contributor struggles with management scope, and the company wants a structured runway before deciding to reassign or separate.

Two edge cases separate employers who get sued from employers who do not. The first is the plan that lands immediately after protected activity. An employee requests FMLA leave on Monday, discloses a diagnosis, or files a harassment complaint, and the plan appears on Thursday. Even where the performance file predates the request, the sequence alone creates a retaliation narrative that costs real money to defend. The second is the reduction in force dressed as performance management. Placing three employees over fifty on plans six weeks before a restructuring is the pattern plaintiffs' counsel look for first, and ADEA analysis will surface it.

• The statement of performance deficiencies is drafted around dated, observable facts rather than characterizations. "Missed four of six client deadlines between March and May, listed by project" survives cross-examination. "Poor attitude" does not, and it is the most common reason a plan collapses.
• The measurable objectives and success criteria force each goal into a number, a deadline and a source of truth. Every objective states how performance is measured and who verifies it, which kills the argument that the employee never knew what success looked like.
• The employer support commitments clause records what the company will actually provide: training hours, a named mentor, revised territory, reduced caseload. Courts read this closely, since a plan demanding improvement while offering nothing reads as pretextual.
• The review schedule and checkpoint dates are fixed in the document itself, with space to record what happened at each meeting. Employers skip this section and regret it, since an unheld checkpoint undermines everything above it.
• The consequences statement says plainly that failure to meet the objectives may result in action up to and including termination, without promising employment for the duration of the plan. The at-will preservation language is calibrated to the state you select.
• The acknowledgment and employee response block records receipt rather than agreement and leaves room for a written rebuttal, which several states make a statutory right. Pairing the plan with an employee write-up form for one-off incidents keeps the personnel file coherent.

California gives employees the most leverage over what sits in the file. Under Labor Code §1198.5, an employer has 30 calendar days to produce personnel records after a written request, and Labor Code §432 entitles the employee to a copy of any instrument they signed, including the acknowledgment page. FEHA adds more: Gov. Code §12940(n) makes failure to engage in a timely, good faith interactive process an independent violation, so a plan issued after any mention of a medical limitation must be paired with an accommodation discussion.

Connecticut imposes the tightest deadline in the country. Conn. Gen. Stat. §31-128b(c) requires the employer to hand the employee a copy of any documented disciplinary action within one business day of imposing it. Section 31-128e(b) goes further and requires the document itself to carry conspicuous language telling the employee they may submit a written statement of disagreement, which stays in the file and travels with any disclosure to a third party. A plan drafted without that notice is defective on its face.

Illinois operates on the Personnel Record Review Act. 820 ILCS 40/2 gives employees inspection rights twice per calendar year, 820 ILCS 40/6 attaches any rebuttal to the disputed portion of the record, and 820 ILCS 40/7 requires written notice before a disciplinary document goes outside the organization. Employers treating a plan as internal-only paperwork miss that last requirement.

Montana changes the analysis entirely. The Wrongful Discharge from Employment Act removes at-will status once an employee clears the probationary period, which runs twelve months from hire where the employer has not set its own. After that the employer needs good cause, and a documented plan with real checkpoints is the main evidence the standard was met.

You start by selecting the state where the employee works, which sets the at-will language, the acknowledgment wording and any statutory rebuttal notice that state requires. The form asks for the employee's role, manager, review period and start date, then generates checkpoint dates from the window you choose. The deficiency section runs entry by entry: for each issue you record the behavior, the dates it occurred and the standard it fell short of. Objectives follow the same pattern, each paired with a metric, a target and a verification source.

The last screens handle support commitments, the consequences statement and the signature block. The file arrives in Word and PDF, so a manager can adjust wording before the meeting and archive the signed copy afterward. The same state-aware logic sits behind our US business and corporate document templates, which matters for founders handling their own HR paperwork alongside company formation.

The mistake that ends cases is the checkpoint that never happened. A plan promising biweekly reviews, with no record that any review took place, tells a factfinder the company had already decided. Hold every meeting you schedule and write one paragraph after each one. Close behind is the unmeasurable goal. "Improve communication" cannot be passed or failed, and an objective that cannot be failed cannot support a termination. Managers also fold protected absences into attendance metrics, converting a defensible file into an FMLA interference claim under 29 C.F.R. §825.220(c).

Inconsistency across a team does the same damage. If two account managers miss the same targets and only one goes on a plan, the difference between them becomes the case. Document why, or place both. Employers also let plans expire without closing them out. Either the objectives were met and the file records it, or they were not and separation follows promptly, with an employee termination letter that tracks state final-pay deadlines. A plan left open past its end date reads as abandonment of the process and undermines every document that came before it.