How to

Time to hire vs time to fill: two clocks, what each measures, worked with dates

On this page
  1. The two formulas
  2. Worked example: one requisition, with dates
  3. Reading the gap between the two
  4. A five-role report
  5. Is there a benchmark?
  6. Definition choices that make the numbers drift
  7. Calculating both in a spreadsheet
  8. How to report it
  9. Common mistakes
  10. Questions people ask

Time to fill and time to hire are two different clocks. Time to fill counts the days from when a job is approved or opened to when a candidate accepts the offer, so it measures how long the seat stays empty. Time to hire counts the days from when the person you eventually hired entered your pipeline to when they accepted, so it measures how fast your process moves once the right candidate is in it. The difference between the two is the time you spent before that candidate showed up.

This page gives both formulas, works them through on one requisition with real dates, shows a five-role report, and lists the definition choices that make the numbers drift. To shorten the clock once you have measured it, see how to reduce time to fill.

The two formulas

MetricClock startsClock stopsAnswers
Time to fillRequisition approved (or job opened)Offer acceptedHow long did the business wait for this seat?
Time to hireHired candidate entered the pipeline (applied, or first two-way contact if sourced)Offer acceptedHow quickly did we move the right person through?
Time to start (optional third clock)Offer acceptedFirst day of workHow long is notice, background checks and onboarding lead time?
Time to fill  = offer accepted date − requisition approved date   (calendar days)
Time to hire  = offer accepted date − hired candidate's entry date (calendar days)
Sourcing gap  = time to fill − time to hire

Some teams stop both clocks at the start date instead of offer acceptance. That folds the notice period into the number, which neither the recruiter nor the hiring manager controls. It is cleaner to stop at acceptance and report time to start as its own line.

Worked example: one requisition, with dates

Invented requisition: senior financial analyst

  • Requisition approved: March 3
  • Job posted: March 5
  • The candidate who was eventually hired applied: March 20
  • Recruiter screen: March 22
  • Offer extended: April 10
  • Offer accepted: April 14
  • First day: May 5

Time to fill: March 3 to April 14 = 28 days left in March + 14 days in April = 42 days.

Time to hire: March 20 to April 14 = 11 + 14 = 25 days.

Sourcing gap: 42 − 25 = 17 days before the right person appeared.

Time to start: April 14 to May 5 = 16 + 5 = 21 days.

Read together, the three numbers tell a story the single 42 would hide. Seventeen days went on finding the candidate. Twenty-five went on moving them from application to acceptance, of which nineteen (March 22 to April 10) sat between the screen and the offer. That middle stretch is interviews, feedback and approvals, and it is usually where the fixable days are.

Reading the gap between the two

The value of tracking both metrics is the comparison. Four patterns come up again and again:

PatternWhat it usually meansWhere to look
Long time to fill, short time to hireFinding the candidate is the problem; the process is quick once they arriveSourcing channels, job description, pay range, a warm pipeline
Short time to fill, long time to hireUnusual; often a strong internal or referred candidate who was slowed by processScheduling, feedback, approvals
Both longHard role and a slow process at the same timeFix the process first; it is the part you control
Both short, but high early attritionSpeed may have come from comparing too few candidatesFirst-year attrition and quality of hire for the same cohort

Time to hire also matters to candidates. A strong candidate who applied on day 1 does not care that the requisition opened three weeks earlier. From their side, the clock started when they applied, and every week without a decision is a week in which another employer can make an offer.

A five-role report

Here is an invented quarter for one role family, with both clocks and the gap between them.

RoleTime to fill (days)Time to hire (days)Sourcing gap (days)Hired candidate's source
A. Senior financial analyst422517Job board
B. Accounts payable lead35305Referral
C. FP&A manager611843Sourced by recruiter
D. Payroll specialist28217Careers page
E. Controller883454Agency
Median422517

The medians come from sorting each column: time to fill 28, 35, 42, 61, 88, so 42; time to hire 18, 21, 25, 30, 34, so 25. The mean time to fill would be (42 + 35 + 61 + 28 + 88) ÷ 5 = 50.8 days, pulled up almost nine days by the controller search.

The report points in two directions at once. Roles C and E had quick processes once the candidate appeared (18 and 34 days) but long searches before that, so the fix for them is sourcing lead time, not interview speed. Role B had almost no sourcing gap but the slowest time to hire in the group: a referred candidate waited 30 days for a decision, which is the kind of delay that loses referrals.

Is there a benchmark?

SHRM's 2026 Recruiting Executives Benchmarking summary reports a median time to fill of 39 calendar days for nonexecutive positions, based on data from over 4,600 organizations. The public summary does not spell out where the clock starts and stops, and it blends every industry and role level, so treat it as context rather than a target. There is no comparable widely published figure for time to hire, partly because the start date depends on how each organization records sourced candidates.

