How to avoid double submissions: a process for agency recruiters
On this page
- How double submissions actually happen
- The pre-submit check, in the order to run it
- What to ask the candidate
- Written consent: per client, per role, dated
- Set up your ATS so the check is fast
- Agreeing the rules with clients up front
- When the client says "we already have this candidate"
- Inside your own agency
- A double-submission checklist
- Questions people ask
To avoid double submissions, check three things before every send: that the candidate has not already reached this client by any route, that they have agreed in writing to be submitted to this client for this role, and that nobody else in your agency is working them into the same account. Most disputes come from skipping the first question or asking it too loosely.
This page is the process around that check: what to ask the candidate, what to record, how to set up your ATS so the check takes a minute, and what to say when a client replies "we already have this resume". The consent document itself is on the right to represent template page; this one is about making sure it is never needed in a dispute.
How double submissions actually happen
Rarely through bad faith. Nearly always through one of five gaps, and each needs a different fix.
| Route | What happened | Where the process broke |
|---|---|---|
| Candidate applied directly | They applied on the careers page months ago and forgot, or thought it did not count | The question "have you applied?" was too narrow |
| Another agency, with permission | The candidate spoke to two agencies and said yes to both | No written, role-specific consent from either side |
| Another agency, without permission | A resume was sent from a database without asking | Not your fault, but you need dated proof of your own consent |
| Two recruiters in your agency | A contract desk and a permanent desk both sent the same person | No shared ownership record, or nobody checked it |
| Referral inside the client | An employee referred the candidate the same week | Timing; the fix is a fast, dated submission and clean terms |
The last two are the ones agencies underestimate. An internal double send embarrasses you in front of the client even though there is no fee dispute, and a referral landing the same week is decided by timestamps.
The pre-submit check, in the order to run it
Run this for every candidate, every role, every time, including candidates you have placed before. It takes a minute or two when the ATS is set up for it.
- Search your own ATS for the candidate by name, email and phone, and look for any activity against this client in the ownership window your terms define. Duplicate records under an old email are the usual miss.
- Check who owns the relationship. If another recruiter in your agency has an active process with this candidate or this client, talk to them before you do anything else.
- Ask the candidate the four-route question (wording below), on the call, and write down the answer with the date.
- Get consent for this client and this role, in writing, before the resume leaves your hands. A general "happy for you to send my resume out" does not cover it.
- Read the client's terms for what counts as an introduction and how long it lasts, if you do not already have that recorded against the account.
- Send the submittal with the date and time visible, to the contact the terms name, from a system that keeps the sent record.
What to ask the candidate
"Have you applied there?" gets a no from a candidate who uploaded a resume to the company's careers site eight months ago. Ask about each route separately. Candidates answer specific questions accurately; they answer general ones optimistically.
Before I send anything to [Client], I need to check a few things,
because if your resume reaches them twice it can slow you down.
1. Have you applied to [Client] in the last year, for any role,
including through their careers page, LinkedIn or a job board?
2. Has any other recruiter or agency mentioned [Client] to you, or
asked if they could send your details, for this role or another?
3. Do you know anyone who works at [Client] who might have referred
you or passed your resume on?
4. Have you interviewed or spoken with anyone there before, even
informally?
[If all no:]
Thanks. I'd like to submit you to [Client] for [Role] only. I'll send
you a short email now; please reply to confirm, and don't let anyone
else send your details to [Client] while we're in process. If another
recruiter calls about them, tell them you're already represented.The last line matters as much as the questions. Candidates often do not know that a second agency sending their resume can hurt them, and many will happily say "already represented" once you explain why.
Written consent: per client, per role, dated
Verbal consent on the phone is real, but it is the candidate's word against another agency's email. Follow every yes with a short written confirmation the candidate replies to. Keep it specific:
Subject: Confirming: your application to [Client] for [Role]
Hi [First name],
Thanks for the call today. As agreed, I'll submit your resume to
[Client] for the [Role] position ([location / remote], [pay range if
shared]).
You told me you have not applied to [Client] or been put forward to
them by anyone else in the last 12 months.
Please reply "confirmed" so I can send it. I won't submit you to any
other company without asking you first.
[Your name]Store the reply against the candidate and the job in your ATS, not in your inbox. When a dispute comes, it arrives months later and often after the recruiter who took the call has left. The full document, with the clauses agencies commonly use, is the right to represent template.
If you interview across state lines and record or transcribe the consent call, tell the candidate at the start. The consent guide has a line you can read aloud.
Set up your ATS so the check is fast
A check that takes ten minutes gets skipped on a busy Friday. These settings make it take one. Field names differ by system; every staffing ATS has an equivalent.
- A submission record, not a note. Log each send as a structured submission against the job, with date, time, contact and the consent reply attached. Free-text notes cannot be searched reliably.
- Duplicate detection on email and phone. Merge duplicates weekly. Most internal double sends start as two records for one person.
- Client fields for the terms. Ownership window in months, what counts as an introduction, and whether the client wants the resume before or after a call. Fill these at account setup, from the signed terms.
- A "submitted to" view per candidate that the whole desk can see, including submissions from other divisions.
- A required field on submission: "direct application / other agency / referral checked, date". If your system allows mandatory fields, use one here.
Agreeing the rules with clients up front
Most fee disputes are really terms disputes. The time to settle them is when the account opens, not when two invoices arrive. Ask these at the first intake meeting, and confirm the answers in writing:
- What counts as an introduction: a resume, a name, or a resume with the candidate's permission?
- If two agencies send the same person, how do you decide who introduced them?
- How long does an introduction last, and does it cover other roles?
- Will you tell us within a working day if you already have the candidate?
- Do you check direct applications and referrals before you reply to a submission?
The fourth question does the most work. A client who replies "already have them" the same day saves you a week of work on a candidate you cannot place there.
When the client says "we already have this candidate"
Stay calm and specific. You want three facts: the date they received the resume, from whom, and whether it came with the candidate's permission. Then check your own record before you argue.
Thanks for telling me straight away. So I can sort this out on our
side, could you let me know when you received their resume and whether
it came from another agency, a referral or a direct application?
Our submission was sent on [date] at [time], after [Candidate] confirmed
in writing that they had not applied or been put forward by anyone
else. I'll speak to them today and come back to you by [time].Then work through what you find:
- Their record is earlier and legitimate (direct application or a permitted agency submission): withdraw, thank the client, and tell the candidate why. Do not argue a fee you are not owed; clients remember who was reasonable.
- Their record is earlier but came without the candidate's permission: send the client your dated consent and the candidate's confirmation, and leave the decision with them under the terms. Ask the candidate to tell the other agency directly.
- Your record is earlier: say so once, with the timestamp, and let the terms decide.
- The candidate forgot: tighten your questions, not your tone with the candidate.
Not legal advice. Who is owed a fee depends on the contract between your agency and the client and on the law that governs it. If a dispute involves a meaningful fee, read the terms with whoever owns contracts at your agency before you reply in writing.
Inside your own agency
Internal double sends are entirely preventable and cost you credibility rather than money. Three rules cover most of them:
- One owner per client contact. Anyone else who wants to send a candidate to that account goes through the owner, even with a perfect fit.
- Candidate ownership is visible and time-limited. The recruiter who screened the candidate owns them for a set period after the last meaningful contact, and the ATS shows it.
- Splits are agreed before the send, not after the placement. A one-line message in the shared channel ("sending Ana to Northwind for the ops role, split 50/50 with Sam as agreed") avoids a month of resentment.
A weekly check helps: pull every submission from the last seven days and sort by client. Duplicates show up immediately, while they can still be fixed with a phone call.
A double-submission checklist
- ATS searched by name, email and phone; no activity at this client inside the ownership window.
- No other recruiter in the agency has an active process with this candidate or this client contact.
- All four routes asked separately: direct application, other agencies, referral, earlier contact.
- Written consent received for this client and this role, stored against the job.
- Candidate told not to let anyone else send their details to this client.
- Client terms recorded: what counts as an introduction and for how long.
- Submission sent to the named contact, with the date and time kept in the system.
Questions people ask
What is a double submission in recruiting?
The same candidate reaching the same client for the same role (or, under many terms, any role) from two sources: two agencies, an agency and the candidate's own application, or two recruiters inside one agency. Whoever the client's terms recognize as first usually owns the introduction.
Who gets the fee when a candidate is submitted twice?
It depends on the client's terms of business and, where they are silent, on what the client decides. Many terms credit the first dated introduction with the candidate's permission; some credit whoever arranged the interview. Read the terms for each client rather than assuming a market rule.
How long does ownership of a candidate last after a submission?
Whatever the terms say. Six or twelve months from the introduction are common choices, but they are contract terms, not law, and some clients do not grant ownership at all. Record the window per client in your ATS so the pre-submit check can use it.
Should I submit a candidate who says they have not applied anywhere?
Ask the question in a way that catches the common misses first: job boards, the company careers page, a referral from a friend who works there, and other agencies who may have sent the resume without asking. Candidates often forget one of those, not because they are lying but because they did not think it counted.