Executive 360 Feedback Review Template and Debrief

An executive 360 feedback review template should help a leader answer three questions: What are people observing? Which interpretation is worth investigating? What will I do differently in a real situation? A report can contain dozens of ratings without answering any of them.

The difficult part is moving from a broad judgment such as “needs to delegate” to a behavior that preserves essential oversight and gives colleagues usable authority. This guide provides a complete review template, a facilitated agenda and a fictional worked example, including an interpretation that changes after further evidence. It focuses on reviewing an existing report. Use our leadership 360 assessment guide for assessment design and our 360 coaching package guide for engagement structure.

Coachful is our #1 recommendation for carrying the agreed development work into coaching: a client goal, specific tasks, recurring practice and reflection before the next session. The assessment provider's scoring and protection process remains the authority for the original report. A coaching workspace supports follow-through; it does not make a homemade survey a validated assessment.

What a 360 review can and cannot tell you

A 360 report combines perspectives from people who see different parts of an executive's work. A board member may observe strategic discussions. Direct reports experience decisions, handovers and interventions. Peers encounter negotiations across functions. Differences can be informative because these people occupy different positions, rather than because one group is necessarily more accurate.

Keep three layers separate. Reported evidence is what the instrument actually contains: an item score, response distribution or comment. Interpretation is an explanation of the pattern. Development choice is what the leader agrees to try. “Direct reports reported unclear decision ownership” belongs in the first layer. “The leader fears losing control” is an interpretation that requires exploration. “Agree an escalation boundary at kickoff” is an action.

A rating is also tied to a question, a scale and an observation period. Do not compare scores from unrelated tools as though a four means the same thing in both. Missing responses can mean insufficient observation or nonparticipation, not agreement. A narrow score range can hide meaningful comments, while a striking comment can be unrepresentative of the wider report.

Use the instrument's manual for scoring and interpretation. This article's template is a coaching aid, not a replacement for required training, qualification or licensed report interpretation. It does not turn feedback into a diagnosis, an employment decision or proof that coaching caused a later business result.

Set the information boundaries before opening the report

Record the purpose, intended recipients and sharing rules first. Is the review developmental? Is an employer expecting a progress summary? Does the executive know whether any rating category is identifiable? Resolve these matters before a debrief becomes an argument about who owns the information.

The ICF Code of Ethics, effective April 2025, calls for agreements about roles, confidentiality and information exchange, together with appropriate handling of records. Translate that into a practical sharing statement for this engagement: who receives the report, what the sponsor receives and what requires further agreement. Payment alone does not define access.

Anonymity requires more than removing a name. A comment referring to the only acquisition in a region may identify the writer. A single supervisor's category may be identifiable by design. Do not promise protection that the instrument or organizational process cannot provide, and do not ask the executive to guess who wrote a comment.

CCL's Skillscope 360 guidance specifies a minimum of three responses for its anonymous peer and direct-report categories. Its combined-score guidance also explains when groups appear together. These are examples of instrument rules, not universal thresholds for every 360. Never reconstruct a suppressed subgroup from other report data.

Before the meeting, decide where the original report belongs, which working notes are needed and when records will be reviewed or removed under the applicable arrangement. Often the ongoing coaching plan needs only the agreed theme and action. It may not need every raw comment, rater detail and sensitive organizational fact.

The executive 360 feedback review template

Copy these fields into a working document. Complete the evidence and limits before writing an explanation. Leave uncertain fields visibly uncertain rather than filling them with confident language.

Use a separate row for each candidate theme. If a report suggests seven development areas, do not squeeze them into one vague goal. Compare their relevance to the executive's actual role, the cost of leaving them unchanged and the opportunity to practice. The selected action should follow from that comparison, not simply from the lowest number.

A strength deserves an operational definition too. “Commercially strong” is difficult to retain deliberately. “Asks customers about implementation constraints before agreeing the scope” names something the leader can keep doing while changing another behavior.

Prepare a debrief that leaves room for thought

The following 75-minute agenda is an example, not a prescribed protocol. Adapt it to the instrument, the leader's preferences and the amount of information. Send the purpose and process beforehand; follow the provider's guidance on when the report itself should be released.

1. First 10 minutes: orient. Reconfirm purpose, access and the leader's questions. Ask whether they would like to start with an overview, a strength or a concern. Explain how you will mark uncertainty.
2. Next 15 minutes: understand the pattern. Read across themes and rater perspectives. Identify what is repeated and what is mixed. Ask which parts fit their experience and which need context.
3. Next 20 minutes: examine one important situation. Reconstruct a specific event, separating intention, observable behavior and reported impact. Compare alternative explanations without looking for a culprit.
4. Next 20 minutes: choose and design a practice. Specify what changes, where the leader has authority and how they will tell whether the action helped.
5. Last 10 minutes: close. Let the leader summarize their understanding, agree the next review and approve any sponsor-facing wording.

