55 manager feedback survey questions to ask employees in 2026

What is a manager feedback survey and what is it for?

A manager feedback survey is an anonymous, upward-only questionnaire in which a manager's direct reports rate the manager's observable behaviors. Its single purpose is development, not evaluation, and only direct reports respond. These questions measure behavior, not personality, which is what managerial effectiveness actually means in practice. Each category below maps to one of the competencies these questions map to.

Results are for development, not compensation. This is not a semantic distinction. When employees believe their answers will affect their manager's pay or promotion, they suppress negative scores. The instrument stops measuring reality and starts measuring what employees think is safe to say.

Terminology: what each instrument is for

How does a manager feedback survey differ from a 360 review and a performance review?

Only direct reports respond to a manager feedback survey. Peers, reports, and the manager's own manager all respond to a 360. Only the manager responds in a performance review. That distinction determines what the data measures and what you can do with it.

Start here if: your organization has fewer than roughly 500 employees and no existing upward feedback program. A manager feedback survey is lower admin, faster to run, and produces actionable data within a single cycle. Add a 360 once you have two or three waves of manager feedback data to give the broader process a baseline to build on.

How many questions should a manager feedback survey have?

Keep the annual survey to 10 to 15 items. The quarterly pulse should be 5 to 8 items. A new-manager check-in needs only 5 to 6 items. Length is the single biggest driver of drop-off, because survey fatigue sets in faster than most HR teams expect.

Question type mix

• Likert (5-point agree-disagree scale): the primary format. Produces trend data you can compare across waves.
• Rating scale (1 to 10): useful for a single summary item, such as overall effectiveness. Gives a numeric score that is easy to benchmark.
• Behavioral: asks respondents to describe a specific instance. Higher quality signal but harder to aggregate.
• Open-ended: one or two per survey. Gives context that a scale item cannot. Do not use more than two, or completion drops sharply.

The most citable rule in this section: ask about observable behaviors only. Questions about abstract qualities force employees to guess, which produces unreliable data.

Item count by organization size

• Under 200 employees: 8 to 10 items per annual survey. Smaller populations produce more sensitive data and require fewer items to reach statistical confidence.
• 200 to 2,000 employees: 10 to 15 items. Enough scale to segment by department, tenure, and manager level.
• 2,000 or more employees: 12 to 18 items for the annual survey, 6 to 8 for the quarterly pulse. Larger populations can sustain a slightly longer instrument without completion-rate penalties, provided the items are tightly worded.

How often should you run a manager feedback survey?

Run a full survey once or twice a year. Run a pulse between waves. The governing rule: survey only as often as you can act on the results. Between full waves, run a short set of pulse survey questions for the quarterly check.

Allow enough time between waves for managers to actually share results and act. Surveying faster than you can act destroys participation. If employees give feedback and nothing visibly changes before the next survey opens, completion rates fall in the next wave.

What is a good manager effectiveness score?

On a 5-point scale, a score between 3.8 and 4.2 is typical for an established manager in a company with a functioning feedback culture. Scores above 4.3 indicate a strong performer. Scores below 3.5 warrant a development plan. A score on its own is not a diagnosis. Pair it with the ten metrics that sit behind the score.

Compare your result against broader engagement survey benchmark data before you decide it is a problem. Manager scores move with the wider engagement picture, so check eNPS benchmarks by industry too.

Can employees answer honestly about their own manager?

Yes, when the anonymity floor is enforced. Most hesitation in manager feedback surveys comes from fear of retaliation, not deliberate dishonesty. Response quality rises when employees know what the threshold is, who sees results, and how results will be used. Set a minimum of five responses before any team-level data is shared, state that clearly in the survey invitation, and honest answers follow.

Anonymity checklist

1. Minimum response threshold: set a minimum of five responses before any team-level result is shown to the manager or HR. State this number in the survey invitation. Do not allow any admin to override it to reveal partial results.
2. No individual response data visible to managers or admins: the platform must aggregate before display. Row-level data should not be accessible by any manager, HR business partner, or admin, even with elevated permissions.
3. Open-text comment masking in small teams: for teams with five to eight respondents, suppress open-text comments entirely or use sentiment aggregation only. A distinctive phrase in an open-text field can identify a respondent on a small team even when the rating is anonymous.
4. State the rule in the invitation: every survey invitation must include a plain-language explanation of what happens if fewer than five people respond. Employees on small teams are more likely to respond honestly when they know the result will not be reported if the threshold is not met.

