How to Handle Multiple Agency Submissions for the Same Candidate

Multiple recruiting agencies submitting the same candidate for an open position is one of the most common operational headaches in technical hiring. You spot a stellar engineer, move forward with conversations, and suddenly discover three different agencies claiming credit for the introduction. Sound familiar?

This scenario creates friction, damages relationships, delays hiring decisions, and sometimes kills otherwise perfect placements. The stakes are high: mishandled duplicate submissions can cost you time, erode trust with agency partners, and create legal complications around commission disputes.

The good news? A clear, documented process prevents most of these problems before they start. This guide covers the operational framework, communication strategies, and tools that help technical recruiters manage multiple agency submissions professionally and fairly.

Why Multiple Agency Submissions Happen (And Why They Matter)

The Mechanics Behind Duplicates

Multiple agencies submit the same candidate for several structural reasons:

Passive candidate networks overlap. Top engineers maintain profiles on multiple platforms and job boards. When an agency sources a candidate from GitHub, LinkedIn, or their internal network, they're often finding people who are already networked with other agencies. The candidate hasn't applied to your job posting—agencies are proactively reaching out on behalf of their clients.

Weak intake processes. If your company doesn't have clear submission requirements or a centralized system for tracking who's been submitted, agencies won't know whether someone else already introduced a candidate. They submit in good faith, unaware of the overlap.

Competitive pressure among agencies. Recruiters work on commission. When multiple agencies service the same talent pool and have the same client (you), speed matters. An agency that moves fast might submit without verifying whether someone else got there first.

Candidate behavior. Some engineers intentionally work with multiple recruiters to maximize opportunities. They might tell each recruiter "submit me to this company" or let multiple agencies pitch them independently.

Why It Costs You Real Money

Handling duplicates poorly creates tangible costs:

Delayed hiring decisions: If you're unsure who submitted first, you might halt the process while agencies fight it out
Commission disputes: Two agencies claim credit. Both demand payment. You're now in a negotiation or legal dispute
Damaged agency relationships: Unfair commission handling makes agencies less willing to work with you in the future
Lost candidates: While you're sorting out who submitted whom, a candidate accepts another offer elsewhere
Team frustration: Your hiring managers and recruiters spend time mediating instead of closing roles

A single bad experience with commission disputes can make reputable agencies deprioritize your open roles. Agencies talk to each other. Handle it poorly once, and you're suddenly last on the call list.

Set Up a Centralized Submission Tracking System

What You Need to Track

The foundation of handling duplicates is knowing exactly who submitted whom and when. This requires a system—whether a simple spreadsheet or integrated ATS—that captures:

Submission details: - Candidate name - Email address - GitHub profile URL (especially useful for hiring developers) - Position(s) they're being submitted for - Submitting agency/recruiter name - Date and time of submission - Submission method (email, ATS, portal, LinkedIn message)

Submission status: - Confirmation of receipt - Whether the candidate is already in your system - Current stage in interview process - Outcome (hired, rejected, withdrawn, etc.)

Agency information: - Agency name - Contact person - Commission agreement percentage - Preferred submission method

Tools That Work

ATS systems with agency portal features (Greenhouse, Lever, JazzHR) allow agencies to submit candidates directly and create automatic timestamped records. This is the gold standard because it removes ambiguity about when each submission arrived.

Spreadsheet-based tracking works for smaller hiring operations. Create a master sheet with a row for each submission, sorted by candidate and date. Include a column for "duplicate flag" and "resolution." It's manual, but it works.

