When a candidate becomes relevant to another branch, do not simply copy the record and hope recruiters compare notes. A good cross-branch candidate transfer keeps one reliable history, makes the receiving owner explicit, and tells the candidate what will happen next. That protects a useful introduction while keeping the originating recruiter’s context available.
For a staffing agency, the practical answer is a transfer workflow inside the recruitment CRM, not an inbox handover or a private spreadsheet. The workflow should record why the move is happening, what has already been promised, who can contact the candidate next, and whether the first branch still has an active role.
Why cross-branch transfers break down
A candidate may live near one office, be available for another region, or be better suited to a specialist desk. The commercial opportunity is real, but informal transfers cause avoidable friction:
- two recruiters approach the same person with overlapping messages;
- the receiving branch sees a name but not the work preferences, availability or prior conversation;
- a candidate thinks their original contact has disappeared;
- a source, referral or client relationship is lost from the record;
- a manager cannot see whether the handover actually led to action.
This is not mainly a data-entry problem. It is an ownership and expectation problem. Your CRM should make the current owner, next action and transfer status visible alongside the candidate’s normal history. That is more dependable than rebuilding the story through calls and forwarded email.
Choose transfer, shared access, or a referral
Before changing ownership, decide what kind of collaboration is needed. A full transfer makes sense when one branch will run the candidate relationship from now on. Shared access works when the original recruiter remains involved, such as a candidate open to assignments in two neighbouring areas. A referral is useful when the originating branch only introduces the candidate and the receiving team takes full responsibility.
Do not treat those states as interchangeable. Give them clear names in the CRM. A recruiter looking at a shared candidate should not have to infer from notes whether they may call. This is the same discipline that helps agencies prevent duplicate follow-up: a visible rule is better than a polite assumption.
The minimum transfer record
Use a short transfer form or structured fields rather than a free-text note. It should capture:
1. the receiving branch or specialist desk; 2. the reason for the move, for example travel area, skill niche or an active request; 3. the named sending and receiving owners; 4. the candidate’s current availability and preferred contact method; 5. promises already made, including any agreed callback; 6. open applications, interviews, documents or client introductions; 7. the exact next action and its due date.
The purpose is not to create a long internal report. It is to ensure the next recruiter can act without asking the candidate to repeat their story. Keep supporting evidence in the existing timeline and link related vacancy or application records; do not duplicate the candidate just to make the transfer feel tidy.
A five-step cross-branch candidate transfer workflow
1. Check the live record first
Search by name, phone number and email before opening a new record in the receiving branch. Review the recent contact history, open vacancies, consent/status fields and tasks. If data looks uncertain, flag it for review rather than overwriting it during the handover. A controlled record is more useful than a fast but conflicting update.
2. Agree the receiving owner before announcing anything
“The Rotterdam team” is not an owner. Name the person or queue that must make the next decision. If nobody can accept the transfer yet, keep the original owner and place the record in a visible pending-transfer state. This prevents a candidate from being told to expect a call that no one has accepted.
3. Set the candidate expectation in plain language
Tell the candidate why another colleague may contact them and what will not change. For example: a specialist desk will discuss suitable assignments, while the original recruiter remains the point of contact until the handover is accepted. Record the contact message and the candidate’s preference. The agency is coordinating internally; the candidate should not have to chase the right branch.
4. Create one receiving action
The receiving owner needs a concrete first task: review suitability for a named vacancy, confirm a travel radius, or make an introduction call. Give it a reasonable due date and attach the relevant record. Avoid creating several generic “follow up” tasks. Clear task design is what turns a transfer into accountable work, as in a recruitment CRM task workflow.
5. Close or keep the original role deliberately
Once the receiving branch accepts, mark the transfer complete and clarify whether the original recruiter retains read access, a referral attribution, or an active application. If the receiving branch declines, return the record to the original owner with a reason. A rejected transfer is useful information, not a silent dead end.
Common mistakes to avoid
The most damaging shortcut is creating a second candidate profile for each branch. It fragments conversations and makes consent, availability and application status harder to trust. Another common error is moving ownership without a handover message: the new recruiter sees a record but not the human commitment behind it.
Also avoid making a branch code the sole routing rule. A candidate may be geographically close to one office but relevant to another desk because of language, work pattern or specialist experience. Let a human choose the route, then record the reason so it is auditable.
Practical checklist
- [ ] Search for the existing record before creating anything.
- [ ] Decide whether this is a transfer, shared access or referral.
- [ ] Name both sending and receiving owners.
- [ ] Record current availability, contact preference and prior promises.
- [ ] Link open vacancies, applications and follow-up tasks.
- [ ] Tell the candidate what happens next.
- [ ] Confirm acceptance or return the record with a reason.
Where AI JOB AGENCY fits
AI JOB AGENCY can support the operational layer around this workflow: structured intake, visible recruiter actions and a CRM timeline that gives the next person context. Automation should surface the handover and prompt the next action; it should not quietly decide who owns a candidate or change their status without review. If your branches are currently relying on forwarded messages, see the recruitment CRM approach or speak with the team about a workflow review.
FAQ
Should each branch have its own copy of a candidate?
Usually no. Use one core record with branch access, ownership and linked opportunities unless there is a clearly defined operational reason to separate records.
Who should contact the candidate after a transfer?
The named receiving owner, once they have accepted the transfer. Until then, the original recruiter should remain accountable for the next expectation.
What if two branches want the same candidate?
Keep the candidate’s choices and active opportunities visible, then agree a clear contact rule. Do not let two teams run competing outreach.
Does a transfer mean the original recruiter loses all context?
No. The history should remain visible. What changes is the active owner and the next responsibility.
How can we measure whether transfers work?
Review accepted versus returned transfers, time to the first receiving action, and reasons records are sent back. Use the review to improve routing rules, not to punish individual recruiters.