How to Track Recruiting KPIs in an ATS

Most hiring teams already have the data they need to track recruiting KPIs in an ATS. The problem is that the data is often messy, because stages, sources, scorecards and disposition reasons are used differently by each recruiter or hiring manager.

That is why teams end up exporting reports into spreadsheets. The ATS has dashboards, but nobody trusts them enough to use them in a weekly hiring meeting.

A useful KPI setup starts with operations, not charts. You define the workflow, require clean fields, standardise source attribution, build dashboards for each audience, set alerts and review bottlenecks on a fixed cadence.

The ATS can then show what is slowing hiring down. It cannot fix weak process discipline by itself.

What recruiting KPIs should you track in an ATS?

Track the KPIs that help you make hiring decisions this week. A long dashboard full of vanity metrics is worse than a short one that shows where candidates are stuck.

Start with speed metrics: time-to-fill, time-to-hire and time in stage. Time-to-fill tells you how long a role takes from opening to hire, while time in stage shows whether the bottleneck is screening, interviews, offers or approvals.

Then add funnel metrics: application-to-screen conversion, pass-through rates, interview-to-offer ratio, offer acceptance rate and candidate drop-off rates. These show whether the problem is volume, quality, process speed or candidate experience.

Source metrics need more care. Candidate volume by source is useful, but source quality depends on downstream conversion into interviews, offers and hires, not on how many applications a job board produces.

For process health, track scorecard completion, interview feedback timeliness, hiring manager responsiveness and overdue candidate follow-up. These are less glamorous than time-to-fill, but they explain why time-to-fill gets worse.

Leadership usually needs a smaller set: hiring plan progress, open roles by department, accepted offers, forecast versus plan, recruiter workload, cost or ROI where the data exists, and diversity reporting where it is legally and operationally appropriate.

Before tracking KPIs, how do you clean up your ATS workflow?

Clean the workflow before you build reports. Greenhouse’s own reporting guidance starts with accurate, clean and consistent data, and that rule applies to every ATS.

Define one standard set of recruiting stages across the company. You can still have role-specific interview steps, but the reporting stages need enough consistency to compare roles without manual translation.

The required fields matter as much as the stages. At minimum, require source attribution, disposition reason, offer status, recruiter owner, hiring manager owner, department, location and job family where those fields affect reporting.

Standardise the definitions that seem obvious. Decide what counts as opened, filled, hired, rejected, withdrawn and offer accepted, because small differences in those definitions can distort every report.

Use scorecards and interview kits consistently if you want pass-through rates to mean anything. If one team completes structured scorecards and another leaves notes in Slack, the dashboard is comparing process discipline rather than candidate quality.

Write rules for edge cases before they appear in an executive report. Reopened roles, evergreen roles, internal candidates, agency candidates, pending offers and candidate withdrawals all need clear treatment.

How do you build a recruiting KPI dashboard in an ATS?

Build dashboards around jobs people need to do, not around every metric the ATS can display. Recruiters, hiring managers, talent leaders and executives need different views of the same hiring funnel.

A recruiter dashboard should focus on today’s work. Show active pipeline, candidates by stage, ageing candidates, upcoming interviews, overdue feedback and follow-up tasks.

The limitation is that recruiter dashboards can become task lists with no management context. Add time in stage and pass-through rates so recruiters can see whether their pipeline is moving, not just whether it is full.

A hiring manager dashboard should show open roles, stage bottlenecks, candidate movement, interview completion and scorecard completion. Keep it simple, because most hiring managers will not study a dense analytics view.

A talent leader dashboard should cover time-to-fill, time-to-hire, time in stage, pass-through rates, source effectiveness, offer acceptance, diversity metrics where appropriate and recruiter workload. This is the operating dashboard for weekly pipeline reviews.

An executive dashboard should be smaller again. Show hiring plan progress, forecast, accepted offers, critical roles, hiring velocity and cost or ROI where the underlying data is reliable.

