A candidate may ask a recruitment team to update the name used in its records during an active hiring process. If one system is changed while other working records remain under the earlier name, consultants can create duplicate profiles or lose the connection between existing interviews, applications and communication.
A controlled name-change review keeps the current candidate identity clear while preserving enough record continuity for the recruitment history to remain understandable.
Start from the candidate's current instruction
Record the requested update through the organisation's authorised process and use the information the candidate has provided. Avoid guessing spelling, format or the reason for the change.
Only seek additional information where the recruitment process genuinely requires it.
Identify the active records affected
Check the candidate profile, current vacancy activity, interview scheduling and other live recruitment records where the earlier name may still appear. Build a bounded list rather than changing unrelated historical material indiscriminately.
This reduces the chance of leaving competing current identities in use.
Protect the link to existing recruitment history
Make sure earlier applications, notes and decisions remain connected to the same candidate after the update. A name change should not create a new candidate journey unless the underlying system genuinely requires a controlled migration.
Where the platform supports aliases or previous-name handling, follow the organisation's approved configuration and data process.
Prevent duplicate profile creation
Alert the relevant working team to the current record where necessary so a colleague searching under the new name does not create another profile. If a duplicate already exists, route it through the normal duplicate-record review.
Do not merge records solely on the basis of a matching name.
Update candidate-facing communication appropriately
Use the candidate's current requested name in future recruitment communication where the process allows. Check active interview or vacancy documents that will be used again rather than reproducing obsolete details.
Historical messages do not need to be rewritten simply to make the record look uniform.
Keep sensitive context out of general notes
The operational record usually needs to show the current name and the controlled update, not unnecessary personal explanation. Follow the organisation's data-handling procedures for any supporting information.
Record only what colleagues genuinely need to manage the recruitment process correctly.
Verify one coherent candidate record
After the update, check that current vacancy activity, contact details and recruitment history still point to the intended candidate profile. Close obsolete duplicate workflow and make the current identity clear to the active team.
A controlled name update preserves continuity without making personal information more complicated than necessary. The candidate should remain one person with one understandable recruitment history before and after the change.