Reviewed by Daniil Lokhanin · Updated

HR analytics is the practice of collecting and analysing employee and HR data to make better people decisions: who to hire and from where, why people leave, what drives performance and what the workforce will need next. It turns HR from opinion-based to evidence-based. HR analytics is built on HR metrics, the individual measurements such as turnover rate or cost per hire, and applies them across the employee lifecycle, from recruitment analytics to retention and performance.

A typical use: HR notices that turnover in one department is double the company average, breaks it down by tenure and manager, finds that most leavers quit in their first year under two specific managers, and targets onboarding and manager coaching there. Without the data the problem would surface only in exit interviews, one person at a time.

HR metrics: the building blocks

HR metrics quantify how well HR activities work and whether they support business goals. Which ones matter depends on the organization, but most teams start with:

  • Turnover rate: how many people leave relative to the workforce.
  • Cost per hire and time to fill: what hiring costs in money and time.
  • Engagement: survey results on how committed people are.
  • Training effectiveness: whether learning changes performance.
  • Absenteeism and headcount: basic workforce health.

The most common formula in HR analytics is turnover rate:

Turnover Rate=(Number of SeparationsAverage Number of Employees)×100\text{Turnover Rate} = \left( \frac{\text{Number of Separations}}{\text{Average Number of Employees}} \right) \times 100

Example: 18 people left during the year and average headcount was 240, so turnover is 18 / 240 × 100 = 7.5%. Average headcount is usually (headcount at start + headcount at end) / 2.

Recruitment analytics

Recruitment analytics applies HR analytics to hiring: sourcing, screening, interviewing, offers and onboarding. It answers questions such as which channels bring candidates who get hired and stay, where candidates drop out, and which stage slows the process down. Core recruitment metrics are time to fill, time to hire, source of hire, offer acceptance rate, candidate conversion rate between stages, quality of hire and cost per hire:

Cost per Hire=Total Recruitment CostsNumber of Hires\text{Cost per Hire} = \frac{\text{Total Recruitment Costs}}{\text{Number of Hires}}

Total recruitment costs include job advertising, agency fees, recruiter salaries, assessment tools and any other hiring spend. For example, $60,000 spent on 20 hires is a cost per hire of $3,000. Small businesses benefit from recruitment analytics as much as large ones: knowing which job board or which job description brings the best applicants lets a small team spend a limited budget where it works. Recruitment analytics also improves candidate experience, because finding bottlenecks usually means faster answers for candidates.

Recruitment metrics dashboard

A recruitment metrics dashboard puts the main hiring KPIs on one screen: open roles, time to fill, cost per hire, source of hire, pipeline by stage, offer acceptance rate, quality of hire, candidate experience ratings and, where tracked, diversity of the pipeline. Its job is to show problems early: a role stuck in the interview stage, a channel that brings volume but no hires, a recruiter with a growing backlog. Update it in real time or at least weekly, and keep it short; a dashboard with 40 metrics is read by nobody.

Historical hiring trends

Historical hiring trends are patterns found in your own past recruiting data: how many people you hired per quarter and in which roles, how time to fill and cost per hire changed, which channels grew or declined, and how labor market changes affected you. They are the basis for workforce planning and recruitment budgets: if you hire 15 sales reps every spring and it takes 45 days each, you know when to start. Past patterns are a guide, not a guarantee; economic changes, new technology and new business lines can break them.

Predictive hiring analytics

Predictive hiring analytics uses historical data and statistical models to estimate how likely a candidate is to succeed or stay in a role. It combines structured data (assessment scores, years of experience) with unstructured data (interview notes, written answers) and applies methods such as regression, decision trees or other machine learning models. It can make screening more consistent, but it is only as good as the data behind it: if past hiring decisions were biased, the model will repeat that bias. Audit models regularly, validate predictions against real outcomes, keep humans responsible for decisions, and check local rules on automated decision-making in hiring before using such tools.

Levels of HR analytics

  1. Descriptive: what happened (turnover last year, hires per month).
  2. Diagnostic: why it happened (turnover by manager, tenure, pay band).
  3. Predictive: what is likely to happen (attrition risk, hiring needs next year).
  4. Prescriptive: what to do about it (which intervention is likely to work best).

Most companies of 50–1000 people get the most value from solid descriptive and diagnostic work: clean data in the HRIS and ATS, consistent definitions, and a few metrics reviewed every month. Common tools are the HRIS, the applicant tracking system, spreadsheets, business intelligence and data visualization tools, and statistics languages such as R or Python for deeper analysis.

How it works in Skailer

In Skailer, HR analytics reads the records HR updates every day: built-in reports cover headcount, retention and turnover, pay as gross, net or total cost of employment, the hiring pipeline and time off balances, and a click on a chart value opens the people behind it. People analytics groups employees by any profile field, adds metrics such as count, sum or average, and saves the result as your own report, exported to XLSX. Each report has its own permission.

FAQ

HR metrics are individual measurements, such as turnover rate, cost per hire or time to fill. HR analytics is the practice of combining and analysing those metrics and the underlying data to explain causes and support decisions.

You might also like