Time to Fill vs Time to Hire: Formulas, Benchmarks and Examples

Time to fill and time to hire side by side

The comparison below makes the difference immediately clear. This helps especially when several recruiters, hiring managers or agencies are working from the same figures.

• KPI: Time to fill. Definition: the total vacancy duration, from the vacancy sign-off or request through to the new hire's start date. Start point: vacancy sign-off or request date. End point: start date. Formula: end date minus start date in calendar days. What it measures: the full hiring lead time for the vacancy. Many benchmarks stop earlier, at offer acceptance.
• KPI: Time to hire. Definition: the time from first contact or application of the hired candidate through to the accepted offer. Start point: first contact or application date of the hired candidate. End point: offer acceptance. Formula: offer acceptance date minus first contact or application date in calendar days. What it measures: how quickly one candidate moves through assessment, interviews and decision-making.

What time to fill and time to hire mean in plain terms

What time to fill actually means

The meaning of time to fill is straightforward: you measure how long a vacancy stays open within your own process definition. This usually contains more steps than teams realise at first glance. Think of the intake, approval, writing the vacancy, sourcing, waiting for responses, internal alignment, interviews, the offer and the gap between acceptance and the first working day. This metric therefore shows how long it takes in total before the role is actually filled.

What time to hire actually means

The meaning of time to hire is about the candidate who is ultimately hired. This metric shows how much time sits between the first point of contact and the accepted offer. That's why this KPI is especially useful when you want to know whether CV review, interview scheduling or decision-making is running too slowly.

Why teams often confuse the difference

The difference between time to fill and time to hire looks small, because both are measured in days. Even so, they cover a different part of the same process. The total vacancy duration can be high while the hired candidate's own journey is perfectly normal. The reverse also happens. That's why you need to fix your dates in advance. Without a fixed definition, a recruitment KPI quickly becomes unreliable.

How to calculate time to fill and time to hire correctly

Formula for total vacancy duration

To calculate time to fill you use a fixed formula: the new hire's start date minus the date of the vacancy sign-off or request, measured in calendar days. Some organisations choose offer acceptance as the end point instead. That's fine, as long as you apply it consistently everywhere. Otherwise you end up comparing different processes with each other.

Formula for candidate lead time

To calculate time to hire you likewise use a fixed formula: the offer acceptance date minus the first contact or application date of the hired candidate, again in calendar days. This calculation mainly shows the speed of assessment and decision-making after first contact.

Worked example with fixed dates

Take a vacancy signed off on 1 March. First contact with the hired candidate happens on 20 March. The offer is accepted on 5 April and the start date is 1 May. The total vacancy duration then comes to 61 calendar days. The candidate's own lead time is 16 calendar days. This immediately shows why the two figures carry a different meaning, even though both are about speed.

Common measurement mistakes

The biggest mistake usually sits in the definition. One recruiter counts from the request, another from the publication date. Sometimes offer acceptance is used as the end point, sometimes the start date. You also often see teams mixing up working days and calendar days. On top of that, relying purely on an average tends to skew the picture, because a handful of difficult vacancies can pull the figure up sharply.

What a high time to fill says about your hiring lead time

If the total vacancy duration is high while the candidate's own lead time stays normal, the delay usually sits early in the process. This often points to a slow intake, late sign-off, a small talent pool, weak response rates or starting sourcing too late. In that situation, the hired candidate actually moves through the process reasonably quickly, but it simply takes too long to get that person in view in the first place.

Possible causes before candidate contact

Early delay often comes from an unclear intake, requirements that are too broad, waiting for sign-off, low response rates or a difficult target group. As a result, the vacancy stays open for a long time before the right conversations can even start. You see this a lot with scarce roles and processes that need heavy internal alignment.

How to make early delay visible

In practice, we find that a good recruitment dashboard helps make acceptance, response and funnel steps before the interview visible. That immediately clarifies whether the delay sits in outreach, follow-up or scheduling. This data doesn't automatically replace every vacancy and offer date from an ATS, so fixed definitions remain essential for a complete measurement.

When time to fill looks normal but time to hire is high

A vacancy can look fast enough overall while the eventual candidate had to wait a long time. This happens when someone comes into view early but then gets stuck in assessment, interview scheduling or internal approval. At that point the vacancy's lead time looks healthy, while the candidate experience and the risk of drop-off are under real pressure.

Possible causes after first contact

Delay after candidate contact often comes from slow CV review, too few interview slots, feedback arriving late, lengthy decision-making or an offer approval that keeps getting stuck. As a result, the average time to hire rises, even if the vacancy's total duration still looks like it falls within a reasonable range.

What agencies and corporates measure differently

Agencies often also look at the speed to shortlist, proposal or placement, because that fits their engagement structure better. For corporate recruitment teams, the total vacancy duration is often more important, combined with internal wait time per stage. That's why it's worth tailoring your reporting precisely to the context you work in.

Time to fill benchmarks by sector: how to compare fairly

A time to fill benchmark is only genuinely useful once the definition, region, year and measurement method match. That sounds obvious, but this is exactly where things often go wrong. Many public sources measure through to offer acceptance, whereas this article uses the start date. As a result, external benchmark figures can come out lower than your own internal numbers, without your process actually being any slower.

Sector benchmarks with context

