Stage 3 · 9 min read read · Last reviewed 2026-05-23

Time to Hire: How to Reduce It — Pipeline Metrics and Where Delays Actually Happen

The average time-to-hire in the UK is 27 days for specialist roles and 40+ days for senior roles. US data is similar. Most hiring managers believe their process is faster than the average. Most are wrong.

This guide shows you how to measure where your pipeline actually slows down, which delays are worth fixing, and which ATS analytics surface the data you need.

Time-to-hire vs time-to-fill: the definitions that matter

Time-to-hire: The time from when a candidate first engages with your process (applies, or is contacted) to when they accept an offer. This measures hiring process efficiency.

Time-to-fill: The time from when a job requisition is opened to when an offer is accepted. This measures the full recruiting cycle, including the time the role sits unfilled before sourcing begins.

The distinction matters because they point to different problems:

Long time-to-hire = your interview process is slow, or offer decisions take too long
Long time-to-fill = roles aren’t approved in time, sourcing takes too long, or the talent pool is thin

Most ATS tools report one or both metrics. Know which one you’re measuring.

Where pipeline delays actually happen

From ATS time-in-stage data across common hiring processes, the delays are predictable:

1. Application to first contact (3–10 days in most SMBs)

The most common delay at this stage is recruiter bandwidth — applications sit unreviewed because the recruiter is managing multiple open roles. A pile-up at the “Applied” stage means too many roles, too few reviewers.

Fix: Set a maximum response time standard (48–72 hours to first decision on applications). Use ATS bulk review to process applications in batches daily, not when you remember.

2. Phone screen to first interview (5–14 days)

Scheduling friction is the primary culprit. Three rounds of email to find a mutual time slot costs 3–5 days on average. Candidates who are actively interviewing elsewhere will progress faster with your competitors.

Fix: Use ATS scheduling tools (Greenhouse, Workable, Ashby all have these) that send candidates self-serve scheduling links. Calendly or Cronofy integrated with your ATS can cut scheduling time from 5 days to 1 day.

3. First interview to second interview (7–21 days)

This stage has two common failure modes:

Interviewer feedback lag: Interviewers submit scorecard feedback days after the interview, rather than same-day. Greenhouse and Ashby both allow same-day feedback submission from mobile — but if you don’t set expectations that feedback is due within 24 hours, it takes 3–7 days by default.

Hiring committee misalignment: Multiple interviewers have different views of the candidate and the decision takes a week of async discussion. A structured debrief (60-minute synchronous calibration call after interview rounds) resolves this faster than email chains.

Fix: Set a 24-hour feedback deadline. Schedule debrief calls in advance as part of the interview loop setup.

4. Final interview to offer (3–14 days)

The two failure modes here are both internal:

Comp approval delays: The offer is ready but needs sign-off from finance or leadership. At companies with bureaucratic approval chains, this can take a week.

Decision paralysis: The hiring team isn’t sure, and “we just want to talk to two more candidates” adds 2–3 weeks to the process. Meanwhile, the candidate you liked accepts an offer from someone who moved faster.

Fix: Pre-approve a salary band for every open role before sourcing starts. Define decision criteria upfront — “we will hire the first person who meets X and Y criteria, not wait to compare against unlimited candidates.”

The ATS analytics that show you where to look

Most ATS tools can show you time-in-stage data. This tells you exactly where candidates are spending the most time — and therefore where your bottlenecks are.

How to access it:

Greenhouse: Reports → Candidates → Stage report. Filter by date range and role.
Workable: Analytics → Pipeline report. Shows average days per stage.
Ashby: Analytics dashboard → Pipeline velocity. Best-in-class visualisation.
Lever: Reports → Pipeline velocity.

What you’re looking for: stages where the average time-in-stage is 2–3x longer than the others. That outlier stage is your bottleneck.

Example diagnosis:

Applied: 2 days (good)
Phone screen: 4 days (good)
First interview: 14 days (problem — scheduling?)
Technical assessment: 8 days (moderate)
Offer: 12 days (problem — approval delay?)

In this example, the fix priorities are: reduce first interview scheduling time (use self-serve scheduling), and pre-approve comp bands to speed up the offer stage.

Benchmark targets by stage

Stage	Good	Acceptable	Needs fixing
Application to first contact	<2 days	2–5 days	>5 days
First contact to phone screen	<3 days	3–7 days	>7 days
Phone screen to first interview	<5 days	5–10 days	>10 days
Interview to feedback submitted	<24 hours	24–48 hours	>48 hours
Final interview to offer	<3 days	3–7 days	>7 days
Offer to acceptance	<2 days	2–5 days	>5 days

Total process target: 15–25 days for specialist roles. 25–40 days for senior/executive roles.

The offer decline risk

Every day between final interview and offer acceptance is a day your candidate is interviewing elsewhere. The most painful time-to-hire problem is a 45-day process that ends in a declined offer — because the candidate accepted something faster.

The data on this is consistent: candidates who receive offers within 5 days of their final interview accept at 80%+. Candidates who wait 14+ days for an offer accept at under 50%.

If your offer acceptance rate is below 70%, your process speed is probably a contributing factor even if it’s not the only one.

What ATS configuration helps most

Mandatory same-day scorecard submission: Configure your ATS to send a reminder email to interviewers 4 hours after their interview. Make scorecard completion a required step before the interview debrief can be scheduled.

Self-serve scheduling: Eliminate the email back-and-forth for scheduling. Greenhouse, Workable, and Ashby all support candidate self-scheduling against real calendar availability.

Defined SLAs per stage: Set stage-level SLA alerts in your ATS. Greenhouse allows custom notifications when a candidate has been in a stage for more than X days. Use this to catch candidates who are stuck.

Offer letter automation: Pre-draft offer letter templates in your ATS. When the offer decision is made, the letter is generated with one click rather than created from scratch.