This guide provides 360 practical prompts for a 360-degree feedback form, plus a printable blank template and a sample. Managers, people teams, project leads, and employees can select relevant prompts for a specific role, review cycle, or development conversation.
Role Clarity and Direction
- Clarifies priorities. Ask whether this person explains what matters most when several assignments compete for attention, so colleagues can focus their effort appropriately.
- Connects work to goals. Use this prompt to learn whether teammates understand how daily tasks contribute to team or organizational outcomes.
- Defines success clearly. Reviewers can describe whether expected results, quality standards, and deadlines are understandable before work gets underway.
- Sets realistic expectations. This item helps identify whether commitments account for available time, dependencies, and the capacity of the people involved.
- Explains changing priorities. Ask for an example of how the person communicates a shift in direction and what colleagues should do differently.
- Shares relevant context. This prompt suits cross-functional work, where people need enough background to make sound decisions without repeated clarification.
- Assigns ownership. Reviewers can note whether tasks have clear owners, decision-makers, and handoffs rather than being left between roles.
- Distinguishes urgent from important. Use this item when colleagues need to know which requests require immediate action and which can wait.
- Provides useful instructions. Ask whether directions include the necessary details while still allowing others to apply their own expertise.
- Checks shared understanding. This prompt reveals whether the person confirms that everyone has interpreted an assignment or decision in the same way.
- Explains decision boundaries. Reviewers can assess whether people know what they may decide independently and when approval is needed.
- Communicates deadlines early. This item is useful for spotting avoidable last-minute pressure caused by late notice of due dates.
- Explains dependencies. Ask whether the person makes upstream and downstream responsibilities visible so teams can coordinate their timelines.
- Maintains consistent direction. This prompt helps assess whether guidance stays coherent across meetings, messages, and changing circumstances.
- Updates plans when needed. Reviewers can describe whether revised plans are shared promptly when assumptions, resources, or delivery dates change.
- Uses clear language. Ask whether instructions avoid unexplained acronyms and jargon, especially when audiences include people from different specialties.
- Summarizes decisions. This item checks whether conversations end with a clear record of what was decided, by whom, and by when.
- Connects priorities to capacity. Reviewers can note whether the person adjusts requested work when the team has limited time or staffing.
- Explains the reason behind requests. This prompt helps colleagues understand the purpose of work instead of following directions without context.
- Sets measurable milestones. Ask whether long assignments are broken into checkpoints that make progress and emerging risks visible.
- Uses a dependable planning rhythm. Reviewers can assess whether regular planning updates help people prepare rather than react to surprises.
- Identifies assumptions. This item is valuable when a project depends on estimates or information that may not yet be confirmed.
- Clarifies scope. Ask whether the person explains what is included in a request and what falls outside its boundaries.
- Protects focus. Reviewers can describe whether unnecessary changes or interruptions are limited when concentrated work is important.
- Explains escalation routes. This prompt checks whether colleagues know whom to contact when a blocker exceeds their authority or expertise.
- Aligns expectations across groups. Use this item when several teams must agree on timing, deliverables, or service responsibilities.
- Revisits priorities at sensible intervals. Reviewers can say whether the person checks that earlier plans still fit current conditions.
- Balances detail with autonomy. Ask whether guidance provides enough direction without dictating every step of a colleague’s approach.
- States meeting purpose. This item helps determine whether participants know the desired decision or outcome before joining a discussion.
- Communicates what has changed. Reviewers can assess whether updates distinguish new information from details that remain unchanged.
- Defines quality standards. Ask whether examples, acceptance criteria, or review steps make the expected level of work concrete.
- Clarifies handoff requirements. This prompt is useful where one person’s deliverable becomes another person’s starting point.
- Resolves conflicting instructions. Reviewers can describe whether the person notices contradictory requests and helps establish one agreed direction.
- Provides a useful roadmap. Ask whether the person explains the sequence of work, key checkpoints, and likely decision points.
- Confirms availability and response expectations. This item helps teams coordinate when people have different schedules or responsibilities.
- Reframes goals when circumstances change. Reviewers can explain whether the person preserves the intended outcome while adapting the route.
Communication and Listening
- Listens without interrupting. Ask whether the person lets colleagues finish explaining concerns before responding or proposing a solution.
- Asks clarifying questions. This prompt reveals whether the person checks meaning instead of relying on assumptions about someone else’s request.
- Adapts communication to the audience. Reviewers can note whether technical detail is adjusted for people who need a different level of explanation.
- Shares information at the right time. Use this item to identify whether colleagues receive updates early enough to act on them.
- Writes messages that are easy to follow. Ask whether written communication has a clear purpose, relevant details, and an explicit next step.
- Responds within agreed timeframes. This prompt is more useful when reviewers consider stated response norms rather than expecting constant availability.
- Checks understanding respectfully. Reviewers can describe whether the person confirms comprehension without making others feel tested or embarrassed.
- Communicates disagreement directly. Ask whether concerns are raised with the people involved instead of being circulated through unhelpful side conversations.
- Uses a considerate tone. This item invites specific observations about word choice and delivery during ordinary work and stressful exchanges.
- Gives others room to contribute. Reviewers can assess whether quieter participants have meaningful opportunities to speak during group discussions.
- Summarizes what they heard. This prompt helps show whether the person understands another viewpoint before moving to a decision.
- Shares bad news promptly. Ask whether the person communicates setbacks early enough for colleagues to adjust plans and reduce avoidable disruption.
- Separates facts from interpretation. Reviewers can note whether reports distinguish confirmed information from personal assumptions or emerging possibilities.
- Uses appropriate communication channels. This item helps assess whether urgent issues, sensitive matters, and routine updates receive suitable handling.
- Explains complex topics simply. Ask for an example of a difficult subject made understandable without removing important qualifications or detail.
- Invites questions. This prompt checks whether the person creates space for clarification instead of treating questions as resistance.
- Gives concise updates. Reviewers can describe whether status reports foreground decisions, risks, and requests rather than burying them in detail.
- Maintains confidentiality in conversations. Use this item to assess discretion around information that should not be shared broadly.
- Shares credit accurately. Ask whether communication recognizes colleagues’ contributions and does not imply one person completed shared work alone.
- Raises risks constructively. This prompt helps distinguish useful early warnings from criticism that offers no information about next steps.
- Notices nonverbal cues. Reviewers can reflect on whether the person checks in when someone appears confused, concerned, or ready to speak.
- Uses accessible meeting language. Ask whether participants can follow discussion without needing unexplained shorthand or insider references.
- Closes communication loops. This item checks whether requests receive an answer or a clear notice that more time is needed.
- Gives people time to respond. Reviewers can note whether the person allows thoughtful pauses rather than demanding instant agreement.
- Communicates across differences. This prompt is useful for assessing respect and clarity when colleagues have different styles or backgrounds.
- Explains the basis for a decision. Ask whether the person shares the relevant considerations, even when not every preference can be accommodated.
- Uses feedback language carefully. Reviewers can describe whether observations focus on actions and effects instead of labels about character.
- Handles sensitive conversations privately. This item helps assess judgment about setting, timing, and audience for difficult discussions.
- Signals when they need more information. Ask whether the person acknowledges uncertainty rather than presenting an incomplete answer as final.
- Follows up after discussion. Reviewers can assess whether important conversations lead to a recap, assigned action, or scheduled check-in.
- Communicates appreciation specifically. This prompt encourages observations about recognition that names a helpful action and its practical effect.
- Receives questions with patience. Ask whether the person treats repeated or basic questions as a chance to clarify shared understanding.
- Adjusts detail as a discussion develops. Reviewers can note whether explanations become more focused when participants identify what they need.
- Uses examples to make ideas concrete. This item works when a proposal or process is difficult to understand in abstract terms.
- Checks tone in written messages. Ask whether concise writing remains respectful and does not create unintended urgency or blame.
- Communicates a clear next step. Reviewers can describe whether people leave an exchange knowing who will do what and when.
Collaboration and Teamwork
- Shares useful knowledge. Ask whether the person makes relevant expertise available instead of allowing information to remain isolated with one individual.
- Follows through on shared commitments. This prompt helps teammates describe whether agreed contributions arrive when others need them.
- Offers help without taking over. Reviewers can assess whether support strengthens another person’s ownership rather than replacing it.
- Coordinates handoffs reliably. Use this item when work passes between roles and missing context could cause rework or delay.
- Includes affected colleagues early. Ask whether people who will implement or maintain a decision are consulted before it is finalized.
- Contributes to group problem-solving. This prompt focuses on actions such as sharing evidence, testing options, and building on others’ ideas.
- Respects team agreements. Reviewers can note whether the person follows shared procedures and raises concerns before changing them.
- Shares workload fairly. Ask whether responsibilities are distributed with attention to capacity, skills, and deadlines rather than convenience alone.
- Supports colleagues during pressure. This item invites concrete examples of practical assistance during a busy or difficult period.
- Brings disagreements back to the work. Reviewers can assess whether conflict stays focused on decisions and evidence, not personal attacks.
- Credits collaborative effort. Ask whether the person names partners who contributed ideas, analysis, or delivery when reporting results.
- Builds on others’ contributions. This prompt reveals whether discussion develops ideas rather than repeatedly restarting from one person’s preferred approach.
- Makes participation equitable. Reviewers can describe whether relevant voices are included even when they hold less senior roles.
- Shares resources responsibly. Use this item to assess whether the person gives teammates access to materials, time, or expertise they need.
- Respects other people’s time. Ask whether the person arrives prepared and avoids creating unnecessary meetings or rushed requests.
- Provides reliable backup. Reviewers can note whether the person documents essential work so colleagues can cover when needed.
- Works constructively across roles. This prompt is useful when functions have different measures of success or distinct constraints.
- Offers a useful perspective. Ask whether the person contributes information that helps the group see risks, options, or consequences more clearly.
- Accepts shared responsibility. Reviewers can describe whether the person owns their part of a team outcome without blaming partners reflexively.
- Asks before assuming availability. This item checks whether requests respect colleagues’ commitments and give them room to negotiate timing.
- Helps new teammates connect. Ask whether the person explains working relationships and practical team norms to people joining the group.
- Documents collaborative decisions. Reviewers can assess whether agreements remain accessible to everyone responsible for carrying them out.
- Contributes consistently in meetings. This prompt invites examples of preparation, relevant input, and attention to the group’s stated purpose.
- Supports a colleague’s development. Ask whether the person shares feedback or opportunities that help others build role-relevant skills.
- Offers assistance across boundaries. This item is useful when shared outcomes depend on cooperation between teams with separate workloads.
- Honors agreed roles. Reviewers can note whether the person respects ownership while still raising concerns about a risk or gap.
- Helps resolve bottlenecks. Ask for an example of a practical action that helped work move through a blocked stage.
- Shares lessons from completed work. This prompt checks whether experience is made available to colleagues facing a similar task.
- Handles shared materials carefully. Reviewers can describe whether documents, equipment, or common workspaces are left usable for others.
- Recognizes different strengths. Ask whether the person notices complementary skills and involves colleagues where those skills can contribute.
- Builds agreement without forcing it. This item helps assess whether the person distinguishes genuine alignment from silence or reluctant compliance.
- Coordinates calendars thoughtfully. Reviewers can note whether the person considers time zones, notice, and essential attendance when scheduling.
- Clarifies mutual expectations. Ask whether collaborators agree on response times, ownership, and quality before relying on one another.
- Shares responsibility for team norms. This prompt encourages examples of constructive action when a working agreement is not being followed.
- Maintains cooperative relationships after disagreement. Reviewers can assess whether people can continue working together once a decision is made.
- Contributes beyond personal credit. Ask whether the person supports the team’s result even when their own contribution is less visible.
Execution and Reliability
- Meets agreed deadlines. Reviewers can consider whether deliverables arrive when promised or whether delays are communicated early with a recovery plan.
- Produces dependable work. This item invites examples of accuracy and consistency across ordinary assignments, not just high-profile projects.
- Prepares before starting. Ask whether the person gathers requirements, materials, and approvals before work reaches a preventable stall.
- Tracks open actions. Reviewers can describe whether commitments are recorded and revisited rather than relying on memory alone.
- Completes work with suitable care. This prompt helps identify whether the person checks details that matter to the intended use.
- Raises a likely delay early. Ask whether colleagues receive warning while there is still time to adjust dependencies or scope.
- Uses time effectively. Reviewers can note whether effort is directed toward agreed priorities without expecting every moment to be visible.
- Maintains accurate records. This item suits roles where others rely on current notes, decisions, or status information to continue work.
- Follows established processes. Ask whether the person uses required steps and proposes a reasoned change when a process fails.
- Checks work before handoff. Reviewers can assess whether obvious errors and missing information are caught before another person receives the task.
- Manages several assignments. This prompt reveals how the person communicates competing deadlines and protects the most important commitments.
- Completes administrative follow-through. Ask whether routine approvals, notes, or required updates are finished promptly enough to keep work moving.
- Delivers what was agreed. Reviewers can compare the promised scope with the delivered result and note any clearly explained changes.
- Uses resources carefully. This item focuses on thoughtful use of shared time, materials, and effort within the person’s role.
- Maintains a workable task system. Ask whether the person can identify current priorities and outstanding actions when colleagues need an update.
- Responds to blockers with action. Reviewers can describe whether the person seeks help, tests alternatives, or clarifies a dependency.
- Balances speed and accuracy. This prompt is useful when deadlines matter but careless errors would create significant rework.
- Completes promised follow-up. Ask whether the person returns with information or a decision by the time they committed to.
- Uses checklists where useful. Reviewers can note whether repeatable tasks receive consistent attention without imposing unnecessary process on novel work.
- Plans for predictable risks. This item invites examples of preparation for known constraints such as review cycles or seasonal workload.
- Maintains continuity during absence. Ask whether essential work and contacts are documented so colleagues can respond while the person is away.
- Corrects errors promptly. Reviewers can describe whether the person acknowledges a mistake, fixes its effects, and informs affected colleagues.
- Keeps project status current. This prompt helps others make decisions from an accurate view of progress, risks, and next milestones.
- Closes completed tasks. Ask whether work is formally wrapped up with the necessary records, handoffs, or notifications.
- Uses meeting time productively. Reviewers can assess preparation, focus, and whether the discussion ends with useful outcomes.
- Protects quality under pressure. This item asks how the person handles shortcuts when workload or timing becomes difficult.
- Maintains commitments during change. Reviewers can note whether the person renegotiates clearly when a new request affects existing work.
- Checks dependencies before delivery. Ask whether required input, approvals, or supporting materials are in place before a deliverable is marked complete.
- Provides realistic progress estimates. This prompt helps distinguish a useful forecast from an optimistic date unsupported by current information.
- Uses feedback to improve the next delivery. Reviewers can describe whether recurring corrections lead to a practical change in process.
- Documents repeatable work. This item is useful when another teammate may need to perform the task or cover it later.
- Meets agreed attendance expectations. Ask about dependability for essential meetings or shifts, while respecting approved flexibility and changing arrangements.
- Flags missing information. Reviewers can assess whether the person identifies gaps before they create errors or delay downstream work.
- Finishes work without excessive reminders. This prompt focuses on follow-through while allowing for legitimate changes in priority or capacity.
- Uses review time effectively. Ask whether the person arrives with specific questions or decisions rather than reopening settled details unnecessarily.
- Makes delivery status easy to verify. Reviewers can note whether colleagues can tell what is done, pending, and at risk.
Leadership and Decision-Making
- Sets an example through actions. Ask whether daily behavior matches the standards the person asks others to meet.
- Makes decisions at the right level. Reviewers can assess whether the person acts within their remit and seeks input when consequences extend beyond it.
- Explains trade-offs. This prompt helps colleagues understand why one option was chosen when every alternative has costs.
- Invites relevant perspectives. Ask whether people closest to the work are heard before decisions that affect their responsibilities.
- Takes responsibility for outcomes. Reviewers can describe whether the person addresses their contribution when a decision leads to an unwanted result.
- Uses evidence in decisions. This item encourages examples of information considered, including what remains uncertain or incomplete.
- Decides in a timely way. Ask whether the person avoids both rushed choices and unnecessary delay when others are waiting.
- Explains who was consulted. Reviewers can note whether the decision process is transparent enough for affected colleagues to understand.
- Balances consistency with judgment. This prompt is useful when established rules need thoughtful application to different circumstances.
- Delegates meaningful ownership. Ask whether assignments include authority and information, not just responsibility for completing a task.
- Supports decisions after agreement. Reviewers can assess whether the person helps implement a settled choice even if they initially preferred another option.
- Revisits a decision when evidence changes. This item recognizes that sound leadership includes correcting course when assumptions prove wrong.
- Protects time for important work. Ask whether the person helps the group avoid distractions that undermine agreed priorities.
- Explains decisions that affect workload. Reviewers can describe whether people receive enough notice and context to plan their work.
- Addresses performance concerns directly. This prompt asks whether expectations and observed gaps are discussed privately and with actionable examples.
- Recognizes good work promptly. Ask whether the person identifies meaningful contributions in a way that is specific and appropriate.
- Creates clarity during uncertainty. Reviewers can assess whether the person distinguishes known facts, open questions, and the next review point.
- Escalates decisions appropriately. This item helps identify whether risks reach the person or group with authority to address them.
- Uses authority responsibly. Ask whether decisions account for their effects on colleagues and avoid relying on status alone.
- Shares decision ownership. Reviewers can note whether the person credits contributors and remains accountable for the final call.
- Balances short-term and long-term needs. This prompt encourages examples where immediate delivery was weighed against future maintenance or team capacity.
- Sets useful team standards. Ask whether expectations are practical, understandable, and applied consistently across comparable situations.
- Handles mistakes without scapegoating. Reviewers can describe whether the response focuses on correction, learning, and fair accountability.
- Encourages responsible initiative. This item checks whether colleagues can act on opportunities without fear of arbitrary criticism.
- Maintains composure in difficult moments. Ask for observable examples of steady communication when a project encounters pressure or disappointment.
- Protects ethical working norms. Reviewers can note whether the person raises concerns when requested actions conflict with agreed standards.
- Explains changes in leadership direction. This prompt helps determine whether people understand what prompted a change and what follows.
- Uses meetings to reach decisions. Ask whether the person identifies the decision owner and prevents discussion from continuing without purpose.
- Develops future decision-makers. Reviewers can describe whether the person shares context and gradually gives others appropriate responsibility.
- Responds to dissent thoughtfully. This item assesses whether alternative views are considered before a choice is finalized.
- Allocates work transparently. Ask whether assignments reflect stated priorities and relevant skills rather than unexplained preference.
- Recognizes when a decision is reversible. Reviewers can note whether the person moves efficiently on low-risk choices and scrutinizes consequential ones.
- Provides direction without micromanaging. This prompt helps assess whether progress checks support delivery while preserving reasonable autonomy.
- Maintains accountability after delegation. Ask whether the person remains available for guidance without reclaiming every delegated decision.
- Connects decisions to agreed principles. Reviewers can describe whether choices reflect values the team has actually discussed and adopted.
- Closes the loop on unresolved decisions. This item checks whether postponed questions receive an owner and a specific revisit point.
Adaptability and Problem-Solving
- Adjusts approach when facts change. Ask whether the person can revise a plan without treating an earlier assumption as untouchable.
- Identifies the real problem. Reviewers can describe whether the person investigates causes before suggesting fixes for visible symptoms.
- Generates more than one option. This prompt reveals whether the person explores alternatives before committing the group to a single route.
- Tests assumptions practically. Ask whether the person seeks a small, informative check when a large decision rests on an uncertain belief.
- Learns from setbacks. Reviewers can note whether a difficult outcome leads to a specific adjustment rather than repeated blame.
- Stays useful when plans are incomplete. This item assesses whether the person can take sensible next steps while acknowledging uncertainty.
- Asks for help at the right time. Ask whether the person seeks expertise before a manageable challenge becomes a larger obstacle.
- Separates urgent response from root-cause work. Reviewers can assess whether immediate containment is followed by investigation where appropriate.
- Adapts to new constraints. This prompt suits changing budgets, schedules, requirements, or staffing, without assuming every change is avoidable.
- Uses feedback to revise an approach. Ask whether the person changes behavior when credible input shows that a method is not working.
- Remains curious about unfamiliar issues. Reviewers can describe whether the person asks informed questions rather than pretending to know everything.
- Recognizes when a workaround is temporary. This item helps colleagues distinguish short-term continuity measures from a completed solution.
- Breaks complex problems into steps. Ask whether the person identifies manageable questions, owners, and checkpoints for a complicated issue.
- Considers consequences before acting. Reviewers can note whether the person anticipates likely effects on customers, colleagues, or later work.
- Uses experiments proportionately. This prompt asks whether small trials are chosen when they can answer a question safely and efficiently.
- Stays open to a better idea. Ask for examples of the person adopting a colleague’s suggestion when it improves the outcome.
- Distinguishes a one-off issue from a pattern. Reviewers can assess whether repeated problems are tracked instead of treated as unrelated events.
- Finds a workable next step. This item focuses on practical movement when a complete answer is not immediately available.
- Changes course without losing the goal. Ask whether the person can adapt methods while keeping the intended result visible.
- Invites lessons after a project. Reviewers can describe whether the person asks what to repeat, stop, and improve next time.
- Handles unexpected requests calmly. This prompt invites observations about prioritizing and communicating when new work arrives without warning.
- Uses specialist advice appropriately. Ask whether the person involves relevant expertise and integrates it without surrendering necessary ownership.
- Identifies preventable rework. Reviewers can note whether the person looks for process improvements after the same correction occurs repeatedly.
- Updates a plan as evidence emerges. This item checks whether milestones and estimates respond to actual progress rather than wishful thinking.
- Explores causes with affected people. Ask whether the person includes those who experience the problem before selecting a solution.
- Balances experimentation with reliability. Reviewers can assess whether new methods are tried without putting essential commitments at unnecessary risk.
- Recovers after a disrupted plan. This prompt focuses on how the person communicates, reprioritizes, and restores momentum after interruption.
- Accepts that a first proposal may be incomplete. Ask whether the person welcomes refinement instead of defending every early detail.
- Identifies decisions that can wait. Reviewers can note whether the person avoids premature commitment when important information is due shortly.
- Maintains perspective under pressure. This item invites specific examples of considering longer-term effects during a demanding situation.
- Looks for transferable lessons. Ask whether the person applies learning from one project to a different but related challenge.
- Responds constructively to changed requirements. Reviewers can describe whether the person clarifies impact and negotiates a realistic adjustment.
- Knows when to stop investigating. This prompt helps assess whether analysis leads to a decision rather than becoming an indefinite delay.
- Uses constraints creatively. Ask whether the person finds a responsible alternative when the original resources or schedule are unavailable.
- Shares emerging solutions early. Reviewers can assess whether colleagues have time to improve a proposal before it becomes fixed.
- Confirms whether a fix worked. This item checks that problem-solving includes follow-up on the original issue, not only implementation.
Respect, Inclusion, and Fairness
- Treats colleagues with respect. Ask for observable examples across routine interactions, including moments when people disagree or make mistakes.
- Uses people’s stated names. Reviewers can note whether the person makes a reasonable effort to use names and pronunciations colleagues share.
- Shares airtime fairly. This prompt helps assess whether discussions make room for contributions beyond the most confident speakers.
- Considers accessibility needs. Ask whether meeting materials and participation methods are adjusted when colleagues identify a practical access barrier.
- Avoids dismissive responses. Reviewers can describe whether questions and concerns receive consideration rather than jokes or abrupt shutdowns.
- Applies standards consistently. This item invites comparisons of similar situations without asking reviewers to speculate about private motives.
- Challenges disrespectful conduct appropriately. Ask whether the person responds in a way that supports the affected colleague and addresses the behavior.
- Invites different viewpoints. Reviewers can assess whether the person asks for perspectives that may otherwise be missed in a familiar group.
- Shares information equitably. This prompt checks whether relevant colleagues receive access to updates needed for their work.
- Gives criticism privately when appropriate. Ask whether corrective feedback is delivered in a setting that preserves dignity and permits discussion.
- Avoids assumptions about capability. Reviewers can note whether the person asks about skills and preferences instead of presuming them.
- Respects cultural and personal differences. This item focuses on considerate workplace behavior without asking anyone to represent a whole group.
- Credits ideas fairly. Ask whether the person acknowledges who introduced a contribution when proposals are discussed or adopted.
- Uses inclusive meeting practices. Reviewers can describe whether agendas, turn-taking, and follow-up support participation by everyone involved.
- Responds to correction without retaliation. This prompt asks whether the person accepts a respectful correction and adjusts their conduct.
- Considers who bears the workload. Ask whether decisions distribute inconvenient tasks transparently rather than repeatedly assigning them to the same people.
- Uses humor thoughtfully. Reviewers can assess whether jokes include colleagues rather than making someone the target of a group exchange.
- Checks the impact of their behavior. This item invites the person to consider how actions land, even when intentions were positive.
- Offers equitable access to opportunities. Ask whether assignments and visibility are shared with attention to role fit and development needs.
- Addresses interruptions fairly. Reviewers can note whether the person helps restore a speaker’s turn when discussion becomes uneven.
- Respects reasonable boundaries. This prompt covers availability, personal information, and workload limits communicated by colleagues.
- Uses neutral, behavior-based language. Ask whether descriptions focus on what happened rather than stereotypes or unsupported judgments.
- Supports participation across experience levels. Reviewers can describe whether newer colleagues are invited to contribute without being put on the spot.
- Responds respectfully to a refusal. This item assesses whether the person accepts a boundary or asks about alternatives without applying pressure.
- Shares meeting materials in advance. Ask whether participants receive documents early enough to review and contribute meaningfully.
- Notices uneven access to information. Reviewers can assess whether the person helps correct gaps that leave some colleagues behind.
- Disagrees without personalizing. This prompt encourages examples of challenging an idea while maintaining respect for its contributor.
- Recognizes contributions beyond visible roles. Ask whether less public work, such as coordination or review, is acknowledged accurately.
- Handles sensitive information discreetly. Reviewers can describe whether the person avoids sharing private details beyond those who need them.
- Asks rather than presumes preferred support. This item helps assess whether help is offered in a way that respects the recipient’s choice.
- Uses fair turn-taking in remote discussions. Ask whether the person makes space for people who may have audio or timing delays.
- Responds to exclusion concerns seriously. Reviewers can assess whether the person listens, seeks facts, and takes an appropriate next step.
- Applies recognition without favoritism. This prompt invites observations about whether praise reflects actual contributions across the group.
- Explains criteria for opportunities. Ask whether selection or assignment standards are visible enough for colleagues to understand the process.
- Welcomes respectful challenge. Reviewers can note whether people can question a proposal without being labeled disloyal or difficult.
- Helps restore respectful conversation. This item suits moments when discussion becomes dismissive and someone needs to reset its tone.
Relationships and Service
- Builds dependable working relationships. Ask whether colleagues can rely on the person to be honest, prepared, and consistent in routine interactions.
- Understands internal partners’ needs. Reviewers can describe whether the person learns what another team requires before making a request.
- Responds helpfully to requests. This prompt considers whether the person answers, routes, or clearly declines requests rather than leaving them unanswered.
- Sets clear service expectations. Ask whether partners understand what support is available, what is outside scope, and when to expect a response.
- Maintains a calm service manner. Reviewers can assess how the person interacts when requests are repetitive, urgent, or frustrating.
- Follows through with stakeholders. This item helps identify whether people receive promised information after a meeting or service interaction.
- Explains limitations honestly. Ask whether the person names constraints and offers realistic alternatives instead of promising an impossible result.
- Repairs a strained interaction. Reviewers can describe whether the person acknowledges their part and works toward a constructive next exchange.
- Balances partner needs with team capacity. This prompt is useful where helpful service must remain sustainable for the people delivering it.
- Confirms what a requester needs. Ask whether the person clarifies the desired outcome before beginning work on an ambiguous request.
- Protects trust through accurate updates. Reviewers can assess whether status messages reflect what is known and what remains unresolved.
- Sets boundaries courteously. This item checks whether the person can decline or renegotiate work while preserving a respectful relationship.
- Anticipates partner questions. Ask whether the person includes the details another team will likely need to take the next step.
- Maintains continuity with key contacts. Reviewers can note whether transitions are communicated so partners know whom to approach.
- Represents the team accurately. This prompt assesses whether the person avoids commitments or statements that colleagues cannot support.
- Responds to service feedback. Ask whether the person seeks specifics and considers a practical improvement after a partner raises a concern.
- Clarifies ownership for incoming requests. Reviewers can describe whether requests reach the right person without unnecessary redirection.
- Uses respectful language with support staff. This item recognizes that professional courtesy should not depend on a colleague’s role or status.
- Communicates delays to affected partners. Ask whether people hear about a changed timeline before they discover it themselves.
- Confirms completion with the requester. Reviewers can assess whether the person verifies that the delivered work addresses the original need.
- Manages expectations during high demand. This prompt asks whether the person provides honest timing and triages requests transparently.
- Builds relationships beyond immediate tasks. Ask whether the person learns enough about partners’ goals to cooperate more effectively over time.
- Handles complaints without defensiveness. Reviewers can describe whether the person listens, checks facts, and explains a fair response.
- Shares useful contacts or expertise. This item helps assess whether the person connects colleagues to the right resource when they cannot help directly.
- Protects partners from avoidable surprises. Ask whether changes that affect another team are communicated before they disrupt its plans.
- Uses clear service handoffs. Reviewers can note whether a referred request includes relevant history and a named next contact.
- Asks for feedback at suitable moments. This prompt encourages timely input after meaningful work rather than constant requests for reassurance.
- Maintains professional boundaries. Ask whether the person keeps working relationships appropriate while remaining approachable and considerate.
- Recognizes partner constraints. Reviewers can describe whether requests account for another team’s schedule, approvals, or technical dependencies.
- Responds consistently across stakeholders. This item checks whether similar requests receive comparable care, clarity, and follow-through.
- Shares credit with partner teams. Ask whether reports describe joint work accurately rather than presenting a shared result as individual work.
- Helps resolve cross-team misunderstandings. Reviewers can assess whether the person clarifies facts and responsibilities without inflaming the disagreement.
- Provides a useful point of contact. This prompt helps partners know where to direct questions when responsibility changes.
- Closes service requests transparently. Ask whether the person explains what was completed, what was not, and why.
- Maintains trust after a missed commitment. Reviewers can note whether the person takes responsibility and gives a credible revised plan.
- Seeks a partner’s definition of success. This item checks whether delivery is judged against the requester’s actual need, not assumption.
Learning, Coaching, and Growth
- Requests feedback with a clear focus. Ask whether the person identifies a behavior or situation so colleagues can give useful observations.
- Receives feedback without immediate rebuttal. Reviewers can describe whether the person listens first and asks questions before explaining context.
- Turns feedback into an action. This prompt asks what specific behavior changed after the person received a useful observation.
- Shares expertise through coaching. Ask whether the person explains reasoning and lets a colleague practice rather than simply taking over.
- Sets realistic development goals. Reviewers can note whether goals connect to current responsibilities and have observable signs of progress.
- Reflects on their own impact. This item invites the person to identify patterns in how their behavior affects colleagues.
- Offers feedback close to the event. Ask whether observations arrive while details are fresh and a change can still be tried.
- Makes feedback specific. Reviewers can assess whether comments include an observable action and its effect, instead of vague praise or criticism.
- Balances strengths and growth areas. This prompt supports a rounded discussion without implying that every review must contain identical praise and criticism.
- Encourages colleagues to learn. Ask whether the person shares time, resources, or opportunities that support role-relevant skill building.
- Admits when they do not know. Reviewers can describe whether the person seeks answers and reports back rather than bluffing.
- Applies new learning at work. This item checks whether training or practice leads to a visible change in relevant tasks.
- Shares lessons from mistakes. Ask whether the person explains what they learned without shifting responsibility or exposing someone unfairly.
- Creates a safe coaching conversation. Reviewers can note whether questions and practice are handled with patience and appropriate privacy.
- Offers actionable suggestions. This prompt asks whether advice includes a next step that fits the recipient’s work situation.
- Recognizes progress over time. Ask whether the person notices improvement rather than judging only against a final target.
- Uses peer expertise. Reviewers can describe whether the person learns from colleagues whose experience complements their own.
- Checks whether coaching was useful. This item encourages the person to ask what support helped and what should change next time.
- Shares development opportunities fairly. Ask whether stretch assignments are discussed openly and matched to interest, readiness, and workload.
- Accepts a different working method. Reviewers can assess whether the person can learn from approaches that differ from their own.
- Explains skills that a task will build. This prompt helps colleagues understand the developmental value of an assignment before accepting it.
- Asks for examples when feedback is unclear. Reviewers can note whether the person seeks clarification instead of guessing at the concern.
- Separates feedback from personal worth. Ask whether the person can consider a behavior change without treating it as a judgment of character.
- Provides coaching at the right level. This item checks whether guidance matches the colleague’s experience rather than overwhelming or underserving them.
- Encourages reflection after a challenge. Reviewers can describe whether the person asks what worked, what was difficult, and what comes next.
- Shares credit for learning support. Ask whether the person acknowledges mentors and peers who helped them build a skill.
- Revisits goals when roles change. This prompt recognizes that useful development priorities may shift when responsibilities or interests evolve.
- Practices a skill consistently. Reviewers can assess whether the person applies a new method beyond the initial training session.
- Uses coaching questions before giving answers. Ask whether the person helps colleagues reason through a problem when independent practice is appropriate.
- Tracks agreed development actions. This item checks whether a coaching conversation leads to a later review of the chosen practice.
- Shares constructive feedback upward. Reviewers can note whether the person offers respectful observations to people with greater authority.
- Recognizes limits in their expertise. Ask whether the person knows when to consult a specialist or learn before advising others.
- Models continuous learning. This prompt invites observable examples, such as seeking input, reviewing new information, or changing a routine.
- Supports learning from peers. Reviewers can describe whether the person makes time for colleagues to compare methods and lessons.
- Names a concrete next growth step. Ask whether the person can translate a broad ambition into a practical action for the next cycle.
- Encourages practice without embarrassment. This item helps assess whether colleagues can build skills through attempts, questions, and appropriate correction.
Results, Quality, and Improvement
- Connects effort to useful results. Ask whether the person checks that completed work serves the intended user or team need.
- Defines quality through observable criteria. Reviewers can describe whether the person uses agreed standards rather than shifting expectations after delivery.
- Checks outcomes after implementation. This prompt asks whether the person verifies that a change produced the result people expected.
- Identifies recurring sources of rework. Ask whether the person looks for a pattern instead of treating each correction as isolated.
- Uses evidence to improve a process. Reviewers can note whether changes respond to observed delays, errors, or user feedback.
- Maintains quality across routine tasks. This item suits work where dependable daily standards matter as much as major deliverables.
- Distinguishes output from impact. Ask whether the person considers what changed because the work was completed, not only the volume delivered.
- Includes relevant users in review. Reviewers can assess whether people who use a deliverable help identify practical shortcomings before release.
- Responds to quality concerns promptly. This prompt invites examples of investigation, correction, and communication with affected colleagues.
- Documents improvement decisions. Ask whether the reason for a process change is recorded so future teammates can understand it.
- Reduces avoidable steps. Reviewers can describe whether the person simplifies work while preserving necessary checks and accountability.
- Checks whether a metric is meaningful. This item helps assess whether numbers inform decisions rather than replacing judgment about the actual work.
- Uses customer or colleague feedback responsibly. Ask whether the person looks for recurring themes without treating one comment as universal proof.
- Maintains quality during handoffs. Reviewers can note whether work remains complete and understandable when another person takes responsibility.
- Shares results honestly. This prompt checks whether reports include limitations, missed targets, and relevant context alongside successes.
- Finds the cause of repeated errors. Ask whether the person investigates conditions that make a mistake likely, not just who made it.
- Uses review findings in later work. Reviewers can describe whether lessons from one delivery influence planning on the next similar task.
- Balances thoroughness with practical value. This item asks whether effort matches the consequences and intended use of the deliverable.
- Sets a useful baseline. Ask whether the person records the starting condition before claiming that an improvement has occurred.
- Communicates quality risks early. Reviewers can assess whether concerns reach decision-makers while options for correction remain available.
- Checks completeness against requirements. This prompt is useful before a deliverable is handed over or presented as finished.
- Looks for simpler ways to maintain quality. Ask whether the person improves repeatable checks without creating needless administrative burden.
- Uses lessons without assigning blame. Reviewers can note whether a review identifies better conditions and practices rather than seeking a scapegoat.
- Explains variance from a target. This item encourages an accurate account of what differed and what the team learned.
- Protects important controls. Ask whether efficiency improvements retain checks that prevent consequential mistakes or missed obligations.
- Confirms improvements are sustained. Reviewers can describe whether a new process continues to work after the first implementation period.
- Shares useful measures with the team. This prompt checks whether relevant indicators are understandable and available to people doing the work.
- Reviews quality with the right partners. Ask whether people who own, use, or support the result contribute where their perspective matters.
- Closes the gap between promise and delivery. Reviewers can note whether the person explains and addresses differences between expected and actual work.
- Recognizes reliable behind-the-scenes work. This item encourages attention to careful review, maintenance, and coordination that may be less visible.
- Uses corrective action proportionately. Ask whether the response matches the size and recurrence of a problem without overreacting.
- Shares improvements that others can reuse. Reviewers can describe whether a successful method is documented for relevant teams.
- Checks whether a solution creates new problems. This prompt asks the person to look for unintended effects after changing a process.
- Protects time for quality review. Ask whether schedules include enough room to inspect work before commitments become difficult to change.
- Explains what good performance looks like. Reviewers can assess whether examples and criteria make expectations understandable to the people involved.
- Identifies one improvement for the next cycle. This item turns a broad review into a practical and reviewable commitment.
Printable 360 Degree Feedback Form Template
Copy or print the blank form below. Choose prompts that match the person’s role and the reviewer’s opportunity to observe; leave fields blank when you do not have enough direct experience to answer fairly.
| Form field | Blank response |
|---|---|
| Person receiving feedback | ________________________________________ |
| Role or team | ________________________________________ |
| Review period | ________________________________________ |
| Reviewer relationship | ________________________________________ |
| Prompt or behavior observed | ________________________________________ |
| What happened? Include a specific example. | ________________________________________ |
| Effect on work, people, or results | ________________________________________ |
| What should the person continue doing? | ________________________________________ |
| What is one useful change to consider? | ________________________________________ |
| Suggested next step | ________________________________________ |
| Optional follow-up date | ________________________________________ |
Sample — fictional details: Reviewer relationship: project teammate. Prompt: communicates changing priorities. Example: “On the Tuesday planning call, Jordan summarized the revised delivery order and sent the updated owners afterward.” Effect: “I could adjust my review schedule without waiting for a separate clarification.” Continue: “Keep pairing verbal updates with a written recap.” Next step: “For the next milestone, include the revised due date in the recap.”
How to Use This List
Start with the purpose of the review. A development conversation, project retrospective, and role-transition review do not need the same prompts. Select items that connect to responsibilities the person actually held during the period, and avoid asking reviewers to judge work they could not observe.
Choose a manageable subset rather than placing all 360 prompts on one form. A practical form often uses a small number of common questions for every reviewer and a few role-specific prompts. Keep the questions focused enough that people can answer with examples. A long survey can encourage rushed or repetitive responses, so remove items that do not support a decision or conversation.
Use more than one kind of prompt. Include observable strengths, a behavior to develop, and an open question about impact or next steps. Ask reviewers to describe what they saw, when it happened, and how it affected work. Concrete examples are easier to discuss than broad labels such as “good communicator” or “not strategic.” Avoid questions that presume a flaw or invite speculation about motives.
Define the rating scale if you use one. Explain what each point means, and include a “not enough opportunity to observe” option. A numerical score without a shared definition can mean different things to different reviewers. Consider keeping written examples alongside ratings so a score does not stand alone without context.
Tell participants how responses will be handled before collecting them. Explain who will see the feedback, how it will be discussed, and whether comments will be attributed or summarized. Do not promise anonymity unless the process can genuinely protect it; small reviewer groups may make identities apparent from examples. Follow your organization’s established privacy and people processes.
Choose reviewers with relevant, direct experience rather than selecting only the closest or most senior colleagues. A balanced group may include a manager, peers, project partners, and direct reports where appropriate. Give reviewers enough time and a clear deadline, and remind them to distinguish first-hand observations from hearsay.
Review the responses for patterns, not just the most striking comment. Compare repeated examples with the person’s goals and role expectations, then discuss differences in perspective without treating every rating as a verdict. The person receiving feedback should be able to ask questions and add context, while still considering the effect of their behavior.
End with a short action plan. Choose one or two changes that can be observed in everyday work, identify what support is needed, and agree when to check progress. For example, a person who receives feedback about unclear handoffs might send a brief recap naming the owner, due date, and open dependency. Review whether the practice helps rather than assuming the form itself creates improvement.
Keep the form accessible and straightforward. Use plain wording, make response fields large enough for examples, and offer a way to skip items that do not fit a reviewer’s experience. If a concern involves a formal workplace process, sensitive information, or a situation requiring specialist guidance, ask the appropriate qualified professional rather than treating this general template as a substitute.
Frequently Asked Questions
What is a 360-degree feedback form?
A 360-degree feedback form collects work-related observations from several perspectives, commonly including a manager, peers, project partners, or direct reports. Its purpose is usually development and reflection; the exact process depends on the organization.
How many questions should I include?
There is no universal number. Use enough prompts to cover the person’s relevant responsibilities while keeping the form practical to complete. Remove questions that reviewers cannot reasonably observe, and prefer prompts that invite specific examples.
Should responses be anonymous?
That depends on the process, the size of the reviewer group, and the organization’s commitments. Explain the handling of responses in advance, and do not promise anonymity if details or group size could reveal a reviewer.
Can I use a rating scale?
Yes, if every scale point has a clear definition and reviewers can choose “not enough opportunity to observe.” Pair ratings with examples so a number has context and can support a useful conversation.
How should I discuss difficult feedback?
Focus on the observed behavior, its effect, and a practical next step. Ask clarifying questions, avoid arguing over a reviewer’s motives, and consider patterns across examples. For formal or sensitive workplace concerns, use the appropriate qualified professional or established internal process.
How often should a 360 review happen?
Use a cadence that fits the role and development goals rather than collecting feedback automatically. A review is most useful when there has been enough time to observe behavior and there is a clear plan to discuss and revisit the results.
Final Thoughts
A useful 360-degree feedback form is selective, understandable, and grounded in behavior people have actually observed. Use the template to gather specific examples, discuss patterns fairly, and agree on a small number of practical next steps. The best prompts are those that help colleagues have a clearer, more constructive conversation about the work.