Recruitment analytics
Recruitment analytics is the practice of using hiring data to answer a defined decision question, from source performance to stage delays and hiring outcomes. It is a discipline, not a dashboard or a recruitment CRM.
Useful recruitment analytics starts with a decision and a stable definition. A chart only helps when both are clear.
Start with the decision
Recruitment analytics connects hiring data to a question someone can act on: which source should receive the next budget, where does a search wait, or does a change in screening improve later outcomes? It can combine time to hire, cost per hire, funnel conversion rate, and outcome measures, but a collection of unrelated cards is not yet analysis.
It is also narrower than people analytics, which can cover workforce questions after someone joins. A recruitment CRM stores and manages candidate relationships. Recruitment analytics interprets the records produced by a hiring process.
Check the definition before trusting the comparison
An apparent source difference may come from attribution rules; an apparent speed difference may come from different clock endpoints. Greenhouse’s time-to-hire by candidate documentation illustrates the point by specifying the events its report uses. Define the population, period, outcome, and exclusions before deciding that one team or channel is outperforming another.
The same applies to pipeline delay. Join’s pipeline-management documentation describes sorting candidates by time spent in stage. That is a visible operational signal. It does not, by itself, establish why a stage is slow or whether changing it will improve hiring quality.
Choose the smallest useful cut
For a small hiring team, one decision and a narrow comparison often beat a broad reporting project. Compare a single role family or source across compatible periods, then inspect the records behind an unusual result. More reporting is rarely the first cure for weak data definitions. Establish the question and the cohort before adding another metric.