Skip to content
Surhires

Article

Find the days before you try to save them

Time to fill is a sum of separate waits with different owners. Shortening it starts with splitting the number, not with working faster.

Reducing time to fill means finding which stage holds the days. Intake quality, client response latency, interview scheduling, offer approval and notice periods each behave differently and have different owners. Measure them separately, fix the agency-side ones you control, and manage the client-side ones through the contract and the briefing.

By Surhires Editorial · Published · Reviewed

A single number hides five different problems

A firm that reports an average time to fill and nothing else has a number it cannot act on. Forty-one days could be four days of sourcing followed by five weeks of a client not replying, or three weeks of sourcing followed by a fast, well-run process. Those are opposite problems with opposite remedies, and the average is identical.

The first intervention is arithmetic, not effort. Split the elapsed time into intervals between events you already record: requisition opened to first submittal, submittal to client response, response to interview held, interview to offer issued, offer to acceptance, acceptance to start. Each interval has an owner, and most of them have an obvious remedy once you can see which one is fat.

Do this before buying anything or changing any process, because it routinely overturns the assumption the firm was operating under. Desks that believe they have a sourcing problem frequently have a client-response problem, and hiring more sourcers makes that measurably worse by increasing the queue in front of the same bottleneck.

Bad intake is the most expensive delay and the earliest

The days lost to a vague brief do not appear as a delay. They appear as rework: candidates submitted and rejected, a shortlist rebuilt in week three, a salary band that was never real. Every one of those cycles costs a week, and the cause is upstream of anything a recruiter does afterwards.

A brief is complete when you can predict rejections from it. That means the must-haves are separated from the nice-to-haves and both are testable, the salary band is what the client will actually pay rather than what they hoped for, the interview process is written down with the number of stages and who is in each, and somebody has said what the last person in this role did all day.

The hard part is not knowing this, it is getting a busy client to sit through it. The lever that works is evidence rather than persuasion: showing an account that nine of their last eleven rejections were on salary converts an argument about process into a conversation about the band.

  • Must-haves stated as things a screen can test, not adjectives
  • A salary band the client has confirmed they will pay, in writing
  • The full interview process, with stage count and named participants
  • The reason the role is open, and what the previous holder actually did
  • The client-side decision maker, and who can act when they are on leave

Client response latency is usually the biggest single interval

On most agency desks the longest wait in the process is between a submittal going out and the client saying anything about it. It is also the interval the agency has least direct control over, which is why it tends to be excluded from internal reporting and therefore never addressed.

You cannot make a client respond faster by wanting it. You can change the conditions. Agree a response window at the point of taking the brief and put it in the terms, so chasing is a reference to an agreement rather than a nuisance. Submit in batches the client asked for rather than one candidate at a time, because a single CV is easy to leave in an inbox and a shortlist of three is a decision. Give the hiring manager a way to respond that takes thirty seconds, which usually means a shared shortlist view with a yes, no or interview control rather than a reply-all thread.

And measure it per account. A client who averages nine days is not the same commercial proposition as one who averages two, and that difference belongs in how you prioritise the desk.

Scheduling loses days quietly

Interview coordination rarely appears as a problem because no single step is slow. A day to get panel availability, a day for the candidate to reply, a day to discover the second interviewer is travelling, a reschedule that costs four more. Across three stages that is a fortnight nobody decided to spend.

The fix is structural rather than diligence. Hold candidate-selectable slots against real calendar availability so the negotiation happens once. Book the next stage before the current one ends, while everyone is in the room and engaged. Have a named substitute for every panel member, agreed at intake, so one person's travel does not stop the process.

Reminders matter more than they should. A confirmed interview that a candidate forgets costs the same days as one that was never booked, and a reminder through the channel the candidate actually reads is the cheapest intervention available.

Offer approval and the counter-offer window

The gap between a decision to hire and an offer in the candidate's hands is often days, and it is nearly always internal to the client: a compensation approval, a signature, a finance sign-off nobody flagged at intake. Ask during the brief who approves an offer and how long it takes. Clients rarely volunteer this and frequently do not know until asked.

This interval matters out of proportion to its length because it is where candidates are lost rather than merely delayed. A strong candidate at offer stage is usually in a process elsewhere, and a week of silence is where a counter-offer lands. Time to fill and offer acceptance rate are the same conversation at this point in the process.

