Leadership 360 Assessment Template: Questions and Process

A leadership 360 assessment template should connect a clear development question with people who have relevant opportunities to observe the leader. It needs more than a list of competencies: explain the observation period, response options, handling of small groups, report audience and what will happen afterward.

This guide supplies an original planning brief, twelve behavior items, administration instructions and a complete fictional example. It is a custom developmental feedback template, not a validated psychometric instrument, licensed survey or basis for a promotion decision. If you need those uses, select an appropriate instrument and follow its authorized administration and evidence requirements.

Choose the purpose before choosing the questions

A 360 gathers perspectives from different working relationships, alongside self-reflection. People may see different work or apply different expectations. The aim is to investigate useful patterns, not settle which rater understands the leader's entire personality.

The Center for Creative Leadership's implementation guidance emphasizes purpose, clear administrative roles, confidentiality and a connection to development. Its own assessment requirements belong to its instruments. Likewise, New Zealand's Leadership Development Centre describes its own nomination, report and accredited-debriefing process. Neither source turns an independently written questionnaire into their assessment.

Use a licensed instrument when its intended use, language, role coverage and evidence fit the need, and obtain the required competence. A custom process can support a narrower developmental discussion when its limits are understood. A polished chart, twelve questions and an average do not establish validity, norms or a reliable leadership ranking.

Keep the purpose stable after collection. If a sponsor wants to use a developmental report for pay or selection, stop and address that different purpose with appropriate professional input. Do not repurpose raters' contributions because the scores happen to be available.

Copy the administration brief and complete every field

Do not fill a field with “confidential as agreed” when nobody has agreed what that means. State who can see raw responses, who can see names and what the leader receives. Anonymous collection, confidential handling and aggregated reporting are different arrangements.

For example, CCL's current Skillscope FAQ sets its own response minimums for peer and direct-report categories. That is an instrument-specific rule, not a universal guarantee that any three respondents are unidentifiable. Small populations, distinctive comments and repeated reports can still reveal information. Follow the actual provider's rules and assess the specific disclosure risk.

Use clear instructions and an explicit response scale

The following wording is original and copyable. Replace the brackets and check comprehension before using it:

Please consider your direct experience of [leader] during [dates]. For each item, rate how frequently you observed the behavior when a relevant opportunity occurred: 1 = Never, 2 = Rarely, 3 = Sometimes, 4 = Often, 5 = Almost always. Choose Not observed when you did not have a sufficient opportunity to judge. Do not infer an answer from reputation or someone else's account.

You may decline the process or leave an item unanswered. Not observed and unanswered are not low scores. Optional comments should describe a relevant work behavior and useful next step without identifying customers, colleagues or sensitive incidents. Contact [administrator and actual route] with a question or concern. Your invitation explains who receives the information and its limits.

This five-point frequency scale is an illustrative design choice, not a claim that frequency is always the best response format. A behavior performed frequently may still be unhelpful in a particular situation. Check meaning, context and effects rather than treating higher as automatically better.

Keep Not observed separate from a zero, a midpoint and a missing answer. If the questionnaire requires a numeric answer to continue, someone without observation may invent one. The collection method should allow the reporting rule you actually promised.

Copy twelve original behavior items

Use the same observation period and instructions for all items. The domains below are organizing headings, not validated subscales. Choose relevant items for the role before launch and preserve the version afterward.

Add two optional original prompts: “Describe one behavior worth continuing and its work effect” and “Describe one behavior that could be more useful, with a practical suggestion.” Explain that a formal complaint needs the appropriate reporting process; an optional survey comment is not an investigation channel.

Avoid items such as “is inspiring and empathetic,” which combine different judgments, or “has unresolved control issues,” which invites an unsupported diagnosis. In their 2012 practice review, Kenneth Nowack and Sandra Mashihi discuss the importance of behavior-specific wording and the risk that averages conceal disagreement. This template applies those cautions without copying a proprietary instrument or claiming their review validates these items.

Pilot the wording before launching

1. Check relevance. Ask whether each item describes work that the nominated relationships can reasonably observe.
2. Check interpretation. Have a small pilot group explain an item in their own words. Look for different meanings and unclear timeframes.
3. Check unavailable evidence. Ask a pilot respondent to answer an item they have not observed. Confirm that the method saves that option without forcing a number.
4. Check the report route. Use invented test responses to verify access, calculations, suppression and comment handling before real collection.
5. Freeze the version. Save the final questions and rules. A change after launch may create incomparable responses; do not quietly merge versions.

A successful comprehension pilot is useful preparation. It does not establish psychometric reliability, predictive validity, fairness for every population or fitness for employment decisions. If the requirement is a defensible selection assessment, a small informal pilot is not enough.

Complete fictional case: a bounded custom 360

Jae manages an operations team. Asha is the independent process administrator and Sol is Jae's coach. Owen is Jae's manager and funds the work. All names, responses, events and dates below are fictional. The case demonstrates decisions and calculations, not a customer result or a validated assessment.

