Time to Hire vs Time to Fill: Definitions, Formulas, and Recruiting Benchmarks

What is the difference between time to hire and time to fill?

BambooHR defines time to hire as the period the successful candidate spends in the recruiting pipeline, from application or sourcing to offer acceptance. Greenhouse defines time to fill from requisition approval to offer acceptance, while BambooHR notes that organizations also use requisition submission or job publication as the starting event.

This distinction changes what teams fix. A recruiter can move the eventual hire quickly while the role still takes weeks to fill because budget approval, publication, or sourcing started late. A ready candidate pool can create the opposite problem, hiding a slow interview and decision process when leaders watch only time to fill.

Time to fill measures the vacancy. Time to hire measures the candidate journey. The gap measures everything that happened before those two timelines met.

The gap is useful only when both clocks use aligned definitions for the same successful hire. Otherwise, the subtraction combines unrelated dates and produces a precise-looking but misleading diagnosis.

How do you calculate time to hire and time to fill?

Calculate time to hire by subtracting the candidate's pipeline-entry date from the offer-acceptance date. Calculate time to fill by subtracting the chosen role-opening date from that same acceptance date. Pick elapsed calendar days or working days, use the choice consistently, and document whether you include the starting and ending dates.

Time to hire formula

Time to hire = offer acceptance date minus candidate pipeline-entry date.

BambooHR and Teamdash use application or sourcing as the beginning of time to hire, while Asymbl also identifies first outreach or referral registration as possible pipeline-entry events. No single event is universally correct. Use the event your organization captures reliably and can apply to every candidate included in the report.

Time to fill formula

Time to fill = offer acceptance date minus the selected role-opening date.

BambooHR notes that published definitions start this clock at different events, including requisition submission, requisition approval, and job publication. Approval captures more of the workforce-planning cycle. Publication creates a narrower recruiting measure. Record both dates when possible, but name one as the official reporting start.

A shared timeline example

1. The job requisition is approved on day 1.
2. The successful candidate applies on day 15.
3. The candidate accepts the formal offer on day 30.
4. Time to fill is 30 minus 1, or 29 elapsed days.
5. Time to hire is 30 minus 15, or 15 elapsed days.
6. The 14-day gap represents the period between requisition approval and the successful candidate's application.

Inclusive counting produces 30 days for time to fill and 16 for time to hire. The gap stays at 14 days, but each reported metric moves by one. Put the convention on every dashboard and report. That one line prevents recurring off-by-one arguments.

To calculate averages, add the elapsed times for individual filled roles and divide by the number of those roles. Run the calculation separately for time to hire and time to fill. Do not substitute the interval between the first opening and final acceptance across a batch of requisitions.

What does the gap between time to fill and time to hire reveal?

When both metrics cover the same hire and end at offer acceptance, the difference measures the time before the successful candidate entered the pipeline. A wide gap points to requisition approval, publication, or sourcing delays. A narrow gap paired with a long time to hire points to slow candidate processing.

Split the timeline into intervals before prescribing a fix: approval to publication, publication to successful-candidate entry, entry to screening, screening to interview, interview to decision, and decision to acceptance. The total confirms a problem. Stage intervals identify the owner who can fix it.

For approval-specific delays, map the owners and escalation points in the job requisition approval process. For candidate delays, define the entry and exit event for each of your recruiting pipeline stages.

Which measurement rules make recruiting reports comparable?

Write a metric contract that fixes six choices: role-opening event, pipeline-entry event, end event, day type, counting method, and pause policy. Store the dates as fields instead of reconstructing them later from emails and calendars. Apply the same rules across teams, then segment the results so unlike roles do not blur one another.

Handle paused and canceled requisitions explicitly

A pause should never disappear from the record. Report total elapsed time and paused time separately, or keep the clock running when vacancy duration is the business concern. Either policy works. Switching policies by department does not.

Exclude canceled requisitions from filled-role averages because they lack an offer-acceptance date. Track them separately with the cancellation reason and age at cancellation. Reopened roles also need a declared rule: continue the original clock or create a new requisition with a fresh start date.

