• What we offer
  • Who we serve
  • Resources
  • Pricing
  • About

Build a Performance Improvement Plan Record That Lasts

Professional header image for informative article: Build a Performance Improvement Plan Record That Lasts

A performance improvement plan rarely fails in the meeting room. It fails in the file.

Six months on, few people remember which targets were agreed, what training was offered, or what was said at the first review. What survives is the written record, and that is what a manager, an HR team, or an employment tribunal will read. A performance management policy sets the framework, but the paper trail built inside it decides whether the process holds up.

This tutorial shows you how to build a PIP record that lasts. We open with why a PIP is judged on the paper trail, then set out what your performance management policy should require and the minimum steps a fair process must show. From there, four practical stages follow: recording the concern with dated examples, setting objectives and a timescale in writing, logging support, training and reasonable adjustments, and writing every review as a dated entry. You will also find worked examples of strong entries, guidance on how performance appraisals feed the record, and notes on data protection, retention and access.

Why a Performance Improvement Plan Is Judged on the Paper Trail

A performance improvement plan is only as strong as the record behind it. By the time a dispute or tribunal claim arrives, nobody recalls the tone or detail of a conversation from six months earlier. What survives is what was written down.

Acas guidance on dismissals for capability or conduct expects evidence of poor performance and of steps taken to support improvement. A structured plan should hold exactly that. Written records are a core discipline principle: the Acas guide Discipline and grievances at work includes a “Keeping written records” section, with appendices covering absence and the basic principles of the Data Protection Act 2018 and Equality Act 2010. The Acas code is not legally binding, but tribunals consider whether it was followed when judging fairness, so the quality of notes carries real consequences.

Capability dismissal should be a last resort. The record must show improvement was genuinely supported and monitored before that point, the same rigour an audit-ready employee file demands.

What Your Performance Management Policy Should Require of a PIP

cagdw13X NUwKVwFISlFd Build a Performance Improvement Plan Record That Lasts

That record does not build itself. Your performance management policy should state when a PIP is appropriate, usually after informal coaching and regular performance conversations have not resolved the concern, and how it sits alongside the normal performance management review cycle. Acas advises trying coaching, mentoring or training before a formal procedure. Set out what must be recorded at each stage: the concern, dated evidence, objectives, support offered, every review date and the reviewer’s name. Name who owns the plan: typically the line manager for day-to-day conversations and an HR contact for the file and process. Confirm the policy is applied consistently, so similar issues are handled the same way across teams, sites and shifts. Point staff to the policy before a plan is ever needed, and keep a record that it was issued and read.

The Minimum Steps a Fair Performance Process Must Show

A policy sets the expectation; the process must then show it was followed. Explain the performance issue clearly, whether at an appraisal or in a separate meeting, and record when and how it was explained. Offer training, coaching or mentoring before concluding that the standard has not been met.

State what good looks like: minimum targets, defined outputs, agreed deadlines. Then supply adequate resources to do the job. If training, tools or time were missing, note that, because it explains the shortfall. That mirrors a wider principle: performance is not measured once a year.

Where capability is linked to a disability, do all you reasonably can to support the person first under the Equality Act 2010, and record the adjustments considered, the adjustments implemented and any alternative roles checked. Anything left unrecorded did not happen, as far as a later review is concerned.

Step 1: Record the Concern With Dated Examples

With those steps established, the record begins with the concern itself. State the gap between the required standard and what actually happened in plain, observable language. “Poor attitude” or “not a team player” cannot be reviewed or answered; “three client reports missed in January and February 2026” can. This is work falling below the required standard through lack of ability, skill or knowledge.

Attach dated examples to each point: a deadline missed on a named date, work returned for rework, or a colleague or customer complaint referenced by date. Note the source of every example, whether a system report, a training record tracking a lapsed certificate, a client email or a supervisor’s observation, so it remains traceable later.

Leave out anything unverifiable or dependent on memory alone. If you cannot date it, question whether it belongs in the file.

Finally, share the concern with the employee and record that you did: the date, the format of the meeting and who attended.

Step 2: Set Objectives and a Timescale in Writing

Next, translate the concern into measurable objectives: state what must be true by the review date and how it will be measured. Objectives should be specific and achievable. “Respond to customer queries within two working days” is straightforward to review; “improve communication” is not. Each objective should trace back to the recorded concern and name the standard required, such as minimum targets, the point tribunals look for when judging fairness (clear standards and minimum targets).

Record the agreed review period in writing: start date, every review date and the end date, as agreed with the employee. Confirm they received a copy of the plan and note their comments, including any disagreement with the objectives, in the file. That keeps the record honest and reviewable, so you can later answer did those objectives actually go anywhere?.

If objectives change mid-plan, record the change, the reason and the date it was agreed, rather than rewriting the original.

Step 3: Log the Support, Training and Reasonable Adjustments

UXXP5MdTBz2eHeOmMzwTC Build a Performance Improvement Plan Record That Lasts

Once objectives are agreed, the record must show what you actually gave the employee to meet them. Log the support offered and provided, each with a date: training sessions, mentoring, shadowing, extra supervision or additional time on a task. Acas expects employers to provide adequate resources, so note what was supplied, not what was proposed.

