A recruitment agency is three weeks into a search for a financial controller when the client calls: the budget is under review, please pause for now. The recruiter sets the vacancy to on hold and moves on to other work. Two candidates at interview stage hear nothing for a month, one of them accepts another job, the job advert stays live on two job boards, and the vacancy keeps counting days in the time-to-fill report. Six weeks later the client calls back, surprised that the shortlist has gone cold. Nobody did anything wrong; the pause simply had no reason, no owner and no date to look at it again. This article explains why every vacancy put on hold in your Applicant Tracking System needs a recorded reason and a review date: why paused vacancies drift, what on hold means and what it does not, what to record, how to agree the pause, what to do with the candidates in the pipeline, how to keep the pause out of your reports, when to resume or close, and how to check with your own data how your paused vacancies really behave.
A recorded pause matters for every segment. Recruitment agencies see searches paused when a client reorganises or freezes its budget. Staffing agencies see volume requests paused when production planning changes or a contract with the client’s own customer is delayed. Secondment firms wait for a project start that keeps slipping. In-house recruitment teams put vacancies on hold during a hiring freeze, a reorganisation or while a budget holder reconsiders the role. Executive search firms see mandates paused when the board changes direction or an internal candidate emerges. In every case the question is the same: why is this vacancy paused, who decided it, and when do we look at it again?
Why paused vacancies drift
- The status changes to on hold, but the reason stays in a phone call or an email
- Nobody agrees a date to ask the client or hiring manager whether the vacancy is still needed
- Candidates in the pipeline are not told, or are told different things by different recruiters
- Job adverts keep running and new applications keep arriving for a role that is not being filled
- The on hold period counts as working time in time-to-fill, or the vacancy is quietly forgotten and never closed
None of this is careless work. A pause feels temporary, so it gets less attention than an open or a closed vacancy, while it is exactly the status in which vacancies and candidates are lost.
What on hold is, and what it is not
On hold is a temporary status for a vacancy that is still expected to be filled, but on which the client or hiring manager has asked you to stop work for now. It has a start date, a reason, a person who asked for it and a date on which you review it.
It is not a parking place for vacancies nobody wants to close: if the client has cancelled the role, filled it elsewhere or stopped the search for good, record the close reason and close the vacancy. It is also not a pause on your side because of workload; that is a question of priority for the vacancy owner, not a status the client should see. And a single candidate waiting for a client decision is not a vacancy on hold; that belongs in the response deadline of the submission.
What to record
Keep the structure simple enough that the whole team fills it in the same way:
- Date on hold — the day work stopped, recorded when the status changes, not weeks afterwards
- Reason — one from a short standard list, such as budget under review, reorganisation, change in the role, project start delayed, internal candidate being considered or client unavailable, with a short note
- Requested by — the name of the client contact, hiring manager or budget holder who asked for the pause
- Review date — the date on which the owner contacts that person to decide: resume, extend the pause with a new date, or close
- Owner — the single owner of the vacancy, who stays responsible during the pause
- Pipeline decision — what was agreed for candidates already in the process, and when they were informed
- History — every pause and every resume kept as a separate period, so a vacancy that was paused three times shows three periods
Agree the pause with the client or hiring manager
When a client asks you to pause, ask three questions in the same conversation: why, until when, and what should happen with the candidates who are already in the process. “Until further notice” is not a date; propose a review date yourself, usually within a few weeks, and record it. For agencies, check the agreed client terms: whether anything was agreed for paused or cancelled assignments, and whether candidates you introduced stay linked to your agency during the pause. For in-house teams, link the pause to the recorded approval: a vacancy paused because the budget is being reconsidered may need a new approval before work resumes. When the role itself changes during the pause, update the structured brief before you resume, not afterwards.
What to do with candidates in the pipeline
Candidates are the first to feel a pause. Tell every candidate in an active stage that the vacancy is on hold, what you know about the reason as far as you may share it, and when you expect to know more. Record that you informed them and give each one a next-action date that matches the review date, so the pause does not show up as candidates stuck in a stage without contact. Candidates who decide not to wait get a withdrawal reason, so you can later see how many candidates a pause cost.
Strong candidates who are still available can be proposed for other vacancies in the meantime and stay in your talent pool; for staffing desks, recheck confirmed availability before work resumes. Pause or end the job adverts for the vacancy and record that, so no new applicants apply for a role that is not being filled. For a vacancy with several positions, record whether the pause applies to all open positions or only to part of the recorded headcount.
Keep the pause out of your time-to-fill
A vacancy that waited six weeks for a budget decision did not take six weeks longer to fill because of your recruiters. Record every on hold period with a start and an end date, so time-to-fill can be reported both including and excluding the pause, and always say which of the two you show. Move the target fill date by the length of the pause, or set a new one when work resumes, and keep the original date in the history. Report the number of paused vacancies and the total time on hold separately; that figure says something about your clients and your planning, not about the speed of your team.
Resume or close on the review date
On the review date, the owner contacts the person who asked for the pause and records one of three outcomes: resume, with a new target fill date and the job adverts back online; extend, with a new review date and a short note on why; or close, with a documented close reason. When you resume, contact the candidates who were waiting before you source new ones, and check whether their situation, notice period or salary expectation has changed. When a vacancy has been extended several times, discuss with the client whether it is still a real vacancy; a pause that is extended again and again is often a cancellation nobody has said out loud.
Let the system help
Several steps around a pause repeat every time and suit automation: requiring a reason, a requester and a review date when the status changes to on hold, a reminder to the owner on the review date, a task to inform the candidates in active stages, a warning when job adverts are still live for a paused vacancy, and stopping the time-to-fill clock during the on hold period. An artificial intelligence helper can draft the message to waiting candidates from the recorded reason and review date, or summarise which paused vacancies are past their review date. The recruiter still checks the text, decides and sends it; artificial intelligence does not replace recruiters and does not resume or close a vacancy on its own.
Common mistakes to avoid
- On hold without a date — without a review date, a pause becomes permanent without anyone deciding it
- Silence towards candidates — candidates who hear nothing assume the worst and accept other offers
- Adverts that keep running — new applicants apply for a role that is not being filled and wait in vain for an answer
- Counting the pause as working time — your time-to-fill looks worse for a reason your team did not cause
- Using on hold instead of closed — cancelled vacancies stay in your overviews and distort every count of open vacancies
Questions teams ask
- How long may a vacancy stay on hold? — Agree a maximum with your team, for example two review dates in a row, after which the owner asks the client explicitly whether the vacancy should be closed
- Do candidates stay in their stage during the pause? — Yes, as long as they are informed and want to wait; record the contact and a next-action date, and record a withdrawal reason for those who stop
- What if only one candidate’s process is paused, not the vacancy? — Then the vacancy stays open; record the delay on that candidate with a next-action date
- Who may put a vacancy on hold? — The vacancy owner changes the status, always with the name of the client contact or hiring manager who asked for it
Check it with your own data
Count from your own records, per client and per segment: how many vacancies were put on hold, how many of them have no recorded reason or review date, which reasons occur most often, the average and the longest time on hold, how many paused vacancies were resumed and how many were eventually closed, and how many candidates withdrew during a pause. Look at those numbers alongside your time-to-fill, and review paused vacancies that are past their review date in your weekly pipeline review. Report the number of vacancies behind each figure. Do not compare with industry averages; how your own paused vacancies end is the number that matters.
A practical start
- Agree a short list of standard reasons for putting a vacancy on hold
- Require a reason, a requester and a review date whenever a vacancy is put on hold
- Inform every candidate in an active stage on the same day and record it
- Pause the job adverts and record every on hold period with a start and an end date
- Review paused vacancies once a week, starting with those past their review date
A pause is a decision, not a drawer
A vacancy on hold is still a promise to a client or hiring manager and to the candidates who are waiting. Record why it is paused and who asked for it, set a date to review it, tell the candidates, pause the adverts, keep the pause out of your time-to-fill and decide on the review date whether to resume, extend or close. Explore the product or book a demo — we show how vacancy statuses, pauses and review dates are set up in BoldATS for your segment.