A well-designed 360 review template helps managers gather useful feedback from the people who actually see the work: peers, direct reports, line managers, and sometimes clients. Used properly, it gives a clearer picture of strengths, blind spots, and development priorities than a single manager review ever can. In performance management, that matters because the best feedback is specific, behaviour-based, and easy to act on.
What matters most before you launch multi-source feedback
- Keep the form focused on observable behaviour, not personality.
- Use a fixed set of competencies so answers can be compared across raters.
- Limit the rater group to people with real working contact and enough context to comment well.
- Explain anonymity, access, and retention rules before anyone starts writing.
- Turn the results into one or two development goals, or the exercise will stall at diagnosis.
What a 360 review is really for
I treat 360 feedback as a development tool first. It is meant to widen the lens, not replace judgement with a spreadsheet. The CIPD describes performance management as a continuous cycle, and that is the right mindset here: feedback should help people improve while work is still happening, not simply judge what went wrong after the fact.
The strength of a 360 process is that it exposes pattern rather than impression. A manager sees one slice of behaviour; peers see collaboration; direct reports see consistency, clarity, and follow-through; clients see reliability and communication under pressure. When those views are combined, you usually get a better read on how someone actually operates in the business.
That said, a 360 process is not magic. If the questions are vague, the rater group is badly chosen, or the results are used punitively, the whole thing becomes noise. The next section shows how I would structure the template so it produces feedback worth reading.
The sections that make the template useful, not just complete
I usually build the form around a small set of fixed sections. That keeps the response time reasonable and makes the output easier to interpret later.
| Section | What it should contain | Why it matters |
|---|---|---|
| Purpose | State whether the review is for development, promotion readiness, leadership growth, or a broader performance conversation. | If the purpose is unclear, people answer cautiously and managers later over-interpret the results. |
| Rater group | Identify whether the feedback comes from a manager, peer, direct report, client, or self-review. | Different raters see different behaviours, so the context has to stay attached to the comment. |
| Competencies | Use 5 to 8 behaviours that matter in the role, such as communication, collaboration, accountability, decision-making, or coaching. | Too many dimensions create vague answers and survey fatigue. |
| Rating scale | Use a simple 5-point scale with a “not observed” option. | It is easier to spot patterns when the scale is consistent and the middle point is defined. |
| Open comments | Ask for one strength, one improvement area, and one example of behaviour in action. | Numbers alone rarely explain what needs to change. |
| Development plan | Leave space for next steps, support needed, and a follow-up date. | Feedback without an action plan tends to fade quickly. |
| Data handling | Explain who will see raw responses, how anonymity is handled, and how long the data will be kept. | This is essential if the review is going to be trusted, especially in a UK workplace. |
Once those pieces are in place, writing the actual questions becomes much easier, because each prompt has a clear job to do.
A 360 review template you can adapt
If I were building this for a manager, team lead, or specialist role, I would keep the form short enough to finish in 10 to 15 minutes. That is usually enough time to get thoughtful answers without pushing raters into rushed, generic comments.
Self-assessment
The self-review should set the tone. I like questions that force reflection, not self-promotion.
- What results did you contribute to most directly this cycle?
- Which behaviour helped the team most?
- What would you do differently if you were starting the cycle again?
The point here is to compare self-perception with outside perception, not to create a polished personal statement.
Manager feedback
Manager comments should link behaviour to outcomes and expectations.
- Where did this person have the greatest positive impact?
- What is the one capability that would most improve their performance next?
- How well do they respond when priorities shift?
This section works best when the manager is specific enough to coach rather than score.
Peer feedback
Peers are often the best source for collaboration, reliability, and communication quality.- How effectively does this person work across functions?
- Do they share information early enough to help others do their jobs?
- How easy is it to rely on them when deadlines are tight?
What I look for here is consistency: do peers repeatedly describe the same strengths or friction points?
Direct report feedback
If the person manages others, this is the section that often reveals the most useful blind spots.
- Does this person set clear expectations?
- Do they listen properly when people raise problems or disagree?
- Do they remove blockers, or do they simply pass pressure downwards?
For people managers, this is usually the section that tells you whether leadership habits are actually landing with the team.
Optional client or stakeholder feedback
Use this only when the person works directly with external or internal stakeholders who can genuinely observe the work.
- How clearly does this person communicate progress and risk?
- Do they keep commitments and follow through?
- How confidently do they represent the team or function?
This section is valuable, but only when the rater has enough exposure to be fair.
Read Also: End of Year Performance Review Examples - Write Better Appraisals
Closing development plan
End the form with a simple bridge into action.
- Top 2 strengths to keep
- Top 2 behaviours to improve
- One goal for the next 60 to 90 days
- One form of support from the manager or organisation
That final block is where the review stops being a report and starts becoming a management tool.
How to run the process without damaging trust
Even a strong questionnaire can fail if the process feels secretive or political. I would run it with a simple, explicit rhythm.
- State the purpose before inviting anyone. Development, promotion readiness, succession planning, and pay decisions are not the same thing, and people should not be left guessing.
- Choose raters who have worked closely with the person for at least three months and can give examples from real interactions. If you want separate peer or direct-report results, aim for at least three responses in each group so the pattern is harder to trace to one person.
- Give people 10 to 14 days to respond. That is long enough to avoid rushed answers without letting the process drift.
- Explain what will be anonymous, what will be summarised, who can see the raw comments, and how long the data will be kept. The ICO is clear that identifiable feedback about workers is personal data, so access and retention should be deliberate, not left to habit.
- Ask for behaviour examples rather than labels. “Gives clear direction in meetings” is useful; “is a great leader” is too broad to act on.
- Close the loop quickly. I would debrief the results within a week of the survey closing and agree the next check-in before the conversation ends.
If you run the process openly and keep the promise of confidentiality, the quality of the comments rises sharply. That matters most when you move on to interpreting the results, because raw feedback can easily be over-read or under-used.
How to read the results without reducing people to a score
I rarely trust a simple average on its own. The useful question is not “What is the score?” but “What pattern keeps showing up, and what does that tell us about day-to-day behaviour?”
| Pattern | What it often means | What to do next |
|---|---|---|
| Strong manager scores, weaker peer scores | The person may be dependable upwards but less consistent across functions. | Work on cross-team communication and follow-through. |
| Low scores across all groups | A genuine capability gap or a role mismatch may exist. | Agree a focused coaching plan and a 60-day review point. |
| Good scores but thin comments | People may be cautious or unsure what to write. | Improve the question wording and ask for examples next cycle. |
| Mixed scores by rater group | The role may be differently experienced depending on proximity. | Compare expectations and clarify what “good” looks like for each group. |
I also pay attention to repetition. One sharp comment can be personal bias; three independent comments pointing to the same behaviour deserve attention. At the same time, I would not ignore context. A person who is leading a difficult change programme will often be judged differently from someone whose role is stable and visible.
The safest interpretation is one that combines numbers, comments, and role context before anyone decides what the feedback really means.
Mistakes that make the exercise noisy or unfair
Most weak 360 processes fail for familiar reasons. None of them are glamorous, and all of them are avoidable.
- Using the review as a trap. If people suspect the exercise is really about catching them out, they will write bland feedback or opt out altogether.
- Asking fuzzy questions. Vague prompts produce vague answers. “Is this person good to work with?” is far less useful than “Does this person share information early enough to help others?”
- Overloading the form. A survey with too many competencies becomes tiring, and tired raters become lazy raters.
- Ignoring exposure. Someone who has barely worked with the person should not be asked to provide deep judgement.
- Sharing raw comments without filtering. Even well-meant feedback can be misread if names, stories, or identifiable details are left intact.
- Stopping after the report. If there is no coaching, no goal, and no follow-up, the whole process becomes a ritual rather than a management practice.
In practice, the biggest mistake is usually not the wording of a single question; it is failing to connect the review to the rest of performance management. That leads straight into the final thing I would keep in place after the first cycle.
What I would keep in place after the first cycle
The best use of a 360 process is not to produce a dramatic one-time insight. It is to create a repeatable habit: gather the right voices, identify the behaviours that matter, and turn the findings into action. If the output does not lead to a coaching conversation, a learning decision, or a clearer set of expectations, the template is doing paperwork rather than work.
- Keep one clear development goal, not five.
- Review progress after 6 to 8 weeks instead of waiting for the next annual conversation.
- Use the same competencies next time unless the role has changed materially.
- Capture whether the issue is the person, the role, or the system.
That is what makes a feedback process valuable in a real organisation: it helps people change behaviour, not just collect opinions.
