A strong project controller applies for one vacancy on Monday. On Tuesday a colleague adds her to a second vacancy for another client, and on Wednesday a third recruiter calls her about an interim role. By Thursday she has received three different stories, one interview invitation and one rejection on the same day, and she asks which of them is actually true. Each recruiter did reasonable work, but nobody saw the full picture. This article explains how to manage one candidate in several vacancies at once in your Applicant Tracking System: what goes wrong without a shared view, how to structure records and statuses, who leads the contact, how to set priorities with the candidate, how the approach differs per segment and how to check with your own data whether parallel processes run smoothly.
Parallel processes occur in every segment. Recruitment agencies present good candidates to several clients when the profile fits. Staffing desks consider the same flexible worker for several assignments in the same week. Secondment firms look at several follow-on assignments for a consultant whose current assignment is ending. Executive search firms sometimes consider one senior candidate for more than one mandate. In-house recruitment teams see applicants who apply for several internal roles at once. In every case the question is the same: does everyone who works with this candidate see all running processes, or does each recruiter only see their own vacancy?
What goes wrong without a shared view
- Several recruiters contact the same candidate on the same day with different messages
- A rejection for one vacancy is read as a rejection for all, and the candidate withdraws
- Two clients receive the same candidate without anyone deciding which process has priority
- An offer arrives for one vacancy while another process is still at interview stage, and nobody prepared for that moment
- Status reports show the candidate twice as available, or not at all
The result is a confused candidate, unnecessary friction with clients and processes that stall because recruiters wait for each other without knowing it.
One record, one status per vacancy
The basis is simple: one candidate record and a separate application per vacancy. Keep it practical:
- One candidate record — contact details, documents and history live in one place; merge duplicates instead of creating a second record
- A separate pipeline status per vacancy — the candidate can be at interview stage for one vacancy and newly added for another
- A visible overview of all running processes — on the candidate record, every recruiter sees each vacancy, its stage and its owner
- Separate outcomes — a rejection or withdrawal applies to one vacancy only, unless the candidate says otherwise
- Shared notes in the right place — notes about the person belong on the record, notes about a specific vacancy belong on that application
This way the history stays complete without one process overwriting another.
Who leads the contact
When several vacancies run at once, agree who speaks with the candidate. Usually one recruiter acts as lead contact and coordinates with the owners of the other vacancies. The lead contact knows all running processes, tells the candidate which steps are planned and makes sure messages do not contradict each other. Record the lead contact on the candidate record, so a colleague who takes over can see it immediately, as in any handover. Other recruiters can still contact the candidate about their own vacancy, but they check the overview first and record what they agreed.
Priorities and transparency with the candidate
Ask the candidate which vacancies they want to pursue and in what order, and record that per application. Ask for consent before every submission, so the candidate always knows which clients have their profile and you avoid double submissions. Discuss in advance what happens when an offer arrives while other processes are still running: the candidate decides, but nobody should be surprised. When an offer is accepted, close or pause the other applications promptly with a recorded reason, and inform the clients and hiring managers involved.
Differences per segment
Agencies use the overview mainly to avoid presenting one candidate to competing clients without a deliberate choice and to keep one consistent voice towards the candidate. Staffing desks combine parallel assignments with confirmed availability, so a worker is not booked twice for the same shift. Secondment firms run follow-on options for a consultant side by side and decide together with the consultant which option comes first, linked to the end date of the current assignment. Executive search firms record carefully which mandates a candidate is considered for, so confidentiality and agreements with clients are respected. In-house teams decide which hiring manager leads when an applicant fits several internal roles, so the applicant gets one clear process instead of several separate ones.
Let the system help
Much of the coordination repeats and suits automation: showing all running applications on the candidate record, warning a recruiter who adds a candidate already active elsewhere, notifying the lead contact when another process moves to a new stage, prompting a review of the other applications when an offer is accepted and flagging processes that stay in a stage too long. An artificial intelligence helper can suggest other open vacancies that match a candidate or summarise the status of all running processes before a call. The recruiter checks the suggestion and decides what happens next; artificial intelligence does not replace recruiters and does not move candidates between vacancies on its own.
Common mistakes to avoid
- A new record per vacancy — history and contact agreements spread over several records
- One status for everything — a rejection for one vacancy hides progress in another
- No lead contact — every recruiter tells their own story
- Submitting without asking — the candidate discovers via a client that their profile was shared
- Leaving other processes open after acceptance — clients keep waiting for a candidate who has already started elsewhere
Questions teams ask
- How many vacancies at once is reasonable? — That depends on the candidate and the roles; ask the candidate and record their choice instead of using a fixed number
- Who is the lead contact? — Usually the recruiter with the first or most advanced process, unless the team agrees otherwise
- Should clients know about other processes? — Share only what the candidate agreed to; you can say a candidate is in other processes without naming them
- What if two clients want the same candidate? — The candidate decides; your role is to give a clear overview and keep both clients informed in time
- Does this also apply to talent pool candidates? — Yes, as soon as a candidate from your talent pool is added to a vacancy, the same rules apply
Check it with your own data
Count from your own records, per team and per segment: how many active candidates are in more than one vacancy at the same time, how many of them have a recorded lead contact, how often a candidate withdrew from all processes after a rejection or offer in one of them, how long other applications stayed open after a candidate accepted an offer and how often the same candidate was added to a vacancy by different recruiters without knowing it. Discuss these figures in your weekly pipeline review and report the number of candidates behind each figure. Do not compare with industry averages; your own trend is the number that matters.
A practical start
- Agree that every candidate has one record with a separate application per vacancy
- Show all running processes on the candidate record
- Record a lead contact for every candidate in more than one vacancy
- Ask for and record the candidate’s priorities and consent per vacancy
- Review parallel processes and open applications after acceptance in your weekly pipeline review
One candidate, one clear story
A candidate who fits several vacancies is an opportunity, as long as everyone sees the same picture. Keep one record, a status per vacancy and a clear lead contact, agree priorities with the candidate, close other processes promptly after acceptance and check your own figures. Explore the product or book a demo — we show how candidates, vacancies and the pipeline work together in BoldATS for your segment.