For many firms, a completed evaluation isn't truly closed until there's a record showing the employee actually received and reviewed it. That documentation step has historically lived outside the platform, in signed PDFs, email threads, or meeting notes. Flo is the fastest shipping company in the legal talent industry, and this release brings that step inside: the Acknowledgment Stage gives admins a structured, auditable way to capture employee acknowledgment as part of the review cycle itself.
Firms have needed a formal record that employees received their performance feedback, whether to satisfy internal policy, support partner review processes, or document that a performance conversation actually took place. Without a native acknowledgment feature, that documentation had to be gathered separately, which meant more manual work, more coordination outside the platform, and records that weren't connected to the review data they referenced.
We built this after hearing from firms that the acknowledgment step was one of the clearest gaps between what the platform supported and what their process actually required.
Admins can now add an Acknowledgment Stage to any review cycle. The stage is configured in Step 1 of the review cycle setup alongside other stage settings. Admins define the acknowledgment text that employees will see, set start and end dates, and choose whether a comment is required. A comment field is always shown to reviewees but is optional unless the admin requires it.
The stage is flexible by design. It can be used to confirm receipt of a released evaluation, document attendance at a performance discussion, or capture any other acknowledgment the firm needs to record in connection with the review cycle.
Acknowledgment completions are tracked in their own column on the Reviewee table once the stage is active, with Pending and Completed statuses. In the main Review Cycles table, the Cycle Progress column now factors in completed acknowledgments alongside completed evaluation forms, so the overall picture of cycle completion stays accurate.
For employees, the acknowledgment stage appears as a task card on their review cycle dashboard when the stage is active. Once submitted, the task is marked complete. If an admin updates the acknowledgment text after employees have already completed it, a warning modal explains that the change will prompt those employees to re-acknowledge. Admins can cancel the change at that point, which reverts the text and leaves existing acknowledgments intact.
Firms now have an auditable, in-platform record that employees engaged with their feedback. That record is connected to the review data itself, not sitting in a separate folder or inbox. The tracking is automatic, the experience for employees is clear, and admins have visibility into who has and hasn't completed the step without chasing anyone down.
The safeguard around text changes also matters: if an acknowledgment statement needs to be corrected, the system makes clear what the downstream impact is before anything changes.
Acknowledgment workflows vary a lot by firm, and we know this first version won't fit every variation perfectly. Tell us where it doesn't match how you run things. That's exactly the kind of feedback that shapes what comes next.
If you're a Flo client and want to dig in, or you're new to Flo and curious how it works, book a demo and we'll walk you through it.