Performance improvement plan: written to be passed, or not worth writing

A performance improvement plan sets out where an employee’s performance falls short, what specifically has to change, what support they will get, and by when it will be reviewed. It is a management document with a legal shadow: used well it turns a vague dissatisfaction into something a person can actually act on; used badly it is the paperwork attached to a decision already taken.

The distinction is visible in the objectives. If someone competent and willing could meet them in the time given, the plan is genuine. If they could not, the plan is a record of the employer going through the motions — and that is how it will read to everyone who sees it afterwards, including a tribunal.

What a performance improvement plan should contain

• The specific shortfalls, with examples and dates — not adjectives about attitude.
• The standard expected, stated so that meeting it is verifiable rather than a matter of opinion.
• What the employee will do, and what the manager and the company will do: training, shadowing, changed workload, clearer priorities.
• Review points, with dates, and what happens at each.
• The timescale, proportionate to the role and to what has to change.
• What happens if the standard is met, and what happens if it is not — stated plainly rather than implied.

The support column is the one most often left thin, and it is the one that decides whether the plan is fair. Poor performance frequently has causes the employee cannot fix alone: unclear expectations, missing training, a workload nobody could carry, or a health issue nobody has asked about.

Before writing one, check the diagnosis

Performance and conduct are different problems with different processes. Someone who cannot do the job needs support and time; someone who will not follow the rules is a matter for the disciplinary procedure. Running the wrong process is unfair and, in a dispute, obvious.

Check also whether a health condition or a caring responsibility is in play. In many jurisdictions that changes the employer’s obligations entirely — adjustments may be required before performance can fairly be judged — and it is not something to discover at the end of a plan.

Set the timescale by what the change requires, not by convention. Thirty days is enough to demonstrate a change in punctuality and not enough to demonstrate a change in the quality of complex work with a long feedback cycle. A period chosen because it is the standard period is the first thing that looks arbitrary.

Running it so the outcome is credible

1. Discuss the draft rather than presenting it: an employee who disputes the facts on day one is telling you something you need to know.
2. Hold the review meetings you scheduled, on the dates you scheduled — a plan with skipped reviews cannot support a conclusion.
3. Record what was discussed each time, including improvements, not only failures.
4. Deliver the promised support, and note when it happened.
5. At the end, decide against the standard you wrote, not against your general impression.
6. If the standard was met, say so clearly and close the plan.

The last point matters more than it sounds. Plans that are never formally closed leave the employee in permanent probation and the manager with an unresolved file. Ettex Docs keeps the plan, its review notes and its outcome as one document with a history, so the version discussed in March and the version concluded in May are both retrievable, and the closure is recorded rather than assumed. Whether the plan itself is fair remains a management judgement, and no document tool improves it.