Most hiring systems are built on one assumption: one person, one record. In practice an employer often holds two or three of you, each under a different email, a slightly different spelling of your name, and a different slice of your history. The recruiter who opens your file sees whichever version their search happened to return.
That is annoying on its own. It gets expensive the moment a recruitment agency is involved, because then the duplicate is not just a data problem, it is a question of who gets paid.
Where the second record comes from
Nobody sets out to duplicate themselves. It happens through ordinary admin, spread over a few applications.
- You applied from a personal address one year and from a work address the next, or the other way round.
- Your name changed, or it went in without the accent, or with a shortened first name, or with the surname order reversed.
- An agency rebuilt your CV in its own template and submitted you with its own formatting, sometimes with its own phone number and email as the contact route. That is a deliberate commercial practice, not a typo.
- You applied directly to a role and a consultant put you forward for the same role a week later.
- You created an account on their careers site once, lost the password, and made a new one with the address you were using at the time.
Each of those is obviously the same person to a human being. To a matching rule, several of them are not.
What the system does about it, and what it does not
Most applicant tracking platforms de-duplicate on the email address first, as an exact match at the point of submission. That check is cheap and reliable, and it is exactly why a second address defeats it. The fallback is a fuzzy match on name plus phone number, and that one is deliberately conservative, because a wrong merge is worse than a duplicate. Fusing two real people into one file is a mess that takes far longer to unpick than leaving two records alone.
So near-misses land in a possible-duplicate queue, where the platform has one. That queue is not the first thing a coordinator opens on a Monday morning.
Merging is a manual act. A person has to decide which record survives as the primary, which fields win, and whether attachments and notes carry across. Nobody does that work for a candidate who is not currently in an active process.
A duplicate is not an error the system corrects. It is a state the system tolerates until a human being is asked to fix it.
The half nobody writes about: which agency the employer thinks you belong to
If you only ever apply directly, a split record is friction. As soon as two agencies are in play, it becomes money, and money changes what the employer does with you.
A contingency agency gets paid only if its candidate is hired, and the fee attaches to the introduction rather than to the work. Supplier agreements therefore carry an ownership clause, variously called right of representation, candidate ownership, or an introduction clause. The usual shape is that the first agency to submit a named candidate holds the claim on that candidate for a defined window. How long that window runs varies by market and by contract, typically counted in weeks or months. It lives in the supplier agreement, not in law. Some contracts scope the claim to a single role, others to the whole employer. Some reset it if the candidate had already applied directly.
First submission usually wins
The clock normally starts at the first complete submission, meaning the moment your CV arrived at the employer, not the moment a consultant phoned you about the role. A conversation is not a claim. This matters, because the consultant who told you about the job on Tuesday may have no standing if a rival sent your CV on Monday.
The collision lands on you, not on them
Two agencies claim the same candidate for the same role, and now the employer has to referee a commercial dispute between two suppliers it wants to keep. There is a cheap way out of that, and it is not to pick a winner. It is to not hire the candidate at all. Plenty of talent teams have a standing habit of parking a contested profile until the window lapses.
Nobody tells you this is what happened. You get a polite no, or you get nothing. It is unfair, and it is also completely rational from their side: a hire fills one role, while a disputed fee is a legal argument and a damaged relationship with a supplier they will need again next quarter.
What you actually control
- Never give blanket permission. "Send me your CV and I will put you forward" is not consent to anything in particular. Ask for the company name and the role before you answer.
- Give the yes in writing, one company at a time, by email rather than on a call. That way you hold a timestamp too.
- Keep your own log. Company, role, agency, consultant name, the date you authorised it, the date they confirmed the CV went in. A spreadsheet is enough, and it is the single most useful thing in this article.
- Use one email address for everything career-related, for as long as you can. Pick the one that outlives employers.
- Ask which name and which contact details they are submitting you under. Ask them not to replace your address with theirs. Some will refuse. Note who refuses.
Keeping one canonical CV file helps more than it sounds like it should. Whether you maintain it by hand or export it from a LinkedIn-to-CV tool like Postulit, send the same document everywhere, so that version drift is not one more reason two records look like two people.
If the collision has already happened
Tell the internal recruiter early, in one short message, with dates and names. Something close to: two agencies have put me forward for this role, I authorised the first on the third, the second submitted me without asking, I would like to be considered on the first submission. Then stop talking. You are handing them facts, not asking them to adjudicate.
Early disclosure turns it into an admin decision. The same information discovered three weeks later looks like you shopped yourself around and let two suppliers fight over your fee.
What a split record costs you at that employer over time
Your history looks thinner than it is. Four applications across two records read as two applications each, and persistence is one of the few things a candidate record can actually demonstrate.
Notes do not travel either. A rejection sits on one record and strong interview feedback sits on the other, so whichever one a recruiter opens, they are starting either from zero or from your worst day. Talent pool searches, the ones that resurface strong past applicants when a similar role opens, will only ever find one of you, and it is usually the older record with the dead address on it.
Data requests have the same blind spot. Ask them to correct or delete your details and they act on the record you named. The other one stays exactly as it was.
Asking for a merge
You can ask, and it is worth asking when you are already in a process. Write to the internal recruiter, or to the careers or privacy contact on their site if you are not. Give them both email addresses, both spellings of your name, the phone number, rough dates for each application, and any requisition references you kept. Say plainly which record should survive as the primary and which address should be the live one.
Set your expectations honestly. Some platforms merge cleanly. Some only flag one record as a duplicate and leave the history where it sat. Some cannot merge across certain boundaries at all. Where local data protection law gives you a right to have inaccurate personal data corrected, framing it as a correction request carries more weight than asking for a favour, though whether that reaches a duplicate record is a question for their legal team rather than for you.
This is the honest position: you control your email address, your written authorisations and your own log, and you do not control the merge button, the supplier agreement or how long the ownership window runs. So spend your effort upstream. Today, pick the address that goes on every future application. This week, start the log of who has sent you where. And before you say yes to the next consultant who calls, make them say the company name first.