8 360 Feedback Questionnaires: Examples by Role and Goal

Title slide: '8 360 Feedback Questionnaires: Examples by Role and Goal' with purple hand-drawn icons (people, lightbulb, chart, target) around it.

Matching the questionnaire to the role and the review goal is what stops 360 feedback from turning into a bland annual exercise. A 360 feedback questionnaire works best when it matches the person, the rater group and the business outcome you want, whether that's leadership development, team health, customer experience or project recognition. In practice, that means using different question sets for managers, peers, direct reports, self-assessment, senior leaders, teams, customer-facing roles and project work.

If you've ever seen feedback collected with good intentions and then left sitting in a report nobody uses, you already know the problem. The questionnaire itself is only part of the process. The rest is the rater mix, the reporting rules, the follow-up conversation and the system that holds it together.

Microsoft Forms, Power Automate, Dataverse and Power BI can support the mechanics of collection, routing and analysis. HRManagement365, a UK and EU HR solution powered by Hubdrive and Microsoft and built on Microsoft Dynamics 365, Power Platform and Dataverse, extends that foundation with its own integrations, workflows, customisations and HR applications so the process can fit real operating rules rather than forcing teams into a generic template.

Table of Contents

1. Manager upward feedback questionnaire

An upward questionnaire gives direct reports a structured way to describe how a manager behaves day to day. The strongest versions focus on communication, fairness, support, decision-making and recognition, then leave space for examples that show where the relationship helps or hinders the team. I've seen this work best when the manager treats it as coaching input, not a score to defend.

An infographic showing the components of a 360 feedback questionnaire programme for employee development.

What to ask and who should answer

A practical question set often uses a 1 to 5 scale and asks whether the manager explains priorities clearly, follows through on commitments, gives fair access to opportunities and recognises good work in a timely way. In a UK professional services firm, annual upward feedback can be paired with a written development plan agreed between the manager and an HR business partner. A Dutch manufacturing team may use the same approach only for groups large enough to protect anonymity.

Practical rule: set the minimum rater number before launch and state it in the invitation, because trust collapses when people guess who said what.

Keep the questionnaire tight. Twelve to twenty items is usually enough to cover the behaviours that matter without exhausting respondents or producing sloppy comments. Direct reports should also know how the result will be used, especially in the first cycle, because linking upward feedback straight to bonus decisions usually damages candour before it improves performance.

Microsoft and HRManagement365 fit

With Microsoft Forms, HR teams can collect the responses, Power Automate can route reminders and close the survey window, Dataverse can hold the structured results and Power BI can show trends by team or cycle. That standard Microsoft stack works well for collection and reporting. HRManagement365 can then extend the process with configured question sets, role-based access, workflow approvals and development-plan tracking so the feedback becomes part of the HR record rather than a separate file on someone's desktop.

2. Peer feedback questionnaire

Peer feedback is where collaboration issues usually surface first. Colleagues see how someone shares information, responds under pressure, supports cross-functional work and handles disagreement, which often looks very different from the view a manager gets. In matrix teams, or in finance and operations environments where one person depends on several other roles, peer feedback is often the most honest rater group in the room.

A UK retail group using Business Central can ask finance analysts to nominate peers from other departments, which broadens the lens beyond the immediate team. A Dublin-based software services company may run a smaller quarterly pulse survey with just a few questions, because the point is to track collaboration patterns more often, not to build a heavyweight annual review.

Keep it behavioural, not personal

Peer questions should describe observed behaviour, not personality. Ask whether the person shares information before deadlines, keeps colleagues informed when priorities change, or raises issues early enough for others to act. Training the raters matters here, because even well-meaning colleagues can drift into vague praise or personal frustration if the prompt is too broad.

Ask about what people have seen, not what they assume. That one discipline makes peer feedback far more usable.

A balanced rater list helps too. One colleague from outside the immediate team can stop the questionnaire from becoming a local popularity test, while a small cap on the number of peer requests per cycle keeps the process fair. HRManagement365 can support this by controlling rater rules, making sure the right colleagues are invited, and keeping visibility restricted to authorised reviewers.

See also how organisations can manage employee comments on appraisal when they need cleaner comment handling and more consistent review workflows.

3. Direct report feedback questionnaire

Direct report feedback is the version most managers remember, because it's the one that reveals how their leadership lands from below. It goes beyond general upward feedback and looks closely at delegation, trust, performance conversations, workload handling, wellbeing support and the way a leader uses authority. In UK and EU organisations, that can be especially useful where managers also handle absence, flexible working or sensitive people issues.

A UK charity might only collect direct report feedback for managers with at least four team members, then discuss the results in a facilitated session led by an external coach. A Belgian logistics company may combine the questionnaire with its engagement survey so it can spot teams where clarity on priorities is weak and leadership support needs work.

