3 ways to automate staff performance reviews
I'm Liam Jones, founder of Pilla and a qualified management consultant. I've helped hundreds of businesses set up workflows, and in this article I'm going to show you three real examples of how to set up your performance reviews. I'll start from the simplest and then add some more powerful options.
You can open up each template in our workflow builder playground as a starting point and experiment for yourself.
If you're looking to automate this part of your operation, speak to an expert and we'll show you what it would take to set up.
The workflows at a glance
- #1 - Simple performance review. Two ratings (responsibilities and behaviours), each grouped with its own evidence, plus a closing group of forward-looking development goals.
- #2 - With guidance. The same groups, each carrying its own guidance note next to the rating or evidence it explains, so a rating means the same thing for every reviewer.
- #3 - With sign-off. The same groups, plus a manager and team-member signature in the closing group, for a record both sides signed.
Article Content
#1 - Simple performance review
Who it's for: Single-site managers running quarterly or annual reviews with a small team. An owner with 5-15 direct reports, or a single-venue manager handling annual reviews themselves.
What it is: The simplest structured performance conversation, arranged into four themed groups: Team member (name and review period), Responsibilities (a rating plus the evidence behind it), Behaviours (a second rating plus its evidence), and Development (goals for the period ahead). CIPD's research on review effectiveness shows the two things that matter most are ratings that mean the same thing across managers, and concrete evidence. Without them, reviews collapse into either a gut-feel "good job all round" or a long write-up nobody reads. Grouping each rating with its own evidence, rather than leaving them to float separately on the form, forces both.
In practice: A single-site pub owner runs annual reviews with 12 direct reports across the year. The canvas sits on their phone. Under Team member they type the name and the review period. Under Responsibilities they give a 1-5 rating on role responsibilities and write the evidence ("ran the December rota with zero gaps"). Under Behaviours they give a 1-5 rating on team behaviours and write the evidence ("calm during the December rush, talked the kitchen down twice when service backed up"). Under Development they set three goals for next quarter. The whole conversation takes 40-60 minutes.
Why it works: The ratings are clearly set at 3 = doing the role, 4 = doing it consistently well, 5 = taking on more. Each rating sits in its own group next to its evidence field, so the conversation never drifts from score to score without something concrete behind each one. The development goals are capped at three, and the team member has to own them.
Steps included:
- Team member: name, review period
- Responsibilities: a 1-5 rating plus the evidence behind it
- Behaviours: a 1-5 rating plus the evidence behind it
- Development: goals for next period (checklist, 3 items)
#2 - With guidance
Who it's for: Multi-site businesses with 3+ reviewers, organisations where ratings have been creeping upward, or teams that hold a review-comparison meeting after the individual reviews.
What it is: The same four groups, each now carrying its own guidance note next to the field it explains. The Responsibilities group carries "Anchor against the job description" above the rating and "Specific examples with dates" above the evidence; the Behaviours group carries "How they show up" above the rating and "Real examples, said face to face" above the evidence; the Development group carries "Three, ownable, with a date" above the goals checklist. The anchors come from CIPD's guidance on keeping ratings consistent: 3 means doing the role to standard, 4 means doing it consistently well over a long stretch, 5 means taking on more than the role asks for.
What it adds to the simple performance review:
- A guidance note inside every group, not a generic panel at the top of the form
- Different managers' 4s become the same 4
- Evidence becomes specific and dated, not just adjectives
- The Behaviours group stops rewarding "being nice" over how someone actually shows up
Why it works: Generic guidance at the top of a form gets skimmed once and forgotten by the second rating. Guidance placed inside the group it belongs to gets read at the point the manager is actually filling in that score, so a 4 from the strictest manager means the same as a 4 from the most generous one, and the comparison meeting becomes a discussion about evidence instead of what each manager meant.
Steps included:
- Team member: name, review period
- Responsibilities: a 1-5 rating plus evidence, with 2 guidance notes on anchoring the rating and dating the evidence
- Behaviours: a 1-5 rating plus evidence, with 2 guidance notes on how they show up and citing real examples
- Development: goals for next period, with 1 guidance note on keeping them owned and dated
#3 - With sign-off
Who it's for: HR-led organisations that run capability processes, multi-site groups that have faced unfair-dismissal claims before, and anywhere a tribunal might later look at whether the review was genuinely fair.
What it is: The same four groups, plus a manager signature and a team-member signature added inside the Development group, next to the goals they both just agreed. The two signatures turn the canvas from a manager's record into a record both sides signed, which is what tribunal hearings often treat as best-practice evidence of a fair process.
In practice: Take a 50-site care provider with quarterly performance reviews across 800+ team members. Their HR team defends roughly 6-12 capability cases a year, and each one might be challenged at a tribunal. Before sign-off, the review record was a manager's tick-list with no confirmation from the team member. After sign-off, the Development group closes with a manager signature committing to the rating and goals, and a team-member signature confirming they agree the review happened as recorded. If the team member later claims they were never told what they needed to improve, that signature on the timestamped canvas is the answer.
What it adds to the simple performance review:
- Manager sign off: a clear commitment to the rating and development goals, which holds up against later challenges
- Report sign off: proof the team member saw and agreed the review happened as recorded, which is key for capability cases and tribunals
- Both signatures sit inside the Development group, next to the goals they confirm
Why it works: A review with two signatures is a record both sides signed, taken at the time of the review. That is what a tribunal treats as evidence of a fair process, rather than a manager's word with nothing to back it.
Steps included:
- Team member: name, review period
- Responsibilities: a 1-5 rating plus the evidence behind it
- Behaviours: a 1-5 rating plus the evidence behind it
- Development: goals for next period, plus a manager sign off and a report sign off
How to pick the right version
You don't need to know our product to choose. Every version here is the same four-group review; the additions change who can run it consistently and what the record proves.
Is it just you reviewing, or several managers?
If you run every review, a 4 means whatever you mean by it. The moment several managers review, a 4 from one has to mean the same as a 4 from another, or the scores don't compare. If it's just you, #1 is enough. If several managers review and you worry their ratings don't line up, #2 puts the anchors inside each group.
Do you need proof, or is a record enough?
A written review tells you what was said and by whom. Proof is something you can put in front of a tribunal if a capability case is ever challenged. If a record is enough, stop at #1 or #2. If you need both sides to have signed off on it, #3 adds the two signatures.
Need both the guidance and the sign-off? Open #3 in the playground and add the guidance notes from #2. That is how the product works anyway: every option here is the same review with steps added.
Related workflows
- One-to-ones - the weekly routine that feeds the bigger review
- Onboarding - the first-week structure that informs the first review
- Interviews - the structured hiring conversation that started the relationship
Conclusion
A performance review is only useful when ratings mean the same thing across managers and the evidence is solid. When ratings don't line up, they tend to creep upward. When ratings rest on memory alone, they're easy to dispute. Businesses running Performance Review #3 tie every review to a record both sides signed.