A 360 feedback template is easy to overcomplicate. The form is not the hard part. The hard part is deciding who rates, whether the answers are anonymous, and how the results will feed the review — then asking only about behaviour the rater has actually seen. This page gives you those three decisions first, then a question bank for peers, direct reports, the manager and self.

Use it with the companion note on whether 360 feedback should be anonymous, the performance review template, and the guide to running a calibration meeting. The Word file is free with your work email; every section also appears on this page. Disclosure: Ash Taherian is Product Sales Executive at Revolut People, which sells performance management software. Treat product mentions as coming from an interested party.

What the template should include, in short

What questions should a 360 feedback template include? Keep it to 8–12 questions that ask about behaviour the rater has actually seen: how the person communicates, collaborates, delivers and handles feedback, plus open questions on their biggest strength and what they should start, stop or continue. Tailor a few questions to each rater group, so direct reports are asked about clarity and support, and peers about collaboration.

Should 360 feedback be anonymous? Decide before you send it, and tell raters. Anonymity can make people more candid, but it makes comments harder to act on and verify. The playbook’s default is to keep upward and peer feedback anonymous and aggregated, with a three-to-five rater floor, and to keep the manager and self views named. Some teams keep upward feedback anonymous and peer feedback named; if you do that, say so clearly. The reasoning, and the sources, are on the anonymity note.

Download the 360 template

The Word file matches the sections below: the three decisions, a rater log, the question bank, the rating scale, a short guide for turning themes into a review, and a fictional worked example. After you download it, upload it to Google Drive and open it with Google Docs if you would rather edit it there. The same sections are also on this page, so you can copy them into a document of your own if you prefer to start in the browser.

Three decisions before you send it

Write these down, in language you can share with raters, before anyone receives a form. The British Psychological Society’s 360 Degree Feedback: Best Practice Guidelines (PDF hosted 2022, as checked 13 November 2026) say that once you decide who can see the ratings, you should stick to it, and seek permission if you have a good reason to change.

Who rates

Invite people with recent working contact, not a long list of distant stakeholders. Typical groups are peers, direct reports (upward), the line manager, and the person themselves. The BPS guidelines say the recipient should help identify raters who are in a position to comment, and that those raters must be credible if the feedback is going to be acted on.

For any group you have promised anonymity, use a minimum of three to five people so individual sources cannot be identified. If a manager has only two reports, combine groups — for example peers and direct reports — rather than showing a two-person cell. That floor, and the advice to combine groups, is from the same BPS guidelines, as checked 13 November 2026.

In Revolut People, public documentation on requesting peer feedback (as checked 13 November 2026) says peer reviews are not assigned automatically — the employee requests them — and recommends choosing people they have collaborated with closely, including cross-functional colleagues where relevant, rather than only close friends. That does not replace the BPS rater floor if you have promised anonymity.

Anonymous or named

Decide this before you send the form, tell raters, and use the same rule for everyone in a rater group. The playbook’s default, set out in Should 360 feedback be anonymous?, is:

Playbook starting point for anonymity, aligned with the companion note and the BPS guidelines (as checked 13 November 2026). It is a default, not a legal requirement.
Rater groupStarting pointWhy
Direct reports (upward)Anonymous, aggregatedHighest retaliation risk. Keep a three-to-five rater floor, or combine groups.
PeersAnonymous, aggregatedSame honesty rationale. Some teams name peer feedback; if you do, say so and do not mix named and anonymous peers in one report.
ManagerUsually namedThe line manager’s view is expected to be discussable.
SelfNamedSelf–other gaps are useful coaching material, and only if the self view is not hidden.

Anonymity makes comments harder to follow up, which is why a manager-led debrief still matters. Do not promise anonymity you cannot keep: two reports and a distinctive turn of phrase is not anonymity.

One product-specific point, from Revolut People’s public documentation on completing upward reviews (as checked 13 November 2026): upward reviews are described as anonymous, they “do not directly affect performance assessments,” and the reviewer can choose whether the feedback is shared only with the manager’s managers, or also with the manager being reviewed. Those pages do not document a general 360 or peer-review anonymity setting, so I have not claimed one.

How the results are used

Say, in one sentence, whether this 360 is for development and coaching, or whether it will also feed pay, bonus or promotion. Then keep that promise.

Smither, London and Reilly’s 2005 meta-analysis of 24 longitudinal studies, as checked 13 November 2026, found small average improvements after multi-source feedback: corrected mean effect sizes of 0.15 from direct reports, 0.15 from supervisors and 0.05 from peers. Excluding self-ratings, the average effect size was 0.25 when the feedback was used only for development, and 0.08 when it was also used for administration. The authors note that very few studies used it for administrative purposes, so that comparison should be read with care. CIPD’s 2022 evidence review (Cioca and Gifford; as checked 13 November 2026) likewise finds that multi-source improvements over time are small, and that more sources do not outperform feedback from direct reports alone. The same review, citing Kluger and DeNisi (1996), notes that over a third of the feedback studies in that systematic review found performance worsened after feedback. Design and follow-up matter more than adding raters.

