Manager observes unmet goals or standards
A performance improvement plan starts before anyone writes a document — it starts when a manager notices a gap between what a role requires and what an employee is delivering, and decides that gap is serious enough to name formally. The sequence below is the full arc a manager should expect, not just the paperwork.
- The manager observes and documents unmet goals or standards. This means specific instances — missed deadlines, error rates, complaints, incomplete deliverables — logged with dates, not a general impression that "things aren't working." The Office of Personnel Management's supervisor guide frames this documentation step as the foundation the rest of the plan rests on, since a PIP that can't point to concrete incidents is hard to defend later.
- Expectations and incidents are documented before the plan is drafted. This is where the manager separates a pattern from a bad week, and confirms the issue is performance-based rather than a single lapse.
- A PIP is drafted with SMART goals, a support plan, and a fixed review period. SHRM's guidance on effective performance improvement plans recommends goals that are specific and measurable enough that both manager and employee can agree, without debate, whether they were met — a target number, a deadline, a quality threshold, rather than "improve communication."
- The plan is delivered in an initial meeting with the employee. This meeting should explain the gap, walk through each goal, and state clearly what support the employee will get and what happens if goals aren't met.
- Regular check-ins run through the review period. These are scheduled, not ad hoc, and each one should produce a short written note on what was reviewed and what feedback was given — university HR guidance from the University of Maryland's staff relations office treats these check-ins as core to the process, not an optional add-on.
- At the end of the period, the plan closes one of two ways. If goals are met, the plan is formally closed and that closure should be documented as clearly as the original issues were. If they are not, the next step — extension, transfer, or termination — follows from what was written into the plan at the start, not from a fresh decision made in the moment.
The length of the review period should be tied to how long it realistically takes to observe a change in the specific metric being measured — a sales number that reports monthly needs a different window than a defect rate that shows up daily — rather than picked as a round number. A template published by the University of Cambridge's HR division illustrates what a completed plan looks like in practice, with goals, dates and review points filled in against a real role.
Human resources sits alongside the manager through this whole sequence rather than after it. HR's role is typically to review the draft plan before it's delivered — checking that the goals are measurable, that the language matches what the organization has used for comparable cases, and that the timeline and support commitments are ones the manager can actually deliver — and then to hold the record of the plan, the check-in notes and the outcome in the employee's file. The OPM guide treats this consistency check as part of what keeps a PIP defensible: a plan that HR never saw, or that departs from how similar issues were handled elsewhere in the organization, is harder to justify if it's challenged later.
What separates a defensible plan from one that collapses under challenge is mostly documentation discipline — dated incident notes, goals that don't shift mid-period, and check-in records that show support was actually offered, not just promised.
Employee receives a PIP
Receiving a PIP is not, by itself, a verdict — it's a document, and how an employee treats it in the first week matters more than how they feel about it. The honest starting point is that a PIP genuinely can end in termination, and it genuinely can end in the issue being resolved; neither outcome is guaranteed by the fact of being placed on one, and the difference usually comes down to what the employee does with the review period, not what they assume about the manager's intent.
Four things an employee on a PIP should do:
- Read the stated performance issues and goals literally, not defensively. The document should list specific, measurable targets. If it doesn't — if the language is vague enough that "meeting the goal" is a matter of opinion — that's worth raising in the initial meeting, because a vague goal is unfair to both sides.
- Use check-ins to ask for feedback, clarification, and the support promised. If the plan says training or mentoring will be provided, ask when and confirm it happened. Silence on support is itself evidence, and it should be noted, ideally in writing (a follow-up email summarizing the conversation is enough).
- Keep a running record of progress against each goal, not just at the end. Screenshots, sent emails, completed tickets, dates — anything that shows movement toward the stated target. This record is the employee's version of the manager's incident log, and it serves the same purpose: turning an impression into evidence.
- Track whether the goals or timeline change mid-period. A plan that keeps moving the target is functioning differently than one meant to help someone succeed, and that shift is worth documenting even if nothing is said about it directly.
On the specific question of whether to quit or resign once handed a PIP: there's no single right answer, because it depends on whether the goals are achievable, whether support is actually forthcoming, and whether the employee wants the job if they keep it. What can be said plainly is that resigning immediately forecloses the chance of a successful close, while staying and doing nothing forecloses it just as surely. The decision worth making early is not "should I quit" in the abstract but "are these goals something I can hit with the support on offer, in the time given" — and that answer usually becomes clear within the first couple of check-ins, well before the period ends.
"Beating" a PIP, in the sense the question usually means, isn't a trick — it's meeting the stated goals on the stated timeline and having the record to prove it. SHRM's step-by-step guidance frames the successful outcome for employees the same way it frames the successful outcome for managers: clear goals, met on time, documented on both sides. There's no separate employee-side maneuver beyond doing that consistently and keeping a parallel record in case the manager's does not reflect it accurately.
Performance issues are addressed only once they are severe
A PIP that arrives as the employee's first real conversation about a problem is usually a sign the process failed earlier, not that the employee failed now. When the formal plan is the first time specific concerns were raised, the employee is often genuinely surprised — and being surprised by a formal document, rather than having seen the issue coming through earlier feedback, tends to make the employee trust the process less, whatever the merits of the underlying concern.
This pattern — issues left unaddressed until they're serious enough to require a formal document — is different from a PIP working as intended. A PIP is meant to formalize and structure a conversation that's already been happening informally: goals that were set, feedback that was given, a pattern that both sides had already discussed before it needed a document. Ordinary performance management is what should have caught the issue earlier:
| Stage | What should happen | What tends to go missing |
|---|---|---|
| Goal-setting | Clear, specific targets set at the start of a role or project | Goals stay vague enough that "meeting expectations" is never defined |
| Regular reviews | Scheduled check-ins on progress, separate from any crisis | Reviews happen but skip specifics, or get skipped when things are busy |
| Ongoing feedback | Timely comments on both what's working and what isn't | Negative feedback gets held back until it accumulates |
| Escalation | A conversation before a document — informal warning, then written note | The PIP itself becomes the first written record of any concern |
One structural issue worth separating clearly: a performance shortfall and misconduct are not the same problem, and treating them the same way is a common mistake. A missed target, a skill gap, or a pattern of late deliverables is a performance issue, and a PIP — with goals, support and a timeline — is the right tool. Dishonesty, harassment, safety violations, or other conduct breaches are a different category, and most organizational policy — including the guidance published by Arkansas's Department of Finance and Administration — routes those through a disciplinary process rather than a PIP, because the fix for misconduct isn't a goal and a timeline, it's a decision about whether the behavior is acceptable at all. A manager who reaches for a PIP to handle a conduct problem is usually doing so because it feels gentler than a disciplinary process, but it tends to produce a document that doesn't match the actual problem and doesn't hold up if the outcome is challenged later.
The other place a PIP goes wrong structurally is when it's written as a documented exit rather than a genuine attempt at improvement. The difference is visible in the details: goals that are achievable within the stated timeline versus goals set just out of reach; support that's actually scheduled and delivered versus support that's promised and never booked; a manager who's available for the check-ins versus one who cancels most of them. None of this is usually stated outright, but it shows up in whether the structure of the plan gives the employee a real chance.
What happens at the end of the review period also deserves more attention than it usually gets. Three things can follow a PIP that reaches its deadline:
- Closure. Goals were met, the plan is formally ended, and that closure is documented in the same file as the original plan — a step Sage's guidance on delivering a PIP treats as necessary precisely because an undocumented "quiet close" leaves no record if the same question comes up again later.
- Extension. Progress was real but incomplete, and the manager extends the timeline with the same or adjusted goals — this should be an explicit decision, not a default that happens because no one acted by the deadline.
- Recurrence or termination. The issue resurfaces within months of a plan that was closed as successful, or the goals weren't met and the next step outlined in the original plan — often termination — proceeds.
Whether the record of a completed PIP stays on file after a successful close, and for how long, is a question of the organization's own record-keeping policy rather than a fixed rule, which is one more reason HR's involvement in drafting and closing the plan matters: it's the function that knows what the file will show if the same employee's performance is ever reviewed again.
The version of this that avoids the whole problem is ordinary performance management done consistently: goals set early, feedback given as issues arise rather than stored up, and reviews that are specific enough to catch a pattern months before it needs a formal plan at all.
Feedback
Feedback is the mechanism that makes a PIP function as improvement rather than paperwork, and it has to be specific enough to act on. Generic feedback — "needs to do better," "isn't meeting expectations" — gives an employee nothing to change; feedback that names the exact gap between the goal and the current result gives them something to work with.
Useful feedback during a PIP tends to share a few features:
- It's tied to a specific goal from the plan, not a general impression of the employee's attitude or effort.
- It names both what's improving and what isn't, so the employee isn't guessing whether partial progress counts for anything.
- It's delivered at the scheduled check-in, not saved up and delivered as a surprise near the deadline.
- It's written down, even briefly, so both sides have the same record of what was said.
The OPM supervisor guide frames regular, specific feedback as the difference between a plan that gives an employee a genuine chance to close the gap and one that simply counts down to a predetermined outcome. That distinction is worth taking seriously on both sides of the table: for a manager, it's the difference between a defensible process and one that looks retaliatory in hindsight; for an employee, it's the clearest signal available for whether the plan is working as intended.
If check-ins are happening but feedback stays vague — "keep at it," "we'll see" — that's worth naming directly rather than assuming clarity will arrive later. Asking, in a check-in, "what specifically would meeting this goal look like by the review date" is a reasonable question at any point in the process, and a manager who can't answer it plainly has likely not finished thinking through what the plan is actually measuring.