Time to Fill vs Time to Hire: The Difference and Which to Use

Time to fill is the number of days from when a role is approved or posted until an offer is accepted. Time to hire is the number of days from when a particular candidate enters the process, usually when they apply or are first contacted, until they accept. The first describes how long the business waits to have the seat filled. The second describes how fast your process moves a candidate, which matters because strong candidates often have other offers. Track both, calculate each by role type and use them to find where time is lost, not to set a single target for everyone.

Many teams use the two terms as if they meant the same thing, which makes comparisons confusing.

Definitions and formulas

Formula for either: days from start event to end event, averaged across hires for a period, split by role type or level.

Choose the start event and stick to it. Some teams count from the posting date, others from the approval date. The approval date captures delays before you even open the role.

An example

A sales role is approved on 1 March, posted on 8 March and filled when an offer is accepted on 15 May. Candidate A applies on 20 March and accepts on 15 May.

• Time to fill from approval: 75 days.
• Time to fill from posting: 68 days.
• Time to hire for Candidate A: 56 days.

The difference is mostly the delay before posting and the time before a good candidate applied. If a competitor made Candidate A an offer in week six, the 56 days would have lost you the hire.

What each tells you

Time to fill helps with workforce planning and with the cost of a vacancy: how long a team works short-handed. It includes delays you may not control, such as approvals and notice periods.

Time to hire helps with the candidate experience and competitiveness: how long a good applicant waits between steps. It is closer to what you control inside the process. See reduce time to hire for where the delay usually sits, and note that most of it is queue time, not work time.

Where the days go

A rough breakdown for a typical process helps you decide where to look:

Track the days between each step. The largest gap is usually the best place to start. See recruiting metrics for the full set.

Compare like with like

Averages across all roles hide differences. A graduate role, a senior engineer and a seasonal job have different time scales. Split by:

• Role family and level.
• Location.
• Source of hire.
• Hiring manager, if the spread is large.

Use medians as well as averages, since a single role that stayed open for six months can distort the mean.

Do not chase speed at the cost of quality

Shortening a process by skipping steps can lead to worse hires. The aim is to remove waiting time and duplicated work, not the work that produces evidence. Fix queues first: faster scheduling, a set time for debriefs and a decision date. See interview debrief meetings and interview scorecard template.

Practical ways to improve

1. Set a service level for each stage, such as screen within three working days.
2. Pre-book interview slots with hiring managers.
3. Screen consistently and early, so good candidates are not waiting in a pile. See high-volume resume screening.
4. Hold debriefs within 24 hours of the final interview.
5. Prepare offer approvals in advance.
6. Keep candidates informed at each step. See candidate experience.

Reporting it

Show both metrics on one page for hiring managers: the target, the current figure and the stage where most time goes. Add a note on what you are changing. That keeps attention on actions, not on the number.

Automated tools can timestamp each stage and calculate these for you. Resume World's pipeline analytics show screening velocity and candidate throughput by role, which gives a reasonable picture of where applicants wait. For a manual setup, a spreadsheet with a date column for each stage works. See applicant tracking in a spreadsheet and cost per hire for the money side.