If your staffing agency keeps seeing the same role appear twice in the CRM, the practical fix is not a monthly clean-up. It is a live rule for deciding whether an incoming request is a true new vacancy, a changed version of an existing one, or a duplicate that should point back to one master record. That is how you stop double sourcing, mixed candidate submissions, and confused ownership across branches.
Duplicate vacancies usually start with good intentions. A client phones one branch, emails another contact, or asks for "just a few more people" without making it clear whether the original order changed. The team reacts fast, but two records are now live for one commercial reality. If you already work on job order intake, multi-branch CRM structure, or vacancy change management, duplicate vacancy control is what keeps those systems from splitting recruiter effort.
Why duplicate vacancies appear so often
This problem is not just bad admin. It is a natural side effect of fast-moving staffing work.
Typical causes include:
- one client request arrives by email, phone, and WhatsApp through different people
- a branch copies an old vacancy because the client wants a similar shift next week
- the volume changes, so somebody opens a "new" record instead of updating the original
- one account manager treats the role as a new order while the desk sees it as a continuation
- the same site requests workers for day and evening shifts, but the shared details are never reconciled properly
Once duplicates exist, the damage spreads quickly:
- recruiters call the same type of candidate from two records
- one record gets profiles while the other holds the real client update
- pipeline counts become inflated
- account and recruitment teams stop trusting the vacancy view
Use the MASTER model
This is a practical operating framework, not an industry standard. It helps agencies decide where one vacancy ends and a real new one begins.
M: Match the commercial basics first
Before opening a fresh vacancy, compare the incoming request with active records using a few operational fields:
- client or site
- role family
- shift pattern
- location
- start window
- approval path
If most of those are the same, the default assumption should be "check before creating," not "create now and clean later."
A: Appoint one master record
When two records refer to the same live demand, pick one master vacancy. That record should hold:
- current client truth
- owner
- latest status
- candidate submissions tied to the role
The other record should not continue as a parallel live vacancy. It should be merged, linked, or closed with a visible reference to the master record.
S: Separate change from new demand
Not every update creates a new role.
Examples of change rather than new demand:
- the client increases headcount on the same shift
- start timing moves by two days
- one must-have changes, but the site and role stay the same
- approval now goes through a different contact
Examples that may justify a new vacancy:
- a different site with different travel reality
- a separate shift pattern that needs different sourcing logic
- a different role family or pay structure
- a new hiring window that should be managed independently
That distinction matters because vacancy prioritization only works when the underlying records reflect real choices.
T: Tie candidate activity back to one truth
Duplicate vacancy control fails when candidate actions keep spreading across both records.
The team should be able to see:
- which vacancy is the master record
- where existing submissions belong now
- which recruiter owns fresh outreach
- which client update invalidated the duplicate
Otherwise the CRM may show control while the desk still works in parallel confusion.
E: Escalate ownership conflicts early
If one branch believes it owns the role and another branch already opened a live record, do not let both keep moving "just in case." Escalate quickly and decide:
- who owns the client relationship for this vacancy
- whether the demand is shared or duplicated
- whether the current record should be updated instead of copied
This is especially important in Dutch and wider European staffing where language desks, regional branches, and site-specific rules often overlap.
R: Review duplicate patterns weekly
One duplicate is a one-off. Repeated duplicates usually expose a workflow design problem.
Check whether duplicates come from:
- weak intake discipline
- copied templates used too freely
- unclear branch ownership
- change requests being treated as brand-new orders
That is where the CRM should support operations instead of quietly recording the mess.
A practical duplicate check before opening a new vacancy
Below is an example check, not a fixed industry template.
Ask:
- Is this the same client and site as an already open role?
- Is the work type genuinely different or only slightly updated?
- Does the client want new demand or a revised version of the current order?
- Would candidates sourced for the old record still be relevant here?
- Does the approval path stay tied to the same decision-maker?
Example:
- A logistics client near Rotterdam asked on Monday for six day-shift pickers.
- On Wednesday another contact says they now need "three more" and also mentions two evening-shift workers.
- The extra three day-shift places may belong under the same master vacancy.
- The evening-shift demand may need a separate record if sourcing, fit, and timing are different enough.
The point is not to force everything into one record. The point is to avoid opening new records before the team decides whether the commercial reality is truly separate.
Common mistakes
Keeping both records open "until we know more"
That usually guarantees that recruiters work both in the meantime.
Treating every volume change as a new vacancy
More headcount is not automatically a separate order.
Linking duplicates only in notes
If the relationship is invisible in the daily queue, the team will still act on the wrong record.
Letting branch politics outrun vacancy truth
Two owners cannot run one live role cleanly for long.
Short practical checklist
- compare client, site, role, shift, start window, and approval path before opening a new record
- assign one master vacancy when two records reflect the same demand
- separate true new demand from a changed version of the current order
- move candidate actions and client truth back to one visible record
- escalate branch ownership conflicts quickly
- review weekly where duplicate vacancies keep coming from
If your team wants less double sourcing, cleaner vacancy ownership, and more reliable CRM visibility, review the Recruitment CRM page, compare the pricing page, or use the contact page to map where duplicate vacancy records are being created today.
FAQ
What counts as a duplicate vacancy in staffing?
A duplicate vacancy is a second record that reflects the same live client demand closely enough that running both creates confusion, double work, or mixed ownership.
Should every shift difference create a new vacancy?
Not always. A different shift may justify a new record if sourcing logic, fit, or timing are materially different. Small updates often belong on the existing master vacancy.
Who should decide the master record?
Usually the person or team with clear vacancy ownership, often the account manager, branch lead, or designated recruitment owner for that client demand.
Can duplicate vacancies hurt candidate experience?
Yes. Recruiters may repeat outreach, promise different details, or submit candidates against the wrong version of the role.
Is this mainly a multi-branch problem?
Multi-branch teams feel it more often, but even a small staffing desk can create duplicates when fast updates arrive through different channels.