Recruitment Metrics That Matter, and How to Read Them

Five metrics carry most of the signal in hiring: time to hire, cost per hire, source of hire, pipeline conversion, and offer acceptance rate. Track them together, because any one on its own can point you at the wrong fix.

• Time to hire shows speed. Break it down by stage to find the delay.
• Source of hire shows which channels actually produce hires.
• Conversion shows where in the pipeline you lose people.

Why do recruitment metrics matter?

Without numbers, every conversation about hiring is a matter of opinion. Someone says it feels slow, someone else says the candidates are weak, and there is no way to settle it or act on it. Recruitment metrics replace that with evidence. They tell you where the process is slow, where you lose good people, and which of your channels and choices are working.

The caution is that a metric read alone can mislead. A short time to hire looks great until you notice your offer acceptance rate has cratered because you are rushing. The value is in reading a small set together, so each one checks the others. What follows is that small set.

Time to hire and time to fill

Time to hire measures the days from a candidate entering your pipeline to accepting an offer. Time to fill measures from the role opening to the same acceptance, which includes the sourcing lead time before anyone applied. The two answer different questions: time to hire is about how efficiently you process a candidate, time to fill is about how long a seat sits empty.

The headline number is almost useless on its own. What makes it actionable is breaking it down by stage: days in screening, days in scheduling, days in approval. That breakdown almost always reveals that most of the total is queue time between stages rather than the interviews themselves, which is exactly the pattern we found when we cut a cycle from 41 days to 18.

Cost per hire

Cost per hire adds up everything you spent to make a hire, job board fees, agency commissions, tooling, and the time your team put in, then divides by the number of hires. It is the metric finance asks about, and it is easy to game by cutting the wrong corners, so treat it as a budgeting input rather than a target to minimise.

The useful move is to pair cost per hire with source of hire. A channel can look cheap per application and expensive per hire if it produces volume that never converts. Looking at cost through the lens of which sources actually deliver people who get hired is what turns this from an accounting number into a decision about where to spend.

Source of hire

Source of hire tells you where your actual hires came from: referrals, a specific job board, your careers page, or direct outreach. It is one of the highest-leverage metrics because it directs your sourcing spend. If referrals produce a third of your hires at almost no cost, you invest in the referral programme. If a paid board produces volume but no hires, you stop paying for it.

The only requirement is that you capture the source on every application, consistently, from the start. Done by hand this decays fast. An applicant tracking system tags the source automatically as candidates arrive, so the data is reliable enough to act on. Our feature set covers how that capture and reporting works in RabbitHR.

Pipeline conversion and stage drop-off

Conversion is the percentage of candidates who move from one stage to the next, and the drop-off is where they leave. Read across your pipeline, it shows exactly where the process leaks. A sharp drop from screening to interview might mean your screen is too harsh or your sourcing is off target. A drop from offer to acceptance points at compensation or a slow, cold candidate experience.

Conversion is also how you size a pipeline. If you know your historical rates from application through to offer, you can work backwards from one hire to the number of applicants you need at the top, and stop guessing whether a role has enough candidates in it. That turns pipeline reviews from anxious into arithmetic.

Offer acceptance and quality of hire

Offer acceptance rate is the share of offers that get signed. A falling rate is an early warning that something upstream is wrong: compensation is off market, the process took too long and a competitor moved first, or the candidate experience left people cold. Because it sits at the end, it is where the cost of problems earlier in the process finally shows up.

Quality of hire is the hardest metric and the most important, because a fast, cheap process that hires the wrong people is a failure dressed as success. There is no single clean measure, but proxies like performance ratings at six and twelve months, ramp time, and early attrition tell you whether your process is selecting people who last. Watch it alongside the speed metrics so you never optimise time to hire at the cost of who you hire.

How do you read these metrics together?

No single metric is a verdict. Read them as a set that checks itself. Fast time to hire is only good if offer acceptance and quality of hire hold up. Low cost per hire is only good if the cheap sources actually convert. Strong conversion at the top is only good if it holds all the way to acceptance. When the numbers disagree, the disagreement is the insight, it tells you exactly where to look.

You do not need an analytics team to do this. If you run hiring through an applicant tracking system, every stage change and source is recorded as it happens, so these metrics fall out of the data rather than requiring a spreadsheet you maintain by hand. For the step-by-step process these numbers measure, see our guide to the hiring process steps, and the AI recruiting page for how ranking keeps screening fast without hurting quality.