Scheduled reports and alerts matter because dashboards are easy to ignore. A weekly email, Slack alert or SLA warning turns reporting into an operating rhythm rather than a monthly slide.

How do you make source tracking reliable?

Source tracking only works if every candidate has one clear source rule. Without that rule, the same candidate can be counted as job board, referral, agency and recruiter-sourced depending on who touches the record last.

Define a source hierarchy. For example, decide whether first touch, last touch, credited source or recruiter-selected source is the reporting standard, then apply it across every role.

Separate source volume from source effectiveness. A job board that produces 500 weak applications may look successful in a volume report, but a referral channel that produces 12 interviews and 3 hires may be the better source.

Track downstream conversion by source where the ATS supports it. The useful view is application to screen, screen to interview, interview to offer, offer to hire and, if your systems support it, retention after hire.

Be careful with paid channels. Job-ad costs, agency fees and source costs are often stored outside the ATS, or they sit in marketplace pages rather than normal reports.

Greenhouse, for example, says some third-party Job Ad Market purchases cannot be edited or refunded after confirming the purchase, and some ads can take up to 10 business days to publish. Cost information is available on the Sourcing page rather than in reports, so cost analysis may need extra work.

Which ATS tools are strongest for recruiting KPI tracking?

Ashby is the strongest fit if you need analytics depth and custom KPI logic inside the recruiting platform. ATSLab ranks Ashby second overall, behind Breezy HR, and records its entry price at $400 per month for teams up to 100 employees.

Ashby Analytics includes out-of-the-box reports, templates, a report builder, filtering, segmentation, drill-down, Slack and email SLA alerts, DEI tracking, hiring goals and recruiting planning. The catch is that Ashby is a better match for scaling teams than for tiny companies that only need a simple pipeline board.

Ashby also sells Ashby Analytics for teams using an existing ATS, and its All-In-One plans include analytics. Its public pricing page lists All-In-One Foundations, Plus, Enterprise and Ashby Analytics, with a 10% discount available for annual commitments on Foundations.

Greenhouse is a strong fit if your priority is structured hiring discipline, scorecards and governance. ATSLab ranks Greenhouse tenth overall, so it should not be treated as the general winner, but it remains a serious enterprise reporting option.

Greenhouse lists Core, Plus and Pro plans on its public pricing page, with pricing customised by plan, hiring volume, organisational complexity and required features. Core includes reporting and analytics, Plus adds AI-powered report filters and BI Connector, and Pro adds enterprise data configuration, security, audit log and developer tooling.

Greenhouse’s reporting materials reference dashboards, 40+ essential reports, pipeline and pass-through reporting, current pipeline per job, interview activity and number of hires. The limitation is packaging: advanced reporting features such as Report Builder and BI Connector may depend on tier names, plan level or legacy support terminology.

Lever is a better fit if your recruiting operation combines ATS and CRM work. ATSLab ranks Lever seventh overall and records it from around $4k, while Lever’s public pricing page uses custom quotes based on organisation size and hiring needs.

Lever says every plan includes its core ATS, CRM, advanced reporting and analytics, and key integrations. Its Visual Insights positioning focuses on funnel health, bottlenecks, nurture campaign performance, executive dashboards, benchmarks from 26,000+ talent teams and AI-powered insights.

That CRM strength is useful if passive candidate nurture is part of your hiring model. It is less compelling if your team only needs clean applicant tracking for a small number of inbound roles.

What pricing and packaging questions should you ask vendors?

Ask which reporting features are included in the plan you are actually buying. Custom dashboards, report builders, scheduled reports, SLA alerts and BI connectors are often the features that move a buyer to a higher tier.

Ask whether the ATS supports custom formulas and field comparisons. That matters when your definition of hiring velocity, time in stage or source ROI differs from the vendor’s default report.

Ask which fields can be filtered in reports. At a minimum, you want recruiter, hiring manager, department, location, source, job family, stage and relevant DEI fields where collection is appropriate.