Email management rules (if you don't have an ATS) can auto-forward all submissions to a dedicated inbox with a timestamp. This creates a chronological record even if submissions come through different channels.

Zapier or Make (formerly Integromat) can automatically log incoming submissions to a central database when combined with your email system, creating an automated paper trail.

The system itself matters less than consistency and accessibility. Every person involved in hiring—recruiting coordinators, hiring managers, even finance—should know where to check whether a candidate has already been submitted.

Establish Clear Submission Guidelines

What Agencies Need to Know

Don't assume agencies know how you operate. Document and share explicit submission guidelines with every recruiting partner:

Submission format: - How should they submit? (Email to specific address, through your ATS portal, LinkedIn message?) - What information must they include? (name, email, GitHub, years of experience, relevant projects) - Which position(s) can they submit for? (Some companies reserve certain roles for certain agencies)

Timing expectations: - How quickly will you acknowledge receipt? - How quickly will you provide feedback on whether a candidate is a fit? - What's your typical time-to-feedback on submitted candidates?

Duplicate handling policy: - What happens if multiple agencies submit the same person? - How do you determine who gets credited if a candidate is already in your system? - Will you accept resubmissions of rejected candidates, and if so, after how long?

Commission terms: - Explicitly state your commission structure - Define when commission is earned (submission, interview, offer, hire date?) - Clarify whether commission applies if a candidate was already in your system

Exclusivity boundaries: - Are certain candidates off-limits because you're recruiting them directly? - Will you tell agencies about internally sourced candidates, or is that assumed?

Share this in writing. A one-page PDF sent to every agency partner prevents most disputes before they happen.

Communication Template

Here's a straightforward approach:

"Thank you for partnering with us. To ensure smooth submissions and fair handling of all candidates:

Please submit candidates to [submission email/portal] with the following information: - Full name, email, phone - GitHub or portfolio link - Years of relevant experience - Position(s) of interest

What we'll do: - Acknowledge all submissions within 24 hours - Confirm if a candidate is already in our system within 2 business days - Provide interview feedback within 1 week

Duplicate handling: - If multiple agencies submit the same candidate, credit goes to the first submission (by timestamp) - We'll notify all submitting agencies of the status - Commission applies only to the credited submission

We value your partnership and aim to treat all agencies fairly."

This removes guesswork and sets expectations before problems arise.

Your Response Protocol When Duplicates Arrive

Step 1: Immediate Verification (Within 24 Hours)

When a submission comes in, immediately check:

Is this person already in your recruiting database? Search by name, email, and GitHub profile. Check recent hiring processes from the past 6-12 months.
Has another agency submitted them for this role? Look at your submission tracker. If the candidate appears, note the earlier submission date.
Is this a direct application? Some candidates apply directly through your careers page. That takes priority over agency submissions.
Is the person already an employee? Rare, but it happens—someone at the company gets recruited by an agency for a role they could transfer into.

Log the findings in your tracking system immediately. This creates your record for later disputes.

Step 2: Communicate Early and Clearly

If it's the first submission: Acknowledge receipt and tell the agency you've received their submission and will provide feedback on a timeline (e.g., "within 5 business days").

If it's a duplicate: Contact the submitting agency within 48 hours and inform them: - "Thank you for submitting [Candidate Name]. We received a submission for this candidate from another recruiting partner on [date]. Per our submission guidelines, we'll work with the first submitted agency and will keep you updated on the outcome."

Be factual and kind. Don't make the agency feel blamed. Many duplicate submissions are honest errors, not malicious.

If you receive the same candidate from three agencies: Contact the first-submitting agency with a status update. Politely inform the other two that the candidate has already been submitted and that you're proceeding with the original submission.

Step 3: Single Point of Contact

Once duplicates emerge, pick one agency as your primary contact for that candidate. Don't update all three agencies separately on interview progress—this creates confusion and invites more disputes.

Communicate with the credited agency about: - Interview scheduling - Feedback and decisions - Offer status - Final outcome

Notify other agencies of the final outcome only (hired, rejected, or candidate withdrew), not of every interview stage.

Handling the Tricky Cases

Candidate Already in Your System But Not Submitted by an Agency

Situation: A candidate applied directly to your job board three weeks ago. Now an agency submits them.

Resolution: You already have this candidate through a non-agency channel. No commission owed. Simply inform the agency that you're already evaluating the candidate and appreciate the introduction, but you'll proceed with the direct application record.

Candidate Was Rejected, Then Resubmitted by a Different Agency

Situation: Agency A submitted a candidate. You interviewed them. They didn't move forward. Three months later, Agency B submits the same person for a different role.

Resolution: This depends on your policy, but generally: - If the candidate was rejected for technical reasons, they likely won't succeed in a different role. Respectfully decline the resubmission. - If the candidate was a nice person but not a fit for the specific role, it's fair to re-evaluate for a different position. - Give the credited agency (A) first right to resubmit their candidate for new roles, or at minimum, notify them before accepting a resubmission from another agency.

The "Warm Introduction" Dispute

Situation: Agency A has a relationship with the candidate and did the initial outreach. But the candidate applied directly to your job board. Now Agency A claims they deserve credit because they introduced the candidate to the job market or your company.

Resolution: Direct applications always take priority over agency introductions, even if an agency can claim they "warmed up" the candidate. Your submission tracking and job board logs are the source of truth. This is one reason direct applications are worth promoting—they eliminate these disputes.

A Candidate Tells You Different Agencies Represent Them

Situation: You're interviewing a candidate. In casual conversation, they mention they're working with three different recruiters at three different agencies, all of whom submitted them.

Resolution: This is common and usually legitimate. Candidates can work with multiple recruiters. Your job is to track which agency submitted them to your company first, using timestamps and submission records. The candidate's personal recruitment strategies don't change who gets credited with the introduction to you.

However, in your next interaction with the candidate, clarify: "We received your submission from [Agency Name] and will be working directly with them on the next steps." This prevents the candidate from later claiming another agency should have been credited.

Commission Disputes: Prevention and Resolution

Set Commission Terms in Writing

The clearest way to prevent disputes is to make commission terms unmistakably clear before partnerships begin. Your agreement should state:

Commission percentage (typical range: 15-25% of first-year salary)
When commission is earned (at hire, at start date, etc.)
Whether commission applies to candidates already in your system
How commission is handled in duplicate submissions (first submission gets it)
What disqualifies a commission claim (candidate turned down offer, background check failed, etc.)

What to Do If an Agency Disputes a Commission

Don't pay twice. Two agencies don't both get paid for one hire. This is non-negotiable.
Pull the record. Show the disputing agency the timestamped submissions from your tracking system. If Agency A submitted on Oct 1 and Agency B submitted on Oct 8, Agency A gets credit.
Offer the losing agency a path forward. "We appreciate your interest in this candidate. While [Agency A] receives credit for this placement, we'd like to continue working with you on future roles. Here's a candidate from our recent rejections who might be a good fit for your network..."
Document everything. Keep copies of all emails, submissions, and timestamps. If a dispute escalates, you want a clear paper trail.
Use a mediator if needed. If the dispute is significant, consider having a neutral party (your procurement team, an HR business partner) review the record with the agency.
Consider a tiebreaker clause. If timestamps are truly ambiguous, you might offer a 50-50 commission split as a one-time gesture of goodwill, but make clear this won't be your standard approach.

When to Walk Away from an Agency

If an agency repeatedly submits duplicates, ignores your guidelines, or becomes aggressive about commissions, it's reasonable to pause the relationship. Document the problems and communicate clearly:

"We value our partnership with [Agency], but we've had several submission guideline issues and duplicate submissions that have complicated our hiring process. We'd like to take a 30-day pause to recalibrate. Here's what we need going forward [restate guidelines]."

This gives the agency a clear chance to improve. If problems persist, you can formally end the partnership without guilt.

Beyond Duplicates: Optimizing Your Agency Sourcing Process

Once you've solved the duplicate problem, you can optimize further:

Tier Your Agency Partners

Not all agencies are equally valuable. Create tiers based on: - Quality of submissions (interview-to-offer ratio) - Speed to submission for open roles - Adherence to submission guidelines - Past commission disputes

Tier 1 agencies get first access to new roles and more open communication. Tier 2 and 3 agencies get access but with stricter guidelines and slower response times. This incentivizes better performance.

Use Zumo to Reduce Agency Dependence

While agency partnerships are valuable, over-reliance on agencies for sourcing increases duplicate submissions, slows hiring, and inflates costs. Consider using developer sourcing platforms that let you directly analyze GitHub activity to identify engineers actively building in your target technologies.

Platforms like Zumo help you source passive candidates directly, reducing your dependence on agency introductions and eliminating many duplicate submission headaches altogether. You can hire JavaScript developers, hire Python developers, hire React developers, and other technical talent by analyzing their actual coding activity, not just their resumes.

Create an Agency Scorecard

Track metrics on every agency partner monthly:

Metric	Target	Actual
Submissions per month	5+	6
Interview conversion rate	40%+	35%
Offer acceptance rate	60%+	55%
Hire success (still employed at 6 months)	90%+	92%
Guideline adherence	100%	85%
Duplicate submissions	0%	8%

Share this scorecard with agencies quarterly. It creates accountability and shows exactly what's working and what needs improvement.

Implement an ATS with Agency Portal

If you're still managing submissions through email, an ATS with a dedicated agency submission portal is worth the investment. Greenhouse, Lever, and JazzHR all offer this. Benefits include:

Automatic timestamping (eliminates "whose submission came first" disputes)
Reduced email clutter and miscommunication
Faster feedback loops to agencies
Centralized candidate history across all submissions
Clear audit trail for commission disputes

FAQs

What if two agencies claim they submitted a candidate simultaneously?

If timestamps are within minutes of each other and you can't determine a clear first submission, you have a few options: (1) Ask the agencies to provide evidence of when they first made contact with the candidate, (2) Offer a 50-50 commission split as a one-time goodwill gesture, or (3) Use your standard first-submission policy and accept that one agency will be disappointed. Option 3 is clearest and most repeatable. Pick whichever aligns with your company values.

Can an agency claim commission if a candidate withdrew or turned down an offer?

Depends on your agreement. Most companies pay commission only on successful hires (candidate accepts offer and starts). If you agreed to pay on submission or interview, commission might still apply. This is why written commission terms matter—spell out exactly what constitutes an earned commission. "Hire" is clearer than "submission."

Should I accept resubmissions of the same candidate for different roles?

Yes, but with conditions. If a candidate was rejected for a specific role (poor technical fit, culture mismatch), they likely won't succeed in a different role. However, if they were just "not quite right" or the timing was off, a resubmission for a different position is reasonable. Set a policy: "Candidates rejected for technical reasons won't be considered for other roles within 12 months. Candidates rejected for role-specific reasons can be resubmitted for different roles after 6 months." Communicate this to agencies so they know when resubmissions are welcome.

How do I handle a candidate who worked with multiple agencies and doesn't remember which one they gave permission to submit them to my company?

This happens. Your submission records are the source of truth, not the candidate's memory. Trust your timestamped submissions. If the candidate's version differs from your records, side with the records. If the candidate genuinely wants to work with a different agency that later submitted them, that's their choice for future applications—but your credit goes to the first submission to your company.

Should I pay agencies if I source a candidate they also submitted?

No. If you sourced a candidate directly (through your career site, your network, or a sourcing platform), and an agency also submitted them, no commission is owed. You already found them. The agency gets no credit. This is another reason direct sourcing matters—it's cleaner and removes agency commission costs. If an agency claims they identified a candidate you also found, your internal sourcing timeline is what matters. Document when you first engaged the candidate internally.

Ready to reduce your reliance on agency submissions? Zumo lets you source developers directly by analyzing their GitHub activity, cutting down duplicates, speeding hiring, and saving commission costs. Explore how developers sourcing platforms can complement your agency partnerships.