A strong performance improvement plan moves from documented evidence to HR-reviewed language the manager can deliver in the room. The draft has to name the performance gap, the measurable improvement goal, the deadline, the support the company provides, the check-in rhythm, and the consequences if improvement does not follow. Write it in that order and the meeting becomes easier.
You have already decided a PIP is the right step, so the question is no longer whether to act. The question is how to write a document the employee can act on and HR can defend. That is what the next seven steps cover, from the first evidence note to the final review before delivery.
- Write the performance gap as a documented pattern the employee can recognize, not as a personality judgment.
- Turn each gap into a measurable goal tied to the actual role and the responsibilities the employee already owns.
- Give the employee enough time and real support, then document each check-in while the plan is running.
- Send the draft to HR and legal before delivery, not after the conversation has gone sideways.
How do you write a performance improvement plan?
Write the PIP in the same order the process has to run: evidence first, improvement plan second, review before delivery. That order keeps the document useful for the employee and defensible for the company.
Start by naming the exact performance gap and pinning it to dated evidence. After that, write the improvement goal in language the employee can act on this week, not a vague aspiration for the quarter. The timeline comes next, because it tells everyone how long the employee has to show sustained change rather than a one-off good week.
The draft also has to say what the company will provide while the plan is active. Coaching, tools or training have to be written in before check-ins start, because you cannot credibly ask for improvement while leaving support vague. Schedule the check-in cadence in writing, state what happens if the goals are not met, and send the draft to HR or legal before the meeting. The federal PIP quick guide lists the same written components: unacceptable performance, specific examples, duration, success criteria, assistance, and consequences.
This is where the Sprad Talent Management Workspace earns its keep. Atlas can pull review history, 1:1 notes and recent performance signals into the drafting screen, so the manager is not writing from memory or last Friday's frustration. If you also want a ready structure to drop the substance into, our role-based PIP templates save another hour of formatting work.
What evidence belongs in a PIP draft?
A PIP draft needs evidence that shows what happened, when it happened, and how the work missed the standard. Write about observable outcomes, not traits or assumptions about the person.
The strongest evidence usually exists already: prior performance reviews, 1:1 notes, missed targets, customer escalations, quality records. A line like "the employee lacks ownership" gives the employee almost nothing to fix and gives HR almost nothing to review. A stronger draft names the assignment, the expected standard, the actual result, and the date or period when the gap appeared. EEOC guidance for small employers pushes in the same direction, asking for communicated standards, consistent application, and factual details such as production percentages or time windows.
Check whether the same standard has been applied consistently across the team before the document leaves your desk. If one employee enters a PIP for a missed production standard while others get a quiet word for the same pattern, the document creates avoidable legal and cultural risk. Sprad's review history and 1:1 records help here, because you can see whether you are documenting a real pattern or a recent irritation. The same evidence discipline that powers a fair PIP also powers the rest of the review cycle, which is why we walk through it in our piece on reviews managers actually complete.
How do you write measurable PIP goals?
Each PIP goal should turn the documented gap into a specific target the employee can measure while the plan is active. The goal connects to the role, not to a manager's preferred style.
A useful goal tells the employee what result has to change and how both sides will know it changed. If the gap is late reporting, the goal names the reporting deadline and the quality threshold. If the gap is customer follow-up, the goal defines the expected response behavior in a way you can actually check during the plan. Employment New Zealand's step-by-step guide calls for clear, measurable, reasonable SMART targets linked to the role and job description, which is the same bar a UK tribunal or a German Betriebsrat would expect.
The common mistake is writing a goal that sounds reasonable but cannot be measured. "Improve communication" gives the employee too much room to guess and you too much room to move the goalposts. A better draft turns communication into a visible work behavior, then connects that behavior to the job description. Before the document leaves draft mode, run the before-and-after wording past our SMART goals walkthrough so the PIP itself stays short.
What timeline should a performance improvement plan use?
A PIP should normally run for at least 30 days, with 60 or 90 days as the more realistic window for work that takes longer to prove. The SHRM guidance on effective PIPs uses exactly that range, and the principle behind it is simple: the timeline has to match the behavior or output being measured.
A short timeline works when the employee can show the required change every day or every week. It becomes unfair when the employee needs a full sales cycle, a customer implementation period or several project milestones to prove sustained improvement. Pick the shortest period that still gives the employee a real chance to meet the written standard.
Do not wait until the final day to assess progress. Milestones inside the timeline let you see whether the employee is moving toward the goal or only hearing about problems at the end, which is also what stops the PIP from feeling like a surprise termination file dressed up as an improvement process.
What support and check-ins belong in the PIP?
The PIP should name the support the company will provide and the check-in cadence the manager will follow. If support is vague or meetings are optional, the plan is weaker than it looks on paper.
Write support as a concrete company action: coaching time, mentoring, job aids, system access, workload clarification, or specific training the employee needs to meet the goal. The point is not to promise unlimited help. The point is to show the company gave the employee a reasonable path to improve, which is exactly what the University of Virginia DHRM policy guide asks managers to document before presentation, alongside weekly or biweekly progress meetings.
Check-ins should run on a predictable rhythm and produce a written summary the employee can keep. During the plan, Atlas turns that cadence into prepared 1:1 agendas and follow-up notes, so you do not lose the thread between week two and week six. The PIP becomes credible when every conversation has a date, a decision and a next action, all of it sitting in the same record the final review will draw from.
What we suggest: Tie every check-in to three written lines. What changed since the last meeting, what is still off-track, and what the employee will do before the next one. That is the minimum record that survives an HR review six weeks later.
What consequences should the PIP document state?
The PIP should state what happens if the employee meets the goals and what may happen if they do not. Write consequences clearly without making the outcome look predetermined.
The language has to be specific enough that the employee understands the stakes. It can also acknowledge that outcomes depend on progress, because many PIPs end with completion, extension or another employment action depending on the evidence at review. Acas capability guidance sets out the same principle for UK employers: if improvement does not happen, the employer may extend the process, issue a final warning or consider dismissal, but only after a fair procedure.
The mistake is using consequence language as a threat, or hiding it so the meeting feels easier. Both choices create problems. A fair draft tells the employee what success looks like, how the company will judge progress, and what options remain if improvement does not happen.
How should HR review the PIP before delivery?
HR and legal should review the draft before you deliver it. Their review has to catch unclear standards, inconsistent treatment, unrealistic timing and language that creates avoidable risk.
Give HR the full draft and the evidence behind it, not a one-paragraph summary. Reviewers need to see whether the goals match the gap, whether the timeline is reasonable, and whether the promised support is real rather than aspirational. Federal guidance is unambiguous on this point: consult HR and legal advisors before, during and after the PIP process, not only when the meeting has already gone wrong.
Prepare the delivery conversation before walking into the room. Open with the purpose of the PIP, explain the evidence and the required improvement, then walk through timeline, support, check-ins and consequences. Invite the employee to respond before you confirm the first follow-up in writing.
- Pre-review packet: full draft, dated evidence, prior 1:1 notes, comparable team treatment for the same standard.
- HR check: goals tied to the role, timeline matched to the work, support specified, consequences not predetermined.
- Legal check: consistent application, no protected-characteristic exposure, accommodation pathway open if requested.
- Delivery prep: opening framing, evidence walk-through, employee response window, written follow-up confirmed within 24 hours.
The draft shapes the PIP meeting
Managers often brace for the delivery meeting as the hardest part. In practice, the meeting mostly reveals whether the document was written well. A PIP built from evidence, measurable goals and real support gives the employee a clearer path and gives the company a cleaner record of fair process. A PIP built from memory and irritation produces the opposite of both.
Two things stay true across every step above. Good documentation protects the process, but the employee still needs enough support to act on the plan. And the best time to fix vague goals or risky language is before the employee ever sees the document, not after the second check-in has already drifted.
Before the next PIP meeting, run the draft through a one-page checklist and send it to HR while there is still time to change wording. If Sprad already holds the review notes and 1:1 history, use that record to pre-fill the evidence and lock in the check-in cadence before the document leaves draft mode.
Frequently Asked Questions (FAQ)
How often should you meet during a PIP?
Weekly or biweekly check-ins are the practical default for most PIPs. The manager should document what was discussed after each meeting and share the summary with the employee, because the record matters as much as the conversation itself. A predictable rhythm also stops the plan from becoming an end-of-period surprise.
Can a PIP be extended if the employee partly improves?
Yes, a PIP can be extended when the employee shows partial or marginal improvement and the company believes more time is reasonable. The extension should state what still has to improve and how long the employee has to meet the remaining standard. Treat the extension as a written amendment, not a verbal agreement.
What if an employee requests accommodation during a PIP?
Start the reasonable accommodation process as soon as the employee makes the request. The company does not automatically have to cancel the PIP, but it may need to pause or adjust the process so the employee has a fair opportunity to improve. Document the request, the response, and any adjustments to the timeline.
Does signing a PIP mean the employee agrees with it?
No, a signature on a PIP can simply acknowledge that the employee received the document. If the company wants the signature to mean receipt only, the form should say that clearly so the employee does not feel pressured to agree with every statement. Adding a comment field also gives the employee a place to record disagreement without refusing to sign.
Can a manager add old performance issues at the final PIP review?
No, the manager should not introduce old issues at the final review if those issues were not part of the written PIP. The review has to focus on the goals and evidence in the plan, because the employee needs to know exactly what they are being measured against. New concerns belong in a separate, properly documented process.
What if an employee refuses to sign a PIP?
A refusal to sign does not automatically invalidate the PIP. The manager should note that the employee refused, give the employee a copy of the document anyway, and continue to follow the written timeline and check-in process. Having a second person present at delivery makes that record cleaner if it is ever questioned later.



