Recruitment Analytics: Build a Dashboard You Can Trust

Recruitment analytics means using hiring-process data to understand where candidates come from, how they progress, what hiring costs, and what happens after someone joins. An applicant tracking system (ATS) can supply much of the data. AI is optional: a spreadsheet can answer useful questions if its records and definitions are consistent.

Start with a decision, not a dashboard. “Why are candidates waiting after interviews?” needs stage timestamps and feedback turnaround. “Did AI screening improve hiring?” needs evidence about time saved, screening errors, candidate access, and subsequent outcomes—not just the number of résumés scored.

Six metrics worth defining first

These are workable dashboard definitions, not universal standards. Document your chosen start dates, end dates, exclusions, and denominators before comparing teams or periods.

Metric	Suggested calculation	What to investigate
Time to fill	Calendar days from requisition approval to offer acceptance	Approval, sourcing, interview, or offer delays
Time to hire	Calendar days from a candidate’s application or first sourcing engagement to offer acceptance	How quickly the eventual hire moved through selection
Stage conversion	Applications advancing from a stage ÷ applications entering it × 100	Where progression changes—and why
Candidate withdrawal rate	Applications withdrawn by candidates at a stage ÷ applications entering that stage × 100	Scheduling friction, assessment burden, or competing offers
Offer acceptance rate	Accepted offers ÷ offers accepted or declined by candidates × 100	Pay, job expectations, timing, and competing opportunities
Cost per hire	Defined internal and external recruiting costs ÷ hires in the reporting period	Spending changes, alongside speed and hiring outcomes

Publish counts beside percentages. For the offer-response definition above, label pending, expired-without-response, and employer-rescinded offers separately; do not silently treat them as candidate declines. For costs, state whether recruiter labor, advertising, agencies, assessments, and onboarding are included, and use the same basis over time.

Check the software’s definitions too. As of October 24, 2026, Workable’s time-to-hire documentation ends its clock when a candidate is moved to “hired,” not necessarily when an offer is accepted. For accounts with its Hiring plan set up, the time-to-fill calculation excludes requisition hold periods. Those numbers cannot be compared directly with a dashboard using different endpoints or counting all calendar days.

For elapsed-time metrics, show the median alongside the average and the number of observations. Also list candidates currently waiting: a quick process for completed hires can coexist with a large unresolved backlog.

Make the funnel describe one group

A common reporting mistake is dividing interviews conducted this month by applications received this month. Some interviewees applied earlier; some new applicants have not reached interviews yet. That ratio is activity, not a reliable conversion rate.

Use three views for three questions:

• Cohort: What happened to applications received during a defined period?
• Activity: What interviews, offers, and decisions happened during that period?
• Snapshot: Who is waiting at each stage on a particular date?

Greenhouse’s reporting documentation makes this distinction explicitly and warns that combining differently filtered reports can combine different candidate groups.

For each cohort, state the observation cutoff and separate advancement, employer rejection, candidate withdrawal, and pending cases. A recent cohort will usually need more follow-up time before its final conversion can be interpreted. Our worked hiring-funnel example shows how to keep those outcomes distinct.

Then check the underlying records:

• Use an application-to-job identifier so one person applying to two roles is not accidentally collapsed into one application. Count each application once per stage in the conversion calculation, rather than counting repeated stage entries.
• Audit duplicate records, missing timestamps, reopened requisitions, and stage reversals.
• Decide how skipped stages count. Greenhouse’s pipeline report, for example, counts candidates who bypassed a stage toward its stage total.
• Record source-attribution rules. First-touch source and the source credited at hire answer different questions.

Test AI improvements against errors and outcomes

“Screening time fell” is a measured process result. “The tool finds better employees” is a separate claim requiring separate evidence.

Before a pilot, define comparable roles, a baseline period, and success criteria. Track recruiter minutes per application, manual corrections, withdrawals, technical failures, and decisions reversed after human review. Compare similar job families and hiring conditions; a change in applicant volume or role difficulty can distort a simple before-and-after comparison.

Include a job-related human review of a sample of screened-out applications. Otherwise, reviewing only shortlisted candidates leaves you unable to examine qualified applicants the process missed. Use consistent criteria and, where practical, keep reviewers unaware of the AI result until they have made their assessment. Human review is a check, not an error-free benchmark.

Post-hire measures can include retention at a fixed tenure and performance against a predefined role rubric. Keep them separate rather than hiding them inside an unexplained “quality-of-hire” score. Neither retention nor a manager rating alone proves the screening tool caused better outcomes.

Add fairness and candidate-experience checks

Break down results by relevant job, location, and process version before relying on organization-wide averages. Where demographic analysis is lawful and appropriate, compare group selection rates and report sample sizes and missing data.

In U.S. federal guidance, the four-fifths rule divides a group’s selection rate by the highest group selection rate. A ratio below 80% generally indicates adverse impact. The EEOC-hosted guidance describes this as a rule of thumb, not a legal definition: a ratio at or above 80% does not establish an absence of discrimination, and small samples can make the comparison unreliable. An operational dashboard is not automatically a legally sufficient bias audit.

The EEOC also advises employers to ensure selection procedures are validated for their positions and purposes; vendor documentation does not remove the employer’s responsibility. This is informational guidance, not legal advice. Confirm applicable requirements with qualified counsel.

For candidates, withdrawal data needs interpretation, not blame. Ask for optional feedback about delays, assessment time, accessibility, and technical problems. Keep analytics access restricted and report aggregates where possible.

Finish each review with one action, an owner, and a follow-up date: shorten an unnecessary assessment, fix scheduling delays, or investigate a screening rule. The dashboard earns its place when it changes a specific hiring decision—not when it displays more charts.