Performance management · 3 min read

How to run a performance management cycle without spreadsheet chaos

Connect expectations, evidence, regular conversations, employee responses and formal review in one explainable performance cycle.

The short answer

A performance management cycle connects clear expectations, ongoing evidence, regular manager–employee conversations, formal review and agreed follow-up. Software should keep the period, objectives, examples, responses and decisions together, but it should support managerial judgement and useful conversation—not reduce a person to a score or automate an employment decision.

Begin with the purpose of the cycle

Decide whether the process is primarily developmental, administrative or both. Development conversations focus on progress, support and learning. Administrative decisions may affect reward, progression or another formal outcome. When several purposes are combined, explain the evidence and decision boundary clearly.

CIPD evidence reviews recommend clarity about purpose and note that developmental and administrative appraisals can involve different judgements. Do not allow one unexplained rating to stand in for several decisions.

Set expectations people can understand

Describe the work, standard or outcome expected during the period and how progress will be discussed. Some roles suit measurable targets; others require quality standards, project outcomes, behaviours or a combination.

Check that the employee can influence the expectation and that the manager can observe or obtain appropriate evidence. Objectives should be revisited when responsibilities or business priorities materially change.

Collect evidence throughout the period

Record specific examples close to the work: a completed outcome, missed commitment, stakeholder feedback, improvement, documented hand-off or another relevant contribution. Keep the date, context and source beside the entry.

Evidence should be proportionate and work-related. Public recognition is not a complete performance record, and private performance evidence should not appear in a recognition feed. Give employees an appropriate route to add context or correct a factual misunderstanding.

Use regular check-ins before the formal review

Short monthly or periodic conversations can surface changing priorities, barriers and support needs before the end of the cycle. CIPD describes performance management as a continuous process in which regular discussions matter alongside formal records.

A scorecard can help structure the conversation, but it should lead back to examples and next actions. Avoid turning check-ins into repeated mini-appraisals with no room for coaching or adjustment.

Make the formal review explainable

Bring together the agreed expectations, period evidence, prior conversations and employee response. The manager should explain the assessment and distinguish observed facts, interpretation and the resulting decision.

Provide a route for the employee to comment, acknowledge or raise a concern according to policy. If moderation or a second reviewer is used, document its role and access. The final record should show how the conclusion was reached.

Close the cycle with specific follow-up

Agree the next expectations, development support, owners and review date. If performance needs to improve, follow the organisation’s approved process and applicable employment requirements rather than treating software prompts as legal or HR advice.

Review the quality of the process as well as completion rates. Look for missing evidence, late reviews, unexplained score changes and employee questions about fairness or usefulness. Use those patterns to improve manager guidance and the next cycle.

Your checklist

  • Define whether each conversation is developmental, administrative or both.
  • Set observable expectations and revisit them when work changes.
  • Capture dated, work-related evidence throughout the period.
  • Give employees a route to add context or respond.
  • Require managers to explain assessments and resulting decisions.
  • Finish with owners, support and the next review date.

Research sources

See the workflow in practice

See monthly scorecards, supporting evidence and employee responses together in the People Impressions review workflow.

Explore performance management ↗

About these guides: reviewed against the product workflows documented for People Impressions and prepared with AI assistance. Scenarios are illustrative, not customer results. Confirm policy, legal and configuration details for your organisation.

Back to all guides ↗