Do not force resolution because the calendar says the session is ending. A reasonable first outcome may be a clarified question and a second debrief. If the executive feels overwhelmed, offer a pause and agree how to continue. Significant distress or safety concerns require appropriate support and judgment beyond completing a feedback worksheet.

Useful opening language is: “We will distinguish what the report says from what we think it means. You can disagree with an interpretation and still examine the observations.” This makes disagreement workable. Requiring immediate agreement can produce a compliant action plan that the leader does not believe.

Worked example: from delegation scores to a decision agreement

This example is fictional. Maya is an operations executive leading six managers. Her sponsor wants fewer avoidable escalations without weakening service controls. A permitted developmental report uses an illustrative five-point frequency scale, with higher scores indicating more frequent behavior. The numbers below are invented teaching data, not a validated instrument or customer result. Self responses are individual whole-number answers; peer and direct-report values are arithmetic means of individual whole-number answers within each group.

1. Read the report before explaining it

The authorized report contains five peer and five direct-report responses. Comments describe uncertainty when a service decision becomes commercially sensitive. Other comments value Maya's rapid help during incidents. The coach records a working theme: decision ownership becomes unclear when commercial risk rises. The report does not establish that Maya interferes in every decision.

The self versus direct-report difference on clarifying decisions is 4 minus 2.8, or 1.2 scale points. That arithmetic identifies a difference to discuss. It does not establish statistical significance, a severity threshold or a personal deficit. Without the instrument's relevant guidance, the coach does not attach any of those labels.

2. Test competing explanations against a recent event

Maya initially says, “They want me to disappear when things are difficult.” The coach asks about the last customer exception. Maya says a manager selected an alternative supplier, then asked her to approve it. She changed the supplier because she believed the customer had a contractual restriction. The manager had never seen that restriction.

Three explanations now matter: Maya habitually reverses decisions; approval limits are unclear; or managers lack information needed to use their authority. More than one could be true. The coach asks, “If the manager had the restriction and the decision boundary in writing, what would still require your intervention?” Maya identifies only exceptions above an agreed commercial limit and legal concerns.

That answer changes the proposed action. “Stop intervening” would remove useful support and ignore missing information. “Write down every task” would create unnecessary administration. They choose a short decision agreement for two upcoming supplier decisions, where there is a real opportunity to test the explanation.

3. Complete the action record

4. Review the experiment and revise the explanation

At the fictional follow-up, the first decision stays with its owner. In the second, Maya gives a new instruction after a customer changes the service deadline. The manager says the written boundary helped, but nobody knew how to update it when conditions changed.

The output is therefore mixed. Both agreements were made; only one remained adequate throughout. Maya adds a change rule: when scope, deadline or risk changes, the owner and executive explicitly renew the agreement. They retain her availability for escalations. They do not report a percentage improvement in delegation or claim that two events prove lasting behavioral change.

The next review asks a narrower question: “When conditions change, do we update the authority agreement before redirecting work?” This is a useful development cycle because evidence alters the plan. A template that only records completion would have missed the remaining problem.

A contrasting case: the apparent weakness is a role requirement

Consider a fictional finance executive whose direct reports want faster independent approvals, while the board requires particular transactions to receive formal sign-off. An instruction to “trust people more” cannot remove that requirement. The review must distinguish decisions the executive can delegate from decisions governed elsewhere.

The development choice might be to make the approval path visible, provide complete decision packs earlier and explain why a transaction requires escalation. The executive can also ask the appropriate governance owner whether the approval policy should change. They cannot promise a new authority level on the strength of a coaching conversation.

This case changes the success measure. The useful question is whether people can predict the approval route and prepare for it, rather than whether all approvals disappear. It also illustrates why a popular development theme is insufficient: a well-designed action addresses the actual constraint.

Turn the template into a practical coaching plan

Start with the agreed behavior rather than uploading the entire report by default. In Coachful, open the executive's client plan and record a goal in their own words, such as “Make decision ownership explicit when a project begins or changes.” Agree what the client can see and what stays in the coach's private working record.

1. Create the first concrete task. For Maya, this is “Draft the supplier decision agreement before Thursday's kickoff.” Include the five fields from the worked example so the task produces an actual output.
2. Add recurring practice only if recurrence fits. A habit can support reviewing the authority boundary before relevant meetings. A one-off board decision needs a task and review, rather than an artificial daily streak.
3. Use a short form or worksheet for reflection. Ask what situation occurred, what the leader did, what response they observed and what remains uncertain. Explain who can read the answers.
4. Review examples during the next session. Compare the behavior with its intended purpose, including cases where it did not help. Update the plan together.