Where a disability or health condition may affect performance, record the reasonable adjustments discussed, agreed and implemented under the Equality Act 2010. Note any alternative roles or redeployment options considered and the outcome, so the file shows what was genuinely explored.

Keep training records current. Attendance, completion dates and certificates should be producible if the plan is queried months later. The same discipline applies when recording training and leave across global teams, where local rules and entitlements add another layer; Managing Leave Across Borders: Global HR Systems That Work explains how structured records help.

Step 4: Write Every Performance Management Review as a Dated Entry

With support and adjustments logged as they happened, the review becomes the next entry in the record. Each performance management review must be a dated entry with a named reviewer, not a verbal update that depended on who happened to be in the room.

Record the outcome against each objective as met, partially met or not met, and cite the evidence behind that judgement. Capture the employee’s responses, including their reasons for missed targets and any support they asked for.

State the outcome plainly: continue the plan, extend it with new dates, change the objectives, or close it. Always set the next review date, and note in the entry that both parties received a copy of the review record.

That sequence, repeated at each review, is what turns a plan into a timeline.

Worked Examples: What Good PIP Record Entries Look Like

The formats below apply that discipline to four stages. They are illustrative examples, not drawn from a real case.

  • Concern: “Concern recorded 4 March 2026: three client reports submitted after the agreed deadline in January and February 2026 (see client emails dated 12 January and 3 February).”
  • Objective: “By 30 April 2026, submit all monthly client reports by the agreed deadline, verified against the project tracker.”
  • Support: “Reporting tool refresher completed 18 March 2026 with the internal trainer; weekly 30-minute mentoring calls agreed from 20 March 2026.”
  • Review: “Review held 15 April 2026, reviewed by the named line manager: two of two reports on time, one objective partially met; plan extended to 30 May 2026, next review 20 May 2026.”

Each entry carries a date, a measurable standard, a traceable source, and where relevant a named person. That is the discipline strong performance appraisal examples follow, and it is what makes a plan readable as evidence months later.

How Performance Appraisals Feed the PIP Record

Those entries show the standard the plan itself must meet. An appraisal is often where a performance issue is first named, so the appraisal note should be dated, specific and shared with the employee, not left as a vague summary.

When you conduct employee performance appraisals, record the evidence discussed and each agreed action with a named owner and a due date. Sharing the note also gives the employee a chance to respond, which the record should capture.

Where an appraisal identifies a persistent gap, that appraisal record becomes the opening evidence for the PIP concern. Reference it rather than rewriting it, because rewriting invites inconsistency between the two documents and breaks the timeline.

Link appraisal records and plan records, for example by quoting the appraisal date in the concern entry, so the sequence runs without gaps if the process is later reviewed.

Acas lists records of regular, fair performance reviews showing consistent issues among the evidence types associated with capability cases. That is one more reason not to file appraisal notes loosely.

Keeping the Record: Data Protection, Retention and Access

Linked records are only useful if they live somewhere permanent. Store the plan, its evidence and every review entry in one place with clear access rules, so the file cannot fragment across inboxes and local drives.

PIP documents are personal data under the Data Protection Act 2018. Collect only what you need, keep it accurate, and restrict viewing to those with a genuine need. The same discipline underpins your wider approach to security and compliance.

Set a retention period and a deletion point, and record them, rather than holding performance records indefinitely by default. Employees can request copies of their record, so the file must be producible quickly and readably.

Record-keeping and data practice are connected. The Acas guide’s appendices cover absence alongside the basic principles of the Data Protection Act 2018 and the Equality Act 2010.

What an Email Thread or Spreadsheet Cannot Reconstruct

Good retention rules keep the file in order, but they cannot rebuild the story behind it. An email thread shows fragments of a conversation, not agreed objectives, a timescale and a confirmed start date. A spreadsheet holds dates, but not the reason for each review outcome, the reviewer’s name or the support provided between reviews.

Neither format reliably answers the first question a dispute raises: what did the employer know, when did it know it, and what did it do about it? A dated, structured record answers that in sequence, from the first concern to the final review outcome.

A system built for the job holds it together. Activ People HR covers appraisals and performance management, employee records and documentation, and training records, and is configurable for small SMEs and larger corporates, including as an employee-facing front end alongside existing enterprise systems. What Changes with a Connected System sets out the practical difference a single record makes.

Conclusion: Build the Record From the First Meeting

Whichever system holds it, the record begins the moment you decide a PIP is needed. Write the concern, the dated examples and the date of the meeting on the same day, while the detail is still accurate. Agree the objectives and timescale in writing, then confirm the employee received a copy.

Log support, training and any reasonable adjustments under the Equality Act 2010 as they happen. Retrospective notes read as reconstruction, and reconstruction weakens the file.

Make each performance management review a dated entry with a named reviewer and a clear outcome: met, partially met or not met. When you conduct employee performance appraisals during a live plan, hold them to the same standard.

Finally, keep the file in one place, with retention and access rules you can explain to an employee, a tribunal or an auditor. Get the discipline right from the first meeting and the record will still stand up months later.