Time to Hire vs Time to Fill Metric Comparison

Time to hire and time to fill measure different stages of the same hiring process. Reading them together reveals whether delay sits in requisition planning and sourcing or in the candidate’s path to an accepted offer. The distinction determines which intervention will improve hiring speed, rather than merely make one part of the process look faster.

Why time to fill and time to hire are not the same metric

A CEO demands that the team “speed up hiring”. The answer depends on which stage is slow. A role waiting for approval presents a different problem from a candidate waiting for interview feedback, even if both eventually produce a late hire. Treating time to fill and time to hire as interchangeable hides that distinction. The team can shorten interviews while leaving the main source of delay untouched.

Time to fill measures organizational speed, from requisition opening or approval to offer acceptance. It includes the posting and sourcing lead time before the eventual hire enters the pipeline, plus any internal approvals that fall after the chosen starting point. Time to hire begins when that candidate enters the pipeline and ends when they accept the offer. It tracks the candidate as the team evaluates them and decides whether to hire them. Both clocks stop at the same event, but their different starting points give them different diagnostic roles.

How to calculate each metric and what the numbers actually represent

Time to fill equals the offer acceptance date minus the requisition opening or approval date. Average time to fill equals the sum of those durations across filled roles divided by the number of roles filled. If a requisition opens July 1 and the candidate accepts August 8, the metric covers that entire span. The starting point requires a documented choice. Starting at job posting rather than requisition approval excludes pre-posting delays, so those two definitions cannot support a like-for-like comparison.

Time to hire is the offer acceptance date minus the date the hired candidate entered the pipeline. Its average is the sum of individual times to hire divided by the number of hires. For the same role, a candidate who applies July 20 and accepts August 8 has a shorter measured journey. Time to fill also covers the period before that candidate entered. It does not prove that no other candidates were considered during that interval, or that approvals caused all of it.

A third measure, time to start, extends the window through the candidate’s notice period to their first day. This measure answers when capacity becomes available. For reliable trends, teams should document their endpoints and use them consistently across reporting periods. Reporting the median with the mean also keeps a six-month executive search from looking like the usual time it takes to hire.

What current benchmarks show about where hiring time actually goes

SHRM’s 2026 benchmarking data shows that median time to fill for executive positions remained unchanged from the previous year, while the nonexecutive median decreased. The executive measure remained below the 60-day median recorded in 2022. SHRM attributes part of the nonexecutive improvement to wider adoption of AI in recruiting. Its 2026 data brief reports that organizations with the most effective recruitment practices use advanced technologies, including AI, and fill roles roughly five days faster than peers.

Energy and Defense have among the longest timelines, while Information Technology moves faster than most sectors in a competitive market. Restaurants and Hospitality also have relatively short timelines, reflecting high volume and lower role complexity. Role mix changes the comparison substantially. A benchmark is useful only when its industry, seniority and measurement boundaries resemble those of the roles under review.

AMS and The Josh Bersin Company report that average time to hire has risen for four consecutive years. That direction contrasts with improvements in some time-to-fill measures, although the findings do not describe identical populations. A team can accelerate posting while evaluation remains slow. Knowing where a metric sits relative to peers therefore becomes useful only when the team also examines how its two measures relate.

Reading the gap between the two numbers as a bottleneck locator

High time to fill, low time to hire points toward the period before the eventual hire enters the pipeline. Approval chains, intake, sourcing and applicant attraction are the first places to investigate. In the July example, the interval from July 1 to July 20 belongs to this part of the timeline. The candidate then moves from application to acceptance by August 8. If that later journey is already efficient, shortening interviews offers less scope to reduce delays.

Low time to fill, high time to hire means the organization gets the role moving quickly, but the candidate spends a comparatively long time in evaluation and decision-making. Here, “low” and “high” refer to relevant expectations, with time to fill encompassing time to hire for the same role. The candidate-stage window dominates the total. Slow screening, scheduling gaps, indecisive hiring managers and offer delays become the likely areas of investigation. More sourcing does not resolve those bottlenecks.

Both high means there are delays across the hiring process that cannot be pinned neatly to one side. The priority is the stage with the largest average delay. Stage data provides the next level of precision. Subtracting time to hire from time to fill locates a window for investigation, but does not identify its cause on its own.

Where time to fill breaks down: pre-posting delays and requisition overhead

When the first pattern appears, the practical response is upstream process discipline. Multi-step approvals can leave a requisition waiting for finance, legal or management sign-off before HR can post it. Those waits count only if they happen after the metric’s starting point. The boundary can hide the problem entirely. A clock that begins at posting cannot reveal how long the organization took to make the role ready.

