The template shapes the conversation. A good one pushes a manager toward something specific; a bad one produces vague praise, inflated ratings and an afternoon nobody gets back. Most companies are still using a form they inherited, and nobody remembers who designed it or what it was for.
Five principles
Start from the purpose. Development, evaluation, alignment and documentation are four different jobs, and a form that tries to do all four does none of them well.
Keep it short. Fifteen to twenty minutes of focused writing per person is the realistic budget. If it takes forty minutes, the form was designed for whoever analyses the data afterwards, not for the manager filling it in.
Balance structure and freedom: required sections so the important things get covered, open questions so the interesting things can appear, and guidance on length so nobody writes three words or three pages.
Force specificity. Good communicator says nothing. Jane’s weekly updates prevented the API integration delay says what to do again. The form should make the second kind easier to write than the first.
And point forward. Roughly a fifth of the conversation on what happened, the rest on what comes next, because the past is only useful as evidence.
What a template needs in it
A self-assessment, covering progress against goals, what went well, what was hard, what support was missing and where the person wants to go. It is the section that most often surprises the manager.
Goal achievement, measured against what was actually agreed, with numbers where numbers exist.
A competency assessment on a scale people can use, exceptional, strong, developing, needs support, with a behavioural example required for each rating. The example is what stops the scale from becoming a mood.
Development areas described as behaviours rather than traits, with the business reason, an action plan, the support offered and a date. And a career conversation: where they want to be in two or three years, what is missing, and what exists internally.
Four templates worth having
A quarterly development check-in: goal progress, wins, obstacles, support needed, one development focus, manager comments. Short by design, because it happens often.
An annual review, weighted rather than averaged: goal achievement around 30%, competencies 40%, values 20%, notable achievements 10%, plus the development plan, the career conversation and an overall rating that follows from the parts instead of preceding them.
A project-based review, run at the end of something rather than the end of a year: deliverables, collaboration, problem-solving, what was learned, and what to do differently next time.
And a 360 summary that synthesises themes instead of listing quotes, compares the self-assessment against how others saw it, and ends with two or three development priorities rather than twelve.
Ready to fix your performance review process?
TalentRewards makes it easy to build a performance management system your team actually loves. Start your free trial today.