Who Owns the Candidate? Prevent Agency Submission Disputes With an Evidence Trail

A practical playbook for agency candidate representation, duplicate submissions, timestamp disputes and client-specific permission.

RoleRise editorial

A timestamp is evidence of an action, not a universal legal right to a person. Design the record before a fee dispute happens.

This field guide addresses a failure that can survive a perfectly configured ATS: a decision made without a clear owner, time boundary or evidence trail. The examples are illustrative, not claims about RoleRise customer results. Use the procedures as operational templates and adapt them to the applicable employment and privacy rules.

The dangerous phrase: “We own this candidate”

A person is not agency property. Commercial introduction rights, exclusivity periods and fee triggers depend on the agreement and applicable law. A candidate may be represented for a specific client and vacancy without giving an agency unlimited rights over their data or career. Separate candidate authorization, contractual introduction rules and ATS submission events into three records.

This guide is an operational control design, not jurisdiction-specific legal advice. Have counsel review your terms, especially duplicate-introduction windows, client affiliates, direct applicants and post-termination provisions.

The five-piece submission receipt

Role and client identifiers, not just free-text names.
Candidate’s explicit scope of representation and the timestamp, with any restrictions.
The exact profile version and permitted recipient.
Delivery event, delivery channel, receipt or API response identifier.
Contract version, introduction window and the person authorized to resolve conflicts.

Store only necessary evidence and enforce access controls. A recruiter’s outbound email proves a message was sent; it does not necessarily prove receipt or entitlement to a fee.

A deterministic duplicate-submission workflow

Before submission, check normalized email and phone with careful human review for false matches. Look for existing client introductions and the agreed window. If there is a possible duplicate, pause and escalate; do not auto-merge identities or automatically disclose another agency’s commercial information. Ask the client to adjudicate under the contract with a minimal evidence packet.

Signal	What it establishes	What it does not establish
Candidate permission	Authorized scope at a time	Client receipt
Email sent	Outbound delivery attempt	Priority under contract
ATS accepted response	System registered submission	Validity of commercial claim
Client acknowledgement	Named recipient received introduction	Exclusive rights beyond agreed terms

What to do when two agencies submit the same person

Freeze external accusations and preserve both event timelines. Confirm the exact vacancy, client entity and candidate identity without sharing more personal information than needed. Compare agreement terms, submission timestamps, acknowledgement and candidate scope. Identify the contractual decision maker and a deadline. Inform the candidate of any delay without making them arbitrate the agencies’ commercial dispute.

Professional shortcut: maintain a dispute packet template with six fields and a redacted event timeline. It reduces ad hoc email forwarding and makes the decision reproducible.

Worked example: first email does not settle the case

Illustrative case: Agency A emailed a CV to a generic inbox on Monday; Agency B submitted a candidate-approved profile through the client portal on Tuesday and received a receipt. The client’s contract requires an acknowledged introduction to the named requisition. Agency A’s earlier timestamp alone does not answer the dispute. The client must apply its agreed terms to both records. Do not generalize this outcome across contracts or countries.

Protect the candidate while resolving the commercial issue

Give the candidate one clear contact, avoid duplicate interview scheduling and do not circulate confidential agency correspondence. If a candidate withdraws authorization or corrects their data, follow the applicable privacy process; a contract claim does not cancel data-protection duties. For cross-border operations, confirm controller/processor roles and retention rules.

FAQ: Is a right-to-represent form always required?

No universal rule applies. Client contracts, applicable privacy law and local recruitment regulation determine the needed authorization and documentation. Treat a form as evidence of a defined scope, not a substitute for a lawful basis or fair contract.

Try the decision check

Submission receipt completeness check

Check whether the audit packet contains the essential elements. A complete receipt does not prove a legal fee entitlement.

Candidate authorization

Exact client and role

Submission receipt

Contract version and window

Choose the documented elements and select Check packet.

The no-accusation escalation script

“We have two recorded introductions for the same requisition. We are preserving both event histories and will apply the client agreement to the verified records. Please pause duplicate scheduling while the authorized owner reviews the submission receipts.”

Keep commercial priority separate from privacy permission

Use two linked but distinct records: a representation scope record (which client, vacancy, permitted information and date) and a commercial introduction record (agreement version, introduction timestamp, receipt and disputed fee window). A candidate’s permission to share data does not, by itself, prove a placement-fee entitlement; likewise a commercial claim does not authorize unrestricted processing. Contract interpretation is jurisdiction-specific.

When duplicate submissions occur, freeze additional circulation, preserve the original records, and give the candidate a neutral choice of contact route. Resolve agency fees with the client under the actual agreement without asking the candidate to adjudicate the dispute. Obtain legal review for contested claims.

Research basis, boundaries and further reading

The linked materials below are the closest topical guidance and research from the accompanying 50-entry reading register. Some sources are broader context rather than direct evidence for a specific operational suggestion. Proposed timings, checklists and examples are editorial methods, not published industry standards.

Additional research to triangulate

These sources add peer-reviewed or regulatory context. Their presence does not validate the original workflow heuristics; those are proposed procedures to test locally. The external pages were located and their available abstracts or descriptions inspected, not all full texts independently audited.