Proactive Duplicate Candidate Detection and Management

Last week, Flo launched another game-changing update. This time it's a capability that recruiting teams have needed for as long as candidate databases have existed: a proactive, intelligent way to find and resolve duplicate records before they create confusion in the pipeline.

The challenge

Candidates enter a firm's database through many paths: direct applications, events, agency submissions, and manual additions by admins. Any of those paths can create a second record for someone already in the system. Over time, a database with duplicate records makes it harder to trust what you're seeing when you review a candidate's history or pipeline status.

For lateral recruiting teams, duplicates can also have a financial impact. If an agency submits a candidate who already exists in your database or was previously submitted by another agency, unclear candidate ownership can lead to agency fee disputes.

What we launched

Flo now uses AI-powered automated matching to scan your candidate list for records that appear to represent the same person. When potential duplicates are found, admins see a notification banner on the Candidates List and Job Details pages. The banner is informational and does not interrupt any other workflow, so your team can address duplicates when it's convenient rather than being forced to stop and resolve them immediately.

Clicking "Manage Duplicates" opens a list of duplicate clusters: groups of records that Flo has identified as likely representing the same candidate. Each cluster can be expanded to see the individual records involved and their details, including whether any agency submissions are part of the group.

From there, admins can merge the records into a single, authoritative entry. When a merge involves candidates who applied to the same job from two different records, a modal appears after the merge to let the admin set the correct application status. For clusters involving two agency submissions for the same job, both submissions are surfaced so statuses can be resolved accurately. All agency submission history is retained in the merged record so nothing is lost.

That visibility gives recruiting teams a clearer record of how and when a candidate entered the system, helping them address potential ownership questions before they turn into agency fee disputes.

If a cluster turns out to be two genuinely distinct candidates, admins can dismiss it, and Flo will treat those records as separate going forward.

Why it matters

A clean candidate database is foundational to reliable recruiting operations. When records are duplicated, application history can be fragmented, status tracking can become inconsistent, and the effort to untangle a single candidate's record after the fact can be significant. In agency-driven lateral recruiting, that fragmented history can also make it harder to establish candidate ownership and determine whether a fee is actually owed. This feature addresses the problem at the source by flagging new duplicates as they arise rather than waiting for the list to become unmanageable.

The decision to retain all agency submission history through a merge is particularly deliberate. Firms need to know which agencies submitted which candidates, and that record should survive even when two entries are combined into one. Maintaining that history gives teams a stronger source of truth when agency ownership or fee questions arise.

Keeping your candidate database trustworthy is an ongoing effort, and this feature is designed to make that easier on a daily basis rather than a periodic cleanup project. Tell us what you'd like to see added to the duplicate management workflow as you use it.

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