Action Planning

How to Read a Manager Report: A Team Leader's Guide from Survey Results to Action

Digital Institute
Last updated: November 20, 2026 · 13 min read
Four colleagues gathered around a table covered with marked-up printed reports, a laptop and notebooks, reviewing the reports together

One morning an email lands in your inbox: "Your Employee Survey Team Report Is Ready." You open it: colorful tables, percentages, comparisons with the organization average and a section of open-ended comments. For most managers the first reflex is the same. The eyes look for the lowest score first, and the next sentence is often "but I don't deserve this" or "who could have written that?"

In short
  • The team report is not a performance grade; it is a tool for understanding your team's voice. The moment you open it, the aim is not to defend yourself or look for someone to blame, but to understand correctly what the team is saying.
  • Read the report in order: participation and reliability first, then the big picture, comparisons, the highest and lowest items, and finally the open-ended comments. This order prevents you from fixating on one bad number.
  • Scores swing in small teams. Instead of a single point difference, read recurring patterns, change from the previous period and themes in the comments together.
  • The report is the beginning of action. After reading, prepare a one-page summary, talk it through with your team and then build the action plan together.

Yet the report is not a report card on you. It is a compilation of what your team is telling you and the organization. How much you get out of it depends on how you read it. The same report leads to defensiveness or panic when read the wrong way, and to a productive conversation with your team when read the right way.

This article focuses on the stage from the moment you receive the report to your first conversation with your team. For what comes next, building the action plan and following it over 90 days, see our 90-day action plan after the survey article. Our goal here is to help you read the report correctly so that you start that plan with the right inputs.

What does a manager report contain?

The report format varies by organization, but most team reports include these components:

  • Participation: How many people in your team responded to the survey.
  • Overall index or dimension scores: Summary results under headings such as engagement, manager, communication and development. Usually expressed as a favorable score or on a 0 to 100 scale.
  • Item scores: Responses to individual statements.
  • Comparisons: Differences from the organization, unit or benchmark and, where available, from the previous period.
  • Highest and lowest items: The statements your team agreed with most and least.
  • Open-ended comments: Opinions written by employees in their own words. Who wrote them is kept confidential.

Knowing this structure lets you read the report with a plan rather than at random.

The reading order: 6 steps

Instead of reading the report from start to finish, we suggest following the order below. The order matters because it keeps you from fixating on a single bad number.

1. Participation and reliability

The first thing to look at is not the scores but participation. If participation is low, the results may not represent your whole team; you may be hearing only from those who are very satisfied or very dissatisfied. In small teams, a handful of responses has a large effect on the average. Our article on sample size and margin of error can guide you here. The aim of this step is not to dismiss the results but to know how precisely you can read them.

2. The big picture

Before going down to item scores, look at the dimension or index level results. Where does your team stand overall? Which dimensions are strong and which are weak? Drilling into single items without seeing the big picture is like looking at the trees without seeing the forest.

3. Comparisons

A score on its own has limited meaning; you need to see what it is high or low relative to. Three comparisons matter:

  • Against the organization or unit: Is your team below or above the average of similar teams?
  • Against the previous period: Are scores rising or falling? Often the direction is more informative than a single score. See our article on score or trend for this.
  • Against your own expectations: We cover this in the next step.

Remember that small differences are not always meaningful. A difference of a few points can be down to chance if the team is small.

4. The highest and lowest items

Look at the highest items first. These are your team's strengths and things you are doing right. Most managers skip this part and jump straight to low scores, but knowing what works is also necessary to keep it going. Then look at the lowest items and ask: are these items related to each other? For example, if several items on communication, feedback and recognition are low together, that may be a symptom of a single issue. For reading scores visually, our article on heatmaps in employee survey results will be useful.

5. Compare with your expectations

Before opening the report, if possible, jot down a short note predicting which topics your team will score high on and which low. When the report arrives, compare it with your predictions. This small exercise shows your blind spots: a low score you did not expect reveals the gap between what the team experiences and what you see. A high score you did not expect may point to a strength you had not noticed.

