Product Updates

Clone Review Cycles: Skip the Setup, Start Where You Left Off

Written by Katherine Allen | Aug 12, 2026, 4:39:58 PM

Flo keeps the updates moving, and this one is a direct response to something we heard repeatedly from the Professional Development and HR teams running review cycles in Flo Performance Management. Cloning review cycles is live, and it makes the start of every new cycle noticeably faster.

The challenge

Firms run review cycles on a predictable rhythm: quarterly, annually, or by practice group. The structure of each cycle tends to be consistent from one round to the next, with the same stages, the same forms, and the same settings. Rebuilding all of that from scratch each time left room for configuration drift and took time that could be spent elsewhere.

What we launched

Admins can now clone any existing review cycle directly from the Review Cycles list by selecting Clone from the Actions menu, or from within a cycle's detail page using the Clone Review Cycle option. Before the clone runs, a confirmation modal explains exactly what will and will not carry over.

The clone opens immediately as a new draft. From there, admins go into Review Cycle Settings to add stage dates and make any adjustments before publishing. Here is what carries over from the source cycle:

  • Stages and stage forms
  • Question visibility settings
  • Reminder and notification triggers
  • Reviewer eligibility rules
  • PDF templates
  • Each reviewee's form assignments


A few things are intentionally left out. Stage dates and the evaluation release date are always cleared, so admins set fresh dates before publishing. Reviewer-reviewee pairings do not carry over, since those assignments typically shift from cycle to cycle. Submissions, matters, per-user eligibility exemptions, and any participants who have since lost access to Flo Performance Management are also excluded from the clone.

Why it matters

For teams managing multiple review cycles a year, the time savings add up quickly. Starting from a cycle that already reflects the right structure means less risk of a configuration being set up differently than intended, and fewer steps between the decision to run a new cycle and actually getting it in front of reviewers.

It also makes it easier to maintain consistency across cycles, which matters when you are comparing performance data over time. If the forms and stages are set up the same way each round, the results are easier to interpret and act on.

This is a straightforward efficiency gain, and we think it will make a real difference for teams running frequent cycles. If there are other parts of cycle setup that feel repetitive or worth streamlining, we would genuinely like to hear about them.

Want to see our latest updates in action? Book a demo and we'll walk you through them.