The purpose is to understand how Jae makes task ownership clear. Jae and Owen explicitly agree that the process is developmental and will not determine pay or promotion. Asha's raw responses go only to Asha; the permitted report goes to Jae and Sol. Owen receives only a later development summary that Jae approves. Those boundaries are established before invitations.

The observation period is 5 October through 13 November 2026. Jae and Owen identify three peers and three direct reports with relevant shared work. Jae also completes the self version; Owen supplies a clearly identified manager response. Nobody is selected simply to produce a favorable score.

On 14 November, Jae, Owen, Asha and Sol approve the completed brief before the 16 November invitations. They retain all twelve items because priorities, responses to questions and coordination provide context for task ownership in this role. The four headings do not become four tested competency scales. Jae is choosing a development focus, not asking Asha to certify a comprehensive leadership profile.

Before launch, two pilot readers flag “empowers the team” as vague. The final L2 wording becomes “Stated which decisions the task owner could make.” On rereading, both can identify the intended behavior and use Not observed appropriately. Their pilot answers are excluded from Jae's results. This repairs a wording problem without claiming validation.

Asha also catches a calculation error in the invented test collection: Not observed was initially stored as zero, so a test item with responses 2, 2, 3, 4 and Not observed displays 2.20. Asha corrects the numeric exclusion rule and reruns the same test. The displayed mean is now 2.75 with four valid responses; a separate item with only three valid responses is suppressed. Those checks are completed before real invitations. The original faulty test remains documented as a configuration repair, not part of the leader's data.

Make the actual collection and privacy arrangement concrete

Asha sends individual invitation links through company email to a restricted collection in the company's approved survey system, with a 23 November deadline. Asha alone holds the identity-to-response key. Questions go by company email directly to Asha. It is not a Coachful questionnaire presented as an anonymous multi-rater engine.

The invitation explains the following completed project rules:

• The self and manager responses are identified. Peer and direct-report responses form one combined pool from the outset; separate role scores will not be produced.
• A pooled item is reported only with at least four valid numeric responses. That is this project's disclosure rule, not a validated reliability threshold or anonymity guarantee.
• Not observed and unanswered items are excluded from the numeric denominator and shown as different response states.
• Asha checks comments for identifying detail. A risky comment may be withheld entirely; removing a name alone is not assumed sufficient.
• Raw responses and the identity key are scheduled for deletion 90 days after collection closes, subject to the stated applicable record obligations. Jae and Sol retain the permitted report until 10 December 2027 under the agreed coaching-record arrangement; Owen does not receive a report copy.

The seven people who actually respond acknowledge the purpose and information notice before submitting. Asha checks the restricted report delivery on 25 November: Jae and Sol can open their authorized copy, while the sponsor account cannot. The later deletion dates are plans to be carried out under the records arrangement, not events observed by the final coaching session.

All invited raters are free to decline. One direct report does decline, and Asha does not tell Jae who declined. Five of the six pooled invitees respond, alongside Jae and Owen: seven respondents altogether. Asha gives only the agreed aggregate completion information. No extra rater is pressured to participate to manufacture a subgroup report.

One optional comment contains a distinctive customer incident. Asha withholds it rather than trying to make the author unrecognizable by deleting the customer's name. The report states that a comment was withheld under the announced information rule; it does not turn that omission into evidence of a low rating.

Calculate the report with visible denominators

Asha prepares the permitted report on 25 November. For this custom exercise, Asha calculates an item mean as the sum of valid numeric responses divided by their count. The means are descriptive summaries of ordered responses. They are not percentages of leadership ability, statistical significance tests or proof that the distance between every scale label is psychologically equal.

For L2, the four valid pooled responses are 2, 2, 3 and 4; the fifth respondent selects Not observed. The arithmetic is 11 ÷ 4 = 2.75, with a range of 2–4. Coding Not observed as zero would incorrectly produce 11 ÷ 5 = 2.20. The variation is useful context, but the scores do not identify whose experience differs.

Jae's L2 self-response is 4 and Owen's identified manager response is 3. These are individual responses on the stated scale, not unexplained decimal self-scores. Their difference from the pool creates a question about expectations and observation; it does not establish that Jae is in denial.

Across the pool there are 60 item-response opportunities, five people times twelve items. All are answered: 55 numeric and five Not observed. C2 has two Not observed responses; L2, R3 and C3 have one each. C2 remains suppressed despite having five overall respondents. No overall leadership score is calculated, and a missing reportable item is not replaced with zero.

Do not calculate separate peer and direct-report means afterward or combine exports to reconstruct suppressed information. The combined pool loses role-specific detail; that is an acknowledged design tradeoff. If those distinctions are essential, reconsider the process before collection rather than weakening the information promise later.