6. Open-ended comments

The reason to leave comments for last is that, having seen the numbers, you can read them in a more accurate context. As you read the comments, pay attention to the following:

  • Look not at individual comments but at recurring themes. Three different people raising the same topic in different words matters more than a single harsh comment.
  • Do not try to find out who wrote what. This is both unethical and removes honesty from the next survey. For the assurance of confidentiality, see our article on anonymity in employee surveys.
  • Do not skip comments you find harsh or unfair. Looking for the emotion and the need underneath is more useful than getting stuck on the content.
  • For how to interpret open-ended answers from a question design perspective, see our open-ended employee survey questions article.

Summary: Reading worksheet

StepAsk yourselfWatch out for
ParticipationHow well do the results represent the team?Low participation and small group effects
Big pictureWhich dimensions are strong and which are weak?Before drilling into single items
ComparisonWhere are we against the organization and the previous period?The chance that small differences are random
High and low itemsWhat are we doing well, and which topics are connected?Do not skip strengths
ExpectationsWhat surprises me?Blind spots
CommentsWhich themes keep recurring?Do not look for the author

Common pitfalls when reading the report

Getting defensive. When you see a low score, it is easy to say "the team didn't understand" or "that's one employee's personal problem." Defensiveness is the biggest obstacle to learning from the data. The report shows the team's perception. Even when a perception is not accurate, it is real to the team and shapes their behavior.

Fixating on a single item. The lowest score usually attracts the most attention, but it is not always the most important problem. Several mid-level items that are connected can reveal a larger pattern than one low item.

Interpreting swings in a small team. In a team of eight, one person answering differently can shift the average noticeably. Do not read small score changes as either "great" or "a disaster."

Trying to find the author. Guessing who wrote a comment from its tone, the incident it mentions or when the person works damages the trust relationship in ways that are hard to repair. The team becomes more likely to stop answering in later surveys or to give "safe" answers.

Ignoring good scores. Focusing only on low scores sends the team the message "they only see us through our shortcomings." Owning the strengths and saying thank you prepares the ground for the development conversation.

Looking only at your own team. If a low score is low across the whole organization, the source of the problem may lie outside your team. Comparing with the organization and unit helps you tell which problem is yours and which is wider.

A team score is not a manager's performance grade

Many managers read the report as their own performance review. Yet a team score is the product of many factors: how long the team has existed, the changes it has gone through, workload, physical working conditions, decisions coming from senior management. Interpretations made without accounting for these factors can be both unfair and misleading.

Still, the manager has a share. In particular, the items directly related to the manager, that is feedback, recognition, communication and fairness, are often the most decisive part of team scores. If you are curious how these items are built and what they measure, see our article on the anatomy of first-line manager questions. Seeing the results not as a personal verdict but as a map of areas you can develop is in the interest of both you and your team.

After reading: Prepare for your first conversation with the team

Going back to the team after reading the report is the most critical step of the survey process. Silence tells employees "what we said interested no one." We suggest this short preparation before the conversation:

Prepare a one-page summary. The page should include:

  • Two or three of the team's greatest strengths.
  • One or two areas that need development.
  • One or two questions you want to clarify with the whole team.

Instead of handing out raw tables and comments, talking from the summary makes both you and the team more productive.

Say up front that you will listen first. An opening like "This is how I read the results, I may be wrong, how do you see it?" creates an atmosphere of curiosity instead of defense. On some topics, a focus group after the survey can also be used to understand the reasons behind the numbers.

Do not underline scores; focus on behavior. Saying "there is feedback that information reaches you late, how can we improve this together?" instead of "the communication score is 62" makes the conversation concrete.

Stay within the organization's framework when sharing results. What information can be shared with the team and at what level of detail varies by organization. For details, see sharing employee survey results with employees.

