Time-to-Fill: The Pipeline Depth Metric That Predicts SLA Success

TL;DR: Time-to-fill is how long it takes from opening a position to hiring someone. It predicts SLA success because it shows whether your pipeline has real depth or just surface-level candidates. Most recruiting teams measure it wrong and ignore the early-stage pipeline that actually moves deals. Pipeline depth wins SLAs, not last-minute scrambling.

Why Most Companies Miss Their SLA on Recruiting

Most recruiting teams miss SLAs because they wait until a requisition is urgent to start filling it. By then, the clock is ticking and panic hiring begins. The best predictor of SLA compliance is not effort at the end. It's pipeline depth before the sprint even starts. If you have 40 qualified candidates at various stages before the deadline hits, you hit the SLA. If you have 4, you don't.

Time-to-fill measures this. It's the calendar days from when you open a role to when you make an offer that gets accepted. Most teams think shorter is always better. That's backwards. What matters is whether your pipeline can sustain that speed without drying up.

What Does Time-to-Fill Actually Measure?

Time-to-fill is the total elapsed time from job posting to accepted offer. The real metric is time-to-fill per pipeline candidate. If you need 40 days and you have 60 qualified candidates in your pipeline, you're safe. If you need 40 days and you have 8 candidates, you're exposed. Most teams don't track this. They only measure the final number and wonder why they miss SLAs.

A 40-day fill that came from 150 sourced candidates is different from a 40-day fill that came from 8 referrals. The speed matters less than the depth behind it. Most teams ignore this distinction.

How Deep Does Your Candidate Pipeline Really Go?

Pipeline depth is the number of qualified candidates at various stages of your funnel before you even need to fill a role. A healthy pipeline has 3 to 5 times as many candidates in early stages as you have open positions. If you have 10 open reqs, you should have 30 to 50 candidates somewhere in the funnel before those reqs open.

Most recruiting teams build the pipeline after the crisis starts. They post a job, wait 30 days, then panic source. By then, the best candidates are already spoken for. Teams that beat SLAs build pipeline continuously during calm periods. They source, interview, and qualify candidates when there's no urgency. When a role opens, they already have candidates ready to move.

The math is straightforward. If your average time-to-fill is 40 days and you have 2 open reqs, you need enough pipeline activity to move 4 to 6 candidates through screening, interviews, and offers during those 40 days. That's about 1.4 to 2 weeks per candidate, end to end. Most teams can't sustain that without a pre-built pipeline.

Why Candidate Velocity Predicts Whether You Make the SLA

Candidate velocity is how fast candidates move through each stage of your recruiting funnel. It's measured in days per stage: screening to interview, interview to offer, offer to acceptance. If your velocity is 7 days per stage and you have 5 stages, your time-to-fill will be around 35 days minimum. If your velocity is 14 days per stage, you're looking at 70 days. If your pipeline isn't feeding those stages consistently, velocity drops because you're hunting for candidates instead of moving them.

The team that predicts SLA success measures velocity first, then builds pipeline to sustain it. They know that if their process takes 40 days average and they need to fill 2 roles in 90 days, they need enough early-stage candidates feeding the funnel at all times. They don't rely on a last-minute surge. They rely on system consistency.

Most teams do it backwards. They measure final time-to-fill only. They don't know their velocity at each stage. They have no idea when candidates are moving too slowly. By the time they notice, the SLA is already at risk.

The Four Stages of Pipeline Depth and Where Most Teams Fail

Pipeline has four stages: sourced, screened, interviewed, and offer-ready. Most teams are strong at one stage and weak at the others. Sourced candidates are plentiful because sourcing is easy. Screened candidates are fewer because screening takes time. Interviewed candidates are rarer because interviews are expensive. Offer-ready candidates are scarce because most teams wait until they need them to build that stage.

If you source 100 candidates, you might screen 40. Of those 40, you might interview 15. Of those 15, you might make offers to 5. Of those 5, maybe 1 accepts. That's a low conversion from source to hire. Most teams respond by sourcing more. That's the wrong lever. The right lever is improving conversion at each stage so you don't need 100 candidates to hire 1.

Teams that beat SLAs focus on interview-to-offer conversion first. They make sure their interviewing process is fast and clear so candidates don't drop between interview and offer. They focus on offer-to-acceptance conversion second. They make sure offers are competitive and communicated fast so candidates accept instead of taking other jobs. By the time they get to sourcing, they need far fewer candidates because the funnel is efficient.

How to Build a Pipeline That Hits SLAs Consistently

Start here. First, measure your current time-to-fill per stage and your conversion rates at each stage. Second, calculate backwards from your SLA deadline to see how many candidates need to enter the funnel at each stage each week. Third, build sourcing, screening, and interview processes that feed those numbers automatically. Fourth, monitor velocity weekly and adjust if any stage slows down.

The best teams work in batches. Instead of reacting to one open req at a time, they source 50 candidates per quarter during slow periods. They screen batches of 20. They interview in cohorts of 8. This keeps the pipeline full and velocity high even when new reqs come in unexpectedly. When an SLA deadline arrives, candidates are already in motion. There's no panic. There's just movement.

This requires discipline. It requires sourcing and screening when there's no urgency. It requires interview slots reserved even when no candidates are ready. It requires an offer process that's fast and repeatable. Most teams skip this because it feels like overhead. Then they miss SLAs and hire in panic mode, which costs more and produces worse outcomes.

Teams that scale recruiting beyond SLA compliance build infrastructure instead of heroics. They track time-to-fill not to celebrate when they get lucky, but to predict whether they'll hit deadlines consistently. They invest in pipeline depth during calm periods. When urgency hits, they execute. That's the difference between a recruiting operation and a recruiting system.

If your recruiting operation is built around reacting to open reqs instead of building pipeline systematically, this is where you should focus. Time-to-fill won't improve until pipeline depth improves. Pipeline depth won't improve until you measure and build it intentionally. That's how teams go from missing SLAs to exceeding them consistently. The metric that predicts it is always the same: candidates in motion before the deadline arrives. Let's talk about your pipeline depth and whether it's set up to hit your next round of SLAs.