The table also contains a possible strength to investigate: D1 is reported at 4.00. It does not cancel the lower L2 mean. A leader can state priorities frequently while leaving decision authority unclear. Conversely, C2 cannot be called the weakest behavior because it has no reported mean. Too few observations describe the available evidence, not the quality of Jae's conduct. These distinctions keep the report connected to a useful question instead of manufacturing a ranked list of traits.

Turn one finding into a tested development action

In their 26 November session, Jae and Sol focus on L2. Jae initially says task owners already know their authority. They inspect Jae's own recent handoff brief, which specifies the result but says nothing about which decisions the owner can make. That concrete omission supports investigating the theme without guessing who supplied a particular response.

Jae chooses one recurring internal planning brief with Leah, a direct report who voluntarily agrees to the practice. Leah is not asked whether or how she rated Jae. Owen approves the time within the team's existing work allocation. The completed plan is:

The first attempt is mixed. Before the checkpoint, Jae changes the order of Leah's draft without asking. Leah says this makes the agreed authority unclear. Jae acknowledges the intervention, restores Leah's chosen order and confirms that the figures still match the approved register. The brief is completed, but task completion does not erase the boundary failure.

On 7 December, Leah prepares the next brief under the same boundary. Jae waits for the checkpoint, asks about one figure and confirms it against the register. Leah's order remains. Leah says this second boundary was clearer. Both briefs are delivered, and the two experiences remain different in the review record.

At the 10 December session, Jae chooses to continue the explicit boundary and checkpoint method independently. No repeat 360 has been administered, no new score is invented and no general improvement across all twelve items is claimed. The full two-session coaching service ends there.

Use Coachful for preparation and follow-through

Coachful is our #1 recommendation for organizing the leader's reflection, agreed development actions and coaching conversations around a 360. Keep rater collection, scoring and protections in the authorized assessment process. Ordinary shared forms do not automatically supply independent multi-rater confidentiality.

1. Prepare a client worksheet. In Forms & worksheets, create original prompts about the report, work example and chosen practice. Assign it deliberately to Jae; copying a private link alone does not grant access.
2. Explain the actual audience. Sol is Jae's sole authorized coach. Raw rater responses and Asha's identity key are not uploaded. Jae shares only the permitted report and selected development material.
3. Add accepted actions separately. Jae's plan can contain the agreed handoff practice and review date. A task tick indicates the named action, not that Leah experienced autonomy or that a 360 score improved.
4. Name the preparation route. Jae sends selected preparation through one-to-one Messages to Sol before the two booked meetings. Receipt acknowledgment is for those sessions, not an additional asynchronous feedback service.
5. Control any sponsor summary. Jae approves the exact short summary before sending it through company email. The employer does not receive private worksheets, journal entries or coach-team review notes automatically.

The approved summary says Jae is using explicit decision boundaries and checkpoints, notes that the first handoff required a correction and that the second preserved the owner's choice. Owen acknowledges receipt. It includes no raw scores, rater identities or claim of proven leadership transformation.

Explore Coachful's features for this development workflow. The executive 360 report-review guide addresses the distinct job of understanding an existing report, while the executive proposal guide helps specify sponsor and reporting arrangements.

Troubleshoot the process before repeating it

Too few usable responses: preserve the announced suppression rule. Consider a different consensual feedback method or defer the report. Do not turn a protected group into identified feedback without addressing the changed arrangement first.

People interpret an item differently: record the limitation. Revise the next version after investigation; do not silently alter the question and treat old and new responses as equivalent.

The sponsor requests raw data: return to the original information agreement and applicable obligations. Development support can be discussed without surrendering protections that contributors were promised.

A low score leads to a personality label: return to observable behavior and examples. A single custom item cannot diagnose motives, a disorder or a stable leadership identity.

A practice succeeds once: retain the specific result and its conditions. Decide whether more practice or a later properly designed review is useful. A convenient repeat date is not by itself a reason to rerun a full instrument.

Frequently asked questions

Is this a validated leadership 360 assessment?

No. It is an original developmental template with illustrative scoring rules. Validation, licensing, norms and permitted uses belong to a particular instrument and administration, not to the presence of a questionnaire.

How many raters guarantee anonymity?

No single count guarantees it. Follow instrument rules and assess the actual population, comments and reporting risks. This fictional project's four-valid-response rule is a local design choice, not a universal scientific threshold.

Should Not observed count as the middle score?

No. It indicates insufficient observation, not a middling judgment. Exclude it from the numeric denominator and retain it as its own response state, separately from unanswered items.

Can the lowest mean automatically become the goal?

Use the role, distribution, observation opportunities and practical evidence. Jae checks a real brief and chooses a relevant behavior. The mean opens an inquiry rather than deciding the development plan alone.

Can I use this for promotion or pay decisions?

Not on the evidence supplied here. Those uses need an appropriately designed and supported assessment process, professional input and clear governance. Do not change a developmental purpose after people have contributed.

Does completing the action prove the 360 worked?

No. Record the specific action and its effects, including failures and other influences. Jae's second clearer handoff is a limited observation, not a causal evaluation or a new overall score.