Protect anonymity and make the next step obvious

The anonymity threshold matters more here than in most questionnaires. If a team is tiny, direct reports can identify each other from the detail alone, so reporting should be suppressed or grouped until the sample is safe. Comments should stay optional, but the wording needs to encourage useful examples, not venting.

  • Ask about support, not style: prompts like “What is one way this manager could help you grow?” produce more useful answers than broad personality questions.
  • Use a minimum reporting threshold: explain up front why very small groups won't be shown separately.
  • Give a development path: share coaching, manager training or follow-up review steps with the score, not just the score itself.

The legal and operational context matters too. A manager who receives feedback about how they handle absence conversations or workload pressure needs a route to improve, not a report that sits untouched. HRManagement365 can connect the feedback cycle to objectives, development actions and follow-up tasks so the outcome is an actual management plan rather than a static result page.

Read more on what direct reports are if you need to align the rater group with the right reporting structure.

4. Self-assessment questionnaire

Self-assessment works because it exposes the gap between how someone sees their own performance and how others experience it. That gap isn't a flaw in the process. It's usually the most useful part. The principle goes back to the Johari window, developed by Joseph Luft and Harrington Ingham in 1955, which is a neat way of explaining why self-awareness and external feedback don't always line up.

A UK-based finance team at a mid-market manufacturer might ask each employee to complete a self-assessment before the annual review and bring two examples of achievement plus one development goal to the meeting. An Irish public sector body may use the same approach at the start of a leadership programme, then work through the results in one-to-one coaching.

Ask for evidence, not confidence

The best self-assessments don't ask people to prove they're right. They ask people to reflect on behaviour with examples. That makes the result easier to compare with peer and manager feedback later, and it usually reduces the defensive reaction that can come from a blunt rating gap.

Self-assessment should feel like preparation for a useful conversation, not a test you can fail.

Keep pay decisions separate where possible. Once self-ratings feel tied to reward, the honest reflection often disappears and the questionnaire turns into a negotiation tool. A manager or coach should help the employee compare the self-view with the wider feedback set, because that's where the development plan usually gets sharper.

The structure also fits reflective practice in other professional settings, including improve patient care through reflection, where the value comes from examining what happened and what changes next.

5. Leadership competency questionnaire

Leadership questionnaires work best when an organisation has a defined competency framework and wants to assess senior leaders against observable expectations. They support executive development, succession planning and leadership programme design alongside the annual review. The rater mix is usually wider, bringing together managers, peers, direct reports and, where relevant, external stakeholders.

A UK housing association might use feedback to shape an executive development plan around several named behaviours. A UK wholesale business using Business Central could assess emerging managers before a new distribution site opens, identifying where its leadership bench needs more depth.

Tie the questions to the real job

Generic leadership language rarely produces useful feedback. Strategic thinking, change leadership, financial judgement and capability building need to become behaviours that raters can see and describe. Questions should ask for evidence, such as how a leader sets priorities during change, handles competing commercial pressures or develops people through delegation and coaching.

  • Align to strategy: use a framework that reflects the organisation's direction rather than copying an external template.
  • Protect access: limit results to people with a genuine development or succession purpose.
  • Use facilitated feedback: an experienced facilitator can help leaders interpret patterns, differences between rater groups and the trade-offs behind the scores.
  • Review annually: strategy, technology and organisational priorities change, so the framework should change with them.

Leadership feedback becomes more useful when it connects to a defined development action, such as coaching, a leadership programme or a broader management capability pathway. HRManagement365 can configure leadership question sets, restrict report access, and connect results with management training and development workflows. Microsoft Teams and Microsoft 365 can support scheduling and follow-up where those tools already form part of the organisation's working process. HRManagement365 extensions may add the questionnaire, reporting and workflow controls that standard Microsoft functionality does not provide.

6. Team effectiveness questionnaire

A team questionnaire measures collective functioning, and a weak result can point to unclear goals, a broken approval path, a trust problem or a role design issue. Each cause needs a different response. J. Richard Hackman's work on team effectiveness helps keep the review focused on direction, structure, context and coaching rather than personality judgements.

A UK finance operations team using Finance and Operations might run a survey after a systems migration and find that decision rights are slowing work. A multinational HR shared service in the EU could repeat the same pulse questionnaire each quarter to monitor whether collaboration across countries improves or deteriorates.

Tie the questions to the actual job

Use questions that describe observable team behaviour. Can people agree priorities when requests conflict? Do decisions reach the right owner without repeated escalation? Are handovers clear enough for colleagues in another country or function to act without rework? These questions connect the score to a review goal, such as improving delivery after a technology change or clarifying responsibility across a shared service.

