Time to hire vs time to fill, and the days screening owns

Our pilot cut the screening stage of a 3,000-applicant campaign from six to ten working days down to one or two. The question I should have asked straight away was which hiring metric that actually moved. Time to hire, certainly. Time to fill, only if screening had been the slowest part of filling the role. That gap between the two metrics is what this post is about.

Time to hire vs time to fill looks like a definitions question, and the definitions take two paragraphs. The useful part is knowing which stages move which clock, so you work on the days you can actually remove. Below: both definitions and formulas with a worked example, a third clock that Indian hiring adds, a stage-by-stage way to find where the days go, and the changes that reduce time to hire without lowering the bar.

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

Time to fill measures how long a job stays open: from the day the requisition is approved or the job is posted until a candidate accepts the offer. Time to hire measures how long your eventual hire spent in your process: from the day they applied or were sourced until they accepted. Time to fill is about the seat; time to hire is about the person.

Those are the definitions Workable uses in its guide to both metrics, and they are the ones most applicant tracking systems follow. Two details trip people up. The start of time to fill is a choice (approval, or the posting date), so pick one and never mix them across roles. And both clocks stop at offer acceptance, not at the first working day.

How to calculate both, with an example

Count calendar days, and keep the formula identical for every role you report on.

• Time to fill = offer acceptance date − requisition approval date (or posting date, if that is your rule).
• Time to hire = offer acceptance date − the date the eventual hire entered the pipeline.

A worked example. A support lead role is approved on 1 March and posted on 3 March. The person you eventually hire applies on 12 March, clears screening, two rounds and an offer, and accepts on 2 April.

The 11-day difference is sourcing: the time it took for the right person to show up. The 21 days are your process. To report an average, add up the figures for all roles filled in the period and divide by the number of roles.

The third clock: time to join

Both standard metrics stop at offer acceptance. In Indian lateral hiring, that is often far from the end. Long notice periods are common, especially at large IT employers, and a candidate who accepts in April may join in July, or not at all if a counter-offer arrives in between.

So add a third clock: time to join, from offer acceptance to the first working day, and record how many accepted offers never reach it. It does not replace the other two. It explains why a role leadership thinks is “filled” still has an empty chair. It also argues for asking about notice and joining dates in the first call, so a mismatch costs minutes rather than four interview rounds.

Where the days in time to hire actually go

An average hides the stage that is slow. Break time to hire into the gaps between stages, using the dates your ATS or tracking sheet already holds:

Look for the gap with the most waiting, not the most work. In high-volume hiring it is usually the first two: applications sit unread, then candidates and recruiters spend days finding a time to talk. In senior hiring it is more often the hiring manager’s calendar or the offer approvals.

How to reduce time to hire without lowering the bar

Each fix below names the gap it closes. Start with the one your breakdown says is slowest.

Read every resume against the role on the day it arrives. Closes the first gap. Scoring resumes against the job as they come in, rather than in weekly batches, removes the queue entirely for the clear yes and clear no.

Ask knock-out questions first. Closes part of the second gap. A candidate who cannot work the shift or join in time should be out of the process in minutes, not after a full first round.

Let candidates book their own first-round slot. Closes most of the second gap. Scheduling by email or phone tag can take longer than the interview. A self-booking link with evening slots removes the back and forth.

Log feedback the same day. Closes the third gap. Our post on interview feedback examples has a five-line format that is fast enough to write between calls.

Block final-round slots before the drive starts. Closes the fourth gap, which no tool fixes. If the hiring manager has two slots a week, time to hire has a floor you can calculate in advance.

What not to do: start the time-to-hire clock later so the number looks better, or rush the final round. A faster process that hires the wrong person shows up a quarter later in a worse metric, which is why we would track screening quality alongside speed.

Which clock does screening move?

Screening sits inside time to hire, in the first two gaps of the table. That is where HireQwik works. Resumes are scored against the role as they arrive, with the reason shown. Candidates who clear the bar get a link to book a 10 to 20 minute AI voice interview at a time that suits them, and the verdict lands within minutes of the call ending, with the transcript, the recording and every answer scored against the job’s rubric. A per-job funnel shows how many candidates are in each stage and how many missed their interview.

In the pilot, that took the screening stage from six to ten working days down to one or two, and HR’s review time from about 18 hours of profile reading down to one or two. It moves time to fill only when screening was the bottleneck in filling the role; if the slowest gap is the hiring manager’s calendar or a long notice period, fix that next.

If your first-round gap is the slow one, book a demo and bring your stage breakdown. Or take the 3-minute live AI interview to see the candidate side first.