Use 360 comments as evidence and coaching material, not as a popularity score or a hidden vote in the grade. The formal rating still comes from your published rating scale, the review write-up, and calibration.

360 questions by rater

The question bank below is original to this playbook. Keep the whole form to about 8–12 questions. Start with the core set, then add two or three that fit the rater. Every item should be answerable from work the rater has seen. Offer a “not observed” option so nobody has to guess — the BPS guidelines ask for this, as checked 13 November 2026.

Core questions (every rater)

  1. How clearly does this person communicate, in writing and in conversation, in the work you have seen?
  2. How reliably do they follow through on commitments they have made to you or to the shared work?
  3. How do they collaborate when the work crosses teams, or when priorities conflict?
  4. How do they handle disagreement or a challenge to their work?
  5. How do they respond when they receive feedback, or when something they own goes wrong?
  6. How do they share information, context and credit with the people they work with?
  7. What is this person’s biggest strength in the work you have seen? Give one recent example.
  8. What should they start, stop or continue? Give an example you have actually seen.

For a self-review, ask the same questions in the first person. If eight questions already fill the form, stop there. Only add the tailored items below if a rater group can see something the core set does not cover.

Peers

  • When you work together, do they leave you with what you need to do your part — context, a decision, or a finished input — in time?
  • How do they contribute in shared work: do they pick up a fair share, and do they flag a problem early enough to fix?
  • How do they treat other teams’ constraints when they need something from you, or when you need something from them?

Direct reports (upward)

This is a short block inside the 360. For the fuller upward-only how-to — a longer question set, how to collect comments safely, and how to use the answers in the manager’s review — see upward feedback questions.

  • How clear are the expectations, priorities and decisions you get from this person?
  • How well do they support you and unblock work when you are stuck?
  • How fairly and specifically do they give you feedback on your work?
  • How safe is it to raise a risk, a mistake or a disagreement with them?

Manager

  • How well have they delivered against the goals and responsibilities you agreed for this period, including work that was added later?
  • How do they grow their own skills, and the skills of people around them?
  • How do they handle a change in scope, a slip, or a conflicting priority?
  • What is the most important development focus for the next period, and why?

Self

  • Which goal or responsibility changed during this period, and how did that affect what you delivered?
  • Where did you have the biggest impact, and what evidence would your manager be able to check?
  • What support or clarity would help you improve in the next period?

For wording in the review conversation itself, rather than for raters, use the manager performance review questions and the performance review examples by rating level (those examples are labelled fictional).

Rating scale and evidence prompts

Use a short behaviour scale for the scored questions, and keep it separate from your formal performance grade. The scale below is a starting point for 360 items, not a published company standard.

Starting scale for 360 behaviour items. Use “Not observed” rather than guessing. For formal grades, use your published scale.
RatingWhat it means
Not observedYou have not seen this behaviour, or it is not relevant to the work you share. Do not guess.
InconsistentYou have seen this sometimes, but not reliably, or only in easy conditions.
Meets the behaviourYou have seen this reliably in the work you share, with at least one checkable example.
A clear strengthThis stands out in the work you share. Others could learn from how this person does it.

Under every scored question, ask for evidence in one or two sentences: what happened, roughly when, and what the effect was. Do not ask people to diagnose personality. If a comment would identify an anonymous rater, keep it out of the shared pack or edit it with the rater’s consent.

Turning 360 results into a review

Do not average 360 scores into a grade. Read for themes. Keep comments that describe behaviour the rater could have seen, and set aside labels and anything that would break anonymity. Bring two or three themes, with examples, into the evidence section of the performance review template. If you also score skills, check those themes against the behaviours in the competency matrix templates, so the 360 input and the review use the same role-and-level bar. Write the draft rating against your published scale, and calibrate before any conversation.

In the conversation, share the themes and the next steps, not a tour of every raw comment. Keep a written record of what you discussed and share it with the employee. Acas (Reviews and appraisals, last updated 23 June 2026, as checked 13 November 2026) asks for a written record of performance conversations, shared afterwards. That guidance is about reviews and appraisals, not a 360 form, but the same habit is useful here.

Fictional worked example

The example below is fictional. The names, company, comments and draft review line were written for this page. They are not real employee data.