Keep the findings at team level. Using them to rank individual colleagues will reduce candour and turn the questionnaire into a blame exercise. Share the results with the whole team, agree two or three priorities together, then repeat the questions after a few months to assess whether working practices have changed.

The video below walks through how a team effectiveness trend dashboard can be built in Power BI without exposing small-group identities.

Standard Microsoft functionality can support the survey, collaboration and dashboarding, while HRManagement365 extensions may connect team feedback to structured actions, approval flows and reporting controls. The practical safeguard is to define the minimum group size for reporting before collection begins, then use the results to track whether an agreed process change has taken hold.

7. Customer-facing role questionnaire

Customer-facing questionnaires work differently because part of the feedback comes from outside the organisation. That means the questionnaire has to separate the employee's behaviour from the wider service context, otherwise the score becomes a jumble of product issues, pricing objections and operational delays. For account managers, service advisers, sales staff and support teams, the useful questions are the ones that isolate responsiveness, clarity, professionalism and relationship management.

A UK-based distributor using Dynamics 365 Business Central can link customer surveys to order records so account managers review feedback alongside the relevant delivery. A UK professional services firm may send a short survey after project milestones and split delivery quality from commercial terms so the employee isn't blamed for something outside their control.

Keep the customer ask short and lawful

Customer surveys should stay brief, ideally with three questions or fewer. If you ask too much, response rates usually drop and the comments get thinner. The privacy notice also needs to be clear before the data is collected, especially when those responses will be linked back to an employee record.

Separate what the employee controls from what the business controls. That's the difference between a fair review and a misleading one.

The practical question set is usually simple. Did the employee respond promptly, explain things clearly and deal with issues professionally? Then add a separate prompt for wider factors, such as products, pricing or operations, so the context is visible and the conversation stays fair. HRManagement365 can connect those customer responses to employee records, while keeping access controls and reporting rules aligned with the organisation's chosen governance model.

8. Project-based feedback questionnaire

Project feedback is strongest when the work is still fresh. A questionnaire issued at project closure captures delivery, collaboration, stakeholder management, risk handling, quality and learning before memory fades into general impressions. That makes it especially useful for organisations running ERP, HR or change projects where people have worked across technical, functional and operational boundaries.

A UK manufacturing SME implementing Business Central might ask each workstream lead for feedback at the end of data migration, training and go-live support. A UK local authority could use a project questionnaire to recognise HR and IT colleagues who helped launch a new employee self-service portal.

Keep the feedback anchored to deliverables

The best project questionnaires ask raters to name the deliverables they saw. That keeps the answers specific and stops the process from turning into a personality review. A short lessons-learned question is also worth including, because it turns the feedback into better planning on the next project instead of a one-off thank-you note.

  • Issue it quickly: send the questionnaire within two weeks of project close while the details are still clear.
  • Ask for evidence: tie feedback to milestones, handovers, testing or stakeholder support.
  • Capture learning: include one question about what should change next time.
  • Use the result twice: feed it into recognition and also into future resourcing decisions.

Project-based review works particularly well in Microsoft-centric organisations because the same environment can hold delivery records, feedback forms, follow-up actions and reporting. HRManagement365 can extend that setup with custom workflows, approvals and reporting so recognition and development don't get lost between the project team and HR.

360-Degree Feedback Questionnaires: 8-Way Comparison

