How employers are advised to run a PIP: their own playbook

The script is published

A plan rarely arrives from nowhere. Behind most of them sits guidance the employer bought or was given, and much of it is public. It comes in two kinds, and they are written for different purposes. HR-vendor material tells a manager how to run the process. Employers' employment counsel tells the company how to defend the decision if it is challenged later.

Neither is law, and neither is a description of what your employer actually did. Individual employers deviate constantly. What the guidance gives you is the expected shape — so you can see what is supposed to happen next, and notice when it does not.

Both readings are useful whichever way you are hoping this goes. If you are trying to pass, the playbook tells you what the plan is meant to provide you and when. If you are planning an exit, the same document tells you what the other side treats as a weak file.

One caveat on the second kind, and it runs through this whole page. The counsel material here is American, written mostly around US federal and Californian practice. The process logic travels; the legal hooks do not. Where you are decides what any of it is worth, and the country pages are where that lives.

The file starts before the meeting

The clearest thing in the vendor guidance is the sequencing. Managers are instructed to gather specific incidents, dates, the standard expected and the business impact before drafting anything. By the meeting where you first hear about a plan, a written record already exists on the other side.

That is not sinister — it is what "document your concerns" means in practice — but it has a day-one consequence worth naming: you start behind on the record, and the gap is only closed by starting your own. The foundation page has what follows from that.

The plan is meant to have two halves

On paper the plan assigns work to the manager as well as to you: coaching sessions, resources, mentorship, and documentation of each. The vendor guidance also makes a root-cause check a required step before the plan is written, and its own list of candidate causes is striking — unclear role expectations, resource constraints, skill and training gaps, process inefficiencies, team communication problems. Every item on that list is the employer's to fix.

That list is the most immediately useful thing on this page. If one of those causes is why the work slipped, naming it in writing, with an example, and asking for it to be addressed inside the plan is not a complaint. It is the step their own guidance says should already have happened.

The same material sets a standard for goals: specific, measurable, time-bound, tied to the role. Its worked example turns "improve communication" into replying within one business day plus a Monday status update. A goal still written in the vague form has not been through the transform the employer's own guidance requires.

The check-in cadence, and why sustained outlives the plan

Expect weekly or fortnightly check-ins, milestone reviews at thirty, sixty and ninety days, and notes taken at each. Two things follow.

The first is that the check-ins are documented by them whether or not they are documented by you. An employee keeping nothing while the manager writes after every meeting is building the asymmetry the plan will later be read through.

The second is the word sustained. The end-of-plan review in this guidance asks not only whether the goals were met but whether the improvement held. Meeting the targets once is explicitly not the finish line, and language about recurrence outlives the plan itself. That matters most to the reader who is passing: the file does not close the way the calendar does, which is why what to get in writing when a plan closes is worth knowing before you get there.

HR is the approver, not the person in the room

Both playbooks describe the same division. HR signs the document off before it is delivered and receives the progress documentation, acting as validator for a decision that may need defending later. The manager is told to own the conversation.

The practical translation is not that anyone is acting in bad faith. It is that the person across the table is not the person the file is being assembled for.

The parallel track is on the calendar, and it is a calendar

One manager-coaching framework, built around a six-week plan, tells managers to begin exploring termination options around weeks four to five, in parallel, where progress has stalled — while the plan is still notionally live.

Read that as what it is. It is contingency planning scheduled to begin whether or not anything has been decided, and it starts on a date rather than on a conclusion about you. It is not evidence that the ending is settled, and this guide will not tell you it is.

What it does establish is that the midpoint is a scheduled step on their side. Around two-thirds of the way through whatever length your plan actually runs — plans in this guide range from about four weeks to six months — something is expected to have happened. If nothing has, that absence is itself a fact worth recording.

Their checklist, read backwards

Counsel's material is written to prevent losses, which means it names the failure modes out loud. An employer-side checklist read backwards is a list of what the other side considers a weak file. Four of them are answerable by you, without access to anything the employer holds.

• Was anything raised before the plan? Inadequate documentation of concerns before as well as during a plan is named on their own side as weakening the employer's position.
• Has anyone else in my role been put on a plan for this, and what happened to them? Before issuing a plan, HR is advised to check whether comparable people in comparable roles were treated consistently. Their guidance calls inconsistency here one of the most common ways a plan is later attacked.
• Was I asked about adjustments before the plan was written? Where a disability is known or suspected, counsel advises that a plan does not replace the accommodation conversation, and that the template should carry a checkpoint for it beforehand. That framing is Californian in the source; the underlying principle is wider, the procedure is not.
• When did the concerns first go in writing? The recurring formulation on their side is that the date on the documentation matters as much as its content — not only whether concerns existed, but when the employer first wrote them down.

One thing the same material is blunt about, and it belongs here rather than in a footnote: raising a complaint does not pause performance management. Counsel says so plainly. What a complaint changes is the scrutiny the employer expects to face afterwards, not whether the plan continues.

Same-day notes are their doctrine

The single most useful fact in either playbook is about timing. Managers are coached that if anything unusual happens in a plan meeting — an allegation, a request, a mention of health or leave, even implicitly — HR should write a signed, dated note to file the same day, while memory is fresh.

The other side practises same-day timestamping as doctrine. Keeping your own contemporaneous record is the same ordinary prudence, done by the other party to the same conversation. It is the seatbelt, not an accusation — and by their counsel's own account, the dates are what the question turns on.

What the guidance says is not what the law requires

Fairhanded is not a law firm. This page describes published guidance written for employers, not what your employer did or what the law requires of it, and the counsel half of it is American. If a plan has arrived and something on this page does not match what happened to you, that mismatch is worth taking to an employment lawyer where you live, along with the dates.