Duplicate Candidate Submission Process

Two staffing suppliers submit what appears to be the same candidate for the same role. One points to an earlier email; the other produces the candidate’s permission to represent them. The hiring manager wants to interview tomorrow. Treating the first timestamp as the whole answer can turn an administrative duplicate into a commercial dispute.

A duplicate candidate submission process establishes whether the records concern the same person and requisition, identifies the applicable submission rules, compares the relevant events, and records an authorized decision. It should also tell the hiring team what may proceed while the commercial question remains open.

This is a recommended operating process for client staffing-program owners, procurement teams and agency account managers. It sits between candidate review and engagement, before onboarding and assignment. It does not establish legal entitlement to a placement fee or replace the parties’ agreement.

Start with the rule, not the fastest email

In this context, “candidate ownership” means attribution of a submission or potential placement fee under particular terms. It does not mean ownership of a person. A useful decision must identify the candidate, requisition, supplier and governing rule together.

Published rules differ. RecruitiFi’s candidate ownership rules connect attribution to candidate-confirmed submissions and a requisition-specific period. Hiring Hub’s marketplace terms, section 11, give consent confirmation and its timing a specific role in duplicate-submission decisions. Neither example establishes a rule for every staffing relationship.

Find the accepted supplier agreement, job-order terms and applicable platform rules. Record their versions and the provisions that determine precedence. If they conflict, the coordinator gathers evidence and refers the interpretation to the authorized commercial or legal owner; the coordinator should not invent a tie-breaker.

The upstream staffing agency agreement checklist helps establish operating terms before the first submission. This process uses those terms to decide a live collision.

Open one case without erasing either submission

The trigger is a duplicate alert, supplier challenge or hiring-manager report. Assign one client-side case owner, normally the staffing-program coordinator. Procurement or the delegated commercial owner approves the attribution decision. Suppliers provide their own evidence; the hiring manager confirms requisition history and next hiring steps.

Preserve both original submission references and receipt events. Check whether the apparent match is genuinely the same person using appropriate existing records and, where needed, a direct clarification. A shared name is not enough to merge profiles. Do not request a national identifier simply to settle an administrative duplicate.

Separate three statuses: the candidate’s hiring stage, the submission’s attribution state, and any disputed fee. A candidate can remain under consideration while attribution is under review, but the hiring team needs an explicit instruction about which actions are authorized. If the agreement or an authorized reviewer requires a pause, record its scope and owner rather than silently cancelling every hiring task.

Use a clause-and-event decision worksheet

Keep one row per question and link to evidence rather than circulating complete candidate files between competing suppliers. The following worksheet is a recommended control, not a universal contractual test.

Use explicit states such as Open, Evidence pending, Commercial review, Decision issued and Closed. “Decision issued” is not the same as both suppliers accepting it. Record a contested outcome as contested, with its next reviewer and due date.

Build a chronology before deciding attribution

Distinguish the events

For each supplier, record when permission was obtained, when the record was submitted, when the receiving system accepted it, and when any required candidate confirmation occurred. Preserve the original timestamp and time zone; add a normalized comparison time without replacing the source. An event absent from the evidence should be marked unknown, not inferred from the order in an inbox.

Then compare the chronology against the actual clause. A rule based on first accepted submission is different from one based on first completed confirmation. Prior contact, an expired window or a different requisition may change the result only when the applicable terms make it relevant.

Worked example: an earlier receipt is not the whole decision

Illustrative scenario: Supplier A’s submission arrives at 09:05, followed by the candidate’s permission at 09:20. Supplier B obtains permission at 09:10 and submits at 09:15. Assume the accepted agreement explicitly requires permission before submission and awards priority to the earliest valid receipt.

Under that constructed rule, A’s earlier email is not enough to establish priority: the coordinator must assess its validity. B has an earlier qualifying sequence on the stated evidence. The approver records the clause and both chronologies before issuing a decision. Under a different agreement, the outcome could differ. The example is not a finding about either supplier’s legal fee rights.

Handle exceptions without rewriting history

Missing evidence: give the supplying party a specific request and a policy-defined response time. If evidence remains missing, escalate or decide under the agreement’s documented procedure. Do not manufacture a consent date or convert silence into acceptance unless the actual terms support that consequence.

Prior direct contact: ask the hiring team for the relevant dated interaction and apply the agreement’s definition. A profile sitting in a talent pool may not satisfy a rule requiring active discussion. RecruitiFi, for example, distinguishes responsive candidate interest from one-way employer outreach; that distinction belongs to its own rules.

Different requisitions: open a role-specific comparison. juucy’s duplicate-submission guidance distinguishes same-vacancy and different-vacancy cases. This illustrates why a company-wide “first supplier forever” assumption is unsafe as an operating shortcut.

System record changes: preserve source links before any authorized administrative correction. Oracle’s contingent requisition ownership documentation warns that changing an agent can affect other requisitions. Verify the behavior of your actual system; do not assume a global profile reassignment fixes one disputed submission.

Unresolved commercial disagreement: escalate with the evidence packet and a clear hiring-continuity instruction. Do not invent a fee split, promise a refund or withhold an unrelated payment as an informal settlement. Keep any authorized commercial remedy separate from the candidate’s profile.

Close with a decision that another reviewer can reproduce

The decision record should state the candidate reference, requisition, supplier claims, governing terms, relevant chronology, accepted and missing evidence, rationale, approver and date. Send each party the appropriate outcome without disclosing the other supplier’s unnecessary confidential material. Tell the hiring manager which supplier channel and next hiring step are authorized.

Keep disputed responses, escalation references and residual commercial tasks attached to the case. Close only after the required notifications and follow-ups have a recorded disposition. Track repeated causes—missing permission, wrong requisition, invalid channel or unclear terms—to improve intake, not to turn an allegation into a worker performance label.

The broader staffing vendor management guide covers ongoing supplier governance. Feed recurring submission failures into that review while keeping each individual attribution decision traceable.

Where Workhint fits

Workhint’s Workflow Engine describes configurable request steps, role-based approvals and requirements for details, files or notes before work progresses. Those building blocks are relevant to gathering a submission evidence packet and routing an attribution decision to the right owner.

The Staffing Managers solution describes organizing workers with profiles, documents and approval status. That supports the surrounding staffing context. The chronology, agreement interpretation and exception rules in this article are an operating design to validate, not a claim that Workhint automatically detects duplicate people, adjudicates fees or interprets supplier contracts.

A configuration review should start with one requisition and two preserved submission references. Define the coordinator, evidence providers and approver; specify what is required before review; and test a missing-consent case and a cross-role claim. Confirm how the proposed setup preserves the original evidence and limits access before relying on it.

FAQ

Does the first supplier to send a CV always win?

No universal rule establishes that result. The applicable agreement or platform rules may depend on a valid submission, candidate confirmation, prior contact, role scope or other conditions. Record the controlling provision before comparing timestamps.

Should duplicate candidate profiles be merged immediately?

No. First establish that they represent the same person, preserve both submission histories and verify the effect of a merge in the actual system. An attribution dispute is not permission to overwrite evidence or alter unrelated roles.

Can the candidate continue interviewing during the dispute?

The authorized hiring and commercial owners should decide under the applicable terms and circumstances. Record any permitted next step or pause explicitly. Do not let an administrative status silently make that decision.

What if neither agreement nor platform rules settle the issue?

Escalate to the authorized commercial or legal reviewer with the chronology and unresolved questions. Keep the case open with a named owner and next action; do not create a new submission or requisition to bypass the dispute.