Track and close a cycle
What this achieves
Section titled “What this achieves”A launched cycle needs watching: some reviewers respond in a day and some never do. This page covers reading where a cycle stands, chasing what is outstanding, and closing it.
Required role: Administrator.
- Go to Feedback & 1:1s → Cycles and open the cycle from the Active tab.
- Read Overall Completion and the metrics beneath it.
- Open the Participants tab to see where each subject stands.
- Open the Reviewers tab to see which individual reviewers have submitted.
- Select Send Reminders to chase outstanding reviewers.
- Select Close when the responses are in, and confirm.
What the cycle shows you
Section titled “What the cycle shows you”| Option | Description |
|---|---|
| Participants | How many people are being reviewed in the cycle. |
| Reviewers | How many reviewer assignments exist. |
| Responses submitted | How many of those assignments have been completed. |
| Completion rate | Submitted responses as a share of assignments. |
| Completion by Relationship | The same figure broken down by Self, Manager, Peer, Direct Report, and External. |
Read completion by relationship first
Section titled “Read completion by relationship first”The overall number tells you whether to worry. The breakdown tells you who to chase, and they usually point at different people.
Example: an HC Corp cycle sitting at 60% overall with self-assessments nearly complete and peer responses barely started is not a communication problem. It is a peer-reviewer problem, and reminding everybody is mostly noise to the people who have already done it.
The relationship breakdown only becomes available once reviewers start submitting — before that there is nothing to break down.
Chasing
Section titled “Chasing”Send Reminders notifies reviewers who have not submitted. Reminders are worth sending, and worth sending sparingly: a cycle that reminds weekly for a month trains people to ignore the reminder.
Editing a running cycle
Section titled “Editing a running cycle”Edit cycle lets you change the start and end dates, the peer reviewer minimum and maximum, and the reviewer-mix switches.
It does not let you change the target scope. The interface states that departments, teams, grades, and hand-picked employees are locked once the cycle is created, and that changing scope means cancelling and recreating.
Closing
Section titled “Closing”Close marks the cycle complete and stops it accepting new responses. Anything not submitted by then is not coming.
Close deliberately rather than letting a cycle sit open. An open cycle with no reminders going out collects nothing and makes the completion figure look like an ongoing effort rather than a finished one.
Example: closing an HC Corp cycle at 85% is a decision that the remaining 15% is not arriving. Leaving it open for another month at 85% is the same decision, taken by not taking it.
Cancelling and deleting
Section titled “Cancelling and deleting”| Option | Description |
|---|---|
| Cancel | Halts the cycle. It is hidden from the Active and Draft tabs. |
| Delete | Removes the cycle. Plans already created from it are not affected. |
Cancel a cycle that should not have run. Close one that ran and finished. The two are not interchangeable — a cancelled cycle is not a completed one with a low response rate.
What happens next
Section titled “What happens next”A closed cycle moves to the Completed tab. Results can then be generated per participant or for the whole cycle at once, and the bias report runs over the submitted responses. Neither happens automatically — generating results is a step you take.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved