What actions can I take from Cycle Management?

From the Manage button on any cycle, you can:

• Edit Cycle → Update dates, scope, or details.

• Clone Cycle → Duplicate an existing cycle for reuse.

• Close Cycle → Mark the cycle as finished and move it to past cycles.

• Delete Cycle → Permanently remove a cycle (irreversible).

Use when:

• The start or end date needs adjusting (e.g., moving from calendar quarters to fiscal quarters).

• You need to rename a cycle for clarity (e.g., “Q4 2025 (Fiscal)” instead of just “Q4 2025”).

• The scope changes (e.g., originally team-only, now needs to apply to the whole organization).

Use when:

• You want to quickly set up the next quarter/year with the same structure and dates.

• You’re running a pilot program (e.g., a team cycle) and want to duplicate it for other teams.

• You want a baseline from an old cycle but don’t want to rebuild everything from scratch.

Use when:

• A cycle has officially ended and you want to lock it for reporting/review.

• To finalize results before launching the next cycle.

• To encourage teams to wrap up their OKRs and prevent further edits.

Use when:

• A cycle was created by mistake (wrong dates, wrong scope).

• A test cycle was set up for training or demos and is no longer needed.

• A cycle is redundant because the org has standardized around a different cadence.

These actions are admin-only for good reason — they affect visibility, alignment, and reporting for the entire org.