Few things damage a client relationship faster than receiving the same CV twice. One recruiter sends a profile on Monday, a colleague sends the same person for another vacancy on Thursday, or the candidate was already presented three months ago and nobody remembers. The client wonders whether your team talks to each other, and when a hire follows, there is a question about which introduction counts. This article explains how to prevent double-submitting the same candidate to the same client in your Applicant Tracking System: why it happens, what to record and how to build a check into the submission stage so it no longer depends on memory.
The risk looks different per segment. In recruitment agencies several recruiters often work the same client for different roles and approach the same candidates through the same channels. Staffing desks send many profiles quickly, sometimes to several branches of one client, where one person is easily offered twice. Secondment teams propose the same professional again when an assignment ends, which is fine as long as everyone knows the earlier proposal and its outcome. In executive search a long list is shared in confidence, and a name that appears again in another search for the same client needs a deliberate decision. In-house recruitment teams see the issue from the other side: the same candidate arrives through two agencies, or through an agency after applying directly, and you need to know who was first.
Why the same candidate gets submitted twice
- Submissions are tracked per vacancy only, so a recruiter working a new role does not see that the candidate was already presented to that client for another one
- The candidate exists twice in the system, for example under a private and a work email address, so the history on one record is invisible from the other
- The client has several branches or entities, and submissions to one of them are not linked to the client as a whole
- Profiles are sent from personal mailboxes, so the submission never reaches the candidate or client record
- An earlier submission was rejected or withdrawn without a recorded reason, so the next recruiter sends the profile again without context
What to record for every submission
- Candidate and client, not only the vacancy — every submission is linked to the candidate record and the client record, including the entity or branch that received it
- Date and recruiter — when the profile was sent and by whom, recorded automatically when the stage changes rather than typed in later
- Vacancy and channel — which role it was for and how it was sent, so the introduction can be traced
- Consent — the candidate’s consent for this specific submission, given before the profile goes out
- Outcome and reason — invited, rejected, on hold, hired or withdrawn, with the reason the client or candidate gave
With this in place, the question “have we presented this person to this client before?” becomes a lookup instead of a round of messages in the team chat. It works because the candidate and client records sit beside the pipeline in one system, not in separate spreadsheets.
Build the check into the submission stage
Add a duplicate check to the written entry criteria of the submission stage. Before a candidate moves to “presented to client”, the Applicant Tracking System shows any earlier submission of the same candidate to the same client, across all vacancies and entities, within the period in which an introduction counts under your agreed terms. If there is a match, the recruiter sees when, by whom, for which role and with what outcome. The submission does not have to be blocked; sometimes presenting someone again is the right call. But it becomes a deliberate decision, recorded with a short reason and, where your process requires it, approved by the owner of the vacancy or the account manager for that client.
Clean candidate records come first
A duplicate check is only as reliable as the records behind it. If the same person exists twice, the check finds nothing. Merge duplicates instead of creating a second record, match on more than a name, such as email address, phone number and profile link, and record the source at the first application. The stage history completes the picture: when every stage change records who moved the candidate, there is no doubt about who presented the profile and when.
Agree how long an introduction counts
Whether a second submission is a problem often depends on time. Many agencies agree with their clients that an introduction remains valid for a set period. Record that period with the agreed terms on the client record, so the check uses the period that applies to this client rather than a general rule. In-house teams can do the same for agencies: record which agency introduced a candidate first and when, so a second introduction of the same person does not turn into a discussion about fees later.
When a second submission is the right call
Sometimes it is: the candidate has gained relevant experience, the earlier role was very different, or the client asks for the profile again. In that case, mention the earlier submission openly in your message to the client, refer to the date and the role, and record why you are presenting again. Clients tend to appreciate that openness; what irritates them is the impression that nobody keeps track. If the earlier submission is still waiting for an answer, follow it up using the response deadline for client submissions instead of sending the profile a second time.
Measure it with your own data
Count from your own records: how many candidate and client combinations have more than one submission, how many of those were deliberate with a recorded reason, how often the check flagged a match before a profile went out and how many disputes about an introduction you had, with the recorded outcome. Report the number of records behind each figure and use the same filters every time. Do not rely on general figures you cannot verify; your own submission history shows where the gaps are, for example a client with many entities or a team that still sends profiles outside the system.
Where artificial intelligence may help — and where it must not
Artificial intelligence may suggest that two candidate records probably belong to the same person, or point out that a profile about to be sent resembles one already presented to that client under a different email address, so a person can check and merge. It may draft a short note to the client that mentions the earlier submission, which the recruiter reads and adjusts. It stays a helper. Artificial intelligence does not replace recruiters, does not decide whether a candidate is presented again and does not merge records without a person confirming it. That judgement stays with the people who know the candidate and the client; the Applicant Tracking System makes sure the history is visible when they make it.
A practical start
- Link every submission to both the candidate record and the client record, including the entity or branch
- Record date, recruiter, vacancy and outcome as fixed fields when the stage changes
- Add a check for earlier submissions to the same client to the entry criteria of the submission stage
- Record the agreed validity period of an introduction with the client’s terms
- Merge duplicate candidate records and review once a month which candidate and client combinations have more than one submission
One candidate, one introduction
Preventing double submissions is not about adding rules. It is about a history that everyone can see before a profile goes out, which protects your relationship with the client, the trust of the candidate and your fee. Explore the product or book a demo — we show how candidate and client records, stage criteria and submissions work together in BoldATS for your segment.