• Overall, all sectors: roughly 44 days. Region: international, often the United States. Year: varies by publication. Definition: usually through to the point the vacancy is filled or the offer is accepted. Source: public market sources that can vary by year.
• Engineering: often around 49 days. Region: mostly international datasets. Year: varies by source. Definition: often through to fill, not through to the start date. Source: public benchmark reports.
• Retail: often lower, for example around 33 days. Region: mostly international datasets. Year: varies by source. Definition: often through to fill or offer acceptance. Source: public benchmark reports.
• Finance: duration often falls somewhere between retail and engineering, depending on seniority and specialism. Region: strongly dependent on the market and scarcity. Year: varies by source. Definition: regularly through to fill, not through to the start date. Source: public benchmark reports.

For extra context and up-to-date source references, take a look at our recruitment statistics. We recommend re-checking the definitions in reports like these every year, since public publications occasionally tweak their measurement method.

How to use a benchmark without drawing the wrong conclusions

Use a benchmark primarily as a diagnostic point, not as a target in itself. First look critically at the role type, scarcity, seniority, region and process setup. A specialised finance role or a senior technical position is, after all, hard to compare with high-volume retail recruitment. A benchmark therefore mainly helps you ask the right questions, rather than pass an immediate judgement.

What the average time to hire really shows

The average time to hire gives a decent first impression, but an average quickly gets skewed by outliers. That's why we prefer also working with the median and the spread. The median shows what's normal for a typical vacancy, while the spread makes clear whether delay is happening right across the board or mainly sits with a few exceptions.

How to track time to fill in a spreadsheet and reporting

Minimum fields for your sheet

You don't need heavyweight software to get off to an effective start. At minimum, use the vacancy ID, the date of vacancy sign-off or request, the date of first contact or application, the offer date, the offer acceptance date, the start date, the role type or department, the recruiter and the status. With this basic data you can track total vacancy duration and candidate lead time extremely reliably.

Work with the median and the spread

Anyone who shows only averages often misses important signals. A handful of difficult vacancies can distort the whole picture quite heavily. That's why the median and spread usually give much better steering information for recruitment managers, agencies and hiring teams who want to know exactly where structural delays sit.

Checklist before you share your figures

• Does everyone use the same starting point for the vacancy?
• Does everyone use exactly the same end point, such as offer acceptance or the start date?
• Is everyone consistently counting in calendar days?
• Are internal wait times per stage clear and visible?
• Are you genuinely comparing only similar role types, regions and periods?

Improve time to fill with targeted fixes per cause

Earlier intake and sharper target group analysis

A clear intake often shortens the very first phase of the process. So set out early on what's genuinely needed for the role and which requirements matter less. This prevents needless restarts, hesitation and searching within a target group that's far too broad. It helps enormously, especially when vacancies drag on for too long before sourcing properly gets going.

Faster sourcing and better follow-up

When outreach starts too late or responses sit around for too long, the total duration climbs quickly. In the Manpower case study you can clearly see how a faster review workflow significantly cut manual work. This helps a lot at the front end of the process, although the rest of the hiring lead time naturally still depends on interviews and decision-making.

Fixed interview slots and short feedback deadlines

Paradoxically, a lot of delay appears once a good candidate is already in view. That's why it helps to book fixed interview slots straight away and agree clear, tight deadlines for feedback. This stops candidates sitting in a waiting room unnecessarily and keeps the flow a lot more predictable.

Make follow-up visible and prevent stalling

Recruitment teams often lose valuable speed when responses, evaluations or approvals sit between different departments. So make it very clear per stage who's responsible and how long a particular task has been open. This gives you much more grip straight away, without unnecessarily complicating the process.

A practical next step

If you want to start small, try this with a single vacancy and track closely, stage by stage, where time gets lost. Pick one clear definition, measure every vacancy the exact same way, and then discuss as a team which step causes the most delay. That makes improving your process very concrete and genuinely doable.

Check your definitions before you report

Good reporting always starts with one clear agreement that everyone sticks to. Set out clearly what the starting point is, what the end point is, and exactly how you count. Then work out which delay happens before first candidate contact and which delay only happens afterwards. Only once that's in place do comparisons between different teams, roles and periods actually become useful.

Frequently asked questions

Which matters more, time to fill or time to hire?

This depends entirely on your goal. If you want to know how long it takes in total to fill a vacancy, the total vacancy duration matters more. If you want to know how quickly a candidate moves through selection and decision-making, the candidate's own lead time is far more useful. Most teams need both figures to steer effectively.

Do you count in calendar days or working days?

We'd recommend calendar days, since it's simply the most unambiguous option and usually lines up much better with external benchmarks. The single most important point, though, is consistency. Once you choose calendar days, everyone needs to apply that exact same method.

Why does my time to fill differ from public benchmarks?

In most cases this comes down to a different definition of the end point. Many benchmarks measure through to offer acceptance, or through to the point the vacancy is officially considered filled. In this article, we instead measure through to the start date. As a result, the number of days logically often comes out a bit higher.

Can you measure time to hire when several candidates are in process at once?

Yes, absolutely. You then measure only the candidate who is ultimately hired. The start point in that calculation is the first contact or application of that specific person, and the end point is that same person's eventual offer acceptance.

What's a good first step if our figures aren't reliable right now?

Always start with one fixed definition for the start point, the end point and the unit of measurement. Then transfer the minimum fields into a spreadsheet or ATS and periodically check that everyone applies the same inputs. Without that kind of solid foundation, benchmark comparisons unfortunately carry very little value.