What reports should an ATS provide, and how do you get a simple answer from them? #

Most recruiting reports are created as a management obligation and then ignored. Four areas are enough to start: hiring quality, speed, the hiring funnel with sources, and rejection reasons. Above all, you do not want more data. You want information that changes a decision.

Most reports are built for someone who does not care about the numbers #

ATS reporting is the continuous measurement of recruiting: how many candidates arrived, where they came from, how quickly they moved, and why they left. Recruiting analytics is what you learn from those numbers and what you change as a result.

In practice, reporting often means producing a spreadsheet for leadership. The table gets delivered, and nobody uses the numbers. That does not mean HR has no interest in data.

You want data because you want more good candidates, a stronger candidate experience, and a clear view of which sources produce value.

If you track one number, make it hiring quality #

If you could choose one metric, use the quality of the hiring process. NPS, or Net Promoter Score, is one practical measure. Pair the score with an open question tailored to detractors, promoters, and neutral respondents.

Do not collect criticism alone. Candidate praise belongs back with the team too.

NPS benchmarks you against yourself over time and can be filtered by recruiter or hiring manager, exposing differences in process quality between people.

This matters in decentralized hiring, such as retail branches where local managers recruit without working in HR. The same applies wherever several recruiters and hiring managers share hiring.

The customer of the hiring process is the candidate. They will tell you whether it was fast, slow, transparent, or misleading.

That is the most direct evaluation. For how to collect feedback at rejection, see candidate rejection.

Speed: time to hire tells you very little on its own #

Speed is one of the issues candidates mention most often, but a single time to hire or time-to-fill number is not enough.

Break the process into stages and count the days in each one. That shows the bottleneck, what to optimize, and what can safely move more slowly.

In a competitive market, companies that respond in days rather than weeks often win the candidate. The useful insight is which stage caused the delay.

Transparency may matter more than speed #

There is one qualification: transparency may be even more important than speed.

No direct metric captures it. Open feedback does: candidates will tell you when a recruiter promised an update in one week and then disappeared.

You can publish a service-level expectation, but the priority is to define realistic response times and measure whether the team meets them.

Use a traffic light, not a KPI poster #

For every hiring stage, define an optimal time and a critical time.

For example, a candidate who applied should receive a prescreening call within one business day. Four business days may be critical.

The ATS can show candidates in green while they are on time, orange after the optimal threshold, and red after the critical threshold across every open role.

Not every stage should be rigid. If a candidate is away for a month, a planned pause is reasonable.

This is not a KPI for the wall. It is a practical definition of how you want candidates to be handled.

The hiring funnel and candidate sources are where many ATS reports stop short #

A hiring funnel shows how candidates moved through the process: applications, prescreens, interviews, offers, and accepted offers.

The funnel becomes useful when you add candidate sources at every stage, not only at entry.

Many systems show how many applications each source produced but not which sources supplied the candidates who passed prescreening or the first interview.

The first view measures volume; the second measures quality. A paid board that generates 100 applicants but fewer than 30 plausible prescreens consumes recruiter time. Another source may deliver fewer applications but far more candidates who remain viable after interview.

A source that still leaves you with eighteen relevant candidates after the first interview can be worth its weight in gold.

Rejection reasons belong in reporting, not only in an email #

The next layer above the funnel is rejection reasons. A good ATS separates them into two groups.

Candidate side: accepted a counteroffer, stopped responding, or expected different compensation. Company side: missed requirements, did not pass an assessment, lacked team fit, or lacked a required skill set.

By stage, the reasons show where people drop out. In aggregate, they show trends. The same increase can signal a hotter market or better screening by recruiters, so context matters.

Enterprise reporting: FTE and reasons for opening a role #

Large companies add a financial layer: how many full-time equivalents are being recruited each month, and how many approved vacancies remain unfilled.

Also record why a role opened: planned leave or retirement is different from turnover following a management change or long-term compensation pressure.

These figures may be secondary for an ordinary business but are often essential in enterprise workforce planning.

Why measure when you do not have enough candidates #

Companies often ask why they need an ATS when candidates are scarce. What is there to manage?

The paradox is that measurement is most valuable in exactly this situation. Without the ATS, the company learns nothing about the shortage.

With two open jobs and no applicants, software may not help. With ten jobs and two to five applicants each, you have enough activity to measure and improve.

Are your sources diversified? What do candidates say after interviews? Are communication or avoidable drop-off driving the problem?

Without data, you have opinions. The recruiter can only guess at the cause.

Data also gives HR a specific case to take to leadership. At high volume, the same measurement helps the team automate and control the workload.

Data versus information #

Nobody enjoys downloading CSV files, opening Excel, and assembling pivot tables. There is also a deeper problem.

Data is a collection of facts. Information is what you take from it — the conclusion that changes a decision.

You do not want to consume a dataset. You want to understand why NPS is low, why candidates are scarce, and what the team should do differently.

Simple reports should feel like a conversation with your data #

AI can turn ATS reporting into a simple pipeline for questions and answers.

The first use is routine but valuable: ask for a table with specific columns instead of spending two days exporting and joining data.

The second is true recruiting analytics: compare periods, identify recruiters above the average NPS, evaluate managers, or summarize 300 written responses.

Keep the analysis within your approved privacy, security, and AI governance rules. Reporting on your process data is different from automatically judging a candidate.

Ask where the calculations happen #

When evaluating an ATS, ask where AI processing runs and what data and context are sent to each model.

Prefer an architecture with clear tenant isolation, contractual controls, retention settings, and documented subprocessors. Do not assume a generic API call is appropriate for candidate data.

These data are company know-how. Treat them accordingly.

What reports should an ATS provide? #

Start with four: candidate-rated hiring quality, speed broken down by stage, the hiring funnel with candidate sources at every stage, and rejection reasons split between candidate-side and company-side causes. Everything else is an extension, often most valuable in enterprise organizations.

Which ATS works for multiple recruiters and simple reports? #

Choose one that can segment data by recruiter, hiring manager, branch, and location while returning an answer without an Excel export. In decentralized hiring, that is the difference between knowing who runs a strong process and merely assuming it.

How do you measure hiring quality? #

Ask candidates. NPS paired with an open question gives you a score to compare over time and the reasons behind it. Filter it by recruiter and hiring manager to see where the experience differs across the organization.

Why track recruiting data when you have too few candidates? #

Because scarcity makes the cause important. Measurement shows whether your sources are too narrow, communication is discouraging candidates, or people are leaving for reasons you can change. Without it, you only have a guess. The exception is two open roles with no applicants at all; a report cannot create activity that does not exist.

Complete list of questions for an ATS vendor →

← Back to the ATS selection guide