HR Hub guide

Time to Fill Calculator Guide: How to Interpret Hiring Speed Without Oversimplifying It

Time to fill is a descriptive duration average for a consistently defined filled-requisition cohort. This guide explains the start event, offer-acceptance endpoint, and why the average does not measure workload, capacity, backlog, or business impact.

By HR Hub Editorial Team · Recruiting operations editor · Published 2026-08-04 · Updated 2026-09-25 · 6 min read

Maintained by Michael Walmer, the site operator. No independent professional review is claimed unless a named reviewer is shown.

What time to fill is measuring

This site's method measures calendar days from one documented requisition start event to candidate offer acceptance for included filled requisitions. It does not use employee start or completed-hire status and does not capture business impact in the average.

The metric becomes even stronger when teams separate approval delay from sourcing delay and candidate-stage delay.

Why this metric matters to leaders

A longer duration can be investigated beside workload, overtime, service, and turnover evidence. The duration average does not establish that any of those outcomes occurred or identify their cause.

The result becomes especially important when leadership is asking whether hiring demand can realistically be met in the planned window.

What to do after the result appears

Check whether the delay is driven by approvals, sourcing, interview throughput, or final-stage conversion. Then compare the result with cost per hire, acceptance rate, and headcount urgency.

The most valuable next step is usually fixing the bottleneck, not just reporting the average days.

Why this matters

  • Shows how recruiting speed affects real operating capacity.
  • Provides a consistent duration average that can be followed by separate stage-level investigation.
  • Creates a stronger link between recruiting operations and workforce planning.

Method, scope, and sources

Closed-requisition average = total calendar-day durations from one documented requisition start event to candidate offer acceptance ÷ the count of included filled requisitions or positions. The compact and advanced views use the same supported core average; unsupported throughput and recruiter-capacity outputs have been removed from the advanced view.

Use the same start event, offer-acceptance endpoint, calendar-day rule, unit, period, role cohort, and inclusion/exclusion policy for every record. Open requisitions, employee start dates, stage time, workload, throughput, backlog, recruiter capacity, and quality require separate data and models. This is not a universal performance benchmark.

Method status: Partially supported.

Worked example

Hypothetical: four included filled requisitions use requisition approval as the start and candidate offer acceptance as the end. Their calendar-day durations are 17, 26, 32, and 45 days. Average time to fill = 120 ÷ 4 = 30.0 calendar days. Open requisitions and later employee start dates are excluded.

Sources

Read the Editorial Policy or contact the publisher with a correction