How SourcingOS handles duplicate candidates and identity conflicts
Multiple sources can describe the same person, but similar names, employers, locations, or usernames are not enough to justify every merge. SourcingOS keeps identity confidence and source provenance as separate review concerns.
Last reviewed: 2026-09-06
Ask SourcingOS about this page
Duplicates are expected in multi-source sourcing
The same person can appear through a people-data provider, ATS record, public profile, GitHub account, research page, or other evidence source. Multi-source duplication is normal and can even strengthen identity confidence when the evidence truly aligns.
False merges are more damaging than visible duplicates
Combining two different people corrupts career history, evidence, contact data, and ranking. When identity is uncertain, preserving a review boundary is safer than silently collapsing records.
Source observations should survive the merge
When profiles are confirmed as the same person, useful evidence should retain its original source and observed context instead of becoming one source-free master record.
Recruiter-confirmed identity is durable context
A recruiter-confirmed merge or separation should be treated as an explicit decision so later searches do not repeatedly recreate the same ambiguity.