If you are searching for recruitment CRM vacancy closure rules for staffing agencies, the practical answer is simple: close a vacancy when live demand is genuinely gone, pause it when the role may return on a defined review date, and rebrief it when the client still wants to hire but the original conditions no longer support useful sourcing. That distinction matters because many agencies do not have a sourcing problem first. They have a vacancy truth problem.
When old, parked, or half-changed job orders stay open in the same view as real live demand, recruiters split time across work that should already have been closed, paused, or rewritten.
If your team is already working on vacancy readiness, vacancy ageing, or stronger pipeline visibility, closure rules are the control layer that stops dead demand from pretending to be active work.
Why staffing vacancies stay open too long
Open vacancies often survive in the CRM for social rather than operational reasons.
Common patterns look like this:
- the client says "hold for now" and nobody sets a review date
- the shift, pay, transport, or start timing changes, but the original vacancy stays open as if nothing moved
- recruiters keep one old vacancy alive because it still *might* come back
- branch teams are unsure whether a role is lost, delayed, or simply under review
The result is expensive in familiar ways:
- recruiters spend time sourcing into stale demand
- candidates get contacted for roles that are not actually ready
- branch leaders cannot see which vacancies still deserve daily attention
This is why closure should be treated as an operating rule.
Use the CLOSE model
This is an original working model, not an industry standard. It gives staffing teams a practical way to decide what happens when a vacancy is no longer clearly live.
C: Confirm whether live demand still exists
Start with one direct question: if a strong candidate appeared today, could the agency still move them forward against this vacancy without rebuilding the brief first?
If the answer is no, the role should not stay in a live sourcing state.
Examples:
- the client froze the requirement
- the start date moved by several weeks
- the headcount was reduced
- transport or housing assumptions changed
- the client contact is no longer responding and the desk has no agreed next point
This is where many teams confuse hope with live demand.
L: Label the right path
Not every weak vacancy needs the same next status.
Use three distinct outcomes:
- Close when the active opportunity is gone and the desk should stop working it
- Pause when the role may return, but not in the live daily queue
- Rebrief when the client still wants candidates, but the brief changed enough that the old version is no longer usable
If those three paths share one generic "on hold" bucket, the CRM stops telling the truth.
O: Own the decision and the next review
A weak vacancy cannot sit under collective ownership.
One visible person or desk should own:
- the close decision
- the next rebrief conversation
- the review date for paused demand
- the update back to recruiters already working the role
Without one owner, the vacancy keeps drifting between sales, operations, and recruiters.
S: Separate paused work from live work
Paused demand should not sit in the same active queue as same-week live vacancies.
If a role is waiting on budget, shift confirmation, or a fresh start window, it belongs in a different status with:
- a reason
- a named owner
- a review date
- a clear rule for re-entry
That protects recruiter focus and reduces false pipeline volume.
E: End false-active demand quickly
If the desk already knows a job is no longer sourceable, do not let it remain open because closing it feels uncomfortable.
When to close, pause, or rebrief
The easiest way to avoid arguments is to define what each path means operationally.
Close the vacancy when the opportunity is no longer commercially live
Typical signs:
- the client filled the role elsewhere
- the requirement was cancelled
- the branch has no realistic next action left
- the desk is no longer allowed to submit against that brief
Closing does not erase history. It protects the present queue.
Pause the vacancy when the opportunity may return on a known timeline
Useful examples:
- the client asked to review next week
- the site start moved to a later payroll period
Paused should mean "not live now, but worth reviewing later." It should never mean "we do not want to decide."
Rebrief when the client still wants support, but the original version is broken
Rebrief is usually the correct path when:
- shift times changed
- rate expectations moved
- transport assumptions changed
- the language requirement changed
- the client now wants a different experience level
In those cases, leaving the vacancy open under the old brief creates bad submissions and recruiter rework. Rebrief first, then resume sourcing.
What your recruitment CRM should show on every non-live vacancy
Useful fields include:
- vacancy status: live, paused, closed, rebrief required
- closure or pause reason
- owner
- last confirmed client contact date
- next review date if paused
- whether recruiters must stop sourcing immediately
Example:
- A warehouse client in Eindhoven originally asked for four night-shift starters.
- Two days later the client cut the volume to one and moved the start date.
- The correct move is rebrief required, one owner, and live sourcing paused until the revised brief is approved.
It also improves candidate experience. Recruiters stop calling people into work that is no longer ready.
A weekly vacancy closure review that actually helps
Most teams do not need another dashboard. They need a short review rhythm.
Review three groups:
- live vacancies with no recent movement
- paused vacancies past their review date
- rebrief-required vacancies still carrying old recruiter work
This is where task management in a recruitment CRM becomes useful. Closure rules need visible ownership and dates, not only smart status names.
Common mistakes
Keeping a vacancy open because "it might come back"
That is what paused status is for.
Using one generic on-hold status
If cancellation, delay, and rebrief all look the same, the desk cannot prioritize correctly.
Letting recruiters keep working after the brief moved
If the role changed materially, the old sourcing effort is no longer aligned.
Hiding closure reasons in notes
Managers and recruiters should not have to read long histories to understand why a vacancy left the live queue.
Confusing pipeline volume with pipeline health
More open vacancies do not automatically mean better demand.
Short checklist
- define separate statuses for close, pause, and rebrief
- require one owner and one date on every paused or rebrief-required vacancy
- remove non-live roles from daily recruiter priority queues
- stop sourcing immediately when the brief no longer supports useful submissions
- review old paused vacancies every week
- track closure reasons so branch leaders can see repeated demand problems
Good vacancy closure rules protect recruiter time, improve pipeline visibility, and stop candidates being pulled into weak processes. If your agency wants to tighten how demand moves from client brief to recruiter action, review the Recruitment CRM page, compare the pricing page, or use the contact page to map where stale vacancies are still consuming the desk.
FAQ
What is the difference between a paused vacancy and a closed vacancy?
A paused vacancy may return on a defined review path. A closed vacancy is no longer commercially live and should stop taking recruiter attention.
When should a vacancy be marked rebrief required?
When the client still wants help, but key conditions changed enough that the old brief no longer supports good sourcing or candidate submission.
Should recruiters see paused vacancies in the same queue as live work?
Usually no. Paused demand should stay visible for review, but not compete with same-day live vacancies.
Why do closure rules matter for pipeline visibility?
Because a CRM full of weak open roles overstates real demand and hides where recruiter time is being lost.
Can automation help with vacancy closure control?
Yes, if it flags overdue reviews, routes rebrief tasks, and separates live from paused demand. It helps less when the underlying status logic is still vague.