Before the Paperwork: Auditing the Informal Decisions That Precede a Performance Improvement Plan

A performance improvement plan arrives with the appearance of procedure: a template, a timeline, a review date. What it rarely shows is the months of informal decision-making that preceded it. By the time the document is drafted, a manager has already decided who receives coaching, who is given a gentler workload, who is moved away from a client, and who is left to struggle until the evidence is sufficient to act. That pre-PIP stage is where inclusion is most often won or lost — and it is rarely audited.

In UK workplaces, the formal architecture is familiar. The ACAS Code of Practice on disciplinary and grievance procedures sets expectations around fairness, investigation and the right to be accompanied. The Equality Act 2010 places duties on employers not to discriminate directly or indirectly, and performance management can engage those duties where criteria, language or support are applied unevenly. Yet the Act does not audit a line manager's casual decision to stop copying a colleague into a project. Only the organisation can do that.

Two failure modes, one pipeline

Most discussion of performance management focuses on the plan itself. The more useful question is how people enter the process at all. In practice, three routes exist. The first is informal support: a conversation about workload, a mentor, a training course, a temporary reduction in responsibilities. The second is a formal capability or improvement process. The third is neither — a quiet arrangement that ends with a settlement agreement, a reference and a departure that is recorded as resignation.

The inclusion risk sits in the gap between these routes. If informal support is allocated through manager discretion, it will follow existing patterns of affinity and confidence. If formal processes are triggered inconsistently, they can become a signalling device rather than a development tool. And if the third route is used disproportionately for certain groups, the organisation will never see it in its PIP data, because those people never reach a PIP.

A quarterly audit should therefore begin before the formal paperwork. It need not be elaborate. A sample of the last twelve months of performance cases, anonymised and reviewed by HR with an EDI or trade union representative, is enough to reveal whether the pipeline is behaving as intended. Where numbers are small, suppress detailed breakdowns and look at patterns across teams and grades rather than named individuals.

Mapping entry points against team composition

Start by identifying every route into and out of performance concern, not only the formal one. That means informal capability conversations, probation extensions, temporary changes to duties, informal warnings, formal PIPs, and exits recorded as resignation or settlement within six months of a performance conversation. Record the route, the team, the grade, the working pattern and, where data is lawfully held and aggregated, protected characteristics.

Then compare those figures with the composition of the teams concerned. A single PIP in a team of six proves little. A pattern in which part-time staff, disabled employees or staff from a particular ethnic background are consistently routed towards formal processes while comparable colleagues receive coaching is a signal worth investigating. The purpose is not to accuse individual managers but to test whether discretion is producing equitable outcomes.

Reviewing the language of objectives

Written objectives are cultural artefacts. They reveal what the organisation values and what it assumes. Pull a sample of objectives from both informal support plans and formal PIPs, and read them side by side. Look for vague trait language: 'resilience', 'executive presence', 'attitude', 'gravitas', 'team fit'. These terms are difficult to evidence and easy to apply selectively. They also tend to disadvantage people whose communication styles, accents, working patterns or caring responsibilities differ from an unspoken norm.

Compare them with objectives that describe observable outcomes: completing a project to an agreed standard, meeting a defined service level, demonstrating a specific skill after training. The latter are fairer because they can be assessed and supported. A useful test is whether the objective could be evidenced by someone who had never met the employee. If it could not, it is probably doing more cultural work than developmental work.

Testing whether support is equivalent

Before any formal plan is signed, ask what support was offered beforehand and whether it was genuinely available. Training, mentoring, reasonable adjustments, workload relief and clearer priorities are all forms of support. They should not depend on a manager's personal commitment or on an employee's willingness to ask twice.

Review a sample of cases and record what was offered, when, and whether it was taken up. Where support was declined, note why. Where it was unavailable, record the reason. The question is not whether every employee received identical support, but whether comparable employees in comparable circumstances had equivalent access to it. A pattern in which some staff received six months of coaching and others received a formal warning after four weeks is a pattern worth explaining.

Questions to ask before signing off any improvement plan

Before approving a PIP, a leader should be able to answer the following without hesitation:

• What support was offered before this point, and what evidence exists that it was available?
• Would a colleague in the same role, with the same manager and the same resources, have received the same treatment?
• Does the plan describe observable behaviour and outcomes, or does it rely on subjective judgements about attitude and fit?
• Are the objectives within the employee's control, and have they had a genuine opportunity to shape them?
• Are reasonable adjustments, flexible working arrangements and caring responsibilities built into the plan rather than bolted on afterwards?
• What does success look like at each review point, and who is responsible for providing the support needed to reach it?
• Has a decision about the eventual outcome already been made, and if so, what is the plan actually documenting?

From documenting failure to designing recovery

A performance improvement plan can be a genuine recovery framework or a carefully worded exit document. The difference is rarely found in the template. It is found in the support that preceded it, the language used within it, and the honesty of the review that follows.

Auditing the pre-PIP stage is not about lowering standards or making it impossible to address poor performance. It is about ensuring that the route into support is as fair as the route out of it. Organisations that track who receives coaching, who receives a formal plan and who quietly leaves will learn more about their culture than any engagement survey can tell them. The aim is not fewer PIPs. It is fewer people arriving at one without ever having been offered a fair chance to flourish.