If the underlying issue is trust in the survey process itself, run employee trust survey questions first.

How do you build a manager feedback survey template?

Seven steps: define the purpose, choose the categories, draft the items, choose the format and channels, pilot with a small group, finalize the template, then launch and set the review date. Each step has a named owner and an elapsed time.

How do you run a manager feedback survey across a mixed or deskless workforce?

Email-only delivery systematically excludes anyone without a company inbox, which in a mixed workforce is most of the frontline. This is the single most common reason manager feedback programs produce skewed data: the employees with the most direct contact with a frontline manager are the ones least likely to receive the survey. This applies specifically to manufacturing, retail, healthcare, and logistics workforces.

Surveys should reach each employee in their preferred language. Translated items must be reviewed by a fluent speaker, not machine-dumped. A machine translation that changes the meaning of a behavioral item produces invalid data.

Which questions should you change for remote, frontline, and new managers?

Swap the item, keep the driver. The thing you are measuring does not change, the observable behavior does. A question about communication clarity measures the same construct whether the team is fully remote or on a factory floor. What changes is which behavior makes communication clear in that context. Shift-based teams need different mechanics entirely. See manager effectiveness on the manufacturing floor.

What should you do when a manager scores low?

The HRBP owns the debrief, not the manager. A written development plan should exist within four weeks of results being shared. A low score is a development signal, not a verdict. Treating it as a verdict is what stops managers engaging with the process.

Before you build a plan, look at the pattern. In our experience, micromanagement is the most common low-score pattern. The development plan should name specific coaching skills the manager needs next. Low scores sometimes point at capacity, not capability, so check for manager burnout before you build the plan.

1. HRBP debriefs the manager on the scores (within two weeks of results): Walk through category scores alongside the benchmark. Name the two or three categories with the largest gap from the median. Present the development conversation as a coaching opportunity, not a disciplinary one.
2. Manager shares a summary with the team and names one thing they will change (within three weeks): This is the most important step for sustaining participation in future waves. Employees who see their manager act on feedback respond at higher rates in the next cycle. The manager does not need to share exact scores. They need to demonstrate that they received the feedback and are doing something about it.
3. Written development plan inside four weeks: The plan is owned by the manager, co-created with the HRBP, and reviewed by L&D. It names specific behaviors to change, not abstract goals like "be a better communicator." Each behavior has a defined indicator and a timeline.
4. Skip-level check at eight weeks: The skip-level manager has a brief informal conversation with two or three team members to gauge whether behavior has visibly changed. This is not a formal survey. It is a temperature check to catch early signs that the development plan is or is not working.
5. Re-measure on the next pulse: A single wave shows a position. Repeated waves show direction. Realistic movement over a 12-month period is 0.3 to 0.5 points on a 5-point scale for a manager who is actively working on their development. A larger jump in a single cycle is unusual and may reflect changed team membership rather than behavioral change.

What mistakes should you avoid in manager feedback surveys?

The single most costly mistake is collecting feedback and not closing the loop. Everything else on this list is recoverable. A program that surveys without acting trains employees to stop responding.

• Overly long surveys: More than 15 items in an annual survey or more than 8 in a pulse significantly reduces completion rates. Every item you add should replace one you remove.
• Ambiguous questions: Questions about abstract qualities, such as "Is your manager a good leader?" cannot be answered consistently. Two respondents will interpret it differently, and neither answer will tell you what to do.
• No anonymity: Named surveys produce suppressed, positively skewed data. If results are not anonymous, do not call it a feedback survey.
• One-size-fits-all: A question calibrated for an office-based manager may be meaningless for a shift supervisor in a manufacturing plant. Segment by workforce type and context before finalizing the item set.
• No action on results: Close the loop. Name one thing that changed. Do it before the next survey opens.
• Infrequent cycles: Annual-only surveys catch nothing in time to fix it. Add a pulse. The annual survey shows position; the pulse shows direction.
• Biased question design: Leading questions, double-barreled items, and loaded language all contaminate the data. Review every item against the principle: ask about one observable behavior, neutrally worded.

Vague vs behavioral