More than half of those responsible for UK organisations with fewer than 10 employees reported having no appraisal system, or one that applied to nobody, in CIPD's 2023 People Management and Productivity Report. Yet installing a review form isn't the same as managing performance.
A performance management review should connect expectations, evidence, feedback and development. Its real test comes afterwards: does the employee receive the promised support, see a credible route to progression and understand what happens next? For HR teams, the overlooked work is often the 30 to 90 days after the meeting, not the meeting itself.
Table of Contents
- How a Performance Review Works as a Cycle
- Setting Objectives That Link to Strategy
- Choosing a Review Cadence and Feedback Rhythm
- Running the Review Conversation Step by Step
- Calibrating Ratings Fairly Across Teams
- Turning Review Data Into Development Plans
- Common Failure Points and How to Fix Them
- Speak to an HRManagement365 specialist
How a Performance Review Works as a Cycle
Only 48% of employees had basic performance management involving specific job objectives, and just 28% experienced systematic performance management combining objectives, monitoring, feedback and accountability, according to the CIPD UK figures accompanying Acas performance management guidance. A useful performance management review is therefore a recurring control cycle, not an isolated annual conversation.
Acas recommends reviewing objectives, behaviours and development-plan progress, keeping a written record and supporting formal reviews with regular coaching and feedback. Put that into practice through this sequence:
- Agree role-relevant SMART objectives. Make them specific, measurable, achievable, relevant and time-bound. Employees should understand both the result expected and why it matters.
- Define the evidence and review dates before work starts. Agree which records demonstrate success and who maintains them.
- Monitor progress through regular one-to-ones. Use the conversation to remove blockers, not just collect updates.
- Give specific, behaviour-based feedback. Describe the action and its impact rather than attaching a personality label.
- Document achievements, barriers and support. Record development actions alongside results so managers remain accountable for their commitments.
- Revisit objectives when workload or business priorities change. Preserve the original agreement and the reason for changing it.
The cycle keeps development connected to everyday work.
Make the cycle operational
Consider a mid-sized UK services company using a 12-month review year. As a proposed operating model, it could agree objectives at the start, capture delivery evidence throughout the year and use scheduled checkpoints to approve changes before the final assessment.
In a configured HRManagement365 process, objective fields, evidence attachments, manager sign-off and overdue reminders can support that sequence. These are implementation choices to agree against the customer's policy, not a reason to impose unnecessary administration.
Practical rule: Capture enough evidence to explain a decision, not enough paperwork to reconstruct every working day.
Score your current process against these six stages. Start with the weakest stage rather than redesigning every form at once.
Setting Objectives That Link to Strategy
In the 2014 CIPD Employee Outlook survey of 2,153 UK working adults, 63% of employees reviewed annually understood how their objectives fitted organisational strategy, compared with 44% reviewed less frequently or never. The survey is old and shows an association rather than proof that reviews caused the difference, but the practical lesson stands.
Managers have to translate company priorities into work employees can influence. Start with the organisational outcome, identify the team's contribution, then agree the individual responsibility. Apply the SMART discipline instead of copying corporate slogans into personal objectives.
Weak objectives rewritten as reviewable objectives
These are illustrative targets to adapt by role, showing format rather than fixed standards.
| Weak objective | Reviewable objective | Evidence to record |
|---|---|---|
| Improve customer service | Reduce average first-response time to under four working hours by 30 September | Service desk timestamps and two quarterly customer feedback samples |
| Be a better team player | Complete two cross-team handovers each quarter using a written checklist agreed with the receiving team | Signed handover checklists and receiving-team confirmation |
| Hire more staff | Fill the five open Leeds engineering vacancies by 30 September, tracking offer acceptance at each stage | Recruitment pipeline records and offer decision dates |
| Keep HR records up to date | Complete contract and onboarding records for every new starter within five working days of their start date, with right-to-work checks completed before the start date | System timestamps and a monthly exception report |
On that final row, right-to-work checks must be completed before employment begins under the applicable pre-employment requirements. The five-day target covers contract and onboarding paperwork only. A post-start administrative deadline is never permission to defer a required check.
Complex work needs objectives that describe contribution rather than count activity. An integration specialist might need an objective covering accepted design decisions, testing quality and operational handover. A tally of completed tickets says nothing about whether the work held up.
Lincolnshire County Council's appraisal guidance uses three to six SMART objectives. That is a workable starting range. A longer list lets routine duties crowd out the priorities that need attention.
Check objectives before approving them
- Strategic connection: Can the employee explain which team or business outcome the objective supports?
- Control: Can they influence delivery, and are dependencies recorded?
- Evidence: Does the measure have an identifiable source rather than a manager's impression?
- Timing: Is there a delivery date and an agreed point to revisit assumptions?
- Quality: Could someone hit the target while producing an unacceptable result?
What the next 30 to 90 days should show
An objective approved in January and ignored until December was never really an objective. Book the first progress conversation within 30 to 90 days of the review and record what it produces: which priorities shifted, which dependencies surfaced, what support was needed. Then compare what changed afterwards. If engagement, internal progression and retention look identical whether objectives were well set or poorly set, the process is producing paperwork rather than performance, and counting completed review forms will never reveal that.
For organisations using objectives and key results, Ekipa's practical OKR guidance for enterprise leaders gives a useful structure for aligning team goals with company priorities. For employee-level implementation, the HRManagement365 guide to performance management objectives shows how to turn priorities into reviewable commitments.
Choosing a Review Cadence and Feedback Rhythm
Cadence works in layers, rather than through one meeting carrying every purpose. Frequent operational conversations and formal assessments need different agendas.
The following is a proposed rhythm to adapt by role, not a requirement to add every meeting to every diary.
Review rhythms and what each one is for
| Rhythm | Main purpose | Content to cover | Common risk |
|---|---|---|---|
| Weekly or fortnightly one-to-one | Monitor progress and remove blockers | Action updates, workload, support needed | Becomes a status meeting with no development talk |
| Monthly check-in | Keep new starters and fast-moving roles on track | Early objective progress, feedback on recent work | Skipped when workloads peak |
| Quarterly review | Adjust objectives and capture evidence | Progress against measures and behaviours | Objectives drift if no notes are kept |
| Six-monthly checkpoint | Mid-year check on results and impact | Evidence of results, agreed mitigating factors | Treated as optional by managers |
| End-of-year review | Final assessment and rating | Evidence per objective, rating and development plan | Ratings appear with no earlier feedback to support them |
A layered timetable helps distinguish immediate support from longer-term assessment.
A public-sector model can combine quarterly conversations with a final rating recommendation. Another workable pattern uses a mid-year checkpoint and an end-of-year assessment, with evidence and mitigating factors recorded at both. Choose the pattern that supports decisions without duplicating conversations.
What if a manager is inconsistent or absent?
In a survey of 2,003 UK employees, 38% said their manager didn't regularly set targets and 34% said their progression wasn't regularly reviewed, while 43% of HR professionals expected line managers to own performance management, according to People Management's report. Ownership on an organisation chart plainly isn't enough.
Give HR a practical intervention route:
- Set minimum evidence standards for objectives, feedback and agreed support.
- Invite employee self-input so an absent manager doesn't leave an empty record.
- Use skip-level calibration and manager prompts to resolve missing observations.
- Escalate missing goals or development discussions to a named accountable leader.
Record why any cadence exception is reasonable. Flexible, remote, part-time and project-based employees shouldn't receive weaker assessments just because their work is less visible.
Microsoft Teams messaging and Power Automate workflows are standard Microsoft capabilities that HRManagement365 can configure into reminders and escalation processes. The configuration must account for permissions, connectors and licensing. A prompt can initiate a conversation; it can't conduct one.
Running the Review Conversation Step by Step
A well-run meeting compares agreed expectations with evidence, then produces decisions the employee can act on. The rating recommendation isn't the final rating until calibration has checked consistency.
Use the following as a recommended meeting protocol, with timings adapted to your policy.
- Prepare. Ask both parties to gather objectives, one-to-one notes, delivery evidence and a written self-assessment at least five working days ahead. Share the material rather than keeping a private manager dossier.
- Open by explaining the purpose, the time available and whether this is a developmental discussion or one linked to pay. Don't let the employee discover the stakes halfway through.
- Review results against the agreement. Work through each objective using its measure and evidence. Distinguish an unmet target from an objective that became obsolete.
- Discuss behaviours using specific examples of a strength and a gap. Explain what happened, its effect and what the employee should continue or change.
- Listen and record. Invite the employee's explanation, including barriers and missing support. Record disagreements accurately instead of forcing artificial agreement.
- Agree two or three development actions, each with an owner, a date and a follow-up appointment. Check that the manager has authority to provide the promised support.
- Close with a written summary in the same week. Separate agreed facts, disputed points, proposed ratings and next actions.
Use feedback without turning it into a vote
Stakeholder input can help where a line manager doesn't observe the work directly. The HRManagement365 guide to 360 feedback questionnaires can help structure questions around observable contribution rather than popularity.
Don't introduce an established performance concern for the first time during the formal review. If new evidence emerges, give the employee time to consider it before reaching a decision.
An employee can acknowledge receiving the review without agreeing with every judgement in it.
Calibrating Ratings Fairly Across Teams
Sales volume, absence and call counts can all mislead when separated from quality and context. A fair rating needs several kinds of evidence, with managers able to explain how they weighed them.
A salesperson inheriting a mature account portfolio and a colleague building a new territory may produce different totals without demonstrating different levels of capability. Calibration should test the interpretation, not just compare the numbers.
Evidence sources for a fair rating
| Evidence source | What it shows | Main limitation |
|---|---|---|
| Objective attainment | Results against agreed measures | Ignores quality and context if used alone |
| Documented behaviours | How the work was done | Depends on the quality of manager notes |
| Employee self-assessment | Employee view of impact and blockers | Can be inflated or understated |
| Peer or stakeholder examples | Impact across teams | Harder to gather for remote or project roles |
| Contextual constraints | Staffing, systems or priorities that affected delivery | Needs a dated, written record to be credible |
The UK Senior Civil Service performance-management framework provides a concrete model: objectives and behaviours are reviewed at least quarterly, with the final quarterly conversation supporting a rating recommendation using bands including Exceeding, High Performing, Achieving and Partially Met. It applies to the Senior Civil Service, not all UK employers.
A private employer can choose its own scale. What matters is that each band has clear anchors describing results and behaviours, not adjectives that every manager interprets differently.
Test judgement before approving ratings
For a pilot, ask managers to bring two or three anonymised examples per proposed rating band. Have the group test each example against the anchors, challenge unsupported assumptions and record why a recommendation changes.
A skip-level reviewer should examine outliers and unexplained differences between teams. Don't force a distribution just because the chart looks untidy: a rating pattern is a prompt for investigation, not proof of bias or accuracy.
UK governance should include consistent criteria, relevant reasonable adjustments under the Equality Act 2010, an employee opportunity to respond and checks for unequal outcomes. Obtain appropriate employment-law advice where ratings affect formal capability, reward or dismissal decisions.
EU employers must consider GDPR requirements when deciding what review data to collect, who can access it, and how long to retain it. Employee-record requirements also vary by member state; a UK retention policy should not be copied across EU operations.
Start with a calibration pilot in one team. Test whether another manager can understand the evidence and reach a defensible judgement before extending the process.
Turning Review Data Into Development Plans
A survey of 2,000 UK white-collar professionals found 35% felt less optimistic about their role after their latest appraisal, while only 16% felt more positive, according to People Management. Completing the meeting therefore isn't a sufficient measure of success.
The development plan should make the next conversation concrete.
Manage the period after the review
Use this recommended recovery workflow when an appraisal leaves uncertainty or frustration:
- Document agreed actions within two working days. Name the employee's commitments and the manager's support obligations.
- Separate development conversations from pay decisions where possible. Explain who decides pay and when, rather than implying that training resolves a salary concern.
- Schedule a follow-up within a month. Check whether support arrived and whether the employee understands the outcome.
- Provide a route to challenge unclear evidence or inconsistent ratings, with a named reviewer and a recorded response.
Each development action should connect a skill, business objective and completion date. For example, an employee learning requirements analysis could shadow a workshop, lead a supported session and submit an accepted requirements document. Attendance alone wouldn't demonstrate application.
Use HRManagement365's development planning examples to distinguish learning activities from evidence that someone can perform the work.
The accompanying video can sit alongside the development discussion.
Measure follow-through, not just completion
A proposed Power BI dashboard should connect process measures with employee outcomes:
- Review completion and overdue actions: Identify unfinished conversations and undelivered commitments.
- Rating distribution by team: Flag patterns requiring calibration.
- Development-plan closure: Check whether actions were completed with evidence, not merely marked done.
- Post-review sentiment: Ask whether expectations, fairness and support are clearer.
- Internal moves and regretted leavers: Examine progression and retention after reviews without claiming the review caused either outcome.
Microsoft Dataverse, Power Automate and Power BI provide the data, workflow and reporting foundation. HRManagement365 can configure development templates, reminders, approval routes and dashboards against a customer's policy; these are configured solutions, not a claim that every dashboard arrives pre-built.
Budget for data preparation, access controls, report definitions and manager training as well as software. More reviews alone won't help if managers lack coaching skills or authority over pay and progression.
Common Failure Points and How to Fix Them
Inconsistent scoring, weak feedback, unclear evidence and mixing development with pay deserve attention before adding more review meetings. CIPD's evidence review on performance management finds that feedback can support performance and learning but can also be detrimental when poorly delivered; employees' perceptions of fairness and usefulness matter.
Treat a missed deadline or unusual rating distribution as a diagnostic signal. HR needs to establish the cause before changing the workflow.
Review problems, causes and first fixes
| Symptom | Likely cause | First fix |
|---|---|---|
| Ratings cluster around the middle | Managers avoid difficult conversations or lack shared anchors | Run a calibration session using agreed examples for each rating band |
| Employees say the review was a surprise | No check-ins during the period | Introduce recorded monthly one-to-ones with a shared action list |
| Objectives never change | Set once at the start and not revisited | Revisit objectives at each quarterly check when priorities shift |
| Reviews stall in one team | Manager not completing reviews or notes | Send overdue reminders and escalate through a skip-level review |
| Employees challenge ratings | Evidence is unclear or not shared | Publish evidence standards and a clear route to respond or appeal |
These are starting hypotheses, not diagnoses. Investigate the circumstances before assuming manager avoidance or employee resistance.
Match the process to the work
Specific, challenging targets suit straightforward work better than complex, interdependent assignments. For a role involving discovery or adaptation, assess the quality of decisions, accepted outcomes and learning applied rather than rewarding easily counted activity.
Automation boundary: A dashboard can show that a conversation wasn't recorded. It can't establish that the manager listened well.
For a quick internal audit, set aside an hour and ask:
- Measures: Does every objective have a usable measure?
- Continuity: Are one-to-ones recorded?
- Consistency: Do team ratings match the agreed anchors?
- Transparency: Was evidence shared before the rating?
- Follow-through: Were actions due within a month closed, and do longer actions have credible progress evidence?
Choose the first fix this month based on the answers, not on which feature is easiest to switch on.
Speak to an HRManagement365 specialist
Start with the gap that costs you most: managerial practice, workflow, or reporting. A useful check is whether objectives carry measures, dates and evidence sources; whether one-to-one notes shape the review; and whether you can see completion beside engagement, progression and retention for the 30 to 90 days after each meeting.
HR Management 365 is built on Microsoft Power Platform and integrated with Microsoft 365 and Dynamics 365. Performance objectives, reviews and continuous feedback can sit with leave, time, records and development data in one modular hire-to-retire setup, with self-service in Teams, Outlook, browser and mobile.
Around your policy, the UK-based team can configure fields, forms, workflows, approvals and reporting without heavy custom code. Power BI can show review status and post-review movement by team, while Business Central and Finance & Operations connections can be scoped where workforce and finance data must stay aligned, including ownership and support responsibilities.
If reviews still measure completion better than follow-through, use the HR Management 365 homepage to arrange a short review of your current process: HR Management 365.