Intake introduces another source of avoidable delay. Meetings scheduled too late, or skipped altogether, can produce job descriptions that attract the wrong candidates and force the team to revisit the search. Pay misalignment can remain unresolved until weeks of sourcing reveal a gap between the budget and market requirements. Reactive sourcing adds further lead time when relationships begin only after a departure. These are distinct causes, even when they appear in the same pre-candidate interval.

The recommended levers are standardized intake, headcount pre-approval during workforce planning and proactive pipelines for recurring or strategically important roles. Maintaining relationships with passive candidates before requisitions open reduces dependence on starting each search from nothing. The intervention should match the recorded delay. If approvals account for the largest wait, a larger candidate pool will not remove it. Where pre-posting overhead dominates the gap, reducing that overhead offers the strongest leverage without changing the candidate’s evaluation experience.

Where time to hire breaks down: candidate-stage friction once someone is in the pipeline

When sourcing brings in candidates but they get stuck, teams should look at how they arrange the steps and make decisions. Manual scheduling requires coordination among recruiters, candidates, interviewers and decision-makers. The emails needed to arrange a single interview round can take several days on their own. Redundant rounds then add further waiting without adding information. The resulting time to hire reflects the design of the process.

Delay can also persist after evaluation is complete. Feedback may sit between an interview and a decision, leaving candidates waiting after final rounds. Offer drafting and approval can then enter another internal queue after a verbal decision has been made. These gaps are visible to the candidate. Because candidates judge how a company treats people by how it treats them during hiring, long silences can lead them to withdraw, cost the company candidates and hurt its employer brand.

The recommended response is to automate scheduling, cap interview rounds and set internal service-level agreements for feedback and offer delivery. Teams should treat gaps in communication as failures in how the process works, even when they look like one person’s oversight. That framing puts responsibility on the workflow itself. It also distinguishes unnecessary waiting from the evaluation needed to reach a decision.

Tracking both metrics over time and deciding which one to fix first

Teams should first calculate both metrics for the same completed hires, using the same definitions each time. Teams should then calculate the gap and identify the dominant pattern before selecting an intervention. Averages alone are insufficient for that decision. Changes in role mix or an unusually long search can shift the aggregate without showing which stage deteriorated. Reporting the median and comparing roles within relevant groups make the trend easier to read.

An applicant tracking system that timestamps application, screening, first interview, final interview and offer allows teams to calculate time in each stage. This separates a growing screen-to-first-interview interval from an extended offer-to-acceptance window. Both can increase time to hire. They require different responses, however, so the aggregate should trigger investigation. Tracking these intervals over time shows whether the chosen intervention reduced the delay it was intended to address.

Time to fill deserves priority when offer acceptance is good but roles attract few applications after weeks of posting, sourcing is inconsistent or headcount approvals arrive unpredictably. Time to hire deserves priority when sourcing produces candidates but acceptance is low, candidates withdraw or go silent, or managers feel rushed while decisions still take weeks. Stage-level data should determine which delay is largest. When both metrics are high, working on that stage first gives the team a clear problem and a way to judge whether things are getting better.

How automated hiring infrastructure affects both metrics simultaneously

As headcount scales, manual coordination can become a growing constraint even when individual recruiters work at the same pace. More hiring creates more approvals, scheduling exchanges and handoffs across systems that were not designed for speed. Automation can affect both metrics because coordination occurs on both sides of the candidate’s entry into the pipeline. Its effect depends on which steps it removes or accelerates.

At the front end, approval workflows, automated job posting and pipeline management tools can reduce delays before a candidate is engaged. At the candidate stage, scheduling automation, stage tracking and offer letter generation address different sources of waiting. These tools serve different operational purposes. Scheduling automation reduces coordination, while stage tracking makes stalled progression visible. Neither substitutes for clear intake requirements or timely decisions from hiring managers, so infrastructure and process discipline must work together.

Offer acceptance creates a separate boundary. Time to hire ends there, but operational drag can continue through payroll setup, device provisioning, benefits enrollment and compliance work. When people have to do those tasks by hand in separate steps using tools that do not connect, the new hire’s first week can become the next bottleneck. Clean recruiting metrics do not capture that friction. Teams therefore need to keep the handoff after acceptance separate from the candidate-stage window they measure, even when one platform supports both.

Workflows that connect can remove the work people have to do by hand to pass tasks between recruiting, payroll, compliance and IT provisioning. For high-growth companies moving from tens to hundreds of employees, the notes’ operational case for integration rests on disconnected handoffs expanding with the number of hires.