Employee evaluations can create useful conversations about work, expectations and development when they are fair, specific and handled consistently. They do not replace employment, human-resources, privacy or legal advice for your jurisdiction.
Begin with a clear purpose
Decide what the review is for. It may be a development conversation, a regular check-in, a probationary review or part of a formal performance-management process. The purpose affects who is involved, what evidence is appropriate and what follow-up is required. Do not use a routine appraisal to handle a serious conduct, safety, discrimination, accommodation or legal issue; involve the appropriate specialist instead.
Set expectations before the review period
Employees should understand their role, priorities and the standards that apply before they are assessed. Use a small number of relevant criteria, such as quality, timeliness, customer care, collaboration or role-specific capability. Define what the criteria mean in observable terms and make sure they are realistically within the employee’s control.
Where measures are used, include the context. A number without its denominator, workload, resources or changing conditions can be misleading. Avoid turning every role into a scorecard: qualitative work and professional judgement often need examples and discussion as well as data.
Prepare with evidence, not impressions
- Review the role description, agreed goals and notes gathered across the whole period.
- Use specific examples: what happened, when, what standard applied and what impact it had.
- Separate facts from interpretation. “The customer report was submitted two days after the agreed date” is clearer than “You are unreliable.”
- Check for missing context, inconsistent standards and recency bias before the meeting.
- Follow your organisation’s privacy, record-keeping and employment procedures.
Make the conversation two-way
Invite the employee to prepare a self-assessment. Ask what they are proud of, what made their work harder, what support they need and what they would approach differently. Listen for information a manager may not see: changing priorities, unclear handoffs, workload, training gaps or dependencies on other teams.
Feedback is most useful when it is timely, respectful and connected to work. Describe the situation, the observed behaviour or output, and the effect; then discuss what should continue or change. Avoid labels, speculation and comparisons with colleagues. Give the person a genuine opportunity to respond.
Agree a small, reviewable plan
End with a limited number of next steps. Each should identify the action, support required, owner and review date. For example, a customer-facing employee might test a revised handoff checklist for four weeks, bring two examples to the next check-in and identify any recurring obstacles. This is an illustrative example, not a universal template.
Development goals should be relevant to the role and the employee’s interests, not a promise of promotion or a disguised disciplinary action. Record any agreement accurately and make sure the employee understands how to raise a concern or request clarification.
Use feedback sources carefully
Peer, customer or 360-degree feedback can add perspective, but it can also introduce confidentiality, bias and power-dynamic issues. Explain the purpose, who will see the information, how comments will be collected and how they will be used. Use a consistent process, give people a chance to respond and avoid relying on anonymous hearsay for high-stakes decisions.
Common problems to avoid
- Surprises: raise routine concerns when they occur; do not save them for one annual meeting.
- Vague praise or criticism: tie feedback to real work and agreed expectations.
- One recent event defining the whole period: use a broader record and invite context.
- Different standards for similar roles: calibrate managers and review the process for consistency.
- Confusing development with formal action: be transparent about the process and seek HR or legal guidance when appropriate.
Review the process itself
After a cycle, ask whether the criteria were clear, whether managers had enough preparation and whether employees understood the next steps. Look for patterns that may point to a process problem rather than an individual one. A fair evaluation system needs regular improvement too.
Frequently asked questions
How often should employee evaluations happen?
Choose a rhythm that suits the role and your organisation. Short, regular check-ins can reduce surprises, while more formal reviews may occur less often. Consistency matters more than adopting a fashionable schedule.
Should an employee sign a review?
Requirements vary by organisation and jurisdiction. A signature may acknowledge receipt rather than agreement. Confirm your policy and obtain appropriate HR or legal guidance.
Can coaching help managers conduct better reviews?
Coaching can help a manager practise preparation, listening and clearer feedback. It should sit alongside, not replace, the organisation’s HR procedures and specialist advice.
Want to strengthen day-to-day management conversations? Book a free 15-minute fit call to discuss whether coaching support is suitable.
