How to reduce time-to-fill without lowering the bar

Time-to-fill is the sum of several separate waits, not one continuous process: the wait to start sourcing after a requisition opens, the wait to get candidates submitted, the wait to get them scheduled, the wait for feedback after each interview, and the wait for a decision once a finalist is chosen. Reducing it means finding which wait is longest for your roles and fixing that one first, because cutting a wait that was already short barely moves the total.

Recruiting agency metrics defines time-to-fill and the related speed metrics with formulas. This page assumes that definition and focuses on where the days actually go and what to do about each stage.

Time-to-fill is the sum of five waits

Most time-to-fill reporting only shows the total, which hides which of the five is dragging. Log the date at each handoff point for a month of requisitions and the longest wait usually stands out clearly once it is broken out this way.

Audit where your days actually go

Time-to-fill audit — [Role / Req #]
Requisition approved: ____
Intake completed: ____          (Wait 1: ____ days)
First candidate submitted: ____ (Wait 2: ____ days)
First interview held: ____      (Wait 3: ____ days)
Feedback given: ____             (Wait 4: ____ days)
Offer extended: ____             (from finalist chosen, Wait 5: ____ days)
Offer accepted: ____

Total time-to-fill: ____ days
Longest single wait: ____

Run this on eight to ten recent requisitions of the same role type before drawing conclusions — one unusually slow search can make a normal process look broken, and one unusually fast one can hide a real problem.

Segment the audit by role type before averaging. A specialized senior role and a high-volume entry-level role have different sourcing waits for reasons that have nothing to do with process quality, and blending them into a single company-wide average tells you less than either number on its own. If your ATS supports it, tag each requisition by role family so you can pull this breakdown without rebuilding it by hand every quarter.

Fixing the front half: kickoff and sourcing

The kickoff wait

This wait is often the easiest to cut and the most overlooked, because it happens before any recruiting activity starts and so does not show up in recruiter-facing dashboards. A requisition can sit approved but unassigned, or assigned but waiting on an intake meeting that has not been scheduled. Set a standing rule: intake happens within a fixed number of business days of requisition approval, on the calendar, not "whenever the hiring manager has time." See intake meeting questions for what that meeting should cover so it does not need to be repeated later.

A second, quieter cause of a long kickoff wait: requisitions that get approved on paper but sit unassigned because no one on the team has capacity. If that is the actual cause, the fix is a capacity conversation with recruiting leadership, not a process tweak — no amount of intake scheduling discipline helps a requisition nobody has picked up yet.

The sourcing-to-submittal wait

If sourcing itself is slow, the fix is usually upstream: must-haves that are too vague produce searches that cast too wide a net, and the recruiter spends the wait sorting through people who were never going to fit. Tight, specific must-haves from intake (three to five, not fifteen) cut this wait more reliably than sourcing harder within a poorly defined search. Where the role type allows it, drawing the first submittals from an existing pipeline rather than starting sourcing from zero also removes most of this wait outright; see how to build a talent pipeline for roles you fill often enough to justify keeping one warm.

Fixing the scheduling wait

This is the wait most organizations underestimate, because each individual scheduling delay looks small (two days here, three there) while adding up to the single biggest chunk of total time-to-fill across a search. Two changes cut it consistently:

• Hold interview time before you need it. A hiring manager or panel with a standing weekly interview block does not need a new scheduling negotiation for every candidate.
• Offer a short list of specific times, not "let me know what works." Open-ended scheduling requests routinely take several email rounds to resolve; two or three concrete options resolve in one.
• Batch scheduling for panels. If a role needs three or four interviewers, sending one scheduling request per interviewer sequentially compounds the wait; send them together and set a deadline for responses.
• Track scheduling wait separately from everything else. Because it depends on other people's calendars rather than the recruiter's own effort, it is the wait most likely to be misattributed as "the search is slow" when the search itself is not the bottleneck.

Fixing the feedback wait

Feedback that trickles in over a week, one interviewer at a time, is one of the most common causes of a long time-to-fill and one of the most fixable. Set a fixed feedback window (24 to 48 hours is common) and make it a standing expectation rather than a request made fresh after every interview. For a structured way to set and enforce this with hiring managers, see recruiting SLA with hiring managers, which covers the full agreement, not just this one wait.

Fixing the offer wait

The gap between choosing a finalist and extending an offer is often a compensation-approval delay, not a recruiting delay. If your organization requires approval above a certain level, get that approval in motion as soon as a candidate becomes a strong finalist, in parallel with final-round logistics, rather than starting the approval only after a decision is fully locked in.

A second common cause here is an offer that goes out without the details a candidate needs to decide quickly — start date flexibility, benefits summary, relocation terms — which turns a same-day acceptance into several days of back-and-forth questions. Have those details ready before the offer call, not assembled in response to the candidate asking.

Worked example: where 42 days actually went

This is the argument for auditing before acting: intuition often points recruiters toward "source faster" as the fix, when the actual biggest wait in this example was scheduling, a problem sourcing effort cannot solve.

A second invented requisition, a specialized engineering role at the same company, illustrates why this has to be audited per role type rather than assumed from one example: total time-to-fill 58 days, with sourcing to first submittal accounting for 26 of those days (45%) because qualified candidates were genuinely scarce, while scheduling took only 6 days because the hiring manager already kept a standing interview block. Applying the first requisition's fix (shrink the scheduling wait) to this one would have done almost nothing; the second requisition needed a wider sourcing effort and possibly a pipeline built in advance, not a scheduling change.

What not to cut

Tracking progress without gaming the number

Track time-to-fill alongside quality-of-hire signals (manager satisfaction at 90 days, early attrition) so a falling number does not quietly mean a falling bar. A time-to-fill that improves because the scheduling wait shrank is a real win; one that improves because fewer candidates were compared or feedback was rushed through without real deliberation is not, even though the dashboard looks the same either way.

One practical check: when time-to-fill improves, look at whether the number of candidates interviewed per requisition also fell over the same period. A drop in both together is worth a direct conversation with the recruiter or hiring manager about whether corners were cut, before the faster number gets reported upward as an unqualified win.