If your hiring team is growing, start with seven recruitment metrics: time to fill, time to hire, source quality, stage conversion rate, pipeline speed, offer acceptance rate, and quality of hire. Together, they answer the basic questions every recruiter, founder, or hiring manager needs first: How long is a role open? How long do candidates wait? Which channels bring usable people? Where does the funnel slow down? And, after someone joins, did the hire actually work?
That is the practical difference between tracking numbers and using recruitment KPIs well. A metric is just a measure. A KPI is a measure tied to a goal. So, do not start by chasing a benchmark you saw somewhere else. Start by defining each measure the same way every time, then use it to spot friction in sourcing, screening, feedback, and scheduling. For most growing teams, the fastest wins usually show up in stage time and stage conversion, because those expose the messy parts of the process fast.
The seven recruitment metrics, at a glance
Before digging into each one, it helps to see how the seven fit together. Some measure speed, some measure quality, and some measure flow. Use them together, because one number rarely tells the full story.
| Metric | Plain-language question | Starter calculation | What it can reveal |
|---|---|---|---|
| Time to fill | How long from requisition open to accepted offer? | Offer acceptance date − requisition opening date | Overall vacancy duration |
| Time to hire | How long does one candidate spend in the process? | Offer acceptance date − application date | Candidate-facing process length |
| Source quality | Which source produces candidates who fit? | Qualified candidates from a source ÷ candidates assessed from that source × 100 | Useful candidates, not just volume |
| Stage conversion rate | What share moves from one step to the next? | Candidates advancing ÷ candidates entering the stage × 100 | Screening mismatch or handoff friction |
| Pipeline speed | Where do candidates spend time? | Stage exit date − stage entry date | Review, feedback, and scheduling bottlenecks |
| Offer acceptance rate | Do candidates accept offers? | Accepted offers ÷ offers extended × 100 | Timing, expectations, or experience issues |
| Quality of hire | Did the hire meet expectations after joining? | Team-defined post-hire review result | Whether speed also produced a fit hire |
The key thing to remember: these recruitment metrics are not universal targets. They are tools for diagnosis. And because the calculations for source quality and quality of hire depend on your own definition, set those rules before you compare results.
What is time to fill?
Time to fill is the number of calendar days from opening a requisition to a candidate accepting the offer. It measures the full vacancy lifecycle, not just the part after someone applies. Use one consistent opening event for every role, such as approval or formal opening, and stop the clock at acceptance, not the first day on the job.
For example, if a requisition opens on June 1 and the offer is accepted on July 1, the time to fill is 30 calendar days. That sounds simple, but teams often mix definitions. Some start at job publication, while others start at requisition approval. Pick one and stick to it.
This is the broadest speed metric in the set because it includes sourcing time, screening time, interview time, and offer time. If it starts rising, do not guess at the cause. Check sourcing, manager feedback, and scheduling. Also, do not treat an open role as a zero-day fill. It is unfinished, not fast.
A useful habit here: keep paused or reopened requisitions labeled consistently. Otherwise, your time to fill data gets muddy very quickly.
How is time to hire different?
Time to hire measures the candidate’s journey, not the whole vacancy’s life. For an applicant, it starts at application and ends at accepted offer. That makes it narrower than time to fill. In the same example, if the candidate applied on June 10 and accepted on July 1, the time to hire is 21 days.
That difference matters. A role can have a long time to fill but a short time to hire, which usually suggests that sourcing took longer than evaluating the eventual hire. On the other hand, a long time to hire often points to screening, interviews, feedback delays, or offer decisions.
For sourced candidates, some teams start the clock at first approach or entry into the process instead of application. That is fine, but label it clearly. Otherwise, you will compare clocks that do not mean the same thing. And that is how teams end up arguing about numbers instead of fixing the process.
Time to fill vs time to hire
| Measure | Starts when | Ends when | Best used for |
|---|---|---|---|
| Time to fill | Requisition opens | Offer is accepted | Vacancy duration |
| Time to hire | Candidate enters process | Offer is accepted | Candidate journey |
| Pipeline speed | Candidate enters or exits a stage | Candidate leaves that stage | Stage bottlenecks |
If you only pick one speed measure early on, use the one that matches the problem you are trying to solve. If the vacancy is staying open too long, use time to fill. If candidates are waiting too long once they enter the funnel, use time to hire and stage timing together.

