A candidate can appear more than once in a recruitment system for ordinary reasons: a different email address, a later application, an import from another source or a record created before an existing profile was found. Treating the profiles as separate people can fragment vacancy activity, while merging them too quickly can attach unrelated information to the wrong record.
A duplicate-profile review establishes identity first, then decides which working information belongs together. The objective is one coherent recruitment record without erasing useful source history.
Confirm that the profiles represent the same person
Compare the identifying information legitimately available to the recruitment team, such as name, contact details and relevant application context. Do not merge records merely because names are similar.
If identity remains uncertain, keep the profiles separate and route the question through the team's normal data-quality process.
Identify the current recruitment activity on each profile
Review live vacancies, applications, interview stages and other active workflow attached to both records. This shows what could be disrupted if one profile is simply closed or overwritten.
Current activity should be understood before any consolidation takes place.
Compare contact information carefully
Where the profiles contain different contact details, determine which information is current from supported candidate communication or another approved source. Preserve relevant history according to the organisation's normal record controls.
Do not assume the most recently entered field is automatically the correct one.
Keep vacancy histories distinguishable
A candidate may legitimately have been considered for several roles at different times. Consolidation should not make those separate recruitment journeys look like one continuous application.
Retain the role, stage and timing context needed to understand each piece of activity.
Review communication before removing a duplicate
Check whether useful candidate instructions, availability changes or other current information exists only on one profile. Move or preserve information through the authorised system process rather than relying on memory.
A merge that loses the latest candidate instruction creates a larger problem than the duplicate itself.
Use the system's controlled merge or correction route
Where the recruitment platform provides an approved way to merge or resolve duplicates, follow that process and the organisation's data-handling controls. Avoid improvised copying that creates further versions of candidate information.
If the platform does not support a straightforward merge, document the chosen current record and the treatment of the duplicate.
Verify the surviving recruitment record
After resolution, check that active vacancies, current contact information and necessary recruitment history remain accessible from the intended record. Close any obsolete duplicate workflow that could still trigger communication.
A disciplined duplicate-profile review protects both operational continuity and record quality. It gives recruiters one usable candidate view without pretending that every similar-looking profile can safely be combined.