United Kingdom version. Written for UK workplaces: Acas guidance on appraisals, the line between development and formal capability, the right to be accompanied at formal meetings, and defensible records. US version
Performance Review Checklist (UK)
Separate development from capability. The moment a review becomes a performance concern, the Acas process and written records start to matter legally.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Performance Review Checklist?
There are two conversations that look similar and are legally different. A development review is about growth and has no particular form. A performance concern that could eventually lead to dismissal engages a capability process, where Acas guidance on fairness, written warnings, reasonable improvement periods and the right of appeal becomes the standard a tribunal measures against.
The failure mode is sliding from the first into the second without saying so. An employee who has had four friendly reviews and then receives a final written warning has a strong argument that the process was unfair, regardless of whether the underlying concern was genuine. Saying explicitly "this is now a performance concern and here is what happens next" protects everyone.
The right to be accompanied applies at formal disciplinary and grievance meetings by a colleague or trade union representative, and offering it before it is requested signals that the process is being run properly.
- Separates development reviews from formal capability procedures
- Follows Acas guidance on fairness, warnings and improvement periods
- Covers the right to be accompanied at formal meetings
- Includes reasonable adjustments and protected-timing risks
- Tick, reword and delete items, then export as a Google Form, PDF, CSV or Markdown
Updated
How to use the Performance Review Checklist
- Decide and say explicitly whether this is development or a formal performance concern.
- Where it is formal, follow the Acas steps, offer the right to be accompanied and set a reasonable improvement period.
- Consider reasonable adjustments before any capability step where disability may be relevant.
- Record what was discussed, agreed and offered, and send it to the employee to correct.
- Separate past-performance assessment from pay decisions and from development planning.
Worked examples
Four friendly reviews then a final warning
Input
Process section, Essentials only
Output
Formal stage restarted with explicit notice
Sliding from development into capability without saying so makes the process unfair even where the concern is genuine, so the fix is to name the stage clearly.
Performance dipped after a disability disclosure
Input
Adjustment items
Output
Reasonable adjustments considered before capability
The duty to make adjustments applies first, and running a capability process over performance affected by a missing adjustment is both unfair and discriminatory.
Formal meeting arranged
Input
Representation items
Output
Right to be accompanied offered in writing
The right applies at formal disciplinary and grievance meetings, and offering it unprompted demonstrates the process is being run properly.
Pay, feedback and development in one hour
Input
Structure items
Output
Split into separate conversations
Where all three happen together the employee hears the pay outcome and little else, so genuine development discussion does not take place.
Background and insight
Good records are the difference between a defensible decision and an indefensible one, and they are cheap to keep: what was discussed, what was agreed, by when, and what support was offered, sent to the employee afterwards so they can correct it. A note the employee has seen and not disputed is worth far more than a manager’s recollection a year later.
Where underperformance may relate to a disability, the duty to make reasonable adjustments applies and should be considered before any capability step. Managing out an employee whose performance dipped because an adjustment was never made is both unfair and discriminatory, and it is a common pattern.
The same applies to performance concerns arising around pregnancy, maternity, caring responsibilities or after raising a grievance or a whistleblowing concern, where the timing itself invites an inference and the process needs to be visibly fair.
On the content of reviews, the UK-specific practice worth adopting is separating assessment of past performance from pay decisions and from development planning. Where all three happen in one conversation, the employee hears only the pay part, and genuine development discussion does not happen.
For the employee side, preparation changes outcomes: a written record of what you delivered with numbers, the things that blocked you and what you asked for, and specific questions about what good looks like at the next level. Arriving without evidence means the review is conducted on your manager’s memory, which is selectively weighted towards recent events.
Grievances and reviews interact badly when a grievance is raised in response to a performance process. Acas guidance is that the processes may need to run separately or be paused, and handling that sequence well is what keeps a later tribunal narrow.
Finally, for a manager, the honest test for whether a review is any good: does the employee know what to do differently on Monday, and would an outsider reading the notes reach the same conclusion from the evidence recorded? If not, the review has produced a feeling rather than a decision.
Common use cases
A normal development review
Structure that produces a decision, not a feeling.
A genuine performance concern
Naming the stage and following Acas.
When disability may be relevant
Adjustments before capability.
Preparing as the employee
Evidence rather than your manager’s memory.
Tips and limitations
- Say which conversation this is. Sliding between them is what makes it unfair.
- Send your notes to the employee so they can correct them.
- Consider adjustments before capability, not after.
- Offer the right to be accompanied before it is asked for.
- Keep pay out of the development conversation.
Sources and further reading
- Performance management, Acas. Appraisals, capability procedures and improvement plans
- Dismissals, Acas. Fair process, warnings and the right to be accompanied
- Equality and Human Rights Commission, UK Government. Reasonable adjustments and discrimination in employment
Frequently asked questions
What is the difference between a development review and a capability process?
A development review is about growth and has no required form. A formal performance concern that could lead to dismissal engages a capability process, where Acas guidance on written warnings, reasonable improvement periods and appeals becomes the measure of fairness.
Can I move straight to a formal warning?
It is risky. An employee who has only had positive reviews and then receives a formal warning has a strong unfairness argument, so the process should be named explicitly when it changes, with the concern, the standard and the consequences set out.
When does the right to be accompanied apply?
At formal disciplinary and grievance meetings, where the employee may be accompanied by a colleague or a trade union representative. Offering it before it is requested is good practice and evidences a properly run process.
What if underperformance relates to a disability?
The duty to make reasonable adjustments applies and must be considered before any capability step. Running a performance process over a dip caused by a missing adjustment is both procedurally unfair and potentially discriminatory.
What records should a manager keep?
What was discussed, what was agreed, by when, and what support was offered, sent to the employee afterwards so they can correct it. A note the employee has seen and not disputed carries far more weight than recollection later.
Should pay and performance be discussed together?
Better separately. Where assessment, pay and development all happen in one conversation the employee hears the pay outcome and retains little else, which means the development discussion effectively does not happen.
Is there an in-depth guide to the Performance Review Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.