The agency-side work here is keeping the candidate warm with something real to say, and having discussed resignation and counter-offer before the offer exists rather than after it arrives.

Notice periods are a constraint, not a delay

A three-month notice period is not inefficiency, and reporting it inside time to fill produces a number that punishes desks for the seniority of the roles they work. This is the strongest argument for measuring time to hire, which ends at offer acceptance, alongside time to fill, which ends at start date.

What you can do about notice is factual. Establish it at first conversation and carry it on the record. Tell the client at submittal rather than at offer, because a start date discovered late is where a placement collapses. Where a client genuinely needs someone sooner, that is a brief-level decision about seniority and buy-out, and it belongs in week one rather than week seven.

Then exclude notice from any internal comparison between desks. Otherwise your executive search desk looks slow next to a temp desk that fills in three days, and you will end up managing the wrong thing.

What the software can and cannot do here

Software helps with the parts that are measurement and coordination. It can timestamp every stage transition so the intervals are computable without anyone maintaining a spreadsheet. It can flag a submittal that has had no client response beyond that client's own normal window. It can hold interview slots and send reminders through the channel a candidate agreed to. It can surface an offer past its response deadline as a task with the context attached.

It cannot make a hiring manager decide, shorten a notice period, or repair a brief that was never taken properly. Any product that implies otherwise is describing a marketing position rather than a mechanism.

The honest claim is narrower and still worth having: most of the days in a slow search are visible in data you are already generating, and the work of finding them is where the improvement comes from.

What you get

Interval decomposition

Splitting elapsed time into six measurable stage-to-stage waits with distinct owners.

Owner mapping

Which intervals belong to the agency, which to the client and which to neither.

Intake completeness test

A brief is complete when it lets you predict which candidates will be rejected.

Salary band verification

Confirming what a client will pay rather than accepting what they hoped for.

Rejection-pattern evidence

Using coded rejection reasons to reopen a briefing conversation with data.

Response-window terms

Agreeing client response times at brief stage so chasing references an agreement.

Batch submittal

Presenting a decidable shortlist instead of single CVs that sit in an inbox.

Thirty-second response paths

Shared shortlist views with a yes, no or interview control instead of email threads.

Per-account latency

Measuring client response time per account and letting it inform desk priority.

Scheduling structure

Candidate-selectable slots, next stage booked in the room, named panel substitutes.

Offer approval discovery

Establishing at intake who signs an offer and how long that internally takes.

Counter-offer preparation

Discussing resignation and counter-offers before the offer exists, not after.

Notice-period separation

Reporting time to hire alongside time to fill so seniority is not penalised.

What software cannot fix

The limits of tooling against client decision speed, notice periods and weak briefs.

Questions recruiters ask

What is a good time to fill?

There is no cross-industry number worth acting on, because definitions, role mixes and clock start points differ so much that published figures are not comparable. The useful comparison is against your own history for the same role type with the same client. Build that baseline from your own data and compare to it.

Should client delay count in our time to fill?

Report both. The total elapsed figure is what the client experiences and what your contract may reference, so you cannot ignore it. The agency-side subtotal is what your desks can be managed against. Reporting only the total means holding recruiters accountable for a hiring manager's calendar, which produces resentment rather than improvement.

Does AI matching reduce time to fill?

It can shorten the first interval, from requisition opened to first submittal, particularly where the right candidate is already in your database and would otherwise not have been found. It does nothing to the client-side intervals, which on many desks are larger. If that first interval is not your bottleneck, matching will not move your total.

How do we get a client to respond faster?

Change the conditions rather than the chasing. Agree a response window when you take the brief, submit a decidable shortlist rather than single candidates, and give the hiring manager a way to answer in seconds. Where a client is persistently slow, treat it as a commercial fact about that account and price or prioritise accordingly.

Is a shorter time to fill always better?

No. Speed achieved by submitting weaker candidates shows up later as failed placements inside the guarantee window, which costs more than the days saved. Watch time to fill alongside offer acceptance and guarantee-period retention, or you will optimise one number by quietly damaging two others.

Where should we start if we have never measured this?

Take your last twenty placements and hand-compute the six intervals from your existing records. It takes an afternoon and it usually identifies the bottleneck immediately. Do that before changing process or buying software, because the intervention only pays if it lands on the stage that actually holds the days.

See it against your own reqs

Bring one live role and three resumes. In twenty minutes you will see the match scores, the shortlist and the placement invoice that comes out the other end.