The earlier form-builder illustration shows ordinary structured prompts, not a specialized 360 scoring screen. The goal view below illustrates the ongoing development work. Use the original assessment process for protected rater collection and licensed scoring. A custom reflection worksheet in Coachful is useful for the leader's learning; it should not be presented as an anonymous multi-rater instrument.

For sponsor conversations, prepare a small agreed summary: development intention, practice underway, support needed and next review. The executive intake questions can help establish that arrangement before the next assessment cycle. Keep the report and the sponsor update distinct so an action reminder does not accidentally expose raw feedback.

Choose a theme using relevance, influence and opportunity

Before committing to a development goal, compare two or three themes against the next period of work. Ask which one affects an important responsibility, which behavior the leader can influence and where a realistic practice opportunity exists. A theme can be important yet unsuitable for immediate practice if the executive is leaving that responsibility next week.

For example, clearer handovers may matter more than presentation confidence when a leader is integrating two operating teams. Presentation confidence could still be worth developing, but the current work offers daily handover opportunities and only one distant presentation. Record that reasoning so the plan reflects the role rather than a preference for the most comfortable topic.

Include the cost of an ineffective experiment. Trying a different opening question in an internal planning meeting may be straightforward. Changing an approval boundary in a regulated process requires the appropriate authorization first. This does not mean choosing only easy actions. It means designing a practice in a setting where learning is possible and consequential obligations remain clear.

Finish the comparison with the executive's commitment: “This matters because…, I can influence…, and my next opportunity is….” If one of those blanks cannot be completed, clarify it before assigning work. A development plan benefits from a reasoned choice more than a long list of impressive intentions.

Follow-up questions that produce usable evidence

A follow-up should match the opportunity to observe. Someone cannot evaluate a new delegation behavior after a fortnight in which no relevant decision occurred. Ask about a recent event rather than demanding an overall verdict on the leader.

• Which decision or conversation did you observe?
• What did the executive do that clarified or complicated the situation?
• What happened to ownership when the conditions changed?
• What should stay the same, and what would help next time?

Agree the collection and sharing arrangement before using these questions. A few follow-up responses can inform a conversation without becoming a new assessment score. If repeating the formal instrument, use its guidance on timing, comparability and interpretation. Changes in role, rater group or workload may affect what a later score means.

Also review the leader's own evidence: which actions were possible, where support was missing and what they learned. If the behavior occurred but did not help, revise the hypothesis. If the behavior never had a fair opportunity, change the practice setting or review timing. Neither situation is resolved by adding more reminders.

Troubleshooting difficult reviews

The leader wants to identify a rater

Return to the agreed process. Explore the observation and its relevance without investigating identity. If there is a concrete concern about retaliation or breached confidentiality, follow the established organizational or assessment response route. Do not use a coaching conversation to promise protection you cannot enforce.

One comment dominates the whole conversation

Acknowledge its impact, then locate it within the report. Is it repeated, contradicted or tied to a specific event? Record what is known and what is missing. A harsh sentence does not become representative through repetition in the debrief.

The executive agrees to everything and changes nothing

Ask which action they actually consider valuable and feasible. Reduce the plan to one relevant opportunity and define an output. Check whether the action depends on a manager's approval, time or information that has never been arranged.

The sponsor asks for the full report afterward

Revisit the agreement and any applicable duties before sharing. Explain what the existing arrangement permits and discuss a revised arrangement with the appropriate parties if needed. Do not solve an access disagreement by forwarding the report informally.

Frequently asked questions

How many development goals should follow a 360 review?

Choose a number that the leader can practice and review meaningfully. One consequential behavior may be enough for an initial cycle. Keep other themes in the record with a reason for deferring them, rather than promising to fix every low-rated item.

Does a self-rating gap prove a blind spot?

No. It shows a difference between perspectives on the instrument's scale. Explore observations, contexts and the item's meaning before proposing an explanation. The gap can be useful without being a diagnosis or a statistically significant result.

Can I use this template with an interview-based 360?

Yes, as an organizing aid, with suitable interviewer competence and clear permissions. Replace item scores with appropriately synthesized observations. Preserve exceptions and avoid revealing a writer through an unusually specific quotation. Follow the assessment process's own requirements.

Should the executive share a development intention with colleagues?

That can make appropriate follow-up easier when it fits the agreement and context. Share the chosen behavior and an invitation for concrete observations. Do not disclose raw responses or pressure colleagues to confirm improvement.

When should I repeat the assessment?

Follow the provider's guidance and allow relevant opportunity to practice. A short coaching review can happen sooner than a formal reassessment. Keep its evidence descriptive and avoid treating a small pulse as equivalent to the original instrument.

Use Coachful's coaching features to keep the chosen behavior, practical work and next review connected. The useful result of a 360 review is an evidence-informed action the executive understands and can revisit.