Vacancy is usually the largest cost in a hire, larger than any agency fee. It is also the most controllable, because most of the delay is internal rather than in the market.
For a related Monitask resource on workforce analytics, see the website.
Here is where the weeks go, and what removes them.
Measure it properly first
Time to fill: requisition approved to offer accepted. Time to hire: first contact with the person you hired, to acceptance.
Track both. The gap between them is your pipeline problem; time to hire alone is your process problem.
Also track the stages: approval to posting, posting to first screen, screen to first interview, first interview to final, final to offer, offer to acceptance.
Almost every organisation that does this finds one stage consuming a disproportionate share, and it is rarely the one they expected.
Where the weeks usually go
Before the search even starts
Requisition approval. Frequently two to four weeks of a chain of sign-offs on a decision everyone already agreed to. Batch approvals, delegate authority to a level that can act, or pre-approve backfills.
Salary range not agreed. If the range is decided at offer stage, you will discover a disagreement at the worst moment and restart. Agree it before posting.
Job description rewritten from scratch. Maintain templates by role family.
During the search
Scheduling. The single largest source of avoidable delay. Interviewers with no availability for ten days will cost you candidates.
Fix: book the panel's availability in advance, as recurring interview slots. Give candidates a scheduling link rather than exchanging emails. Have a designated backup interviewer for each stage.
Feedback collection. A debrief that waits for one person's calendar adds a week per stage.
Fix: scorecards submitted within 24 hours, no exceptions. Decision made on the scorecards, with a meeting only where scores diverge.
Too many stages. Five stages with three interviewers is thirty scheduling problems and roughly a month of elapsed time.
Fix: three stages for most roles. Screen, a structured panel covering the competencies, and a final conversation. Structured interviewing lets you cut stages because each one produces real evidence. See structured interviews.
Waiting to build a full shortlist. Holding strong candidates while you assemble a comparison set loses the strong ones.
Fix: interview as candidates arrive. If someone is clearly right, move.
At the end
Offer approval. Another sign-off chain, at the exact moment speed matters most.
Fix: pre-approve the range so the offer can be made same-day within it.
Slow references and background checks. Start them at the shortlist stage where appropriate, not after acceptance.
The changes with the largest effect
1. Cut to three stages. Usually removes one to two weeks and rarely worsens decisions.
2. Book the panel in advance. Removes the scheduling bottleneck entirely.
3. 24-hour feedback rule. Removes a week per stage.
4. Pre-approve the salary range. Removes days at the point of maximum risk.
5. Publish the range in the posting. Fewer wasted screens, better-matched applicants.
6. Improve the posting. Better applicants means less screening time. See how to write a job posting people respond to.
Speed and quality are not opposed
A common objection is that moving faster means hiring worse. In practice the opposite is usually true.
Long processes do not add rigour; they add elapsed time and repetition. Five unstructured conversations produce less usable evidence than three structured ones, and they lose the candidates who have other options — which are, systematically, the strongest ones.
What improves decisions is structure: defined competencies, consistent questions, written scores. That makes processes shorter and better at the same time.
Set a target and publish it
Agree a target — for example, first interview to offer within fourteen days — and share it with hiring managers.
Then report against it. Nothing changes behaviour like a visible number attached to a named manager.
When the delay is genuinely the market
Sometimes it is not process. Scarce skills, a narrow geography, or a compensation range below market will produce a long search regardless.
The signal: your pipeline is thin at the top, not slow in the middle. If you are getting few qualified applicants rather than losing them in the process, the fix is sourcing, compensation, or requirements — not scheduling.
Check the requirements first. An unnecessary degree requirement or an inflated years-of-experience figure shrinks a pool for no benefit, and it is the cheapest thing on this page to change.
What it is worth
Take the fully loaded cost of the vacancy per week — lost output, delayed projects, overtime covering it — and multiply by the weeks you remove.
For most roles, cutting three weeks off the process saves more than the entire recruitment spend. See what it really costs to fill a role.
PJP manages scheduling, feedback collection, and candidate communication as part of every search. Direct-hire recruitment → For broader reference, consult U.S. Department of Labor hiring resources.