Split-Fee Recruitment: A Practical Agency Handoff Guide

One agency knows the client. Another knows the candidate. The introduction looks easy until both consultants send different role details, the candidate receives two follow-ups and nobody can explain what happens if the client already has the CV. A split-fee agreement needs a working handoff, not just a percentage.

What should a split-fee recruitment handoff include?

Agree the permitted assignment, each agency’s responsibilities, candidate communication, introduction evidence, duplicate handling and the contractual payment trigger before transmitting a profile. Confirm who speaks to the client and candidate, and what information each party may receive or reuse.

Keep the commercial agreement and the data-sharing assessment connected but separate. A promise to share a fee does not, by itself, justify sharing someone’s personal data or establish that a candidate authorised a particular introduction. Both parts need an accountable owner.

This guide addresses collaboration on direct-hire recruitment. It does not set a standard fee split, interpret a particular contract or cover all temporary-worker supply-chain duties. Use qualified advice for the actual engagement and jurisdictions involved.

Name the assignment and the parties precisely

The collaboration should apply to a defined search, not an unrestricted exchange of candidate records.

Identify the client entity, role reference, location and current brief version. Confirm that the client-facing agency is allowed to involve a partner. An exclusive search agreement or client procurement arrangement might impose conditions that cannot be bypassed by calling the partner a referrer.

Write down which legal entity contracts with which party. A trading name, personal email signature or membership in a network is not enough to resolve that question. Give each agency an operational contact and a separate escalation contact for contractual or privacy matters.

GOV.UK distinguishes an employment agency making introductions from an employment business supplying workers. That distinction matters when defining the collaboration. Do not copy a direct-placement checklist into temporary staffing and assume payroll, worker-supply and other duties have been addressed.

Agree money terms without making them the whole workflow

Document the commercial trigger and exceptions before anyone relies on an informal promise.

The parties should settle the fee basis, invoicing event, payment conditions, currency, taxes where relevant and handling of a cancellation or replacement. This article supplies questions to resolve, not terms that are legally right for every agency. There is no universal split that makes an arrangement fair.

Address situations that create ambiguity: a different role at the same client, a later hire, a candidate already known to the client, a delayed start or a disputed introduction. Avoid vague language such as “our candidate” when the real issue is which agreed activity creates a contractual entitlement.

Make operational instructions consistent with the terms. If payment depends on a confirmed start, somebody must obtain reliable start confirmation. If a guarantee affects both agencies, someone must notify the partner of a relevant event. An agreement nobody can operate becomes a future dispute file.

Give the candidate one clear account of the process

Explain who is involved and assign a single lead for routine candidate communication.

Tell the candidate which agency holds the client relationship and which consultant will coordinate next steps. Explain the role and proposed recipient before sharing the profile. Do not hide the collaboration behind a vague “our partner network” explanation when a specific organisation will receive personal information.

Confirm the candidate’s wishes and the appropriate information-sharing basis for the arrangement. Keep a dated record of what was explained and agreed. Permission to discuss one role does not mean the candidate wants both agencies to circulate their profile to unrelated clients.

Agree how changes reach everyone who needs them. If the candidate withdraws, corrects an employment date or changes availability, the lead should notify the partner promptly and seek acknowledgement. The candidate should not have to manage the agencies’ internal coordination problem.

• One named lead for routine candidate updates.
• A clear description of the client, role and partner agency.
• The latest approved profile and known factual corrections.
• A practical route for withdrawal, questions and changes.

Check duplicate representation before a live introduction

Resolve uncertain prior contact without circulating more data than necessary.

Ask the candidate about relevant existing applications or introductions. Then use an agreed, proportionate check with the partner and client-facing owner. A full CV broadcast to test whether anyone recognises the person defeats the purpose of a controlled handoff.

Treat uncertainty as uncertainty. A name in a historic database does not automatically establish current representation, consent to this role or a fee entitlement. Equally, the sourcing agency should not ignore evidence that another active process already exists. Apply the actual contract and escalate disputed cases.

Keep the operational status neutral while the issue is unresolved. Avoid accusing the candidate of dishonesty because they cannot remember every agency conversation. Pause the introduction, clarify dates and role references, then tell the candidate what will happen next.