Keep multiple useful dates without mixing definitions

Capture requisition submission, approval, publication, candidate entry, every stage transition, decision, offer issuance, and acceptance. The official metric can still use one start and one end. Other timestamps diagnose delays without forcing the headline definition to change whenever a stakeholder asks a different question.

What are good time-to-hire and time-to-fill benchmarks?

BambooHR cites The Josh Bersin Company as reporting an average time to hire of 44 days in 2023, while Teamdash reports an average of about 36 days in the UK. Treat these as reference points, not universal targets. Role difficulty, location, labor supply, seniority, starting events, day-count rules, and reporting methods all affect the result.

The functional spread matters more than the headline average. Teamdash reports UK time-to-hire figures of 27 days for marketing, 24 for IT and finance, 22 for administration and HR, 20 for customer service, and 65 for engineering. One blended target treats structurally different searches as interchangeable. They are not.

How should recruiting teams segment and review these metrics?

Segment time to hire and time to fill by role family, seniority, geography, candidate source, and department. Keep the company-wide average for executive planning, but inspect each segment before assigning accountability. Pair the results with offer-acceptance rate and quality of hire so faster hiring does not damage outcomes.

Start with segments tied to an operating decision. Source segmentation tells recruiting where to search. Department views expose inconsistent manager response times. Seniority and role-family breakdowns support realistic workforce plans, while geography helps separate internal delays from local labor-market conditions.

Every report should show the number of filled roles behind the average, the reporting period, date definitions, and pause policy. Without that context, a change in role mix can masquerade as a process improvement or decline.

Use a small set of recruiting metrics that drives decisions instead of filling a dashboard. Time metrics belong beside funnel conversion, acceptance, and hiring quality. Growing teams should also connect them to broader HR operations metrics such as headcount and onboarding readiness.

How can you reduce time to hire and time to fill without lowering quality?

Fix the interval that is actually slow. Tighten requisition ownership and sourcing to improve time to fill. Improve screening, scheduling, structured interviews, feedback, decisions, and offer preparation to reduce time to hire. Keep acceptance and quality indicators visible so speed remains a constraint rather than the only objective.

1. Set a named owner and service target for requisition review, publication, interview feedback, final decision, and offer preparation.
2. Use applicant tracking system reporting to track pipeline-entry and stage-transition dates consistently.
3. Automate interview scheduling where calendar coordination is the dominant delay.
4. Use structured interviews with the same questions and scoring dimensions for comparable candidates.
5. Require prompt scorecard submission before interview details fade or group discussion changes independent judgments.
6. Strengthen sourcing channels when the time-to-fill gap shows that qualified candidates are entering too late.
7. Review time metrics beside offer-acceptance rate and quality of hire before declaring an improvement.

BambooHR reports that 29% of hiring managers who lost a good candidate attributed the loss to taking too long to make an offer. That does not justify rushing every process. It shows that avoidable waiting after the evidence is complete carries a real recruiting cost.

A consistent interview scorecard makes feedback easier to compare and gives decision makers a clear record. Fix the stage with the longest avoidable queue first, then recalculate both metrics under the same definitions.

How Cogniver helps reduce hiring handoffs

Cogniver runs the hiring process from job post through signed offer and day-one onboarding in one portal. Recruiting-funnel dashboards show current pipeline health, giving HR and hiring managers a shared view of the stages behind time to hire and time to fill.

Candidates apply through a branded job portal with their own accounts. AI CV screening supports the initial review, while the fairness-configured text AI interviewer uses the same questions and scoring dimensions for every candidate.

Accepted offers support click-to-sign e-signatures and produce a signed PDF. The incoming hire also reserves a seat on the shared org chart before the first day. Recruiting and organization planning stay connected instead of creating another handoff after acceptance.

For growing companies, that operating model is the point: the hiring pipeline, AI-assisted screening, consistent interviews, signed offer, day-one onboarding, recruiting dashboard, and future org-chart seat work together. Live recruiting-funnel dashboards make stage delays visible in the same portal.