Ask whether job-ad costs, source costs, agency costs and AI-screening usage appear in reports. If those costs live outside the reporting layer, ROI analysis becomes a spreadsheet job again.

Pricing transparency varies. Ashby publishes an entry price of $400 per month for Foundations up to 100 employees, while Greenhouse and Lever use custom quote flows on their public pricing pages.

ATSLab records Greenhouse from around $6k and Lever from around $4k, but those are site records rather than vendor-published list prices. Treat them as budget signals, then confirm the quote, contract terms and included reporting features.

What hidden costs affect ATS KPI reporting?

The fees that catch people out are usually tied to usage, integrations or higher-tier reporting. Ask about them before you sign, because they can change the true cost of a reporting setup.

Job ad marketplaces are one watch-out. Purchases may be non-refundable, delayed or hard to analyse inside normal reporting, which weakens source ROI unless you track cost data elsewhere.

AI sourcing and screening can also have usage rules. Workable, for example, shows Standard pricing at $299 per month for 1–20 employees and offers a 15-day free trial, but Workable Agent uses credits where 1 credit equals 1 candidate and extra credits are sold in bundles.

That does not make usage pricing bad. It means buyers should model candidate volume before relying on AI screening or sourcing as part of their KPI workflow.

Other costs to check include SMS, interview notetaking, onboarding, BI connectors, implementation, data migration and premium support. Some vendors include these, while others package them as add-ons or higher-tier features.

If price is the main constraint, free or low-cost ATS products can still help you track basic pipeline metrics. Zoho Recruit has a Forever Free plan with 1 active job per recruiter licence, while Manatal’s annual Professional plan is listed at $15 per user per month with a 14-day free trial.

The trade-off is reporting depth. Free and low-cost tools can be enough for a small team, but advanced dashboards, custom logic and executive reporting usually point towards Ashby, Greenhouse or Lever.

What mistakes make ATS recruiting KPIs unreliable?

The first mistake is tracking too many metrics without linking them to decisions. If nobody changes an action after seeing a KPI, remove it or move it to a secondary report.

The second mistake is comparing teams that use different stages, source rules or disposition reasons. The chart may look precise, but the underlying maths is wrong.

The third mistake is obsessing over time-to-fill while ignoring time in stage. Time-to-fill tells you that hiring is slow; time in stage tells you where it is slow.

Applicant volume is another trap. High volume can hide weak sourcing if candidates fail at screening or disappear before interview.

Offer reporting also needs discipline. Pending offers, declined offers, accepted offers and withdrawn candidates must be handled consistently, or offer acceptance rate becomes meaningless.

Hiring manager behaviour is often the hidden bottleneck. If managers skip scorecards or delay feedback, structured reporting breaks and candidates wait longer than they should.

The final mistake is treating dashboards as monthly reporting artefacts. Good recruiting KPI tracking is a weekly operating habit.

What is the practical setup checklist?

If you want to track recruiting KPIs in an ATS reliably, start with definitions. Write down what each KPI means, which dates it uses and which records are excluded.

Then clean the workflow. Standardise stages, require core fields, define disposition reasons, set source rules and decide how to treat edge cases.

Build dashboards by audience. Recruiters need action queues, hiring managers need bottlenecks and scorecards, talent leaders need funnel health, and executives need plan progress.

Add scheduled reports and alerts. SLA alerts for overdue feedback, ageing candidates and stalled stages are often more useful than a polished dashboard nobody opens.

Choose the ATS based on the reporting job you need done. Ashby is the stronger fit if analytics depth and custom KPI logic matter most; Greenhouse fits structured-hiring teams that can fund enterprise reporting discipline; Lever fits teams that combine ATS, CRM and nurture analytics.

If your team is still small, do not overbuy. A simpler ATS can work until hiring volume, reporting pressure or leadership planning makes deeper analytics worth the cost.