Read a cycle result

What this achieves

A result combines everything reviewers said about one person in a cycle into a single view: scores by relationship, competency and skill ratings, strengths, and development areas. Reading it is the preparation for the conversation; recording that conversation is what closes the loop.

Required role: Administrator or Manager.

Before you start

Results are not produced automatically. The cycle needs responses, and somebody has to generate the result.

Steps

Go to Feedback & 1:1s → Cycles, open the completed cycle, and open the participant.
Select Generate this result, or Generate all for cycle to produce results for everyone at once.
Read Scores by Relationship and the Comparison.
Work through Competency Results and Skill Results.
Read Top Strengths and Development Areas.
Have the conversation with the person.
Select Record Discussion, set the Discussion date, write the Notes, and save.
Select Push to Skills Profile if you want the ratings to update their profile.

What the result contains

Option	Description
Scores by Relationship	The average score from Self, Manager, Peer, and Direct Report reviewers, kept apart rather than blended.
Comparison	How far the person’s self-assessment sits from what everyone else said, in points.
Competency Results	Per-competency ratings, with a column per relationship and an overall.
Skill Results	The same, per skill.
Top Strengths	The highest-rated areas.
Development Areas	The lowest-rated areas.
AI Summary	A generated narrative summary of the result.
AI Action Recommendations	Generated suggestions for what to do next.
Manager Discussion	The record of when you discussed this with the person, and what was agreed.

The gap between self and others is the conversation

The Comparison figure is usually the most useful thing on the page. A person rating themselves well above everyone else and a person rating themselves well below are both worth a conversation, and they are opposite conversations.

Example: James Whitfield rating himself two points below what his peers and his manager said is not modesty to be corrected in passing. It is the thing to open with, because he is working from a picture of himself that his colleagues do not share.

The AI summary is a draft, not a verdict

AI Summary and AI Action Recommendations are generated from the responses. Read them as a first pass over material you are about to read yourself, not as the conclusion.

The words that reach the person should be yours. You are the one who has to say them out loud and stand behind them.

Who can read this

The results screen is for Administrators and Managers. It is not the employee’s own view of the cycle — an employee’s own feedback page shows the reviews they submitted, read-only, rather than the combined result about them.

That makes Record Discussion the mechanism by which the person actually learns what the cycle said. A generated result that nobody discusses has told the subject nothing.

Example: generating results for all 21 people in HC Corp’s Sales cycle and never booking the conversations produces a complete dataset and zero benefit to anyone reviewed.

Pushing to the skills profile

Push to Skills Profile updates the person’s skill and competency profile from this cycle’s ratings. The confirmation names the person before it does anything.

Do this after the discussion, not before. The ratings become part of their profile and feed gap reports and recommendations elsewhere, and a person should hear their result from you rather than notice it appearing on their profile. Once pushed, the result records that it has already been propagated.

What happens next

Recorded discussions stay on the result with their date, which is the evidence that the cycle produced a conversation rather than a report. Pushed ratings flow into the skills profile, where they feed gap analysis and learning recommendations. The result itself stays available as history alongside the person’s earlier cycles.