Time to hire is the number of calendar days between the date a candidate enters your pipeline and the date that same candidate accepts the offer. Frontline hiring runs on the candidate’s clock: 57% of frontline candidates name a slow hiring process as their top frustration, and 52% cite ghosting or a lack of updates between stages, per the 2025 Fountain Frontline Report.
That makes decision speed a competitive priority, but the number on its own says nothing about whether the people hired that fast ever show up. This guide covers what the metric measures, how to calculate it consistently, and how to read it against the checks that catch what speed misses.
What is time to hire?
Which event opens the clock depends on how the candidate arrived. For an applicant, the start event is the application timestamp, the moment the submission lands in your system. For a sourced candidate, it’s the date your team identified them. If you instead measure from first response, label that convention and apply it consistently, because the two can sit several days apart on the same hire.
Because the metric follows an identified candidate through acceptance, calculate it for the candidate hired, not the requisition. A req that ran three finalists through interviews produces one time-to-hire number, belonging to the person who accepted. Do not include the other two in that calculation.
A common mismeasurement stretches the endpoint to the new hire’s Day 1. That window belongs to a different metric, time to start. Folding that post-offer period into time to hire inflates the number and breaks every comparison against a funnel that measured to acceptance.
How to calculate time to hire
The formula for one hire is the offer acceptance date minus the date the candidate entered the pipeline. For a team or a reporting period, calculate the average time to hire by totaling those days across every completed hire and dividing by the number of accepted offers. Three hires that took 8, 10, and 15 days total 33 days, for an average time to hire of 11 days.
Treat that result as an internal baseline rather than a target.
Consistency is what makes the number comparable: use the same start and end events for every hire, log them the day they occur, and count calendar days, including weekends and holidays. Then segment by role and location before averaging, and avoid blending salaried searches with hourly hires into a single operating target.
Time to hire vs. time to fill (and time to start)
Time to hire runs from candidate entry to offer acceptance. Time to fill starts earlier, when the requisition opens, so it absorbs requisition approval, budget sign-off, and the posting work that happens before any candidate exists.
Both end at acceptance, which is why a requisition that waited weeks on approval can post a far longer time to fill than time to hire for the very same candidate. You can model the full requisition-to-acceptance window with Fountain’s time-to-fill calculator.
Across more than 4,600 organizations, the median time to fill was 39 days for nonexecutive roles, per SHRM’s 2026 recruiting benchmarking brief. That is a time-to-fill figure, requisition open through offer acceptance. Comparing your time-to-hire number against it will make your team look faster than it is.
Unlock the insights shaping retention, scheduling, and hiring outcomes
Frontline teams are changing fast, and strategies that worked in the past are no longer sufficient. The Frontline Report 2025 breaks down what nearly 2,000 frontline workers said they needed to stay engaged, supported, and committed.
Discover the trends driving turnover, the early-stage moments that matter most, and the operational shifts that help employers cut costs and build more stable teams.
Get the research-backed guidance you need to strengthen your workforce in 2o26.
Time to start picks up where both metrics end, covering offer acceptance through the first shift worked. For hourly roles, track that post-offer period separately to identify no-shows.
Where time to hire fits among recruiting metrics
Time to hire is an efficiency indicator. Alone, it rewards speed regardless of what that speed produces, so it belongs in a scorecard with the hiring metrics that check its output.
- Offer acceptance rate: A fast funnel still has to end in a yes, and acceptance rate shows how often it does.
- Day 1 show rate: Show rate catches the hires who accepted and then vanished before a first shift.
- 90-day retention: Retention is the quality check on screening; it shows whether speed came at the cost of fit.
- Cost per hire: The cost to produce each hire is the efficiency pair to time to hire, and it reads honestly only alongside retention.
Treat a funnel that produces an accepted offer in 5 days and a no-show on Day 1 as an unresolved vacancy. It has just moved past the point where most recruiting dashboards stop watching.
Why time to hire matters to the business
Slow decisions and long gaps between updates give candidates time to accept another employer’s offer. The two frustrations frontline candidates name most often, a slow process and silence between stages, are both timing problems. Every candidate lost to a faster employer restarts sourcing and screening from scratch.
That restart is not free. Replacing a frontline worker costs about $7,000 on average, per Fountain’s frontline retention research with Lighthouse Research & Advisory, and the vacancy keeps costing money while it sits open: overtime and manager coverage are operating costs of an unfilled role even when they never appear on a recruiting dashboard.
Offers themselves are not sure things. NACE’s 2022 benchmark put offer acceptance among entry-level college hires at 69.3%, and that is a population with structured timelines and months of runway.
Frontline hourly candidates decide faster, so read the figure as context rather than a frontline benchmark.
What drives time to hire up, and what compresses it
Desktop-first applications, manual screening, interview scheduling, poor status communication, and end-loaded compliance drive time to hire up; targeted automation and earlier sequencing compress it.
Applications built for desktops lose candidates before screening begins, and manual screening then stacks days onto every hire at volume: screening and interviewing average 8 to 9 days each, per SHRM’s 2025 benchmarking.
Interview scheduling adds its own tax through calendar back-and-forth, silence between stages gives candidates a reason to keep interviewing elsewhere, and compliance stacked at the end compounds all of it, because a candidate who cleared the interview is still waiting while required checks run.
Each bottleneck has a specific counter-measure, and none of them adds recruiter effort: automation moves candidates between stages while recruiters and hiring managers make every advancement and offer decision.
- Mobile-first applications: A form a candidate can finish on a break keeps the top of the funnel from leaking.
- Agentic screening: Voice screening qualifies and scores candidates the moment they apply, so nobody sits in a queue waiting for a recruiter to open an inbox.
- Candidate self-scheduling: Applicants book interviews against synced calendars, which cuts the coordination loop entirely.
- Automated status updates: SMS and email at every transition replace the silence that 52% of candidates flagged.
- Parallel compliance: Document collection and check initiation start as early as the process allows, so required checks run alongside the funnel instead of after it.
Start with one workflow: calendar-synced self-scheduling for your highest-volume role, since scheduling is usually the most fixable delay. Then sequence the rest to take days out of every stage; the tactic-by-tactic version for hourly roles is in Fountain’s average time to hire playbook.
What a good time to hire depends on
Role complexity and verification load set the floor, which is why a single benchmark number misleads. Roles with light verification can move from application to offer in days, while a CDL driver or credentialed clinician carries checks other roles do not: federal rules mandate specific commercial-driver background inquiries, and California publishes its own RN verification timelines.
For regulated roles, the work is eliminating every avoidable day above that floor. No single number qualifies as good across roles and markets. The closest thing is a before-and-after inside one funnel.
Take Stitch Fix. The warehouse ramp cut median time to hire from about 3 weeks to 9.16 days, and applicant conversion rate, the percentage of applicants who pass background checks and show up on day one, rose from 68% to 95%.
Treat it as one hourly funnel’s outcome after specific process changes, not a universal benchmark; speed and quality moving together is the transferable part.
The other reading trap is the average itself. An 11-day company-wide number can conceal a 15-day metro or role family where scheduling or screening is quietly broken, so review the metric segmented by location and role before treating it as a verdict.
How Fountain compresses time to hire for frontline teams
Fountain’s Frontline Superintelligence moves candidates between screening, scheduling, status updates, and onboarding without waiting for a recruiter to trigger each handoff. That matters because automating one stage in isolation rarely moves total cycle time; a faster screen just delivers candidates to the next queue sooner.
Cue, the orchestration layer and single entry point to Fountain’s agents, takes a hiring goal in plain language, “Hire 25 cashiers across Atlanta by Friday, screened and scheduled,” and coordinates the work across agents and products while recruiters and hiring managers approve every advancement and offer.
The agents under Cue map to the delays this article has been counting:
- Anna runs voice screening interviews 24/7 and scores candidates as they apply, so someone who applies on a Saturday night is screened before a recruiter’s Monday coffee.
- Emma answers candidate questions over voice and SMS at every stage, closing the silence between stages that candidates read as ghosting.
- Sam runs post-hire check-ins that surface early quit risk, the check that tells you whether a faster funnel is still hiring people who stay.
Underneath, the ATS carries the mobile-first application, candidate self-scheduling, and automated status updates from the compression list above, and Onboarding starts document collection and compliance checks the moment an offer is accepted, so verification runs in parallel instead of at the end.
That stack is how Alto hires W-2 rideshare drivers: per Fountain’s case study, first contact within 28 hours, a 2 to 7 day time to offer, and 450 drivers hired in 6 months with a team of 3 recruiters.
Frontline hiring runs on the candidate’s clock, and the clock only stops at an accepted offer that becomes a worked first shift. If your time to hire is sitting above the floor your roles require, see where the days go: book a demo and walk through Cue’s plain-language workflows, Anna’s screening pace, and the segmented time-to-hire views this article recommends.
Frequently asked questions about time to hire
Is a shorter time to hire always better?
No. Some regulated roles carry mandatory verification steps that should not be removed to shorten the metric, and a number that drops because screening got thinner shows up later as no-shows and early quits. Shorter is better only when Day 1 show rate and 90-day retention hold steady for the same cohort of hires.
Who owns time to hire, recruiting or operations?
Time to hire is formally a talent acquisition KPI, but hiring managers control real parts of the elapsed time through interview availability and decision speed. Rather than assigning the number to one function, set shared turnaround expectations for every stage, the way service level agreements work between recruiters and hiring managers.
Why doesn’t our time to hire match published benchmarks?
Because publishers measure different windows on different populations. Time to fill starts when the requisition opens, while time to hire starts when a candidate enters the process, so the two produce different figures for the same hire, and benchmark samples rarely match a frontline role mix. A benchmark is only comparable when its start event, end event, and population match yours.