What does source quality measure?
Source quality asks whether a channel produces candidates who meet the role’s requirements, not just how many applications it sends. That is the right question for hiring teams that are drowning in volume but still not finding fit.
A simple starter definition is the percentage of candidates from a source who pass the same agreed screen. For example, if a job board yields 6 qualified candidates out of 60 assessed, that is 10%. If referrals yield 6 qualified candidates out of 15 assessed, that is 40%. Both sources produced six qualified people, but one source was far more efficient.
That is why source volume and source quality are not the same thing. A channel can send a lot of applicants and still produce very few people who make the cut. Another channel can send fewer applicants but more useful ones.
Use consistent source labels, especially when candidates touch more than one channel. Compare sources within similar roles and time periods, because different job types behave differently. Also, keep small denominators in mind. A source with only a handful of candidates can look wildly better or worse just because the sample is tiny.
CVViZ provides recruitment analytics that help teams examine sourcing-channel performance. More importantly, it keeps candidate records, source information, and stage history together, which makes a basic source-quality view possible in the first place.
What is a stage conversion rate?
A stage conversion rate is the share of candidates who move from one hiring stage to the next. It is one of the most useful recruitment KPIs because it shows where people stop moving forward.
Here is the basic formula: candidates advancing from a defined stage ÷ candidates entering that stage × 100. So if 100 people apply, 20 pass initial screen, and 10 reach interview, application-to-screen conversion is 20%. Screen-to-interview conversion is 50%. Those are different numbers, and they answer different questions.
This is where teams often get sloppy. Some reports use a cumulative denominator, while others use the immediately previous stage. Neither is wrong, but you have to label the denominator. If you do not, the funnel looks better or worse than it really is.
A low conversion rate does not automatically mean the screen is broken. Sometimes it means the requirements are too narrow. Sometimes it means the channel brought in a poor fit. And sometimes it means the stage definition itself is unclear. So, use this metric as a pointer, not a verdict.
Adjacent-stage vs cumulative conversion
| Type | Denominator | Example | What it tells you |
|---|---|---|---|
| Adjacent-stage conversion | Candidates entering the previous stage | 2 of 3 interviewees advance | Step-to-step movement |
| Cumulative conversion | All initial applicants | 10 of 100 applicants reach interview | Funnel-wide movement |
If you are trying to understand where candidates disappear, start with adjacent-stage conversion. It is usually the cleaner signal.
What is pipeline speed?
Pipeline speed is the time candidates spend moving through the stages of the hiring process. In practice, that means looking at how long a candidate sits in screening, interview, feedback, or scheduling before moving on.
The simplest version is time in stage: record when a candidate enters a stage and when they leave it. If four candidates spend 1, 2, 5, and 8 days in a stage, the average is 4 days and the median is 3.5 days. That is not a benchmark. It is just a clean way to see the shape of the delay.
This measure is useful because it shows where the process slows down, even when conversion stays fine. A stage can convert well and still make candidates wait too long. For example, a pileup in initial review often means resume screening capacity is tight. A long pause after interview often means feedback or decision-making is slow.
Also, keep waiting candidates visible. If you only look at completed cases, the people still sitting in the queue disappear from view. That can make a bottleneck look smaller than it really is.
Pipeline speed and stage conversion should always be read together. One tells you how many move. The other tells you how long they wait.
What does offer acceptance rate tell us?
Offer acceptance rate is the share of offers extended that candidates accept. The formula is simple: accepted offers ÷ offers extended × 100. If a team extends 4 offers and 3 are accepted, the rate is 75%.
This number does not just point to compensation. Timing, benefits, role expectations, company values, and candidate experience can all affect the result. So, when an offer is declined, treat it as a conversation, not an automatic verdict.
It also helps to show the offer count next to the percentage. A small team’s rate can swing a lot when only a few offers are involved. That is normal. Just do not overread it.
One important distinction: an accepted job offer is not the same thing as a person starting work. For the metrics in this article, the accepted offer ends the clock for both time to fill and time to hire. Start date is a different event.
If you are tracking recruitment metrics for the first time, this one is a useful reality check. A healthy funnel that ends in repeated declines still needs attention.
Why include quality of hire in a beginner’s set?
Quality of hire asks whether the person hired actually succeeds after joining. It is the best check against speed-only thinking, because a fast process is not useful if it produces weak hires.
Unlike time to fill, there is no single universal formula. A practical starter method is to agree before hiring on a few role-relevant expectations and a review point, then record whether each new hire meets them. For example, if 3 of 4 assessed hires meet the team’s pre-agreed criteria, that is 75% under that team’s definition. It is not a universal benchmark.
Keep the criteria clear. State the review date. And do not judge hires who have not yet been reviewed. That sounds obvious, but teams often rush to label a hire too early because they want a clean report.
Longer-term retention can add context, but it should not be treated as the whole story. Quality of hire is a lagging measure, which is why the other six matter while the team waits for post-hire evidence.
In other words, this metric closes the loop. It tells you whether your process did more than move people through stages. It tells you whether it found the right people.
One practical measurement sequence
If your team is just getting started, do not try to measure everything at once. Use a simple sequence instead.
- Map the stages. Write down requisition open, application or first contact, screen, interview, offer, and offer accepted. If you are measuring quality of hire, add a post-hire review point.
- Choose one clock. For the basics in this article, use calendar days for time to fill. Then decide whether candidate and stage durations also use calendar days.
- Capture the core fields. Record requisition dates, source, application or approach date, stage entry and exit, offer result, and post-hire outcome.
- Review comparable groups. Look at one role or similar roles. Keep unresolved candidates visible, and show counts beside the percentages.
- Investigate one friction point. Compare candidate source quality with application volume, stage time with stage conversion, and declined offers with candidate feedback.
- Close the loop after hire. Check the post-hire review so speed does not become the only goal.
That is enough to start turning raw hiring activity into usable recruitment KPIs without turning your team into spreadsheet janitors.
What is the simplest way to think about these seven metrics?
If you want the shortest useful summary, think of the seven in three groups. Time to fill and time to hire measure speed. Source quality, stage conversion rate, and pipeline speed show where candidates come from and where they get stuck. Offer acceptance rate and quality of hire tell you whether the process ends well.
That is why these are the first recruitment metrics a growing team should learn. They are not advanced, and they are not decorative. They are the basic dashboard for understanding whether hiring is moving, where it slows down, and whether the result is worth the effort.
CVViZ supports that kind of measurement by keeping applications, resumes, source information, messages, notes, and stage history in one connected candidate record. That does not solve hiring by itself. But it does make consistent tracking far easier than juggling spreadsheets, inboxes, and separate job boards.
FAQ
Which recruitment metrics should we track first if we only have spreadsheets?
Start with requisition-to-acceptance time, applicant-to-acceptance time, source and qualification counts, and timestamps for one or two stages where work stalls. Then add offer outcomes and later post-hire reviews. That gives you a useful first pass without building a complex reporting system.
Is time to hire the same as time to fill?
No. Time to fill begins when the requisition opens. Time to hire begins when the candidate enters the process, usually at application or first contact for sourced candidates. They measure different things, so they should not be used interchangeably.
What is a good time to fill?
There is no universal good number for every role. A descriptive median can give context, but it is not a goal for every team. Compare similar roles using the same definition before drawing conclusions.
Why do we have many applicants but few interviews?
Usually, the issue is not just volume. Compare channel-specific source quality, application-to-screen conversion, and screen-to-interview conversion. That usually tells you whether the problem is the source mix, the screen, or both.
Does an accepted offer prove quality of hire?
No. Accepted offer is a recruiting outcome. Quality of hire requires post-hire evidence against agreed criteria.



