Posted Jun 05, 2026
What Slow Hiring is Actually Costing Your Project
Most organisations know a vacancy slows things down. What’s less often calculated is exactly how much — and where the damage really shows up.
There’s a number most project managers never see on a risk register. It’s not the cost of a data breach, or a failed sprint, or even a contractor walking off mid-engagement. It’s the compounding, invisible cost of a vacancy that sits open for three, four, or six weeks while the hiring process moves at its own pace.
The vacancy isn’t the problem — the untracked drag that comes with it is. And by the time most clients formally acknowledge the cost, the project is already behind.
£1,200 – Estimated daily cost of a vacant mid-level tech role (productivity loss)
38 days – Average time-to-hire for specialist roles in the UK public sector
67% – Of projects report scope reduction when key hires are delayed by 4+ weeks
Where the cost actually hides
It’s rarely just about lost output. When a specialist role sits unfilled, the damage appears in three places that rarely show up on a traditional risk register — and each one compounds the others.
-
Existing team overload
When a gap isn’t filled, work doesn’t disappear. It redistributes. The most capable people on your team — often your most senior — absorb the extra load because they’re the ones who can. Their own priorities slip. Decisions slow down. And because this redistribution happens quietly, there’s rarely a formal record of the cost.
The longer the vacancy, the more normalised the overload becomes. People stop flagging it. They work longer hours and call it temporary. By the time the hire is made, the team may be months into a pattern that’s difficult to unwind.
-
Milestone creep
Delivery dates move, often quietly and often incrementally. A two-week delay here, a sprint extension there. No single event looks catastrophic enough to escalate. But when you look back across a project, slow hiring at a critical juncture is frequently the thread that unravels a timeline.
This is particularly acute in public sector projects, where delivery milestones are often contractually tied. A delayed hire doesn’t just slow a sprint — it can put formal programme commitments at risk.
-
Candidate drop-off
The best contractors and specialists have options. A process that takes five or six weeks doesn’t just feel slow — it communicates something to the candidate about how the organisation operates. The strongest applicants accept offers elsewhere. You restart from scratch with second-choice candidates, often under more pressure and with less leverage.
This isn’t hypothetical. In a tight specialist market — cleared security professionals, senior digital architects, niche data engineers — the window between a candidate being available and being committed elsewhere can be as short as 72 hours.
“The vacancy isn’t the problem — the untracked drag that comes with it is. By the time most clients realise the cost, the project is already behind.”
Why hiring processes slow down
The causes of slow hiring are well-known but rarely fixed. They tend to cluster around three structural problems:
- A brief that’s written during the search, not before it — leading to scope creep and changing requirements mid-process
- Interview stages that multiply over time, each requiring coordination across diaries and stakeholders
- Decision-making that’s distributed across too many people, none of whom have the authority — or appetite — to move fast
Each of these problems is solvable. None of them require a wholesale overhaul of how your organisation hires. But they do require someone to name them clearly and own the fix.
What good actually looks like
Organisations that consistently fill specialist roles quickly share a few common practices. They’re not dramatic. But they’re consistently absent in the organisations that struggle.
- The brief is agreed before the search begins — scope, must-haves, nice-to-haves, and the decision criteria are locked before a single CV is reviewed
- The process has two stages maximum — a screening call and a technical or stakeholder interview. Not three stages. Not four.
- A single named decision-maker has authority to make an offer — not a committee, not a group email chain, not approval from someone on annual leave
- Feedback is given within 24 hours of each stage — both to preserve candidate engagement and to maintain momentum internally
None of these are radical. They’re the basics. But in practice, they’re surprisingly rare.
How frameworks change the equation
One of the most significant structural fixes available to public sector organisations is procurement frameworks. A framework agreement — such as the Government Commercial Agency’s DOS7 (Digital Outcomes and Specialists 7), on which Spinwell Global is an approved supplier — removes the procurement overhead that traditionally slows down the start of a search.
The legal and compliance groundwork is already done. The commercial terms are pre-agreed. The conversation can start at capability, not contract. In practice, this alone can reduce the time from ‘role approved’ to ‘search begins’ from several weeks to a matter of days.
When you combine a framework-based engagement with a supplier who already has a deep pool of pre-screened specialists in your sector — cleared professionals, digital delivery experts, risk and security specialists — the time-to-fill compresses further still.
The question worth asking now
If you have a role open today, or one you know is coming, the most useful thing you can do isn’t to start the search. It’s to ask: what is slowing down our ability to move once a strong candidate is in front of us?
The answer is almost always process. And process is fixable — faster than most people think, with the right partner involved early enough.
Get in touch with us
NK
