Running the Appraisal Cycle Without Chasing Reminders
Your review form is not the problem. Completion is. When deadlines sit in spreadsheets, reminders depend on memory, and HR becomes the default chase function, even a well-designed performance management process stalls. The fix is not more email nudges. It is a workflow that carries the sequence for you.
Acas guidance points to regular reviews and written records, so completion matters for compliance as well as culture. This post focuses on the operational layer: the dates, nudges, visibility and ownership rules that keep reviews moving.
In this guide, you will learn how to build a dated cycle calendar with a deadline for every stage, set automatic nudges for reviewers and reviewees, and give HR a completion view they can act on. You will also define what happens when a manager changes role mid-cycle, spot when a chase should become a supportive conversation, and configure the performance management process once so the chasing stops. The aim is simple: predictable reviews, clearer records, and less manual follow-up for HR.
Why performance management cycles fail on completion, not the form
Most HR teams can produce a polished appraisal form. Far fewer can describe the end of the performance management cycle without a scramble. The failure is rarely design; it is timing and ownership. Treat completion as the metric you manage.
Acas advises regular performance reviews for anyone with employee status, at least once a year as good practice, and says a written record of what was discussed should be shared with the employee afterwards. An unfinished review therefore leaves a documentation gap as well as a management gap. The obligation is the conversation and the record, not the form.
Objectives matter too. Acas recommends SMART objectives with a reasonable time frame; its worked example sets the next review three months out, with progress picked up in regular check-ins. Dates only work if someone owns them. Formal reviews are also meant to sit alongside feedback, coaching and one-to-ones, so a chase workflow is scaffolding, not a replacement. See how to check performance conversations are happening between cycles.
Every stage in the performance management process needs four things: a named owner, a start date, a deadline and a visible status. Remove any one and chasing becomes somebody’s side project. Build that discipline into absence planning too, as set out in Day-One Statutory Sick Pay: Rebuilding Your Absence Rules, because reviewer availability drives stage dates.
Build a dated cycle calendar with a deadline per stage
Break the performance management cycle into six named stages: reviewee preparation and self-review, objective setting, reviewer write-up, moderation or calibration, the feedback meeting, and sign-off with the record filed. Give each one a single owner, a start date and a hard deadline. A lone end-of-cycle date tells nobody what to do this week.
Work backwards from the feedback meeting:
- Set the feedback meeting date first. Everything else schedules around it.
- Place preparation and self-review deadlines ahead of it, allowing the reviewer time to read the input before drafting.
- Set the reviewer write-up deadline so no manager is writing on the morning of the meeting.
- Book moderation or calibration before the meeting, not after.
- Close with sign-off and filing. Acas advises keeping a written record of the discussion, shared with the employee afterwards.
Publish the calendar before the cycle opens, so managers and employees can plan around annual leave, peak trading periods and project deadlines. Performance is not measured once a year, and a dated calendar is what keeps the cycle moving between check-ins.
For international or multi-site teams, check stage dates against local leave patterns. Statutory balances such as ROL in Italy, RTT in France and seniority-based leave can empty a week of reviewers, so build buffer into those stages. The same principle applies to the value of a date that warns ahead of time: the deadline’s worth is the notice it gives you.
Set next cycle’s dates at this cycle’s meeting, with a review date recorded for each objective as Acas recommends for SMART objectives, so the calendar is agreed rather than negotiated later.
Set nudges for reviewer and reviewee at each step
With the calendar agreed, the next task is configuring the prompts that run against it. Treat nudges as a sequence, not one reminder: a pre-warning a few working days before the deadline, a due-date prompt, a short grace-period notice, then escalation to HR. Present these timings as a recommended design choice. No published guidance prescribes lead times, grace periods or wording, and the CIPD’s evidence review on performance feedback explicitly excludes automated feedback from its scope.
Trigger prompts by stage and role, not by individual. The reviewee receives preparation prompts; the reviewer receives write-up and sign-off prompts; HR sees that both were sent. This mirrors the trigger logic many teams already apply to absence, set out in Five questions to ask about your absence triggers today.
Write different messages for each audience. The employee needs to know what to prepare and by when; the manager needs to know what is outstanding and who is waiting on them. Keep early prompts neutral and factual, because feedback can harm performance as well as improve it, so the first message should inform rather than judge. Save firmer language for the HR escalation stage.
Do not fire the first nudge on the morning of the deadline. People need several working days to act, or the prompt simply documents the problem. Automating the sequence stops reviewers chasing peers and HR sending blanket emails, freeing capacity for priorities such as the 2026 Budget’s implications for HR teams. HR then needs one view of where the cycle actually stands.
Give HR a completion view they can act on
Once nudges are automated, HR needs one screen showing every review in the cycle by status: not started, in progress, submitted, meeting held, signed off and overdue. Filter and sort by manager, department, site and stage. That tells you where the cycle is genuinely stuck rather than prompting another blanket email.
Show the age of each overdue item, not just a red flag. A two-day slip calls for a nudge; a three-week stall calls for a conversation. Use the view to target support, not blame. A manager with twelve outstanding reviews may need workload freed or coaching, not another reminder.
Keep the audit trail of who completed what and when, so the written record Acas advises you keep can be produced without chasing managers for notes. The view should also prompt the right question: Don’t just report the numbers. Ask what they mean. A cluster of overdue reviews in one team tells a different story from a single late form.
Where a front-end HR system feeds enterprise systems, check that sign-off status reconciles with the master record. This is a configuration point to confirm with your provider, not an automatic outcome. Because a completion view holds personal performance data, keep monitoring transparent and proportionate, telling employees what is tracked and why: monitoring performance.
The same view also exposes the gap when a manager changes role mid-cycle.
Define what happens when a manager changes role mid-cycle
The completion view shows what is stuck. It will also expose reviews whose named reviewer has moved on, so agree the handover rule before the cycle opens. Treat this as a design choice: Acas advises keeping a shared written record of the discussion, but it does not prescribe a handover rule. Set one that fits your structure and apply it consistently.
Your rule should cover the reviewer who leaves, moves role, is promoted, or takes long-term leave with reviews still open. Route unfinished reviews to a named fallback, such as the new line manager, the next-level manager or HR, with a reassignment deadline attached. Unowned reviews are the ones that quietly expire.
Transfer the evidence, not just the task. Notes, objectives and check-in comments should move with the review so the incoming reviewer is not starting from a blank page weeks before sign-off. Tell the employee what has changed and who now holds their review, so a mid-cycle switch does not read as a judgement on their performance.
Do not reassign health and capability matters automatically. Flag them to HR instead. Acas advises understanding the cause before responding, and reasonable adjustments must be considered where a condition may amount to a disability.
With that rule written down, the next question is when a missed deadline should become a conversation rather than another reminder.
Know when a chase should become a conversation
Reassignment fixes the process problem; it does not explain why the review stalled. Treat a missed deadline as either an administrative slip or a signal, and work out which before escalating. A manager who is simply short of time responds to a nudge; one avoiding a difficult conversation does not.
Acas distinguishes capability from conduct and advises employers to establish the cause before responding, so a stalled performance management review is a prompt to diagnose, not an automatic disciplinary step. Where a condition may amount to a disability, consider reasonable adjustments before any disciplinary action is taken against either the reviewer or the reviewee.
A practical escalation pattern, presented here as a design choice rather than a sourced rule, runs in three steps:
- An HR nudge, factual and dated.
- A direct conversation with the manager, asking what is blocking the review.
- A decision on the review itself: reassign it, extend it with a new date, or appoint a temporary reviewer.
For managers who repeatedly stall, offer coaching and one-to-ones rather than firmer reminders. Formal reviews work best alongside regular feedback and check-ins, and repeated difficulty with the conversation usually needs support, not sanction.
Then cap the sequence. After the escalation point, the review is either completed or formally rescheduled with a recorded reason. An open loop that runs indefinitely is exactly what turns chasing into a permanent job.
Configure the performance management process once
With the escalation rule agreed, the final design task is to build the whole sequence into your HR system so it runs without manual intervention.
Set up the cycle template, stage dates, nudge sequence, escalation point and completion view rules once. In later cycles you adjust dates only, rather than rebuilding the performance management process. Store the calendar as a cloneable template, so the performance management cycle does not depend on one person’s diary and survives a change of HR lead.
Before going organisation-wide, pilot the sequence on one department, one stage and one cycle. Check that prompts reach the right roles: employee, reviewer and HR. Then assign a named owner to every stage in the system, as set out at the start of this guide.
Scale the approach honestly. A large corporate may need every stage automated and reconciled with an enterprise system, while a small team may need only a shared status view and two diary checkpoints a week. See how Activ People HR can help with that configuration. The test is simple: has chasing stopped being a separate job?
Conclusion: stop chasing, start configuring
Configured once, the performance management process stops depending on someone remembering to chase. Before your next cycle opens, draft the stage calendar, give every stage one owner and one hard deadline, and publish it so managers and employees can plan around it, with the nudge sequence you configured doing the prompting.
Build the completion view before the cycle starts, not after it stalls, and use it to direct support at the managers who are genuinely behind rather than emailing everyone.
Finally, write down the manager-change rule and the escalation rule, tell employees what both mean, and decide in advance when a reminder should become a conversation. That is the point at which chasing stops being a second job and the performance management cycle starts running itself.