Priya Shah is an engineering manager at Northwind Pay, a fictional company. Four peers and four direct reports give anonymous, aggregated input; her manager’s view is named. Upward comments cite a March incident-response rota she reset the same day a paging gap appeared, and ask her to close decisions in writing after meetings. Peers describe API-change context shared a sprint early for a May checkout cutover, and one notes that hand-offs still slipped during a freeze. Her manager records that after a February planning review she cut two committed epics and told stakeholders within a week.

A manager might write: “Priya’s mid-year record shows reliable delivery on the platform roadmap and clear weekly direction for her team, with checkable examples from the March rota change and the May checkout cutover. The development focus for the next period is written follow-through on decisions, which appeared in more than one upward comment.” That is evidence for a review and for calibration, not a 360 average turned into a grade. The same example is in the Word template.

In Revolut People, public docs on completing peer reviews (as checked 13 November 2026) describe a peer review as covering goal attainment, skills, company values and written feedback, and ask raters to be objective, specific and constructive. Upward reviews, on the page already cited, assess management behaviours rather than goals or skills. Use those structures if you run the process in that product; the decisions and question bank on this page still apply. For a walkthrough of how peer and upward reviews sit in a cycle, book a 15-minute review.

Common mistakes

  • Sending the form before the three decisions are written down. Raters should know who will see their answers, and whether the 360 feeds development only or pay as well.
  • Promising anonymity without a rater floor. Two reports is not an anonymous group. Combine groups, or do not call it anonymous.
  • Asking 20 or 30 questions. People guess, or they drop out. Stay close to 8–12, and allow “not observed”.
  • Inviting people who barely work with the person. Distant raters turn a 360 into a popularity contest.
  • Averaging scores into a grade, or using a developmental 360 as a hidden pay vote. Themes are evidence; the grade still needs a published scale and calibration.
  • Collecting comments and skipping the debrief. Agree a few actions and a check-in date, or the report goes unread.
  • Personality labels instead of examples. “They’re difficult” cannot be calibrated. “They changed the API contract the day before release, without warning Payments” can.

Related guides

Upward feedback questions: how to ask about managers · Should 360 feedback be anonymous? · competency matrix templates by role and level · performance review template with worked examples · performance review examples by rating level · what questions a manager should ask in a performance review · employee performance rating scales explained · how to run a performance calibration meeting · year-end performance review: HR run sheet and template · staff appraisal template (UK) · performance calibration · performance management framework · pricing estimator · free tools · book a 15-minute review · People Performance Playbook home

Free tools: estimate what your review cycle costs with the performance review cost calculator, or get a dated view of published vendor prices with the pricing estimator.

FAQ

What questions should a 360 feedback template include?

Keep it to 8–12 questions that ask about behaviour the rater has actually seen: how the person communicates, collaborates, delivers and handles feedback, plus open questions on their biggest strength and what they should start, stop or continue. Tailor a few questions to each rater group, so direct reports are asked about clarity and support, and peers about collaboration.

Should 360 feedback be anonymous?

Decide before you send it, and tell raters. Anonymity can make people more candid, but it makes comments harder to act on and verify. The playbook’s default, drawn from the British Psychological Society’s 360 guidelines (as checked 13 November 2026), is to keep peer and upward feedback anonymous and aggregated, with a three-to-five rater floor so individuals cannot be identified, and to keep the manager and self views named. Some teams keep upward feedback anonymous and peer feedback named; if you do that, say so clearly and use the same rule for everyone in a group. There is a longer treatment on the anonymity note.

Who should give 360 feedback?

People with recent working contact: typically peers, direct reports, the line manager, and the person themselves. The British Psychological Society guidelines (as checked 13 November 2026) say the recipient should help identify raters who are in a position to comment, and that each anonymous group should have a minimum of three to five people, or be combined with another group if it is smaller.

How do you use 360 results in a review?

Read for themes and checkable examples, not an average score. Bring two or three themes into the evidence section of the performance review template, write the draft grade against your published scale, and calibrate before any review conversation. Keep 360 input developmental: Smither, London and Reilly (2005, as checked 13 November 2026) found larger effects when multi-source feedback was used for development rather than administration.

How many questions should a 360 include?

Keep the form to about 8–12 questions, including the open ones. That is long enough to cover communication, collaboration, delivery and feedback, and short enough that raters can answer from what they have actually seen.

How many raters do you need?

For any group you have promised anonymity, the British Psychological Society guidelines (as checked 13 November 2026) set a minimum of three to five people so individual sources cannot be identified. If a manager has only two reports, combine groups rather than showing a two-person cell.

Follow us on Google

Want a second look at your 360 rules before the next cycle?

Bring your rater lists, anonymity rule and the sentence you will share with raters to a 15-minute review. We will check whether the form stays short, whether anonymity is real, and how themes will feed the review without becoming a popularity score. Soft fit-check only.

The PDF asks for a work email. The 15-minute review is a fit-check, not a sales pitch.