Send a small, usable introduction pack

The receiving consultant needs enough context to represent the candidate accurately, not the entire relationship history.

A useful pack contains the role reference, candidate-approved profile, relevant evidence of fit, unresolved questions, current process status and next action. Distinguish facts provided by the candidate from recruiter interpretation. Mark anything that still needs confirmation rather than polishing it into certainty.

Keep commercial terms away from general candidate notes. Restrict unnecessary personal details and do not forward unrelated client conversations or sensitive interview material. The ICO’s data-sharing guidance recommends clear purposes, roles and handling rules; an agreement is not automatic permission for every disclosure.

Use an agreed secure channel and obtain acknowledgement from the named recipient. Record what was sent and when. The receiving agency should check the role version and follow-up responsibility before contacting the candidate, especially if several searches are running between the same firms.

Illustrative case: a specialist researcher and a client-owning boutique

Walk through the difficult branch before the first real candidate is involved.

In a fictional collaboration, a UK search boutique holds a finance-leadership mandate and a sector specialist identifies a potential candidate. The specialist confirms interest in the named role and explains the receiving agency. The boutique checks the introduction against the client’s existing process before accepting the profile.

The client then says it received the same person’s CV for another vacancy months earlier. The agencies pause any fee assumption and inspect the actual terms and dates. They do not ask the candidate to choose a “winner” or submit the same CV again to create a newer timestamp.

Once the position is clarified, one consultant owns updates and the other supplies agreed sector context. A later salary change goes through that same lead. The example illustrates coordination, not a conclusion about who is entitled to payment under a real contract.

Close the loop after an outcome or a disagreement

A handoff remains active until each agency knows what happened and what it must do next.

For a hire, confirm the outcome through the agreed channel and reconcile the records needed for invoicing under the engagement. Do not publish the placement or use it as a case study without the relevant permissions. Commercial success does not erase confidentiality responsibilities.

For a rejection, withdrawal or cancelled role, tell the partner what can be shared and who will communicate with the candidate. Apply the agreed retention and reuse rules. A collaboration for one vacancy should not quietly turn into a shared talent database with no clear purpose.

For a dispute, preserve the relevant evidence, stop contradictory candidate contact and escalate to the named decision-makers. Keep allegations out of routine candidate notes. Review the handoff after resolution so the next collaboration does not depend on reconstructing scattered messages.

A practical split-fee handoff checklist

Use this as an operational checklist alongside properly reviewed engagement and data-sharing arrangements.

Where a checklist is not enough

Fee rights, exclusivity, replacement obligations and candidate representation depend on the actual contracts and facts. This is not a model contract and does not establish an industry-standard entitlement.

Cross-border sharing, temporary staffing and regulated intermediary arrangements need their own assessment. The ICO notes that its data-sharing guidance is under review following UK legislative changes; check current guidance and obtain advice for the real arrangement.

Questions about split-fee recruitment

Resolve these practical issues before the first introduction, not at invoicing time.

What is the normal split-fee percentage?

There is no percentage this guide can prescribe. Agree terms that reflect the work, risk and responsibilities of the actual engagement, then document how the agreed basis operates.

Does the agency that found the candidate always own the fee?

Finding a person does not settle contractual entitlement. Relevant terms, prior introductions, client arrangements and the facts need review. Avoid treating a database timestamp as a universal ownership rule.

Can both agencies contact the candidate?

They can agree a coordinated process, but routine updates should have one clear lead. The candidate should understand the roles and should not receive contradictory instructions or duplicate requests.

Does Yena automatically calculate and settle split fees?

This article makes no such product claim. Evaluate Yena for organising recruiting context; keep fee calculation, contractual interpretation and payment handling with the responsible people and appropriate systems.

Primary sources behind the boundaries

These sources clarify agency models, responsible information sharing and professional candidate treatment. The checklist itself is an editorial workflow, not a legal template.

• GOV.UK: employment agencies and employment businesses are different arrangements
• ICO: data-sharing agreements, roles and limits; guidance currently under review
• AESC: candidate confidentiality and professional assessment principles

Build a reliable agency collaboration process

Review recruitment-agency contracts · Keep reference-check permission specific · Control shortlist versions · Explore a recruiting CRM for agencies