A 360 degree feedback report collects ratings of one person from their manager, peers, direct reports, and themselves, then presents them side by side. A standard report has six parts: an overview, competency scores by rater group, the self versus rater gap, highest and lowest rated items, verbatim written comments, and a development section. The single most useful number in it is the gap between how the person rated themselves and how everyone else did. Here is what each section contains, how to read the scores without over-reading them, and the mistakes that turn a good report into a bad conversation.
What is included in a 360 degree feedback report
Report layouts differ by vendor, but the content converges because the underlying data is the same: several rater groups answering the same competency items about one person. Almost every report you will see is built from these six blocks, usually in this order.
| Section | What it shows | What to do with it |
|---|---|---|
| Overview or summary page | Overall average, response rates by rater group, and often a two or three factor profile placing the person on broad dimensions | Check response counts first. A peer average built on two responses is not a finding |
| Competency scores by rater group | Each competency rated separately by self, manager, peers, direct reports, and sometimes customers or stakeholders | Read across the row, not down the column. Where groups disagree is where the information is |
| Self versus rater gap | The difference between the self rating and the combined rating from everyone else, per competency or per item | Sort by gap size. Anything beyond about one point on a five point scale is worth a conversation |
| Highest and lowest rated items | Usually the top five and bottom five individual behaviors across all raters | Use the top five in the debrief before the bottom five, or nothing after that gets heard |
| Verbatim comments | Open text answers, grouped by rater category and normally unattributed | Look for themes repeated by different groups. A single sharp comment is one person, not a pattern |
| Development section | Space for two or three chosen focus areas, actions, and a review date | This is the only page that changes anything. Two priorities, not eight |
What does a 360 degree feedback report look like
Take a fictional example to make the shape concrete. A director is rated on eight competencies by their manager, six peers, and five direct reports, on a one to five scale. The overview page reports an overall average of 3.9 with a 92 percent response rate. The competency table then breaks it apart, and that is where the report stops being a grade.
Under "delegates effectively", self rates 4.5, the manager 4.0, peers 3.9, and direct reports 2.8. The overall average for that competency is a respectable 3.6, which on the summary page looks fine. The row tells a different story: the people receiving the delegation experience something the person doing it does not. That is a real, specific, actionable finding, and it exists nowhere on the summary page. This is why experienced readers skip the front page and start at the competency table.
Two more things show up in a well-built report. Some vendors present normed or standardized scores alongside raw ones, so a 3.9 becomes a percentile against a comparison group of other managers. Normed scores answer "compared to whom" and are more honest than a raw average, but only if the norm group actually resembles your organization. And better reports show the spread within a rater group, not just its average, because six peers averaging 3.5 could be six people at 3.5 or three at 5 and three at 2. Those are different findings entirely.
Sample 360 degree feedback report
Descriptions of report structure only get you so far. Below is the competency page from that same fictional director's report, filled in, so you can see the shape of real output instead of reading about it. The scores are illustrative and were built to demonstrate how the columns interact. They are not data from any organization, vendor, or norm group.
One convention matters before you read it. The "all raters" column here is the average of the three rater group means, each counted once, rather than an average of all twelve individual responses. Many vendors do it this way so that a group of six peers does not drown out a group of one manager. It changes the numbers, sometimes by a couple of tenths, so check which method your report uses before you compare a score to anything.
| Competency | Self | Manager (1) | Peers (6) | Direct reports (5) | All raters | Gap |
|---|---|---|---|---|---|---|
| Sets clear direction | 4.0 | 4.1 | 3.9 | 4.0 | 4.0 | 0.0 |
| Delegates effectively | 4.5 | 4.0 | 3.9 | 2.8 | 3.6 | -0.9 |
| Gives useful feedback | 4.2 | 3.8 | 3.6 | 3.0 | 3.5 | -0.7 |
| Communicates decisions | 3.6 | 4.0 | 4.2 | 4.1 | 4.1 | +0.5 |
| Develops the team | 3.8 | 3.9 | 3.7 | 3.4 | 3.7 | -0.1 |
| Manages conflict | 3.2 | 3.9 | 4.0 | 3.8 | 3.9 | +0.7 |
| Delivers on commitments | 4.4 | 4.3 | 4.2 | 4.1 | 4.2 | -0.2 |
| Builds cross team relationships | 3.5 | 4.2 | 4.4 | 4.0 | 4.2 | +0.7 |
Gap is all raters minus self, so a negative number means the person rated themselves above everyone else. The overall all-rater average across the eight competencies is 3.9, which is the number the summary page leads with, and it is the least informative figure in the whole document.
Read the sample the way a practitioner would and three findings fall out in about a minute. Delegation is the blind spot: a 0.9 gap driven almost entirely by direct reports at 2.8 while the manager sees 4.0, which means the person delegates in a way that reads as competent from above and as something else from below. Feedback is the same pattern one notch weaker, direct reports at 3.0 against a self rating of 4.2, and the fact that two separate competencies both split along the manager and direct report line is what turns two rows into one theme. Against that, conflict at +0.7 and cross team relationships at +0.7 are hidden strengths where the person is underselling themselves, and delivering on commitments at 4.2 with near total agreement is a confirmed strength to open the debrief with.
Notice what the summary average of 3.9 hides. Nothing in that number tells you the person has a specific, fixable problem with how delegation lands on their team, and the entire value of the report sits in that one row. This is the whole argument for reading across rows rather than down columns.
360 feedback report template: what to require before you buy
If you are comparing 360 vendors or building the report yourself in a survey tool, treat the report as the product. The questionnaire is easy to get right and most instruments are broadly similar; the output is where platforms actually differ, and it is the thing your managers will be handed. Use the list below as the template a report has to satisfy, and ask to see a filled-in redacted example during the evaluation rather than a marketing screenshot of the front page.
| Element the template must contain | Why it matters | Walk away if |
|---|---|---|
| Response counts per rater group, on the page | A group average with two responses is noise, and readers cannot know that unless the count sits next to the score | Counts appear only in an appendix, or not at all |
| Competency scores split by rater group | Disagreement between groups is the finding. A single combined average destroys it | The report shows one blended score per competency |
| Self versus rater gap, sortable or pre-sorted | Gap size is the fastest route to the two items worth discussing | You have to calculate the gap yourself from two columns |
| Spread or distribution within a rater group | Six peers averaging 3.5 could be six moderates or a split camp, and those are different problems | Only group means are shown, with no range, standard deviation, or response distribution |
| Item level detail under each competency | Competency averages tell you where to look; the individual behaviors tell you what to change | The report stops at competency level |
| Verbatim comments grouped by rater type, with a suppression rule | Comments carry the detail ratings cannot, and small groups make them identifiable | The vendor cannot state the minimum group size at which comments are suppressed |
| A stated norm group, if normed scores are shown | A percentile is meaningless unless you know who it is a percentile against | Percentiles appear with no description of the comparison population |
| A development page the recipient fills in | It is the only section that changes behavior, and two priorities beats eight | The report ends at the data with no structured planning section |
| Prior cycle comparison, once you have run it twice | Direction over time carries more information than any single score | Cycles cannot be compared because the item wording is not locked |
Two things belong on the template that vendors rarely volunteer. The first is a plain statement of who receives the full report, printed inside the report itself, because rater honesty depends on that being known before the survey opens rather than negotiated afterward. The second is an export you actually own, ideally per item and per rater group, since the moment you want to look at patterns across thirty reports you will need the underlying data and not thirty PDFs.
How to read the self versus rater gap
The gap is the difference between the self rating and the combined rating from everyone else, and it is the part of the report that most reliably produces a useful conversation. It comes in two directions and both matter.
- Negative gap, where self is higher than raters. A blind spot. The person believes they are doing something they are not experienced as doing. These are uncomfortable and are usually the highest value items in the whole report.
- Positive gap, where self is lower than raters. A hidden strength, and often a confidence problem rather than a capability one. People under-rate themselves on exactly the things they should be doing more of.
- No gap, high score. A confirmed strength. Name it in the debrief and move on.
- No gap, low score. Shared awareness. The person already knows, which usually means the barrier is a resource, a process, or a competing priority, not a lack of insight.
Common practice among 360 practitioners is to treat gaps larger than about one point on a five point scale as significant enough to discuss and to ignore smaller ones as measurement noise. That threshold is a convention rather than a statistical rule, so treat it as a way of ranking the conversation, not as evidence. What makes a gap credible is corroboration: a rating difference that also shows up in the verbatim comments from the same rater group is a pattern, while a rating difference nothing else supports may just be different people using the scale differently.
How to read a rater group that disagrees with itself
The most common misreading of a 360 report is treating a rater group average as a verdict from a unified constituency. Direct reports averaging 3.0 on "gives useful feedback" might reflect a manager who invests heavily in two people and not in the rest, which is a completely different problem from one who gives thin feedback to everyone. If the report shows distribution, look at it. If it only shows averages, the verbatim comments are your only route to the spread, which is one reason the comment section deserves more attention than it usually gets.
Rater groups also apply different standards, and this is normal rather than a flaw. Managers tend to rate against role expectations, peers against their own experience of working alongside the person, and direct reports against how the relationship feels from below. A person can be genuinely strong at the competency their manager cares about and genuinely weak at the version of it their team experiences. The report is not contradicting itself. It is showing that "effective" means different things at different vantage points, which is the entire reason the method exists.
Reading the verbatim comments without doing damage
Written comments carry the detail that ratings cannot, and they are also where anonymity is most fragile. Three rules keep the comments useful. First, do not attempt to identify authors, and shut down anyone in the debrief who tries. Second, suppress comment sections for rater groups with fewer than about three or four responses, because a comment from a group of two is effectively signed. Third, read for repetition across groups. When a peer and a direct report independently describe the same behavior in their own words, that is the strongest signal in the entire report, stronger than any rating.
One caution about tone. Written 360 comments read harsher than the same feedback spoken, because people write more bluntly when unattributed and the reader has no face or tone to soften it. Anyone receiving a report cold, without a trained debrief conversation, tends to fixate on the single most negative sentence and discount everything else. That is a predictable human response to the format, not a sign the feedback was unfair.
Five mistakes that ruin a 360 report
- Sending the report without a debrief. A 360 report handed over as a PDF with no conversation is the most common way the process backfires. The research literature on 360 feedback is consistent that results improve when feedback is delivered with structured follow-up, and that some recipients get worse without it. Budget for the conversation or do not run the survey.
- Reading the summary average as a score. The overall number blends rater groups that disagree, which is precisely the information you commissioned. Averaging it away and calling it 3.9 discards the finding.
- Acting on eight development areas. Nobody changes eight behaviors. Two, with a named action and a review date, is the maximum that survives contact with an actual job.
- Using it for pay or promotion decisions. The moment raters believe their input affects someone's compensation, ratings inflate and the instrument stops measuring anything. Keep 360 results developmental and keep them out of the compensation file. Pay decisions should rest on documented, defensible pay bands built from real market data, which is a separate exercise with a separate evidence trail, and several states now require a posted range anyway.
- Running it once. A single report is a snapshot with no direction. The value appears on the second cycle, when the same items are re-rated and you can see whether the gap closed. Re-run the identical question set or you lose the comparison.
What a 360 report cannot tell you
A 360 report is a measurement of one person, assembled from opinions about that person. That is its strength and its ceiling. When five separate reports across a leadership team all show weak scores on the same competency, the honest reading is usually not that five individuals independently share a flaw. It is that something in the organization produces that behavior: a promotion path that rewards individual output over developing others, a workload that leaves no time for coaching, a culture where candid disagreement carries a cost.
Individual reports cannot see that, because none of their questions are about the company. Diagnosing it takes a different unit of analysis, one that scores the organization rather than its people. That is the distinction we set out in 360 degree feedback versus organizational assessment, and if you are still deciding whether the method fits your situation at all, the mechanics are covered in what 360 degree feedback is and how it works. When you need the wording for the instrument itself, our 360 degree feedback questions set gives 50 examples by competency.
Assessmentcloud measures the organizational layer rather than individuals. It scores culture and engagement, process maturity, digital maturity, skills, and compliance readiness 0 to 100 against your industry median and ranks the weakest first, so a pattern showing up across several 360 reports can be checked against the conditions that might be causing it. Run an organizational diagnosis to see the whole-company view, or a psychological safety assessment if the recurring theme in your reports is that people do not speak up. One boundary, stated plainly: Assessmentcloud does not run 360 feedback and does not rate individuals. Use a dedicated 360 platform for that, and use this for the company around them.
Frequently asked questions
What is included in a 360 degree feedback report?
A 360 degree feedback report normally includes six sections: a summary page with the overall average and response rates, competency scores broken out by rater group, the gap between self ratings and everyone else's, the highest and lowest rated individual behaviors, unattributed verbatim comments, and a development planning section. Some reports add normed scores comparing the person against an external benchmark group of similar roles.
How do you read a 360 feedback report?
Start with response counts, not scores, because a rater group with two responses cannot support a conclusion. Then read the competency table across rater groups rather than down the summary column, since disagreement between groups is the actual finding. Sort by the self versus rater gap and look at the largest ones. Finally, check whether the verbatim comments independently support the pattern the ratings suggest. Pick two development priorities, not eight.
What is a good 360 feedback score?
There is no absolute threshold, and treating one as a pass mark misuses the instrument. On a five point scale most competency averages cluster between 3.5 and 4.2 because raters avoid the extremes, so a 3.6 is unremarkable and a 2.8 stands out. What matters is the comparison: this competency against the person's other competencies, this rater group against the others, and this cycle against the last one. Direction over time carries more information than the number.
What is the gap in a 360 feedback report?
The gap is the difference between how a person rated themselves and the combined rating from everyone else. A negative gap, where self is higher, indicates a blind spot: the person believes they do something they are not experienced as doing. A positive gap, where self is lower, indicates a hidden strength. Practitioners commonly treat differences beyond about one point on a five point scale as worth discussing and smaller ones as noise.
Who sees the 360 degree feedback report?
In a developmental 360, the full report goes to the recipient and to whoever facilitates the debrief, usually a coach or HR partner. Practice varies on whether the recipient's manager sees the full report or only the development plan the recipient chooses to share. Individual rater responses are never shown to anyone. Decide and publish this policy before the survey opens, because if raters are unsure who reads their answers, they rate safely and the data is worthless.
How do you write a 360 feedback report summary?
Write it in four short parts. State the response rates and any group too small to report on. Name two or three confirmed strengths where self and raters agree at the high end. Name the one or two largest gaps and describe the behavior concretely rather than labeling the person. Close with the two development priorities, each with a specific action and a review date. Keep the language behavioral: what was observed, in what situation, not what kind of person the recipient is.
Is there a standard template for a 360 degree feedback report?
There is no single industry standard template, but good reports converge on the same nine elements: response counts per rater group, competency scores split by group, the self versus rater gap, spread within each group, item level detail under every competency, grouped verbatim comments with a stated suppression rule, a named norm group if percentiles are shown, a development planning page, and a prior cycle comparison.
How often should you run 360 feedback?
Annually or every eighteen months is the usual cadence for a full 360, because behavior change takes months to become visible to raters and running it more often produces survey fatigue and unchanged scores. The exception is a shorter targeted pulse on the two competencies someone is actively working on, which can be repeated at six months. Whatever the interval, keep the question wording identical or you lose the ability to compare cycles.
RUN IT, NOT JUST READ IT
Score this dimension for your company
The interactive sample readout on the homepage shows exactly what you get: scored dimensions, industry benchmarks, and a prioritized action plan. Flat pricing from $49 a month.