Your own trailing median, by role family, is the more useful comparison. A payroll specialist and a controller should never share a target.

Definition choices that make the numbers drift

Most arguments about time to fill are arguments about definitions. Settle each of these once, write the rule at the top of the report, and do not change it mid-year.

  • Approval date or posting date. Starting at approval captures the days a requisition sits unassigned; starting at posting hides them. Approval is the more honest start.
  • Sourced candidates. Start time to hire at first two-way contact (a reply or a call), not the day a recruiter viewed a profile. Otherwise sourced hires look slower than inbound ones for no real reason.
  • Silver medalists. A candidate who interviewed for an earlier role and was hired for this one: start their clock when they were first considered for this requisition.
  • Reopened requisitions. If an accepted offer falls through and the role reopens, either restart the clock and note it, or keep the original date and flag the row. Mixing the two produces numbers nobody can explain.
  • Requisitions with several openings. Count each hire separately: three hires against one approval date give three time-to-fill values, not one.
  • Evergreen requisitions. High-volume roles that are always open have no meaningful approval date. Report time to hire for them and leave time to fill out.
  • Paused requisitions. A hiring freeze of six weeks is not recruiting time. Either subtract documented pause days or report the paused roles separately.

Calculating both in a spreadsheet

You need one row per hire, not per requisition, with four dates. Most ATS exports have them; if yours does not, add the fields now and backfill what you can.

HIRES (one row per hire)
ReqID | Role | RoleFamily | ReqApproved | CandidateEntered |
OfferAccepted | StartDate | Source | Reopened (Y/N)

TimeToFill     =OfferAccepted - ReqApproved
TimeToHire     =OfferAccepted - CandidateEntered
SourcingGap    =TimeToFill - TimeToHire

Median time to fill for one role family (Excel 365, Google Sheets)
=MEDIAN(FILTER(TimeToFill, RoleFamily="Finance"))

Check for negative sourcing gaps. They mean a candidate's entry date is earlier than the requisition's approval date, which happens with pipelined or silver-medalist candidates. Apply the rule you chose above rather than leaving the negative number in the median.

How to report it

A useful monthly or quarterly view has one line per role family and five columns: hires, median time to fill, median time to hire, median sourcing gap, and the slowest role with a one-line reason. Show the count of hires next to every median; a median of three hires is a list, not a trend.

TIME TO FILL AND TIME TO HIRE, Q2
Definitions: fill = req approved to offer accepted; hire = candidate
entered (applied, or first reply if sourced) to offer accepted.
Medians, calendar days.

Role family   Hires  Fill  Hire  Gap   Slowest (reason)
Finance         5     42    25    17   Controller, 88 (sourcing)
Engineering     8     51    29    22   Staff engineer, 97 (pay band)
Support        14     23    12    11   Team lead, 41 (panel scheduling)

Put the process portion in front of the people who own it. Time to hire is largely made of scheduling and feedback waits, which belong to hiring managers as much as to recruiters; a recruiting SLA with hiring managers gives those waits an agreed limit. The sourcing gap belongs to the recruiting team and to whoever sets the pay range. For weekly reporting, the recruiter weekly report template has room for both.

Common mistakes

MistakeEffectFix
Using the two terms interchangeablyTwo teams report different numbers for the same roleName both clocks in every report header
Averages instead of mediansOne slow search moves the number by a weekMedians, with outliers listed
Stopping at start date for some roles and acceptance for othersNotice periods leak into some rowsStop at acceptance; report time to start separately
Counting cancelled requisitionsRoles that were never filled distort the numberFilled roles only; count cancellations on their own
Chasing speed aloneFewer candidates compared, weaker hiresReport next to quality of hire for the same cohort

Questions people ask

Is time to hire the same as time to fill?

No. Time to fill runs from the day the job was approved or opened to the day an offer was accepted, so it includes the time spent finding the person. Time to hire runs from the day the hired candidate entered your pipeline to the day they accepted, so it only measures how fast your process moved once you had them.

Which one should I report to leadership?

Report time to fill to leadership, because it answers how long a seat stays empty, which is what the business feels. Report time to hire alongside it, because the gap between the two tells you whether the delay was in finding candidates or in moving them through interviews.

When does the clock start for a candidate we sourced rather than one who applied?

Use the date of first two-way contact, such as the day the candidate replied to your outreach or had a first call, not the day you first viewed their profile. Write the rule down so sourced and inbound hires are counted the same way.

Should I use the average or the median?

Use the median. Durations are skewed by the occasional search that runs for months, and a single slow role can move the average by a week or more while the median barely changes. List the outliers separately so they are not hidden.