A performance improvement plan gets a bad reputation it doesn't always deserve — treated as a formality before termination rather than what it's actually meant to be: a documented, fair chance for an employee to close a specific gap, with clear support and a clear timeline. Written well, a PIP protects both the employee and the company. Written poorly, it protects neither.
Here's a practical structure, a worked example, and what to get right.
What a PIP Is (and Isn't)
A performance improvement plan is a formal, written document that outlines a specific performance issue, the expectation for improvement, the support being offered, a defined timeline, and the consequence if improvement doesn't happen.
It is not a substitute for ongoing feedback — if a PIP is the first time an employee is hearing about a serious performance concern, something upstream has already gone wrong. It's also not purely punitive; a well-run PIP includes genuine support, not just a warning with a deadline attached.
Why Documentation Matters Here Specifically
Of all the documents in the performance management System lifecycle, a PIP carries the most weight if an employment decision is ever challenged or reviewed later. Vague language, inconsistent application across employees, or a plan that was never actually followed up on creates real risk — both for fairness to the employee and for the company if the outcome is eventually contested.
This is the single biggest reason to use a consistent, structured template rather than writing each PIP from scratch under time pressure.
The Core Structure of a PIP
1. The Specific Issue
State exactly what's underperforming — not a general impression, but a specific, observable gap. "Not a team player" isn't usable. "Missed 4 of the last 6 sprint deadlines, with average delay of 3 days" is.
2. The Expectation
Define precisely what improvement looks like, using the same specificity as a SMART goal. If the expectation itself is vague, the employee has no clear target to work toward.
3. The Support Being Provided
List what the company is doing to help — additional training, closer check-ins, mentorship, adjusted workload. A PIP without any listed support reads as purely punitive, and often is treated that way if challenged later.
4. The Timeline
Set a specific duration — commonly 30, 60, or 90 days — with defined check-in points within that window, not just a single deadline at the end.
5. The Consequence
State plainly what happens if the expectation isn't met by the deadline. This should be decided and documented before the PIP begins, not improvised at the end.
Worked Example
Issue: Over the last two review cycles, [Employee] has missed 4 of 6 sprint deadlines, with an average delay of 3 days per missed deadline, based on sprint tracking data.
Expectation: Meet 100% of assigned sprint deadlines for the next two sprint cycles, or communicate any blocker to the team lead at least 2 days before the deadline if a delay becomes unavoidable.
Support provided: Weekly 1:1 check-ins with the team lead for the duration of the plan; pairing with a senior engineer on the next two sprints; adjusted workload to remove one non-critical task from the current sprint.
Timeline: 60 days, with a formal check-in at day 30 and a final review at day 60.
Consequence if not met: If the expectation is not met by day 60, this may result in further formal action up to and including termination, per company policy.
How to Run the Process Fairly
1. Have a Direct, Documented Conversation First
The employee should never be surprised by a PIP if feedback has been given consistently beforehand. If this is the first formal mention of the issue, the conversation needs to happen before the plan is issued, not folded into the plan itself as the first notice.
2. Apply the Same Standard Across Employees
A PIP process that's used strictly for some employees and skipped or softened for others — even unintentionally — creates a fairness and consistency problem that becomes very visible if ever scrutinized.
3. Hold the Scheduled Check-Ins, Not Just the Final Review
A PIP with a 30-day check-in that never actually happens undermines the entire premise that the plan includes genuine support, not just a countdown.
4. Document Outcomes at Each Stage
Whether the employee is meeting, partially meeting, or not meeting the plan's expectations should be documented at each check-in — not reconstructed from memory at the final review.
5. Base the Plan on Real Performance Data
A PIP grounded in documented goal completion rates, appraisal history, and specific incidents is far more defensible — and fairer to the employee — than one based on a manager's general impression. This is exactly why consistent goal tracking and review history matter well before a PIP is ever needed.
Conclusion
A performance improvement plan works as intended only when it's specific, genuinely supportive, and consistently followed through on — the same structure applied the same way for every employee, backed by real documented performance history rather than a manager's general impression assembled after the fact.
OfficePortal keeps appraisal scores, goal completion rates, and banding data connected to the same employee record, so a PIP can be built on documented performance history rather than reconstructed from memory — with employee memos and formal correspondence logged in the system for later reference. See how OfficePortal supports performance documentation.
Reference Pages
Succession Planning Template: Free Framework for HR Teams
Attendance Policy Template: Grace Period, Late Coming & Regularization Rules
Employee Performance: How to Measure, Track & Improve It
Free Attendance Tracking Software for Small Business (2026)
Free Leave Management System for Small Business (2026)