Questionnaire Type Process / Complexity 🔄 Resource Requirements ⚡ Expected Outcomes 📊 Ideal Use Cases 💡 Key Advantages ⭐
Manager (Upward) Feedback Questionnaire Moderate, anonymous distribution, aggregation rules and coaching debriefs Forms + workflows (reminders, anonymity rules), reporting and HR coaching time Behavioural insight on line managers; development actions; early issue detection Development-focused 360 cycles; managers with teams above confidentiality threshold Reveals upward perspective managers rarely receive; supports coaching and culture of upward feedback
Peer (Colleague) Feedback Questionnaire Low–moderate, rater selection and approval to avoid bias Lightweight pulse tools, rater management and brief rater guidance Cross‑functional collaboration and influence insights grounded in examples Matrix organisations, finance/operations, quarterly pulse checks Highlights day‑to‑day collaboration; strengthens teamwork; practical examples for development
Direct Report Feedback Questionnaire Moderate, strong anonymity safeguards and facilitated follow‑up Forms, anonymised aggregation logic, facilitation or coaching for leaders Clear view of people leadership behaviours and psychological safety issues Managers of teams where people leadership is central; small team considerations Direct evidence of how leaders support and develop staff; uncovers micromanagement or inconsistency
Self‑Assessment Questionnaire Low, simple to administer but needs careful framing to avoid bias Minimal tooling; linkage to development records and coach/manager time Baseline self‑view; prompts reflection and prepares for feedback conversations First step in 360s, coaching programmes and personal development planning Encourages ownership of development; highlights gaps between self and others
Leadership Competency Questionnaire High, competency framework, multi‑rater design and confidentiality controls Significant: framework maintenance, analytics, secure access and senior coaching Strategic capability mapping, succession insight and targeted leadership development Executive development, succession planning and leadership pipeline reviews Creates shared leadership language; links competencies to business outcomes and succession
Team Effectiveness Questionnaire Moderate, team‑level design, aggregation and repeat measurement Forms with team aggregation, facilitated team sessions and action tracking Identifies structural vs behavioural vs relational issues; team action plans Team development after change, post‑migration or when under pressure Focuses on collective functioning; provides a shared baseline and tracks progress
Customer‑Facing Role Questionnaire Moderate, combines internal and customer inputs and GDPR checks CRM integration, short customer surveys, privacy/legal oversight and linking to cases Connects individual behaviours to customer experience and service outcomes Account managers, sales and support roles; post‑interaction surveys linked to CRM Links employee behaviour to customer outcomes; useful for coaching and process fixes
Project‑Based Feedback Questionnaire Moderate, project anchors, stage gate triggers and varied stakeholders Integration with project records, timely distribution at close and stakeholder coordination Timely evidence of project contributions; lessons learned and skills capture Project closures, implementations (ERP, Dynamics, Power Platform) and programme reviews Captures fresh, specific evidence of delivery and collaboration; informs resourcing and recognition

From sample questions to a working feedback cycle

A strong 360 feedback questionnaire is only useful if the organisation turns it into a repeatable cycle. Start with one team or one role family, rather than rolling it out everywhere at once. That gives HR a chance to test the rater mix, the wording, the reporting thresholds and the manager follow-up before the process becomes business-as-usual.

The safest pattern is simple. Define the purpose before launch, set a minimum rater threshold, tell people exactly how results will and won't be used, then review the process after the first cycle. If the questionnaire is for development, keep it separate from pay and promotion in the first instance. If it's for a leadership group or project team, make sure the follow-up is tied to concrete actions, not just a report in circulation.

UK and EU organisations also need to be deliberate about governance. The ICO says workers should be consulted where workplace monitoring is being introduced and that retention, access and lawful basis need to be clear. Even when a 360 process is not traditional monitoring, the same discipline helps because feedback still becomes personal data once it's linked to an employee record. Acas guidance on performance reviews also supports making the discussion structured, written down and focused on what the person does well, where they need support and what development comes next.

HRManagement365 fits naturally here. It's a flexible UK and EU HR solution powered by Hubdrive and Microsoft, extended with its own integrations, customisations, workflows and applications to solve real-world HR and employee lifecycle requirements. Built on Microsoft Dynamics 365, Power Platform and Dataverse, it can support feedback forms, rater rules, access control, workflow approvals and reporting in one environment, while keeping the process close to the rest of the HR and Microsoft estate.

For many teams, that combination is the difference between collecting opinions and managing a feedback cycle. The questionnaire, the rater logic, the manager review and the action plan can all sit together, which makes follow-up easier and reporting more reliable.

Speak to an HRManagement365 specialist

Discover how HRManagement365, powered by Hubdrive and Microsoft, can help improve, connect and automate your HR processes across the UK and EU.

Phone +44 1522 508096 today

Send us a message:
https://www.hrmanagement365.com/contact/


HR Management 365 can help you build 360 feedback questionnaires that fit real roles, rater groups and review goals, with Microsoft-based workflows for collection, routing and reporting. If you want a process that's easier to govern and simpler to follow through, visit HR Management 365 to see how it can support your HR review cycle.

author avatar
Chris Pickles Director | Dynamics 365, Power Platform & HR Solutions Architect
I help HR leaders get off the admin hamster wheel with a Dynamics-based HR Management solution built on Hubdrive. HRManagement365 gives organisations a flexible HR platform within the Microsoft ecosystem that can be easily customised around the way they already work — rather than forcing teams into rigid, one-size-fits-all processes. It can be tailored to your HR workflows, integrated with Microsoft Dynamics 365 Business Central (BC) and Finance & Operations (F&O), and extended with Microsoft Power Platform to automate processes and connect HR more closely with the wider business. For employees, the experience stays familiar. They can interact with HR processes through the Microsoft tools they already know and use every day, including Teams, Outlook, Word and Power BI, helping drive adoption without introducing another unfamiliar system. The goal is simple: less manual admin, better-connected processes and an HR solution that fits your organisation. If you’re using Microsoft Dynamics and want HR to work as part of the same ecosystem, ask me about HRManagement365.

Related Posts