End with a small, concrete commitment. At the end of the first conversation, agreeing on one or two small, concrete steps is enough, rather than big promises. For turning these steps into an action plan, assigning an owner and a date and setting up a follow-up rhythm, our 90-day action plan after the survey article gives detailed guidance.

If the results came out much lower than you expected, our article on what to do when employee survey results are bad can also help you move forward without panic.

When should you ask for support?

You are not expected to solve everything alone. Asking for help from your HR business partner, your own manager or internal support teams is the right step in these situations:

  • If the sources of low scores lie in organizational matters outside your control.
  • If the comments contain a serious sign of inappropriate behavior, discrimination or a safety concern. Do not manage such findings on your own; pass them to the relevant function.
  • If you need a neutral facilitator to rebuild the team's trust.
  • If scores have been falling for several periods and what you have done is not working.

On deeper topics such as psychological safety, additional measurement may be needed. You may find our psychological safety survey article useful for this.

For HR and leaders: How to design a good manager report

How readable manager reports are depends largely on their design. For the teams that prepare them, these principles make a difference:

  • Keep it simple. Instead of fifty pages of tables, give the manager a short summary on the first page that conveys the big picture.
  • Highlight strengths. A report that at first glance shows only shortcomings increases defensiveness.
  • Give comparisons with context. Add indicators showing whether small differences are meaningful.
  • Protect confidentiality thresholds. Not showing results for very small groups protects trust.
  • Add a reading guide. A short guide on how to read the report and suggestions for conversations with the team increase the rate at which managers move to action.
  • Do not leave the manager alone. Report distribution should be planned together with a short briefing session and, where needed, one-to-one support.

For how to present results to management and across the organization, see our article on how to analyze and present employee survey results.

Conclusion

The manager report is a compilation of what your team has told you. Reading it not as a report card but as the start of a conversation serves both you and your team. First check participation and reliability, look at the big picture and the comparisons, own the strengths, look for patterns in the low items and read the comments by theme. Then talk with your team around a short summary and start with a small, concrete step.

The path from reading the report to putting action into practice is where the real value of the survey emerges. If you would like consulting support on report reading sessions for team leaders, manager report design and turning results into team actions, get in touch with us.

Start preparing your survey
Our guide includes sample questions and a step-by-step preparation checklist.
Download the Guide

Frequently asked questions

My team report came out below the organization average. Does that mean I am a bad manager?

No. A team score cannot be read apart from the team's context. A newly formed team, a unit going through heavy change, shift workers or a group under high pressure can all produce different results. What matters is not only where the score sits against the organization average, but also the direction compared with your team's previous period and how you respond to the result.

Which score should I look at first in the team report?

Look at the participation rate first, because with low participation the scores may not represent the whole team. Then look at the overall index or dimension-level results. Only after you have seen the big picture should you drill into individual items, which keeps you from spending time in the wrong place.

Is it acceptable to try to find out who wrote an open-ended comment?

No. Trying to identify the author of data that was collected under a promise of anonymity is unethical and seriously damages participation and honesty in the next survey. Read comments as themes, independent of individuals.

How far can I trust results if scores swing a lot in a small team?

In small teams, even a single person's answer can shift the average noticeably. So do not read meaning into a single point difference. Look at patterns seen across several items, a direction consistent with previous periods and recurring themes in the open-ended comments. Talking with your team is the most reliable complement to the numbers.

When and how should I share the report with my team?

Share it within a few weeks at most after the report reaches you, once you have done your own reading and prepared a short summary. Start with strengths, then development areas and what you understood, and then ask them. Rather than handing over the raw tables, it is usually more productive to run the conversation around a one-page summary.

How should I build the action plan after the report?

First choose one or two priorities by talking with your team, then define small, concrete actions with an owner, a date and a measure. For a step-by-step roadmap, see our article on the 90-day action plan after the survey.

Author
Digital Institute
A research and consulting firm that runs employee satisfaction and engagement surveys, bringing research, technology and consulting together.