These three questions are the diagnostic framework behind every ATS and HRIS audit worth running. Work through them against your own system.
Most TA teams find at least one they can't answer with a specific number. That's usually where the cost is.
This asks for a clear account of the gap between what your ATS was built to do and what it's actually doing right now.
A TA team that can answer it confidently can tell you which parts of the system are actively doing work and which have been quietly idle since implementation. They can produce that picture in roughly ten minutes, without opening a spreadsheet.
For most teams, the honest answer is somewhere between "we use the main features" and "it does what we need it to do." Those answers describe a system that's running. The gap between running and fully utilized is a different question.
The specific gaps that surface most often in an ATS review: pipeline stages that reflect go-live configuration rather than how the team actually stages candidates today, and automation rules that were set up and never validated. Integrations and reporting get their own scrutiny: job board connections passing incomplete data, reporting built around vendor defaults rather than how this business measures hiring performance.
For an HRIS, the same question typically surfaces workflow automation that was deprioritised at go-live and self-service functions that were never fully turned on.
If you can describe your system's underuse precisely and by degree, you've answered this question. If the description is vague, the gap is real. It's just unmeasured.
This is where most teams stop.
A TA leader who can answer this question has numbers. They know roughly what the manual reconciliation between their ATS and their tracking spreadsheet is costing in hours per week. They know what a day of vacancy time is worth for the roles currently open, and they can apply that figure to their current pipeline data.
Most can't. The answer is usually "probably significant" or "we know we're losing time." Both are honest, but without a number attached the conversation has nowhere to go.
The cost sits in predictable places for TA: vacancy time compounded by reporting gaps that slow pipeline decisions, and manual hours absorbed by process workarounds the ATS was supposed to eliminate.
For HR, the same calculation applies to process duplication and workforce planning decisions made on data nobody fully trusts.
An estimate is enough to work with. A gap with no number attached stays on the list indefinitely.
This question requires the first two to have been answered properly. Most TA and HR teams reach it without the data they'd need to answer it well.
A clear answer looks like a prioritised roadmap: each item ordered by the combination of business value and implementation effort, with the cost of each gap made explicit. The highest-value, lowest-effort fixes are at the top. The more structural items come with a clear argument for why they're worth the effort and when.
What most teams have instead is a list: items added because someone flagged them, in the order they were flagged.
Some are operational inconveniences. Some carry real cost. Without the cost data from question two, there's no way to tell which is which.
The practical consequence: the fixes that would recover the most value often sit in the middle of the list, below items that feel urgent but cost less.
If you worked through all three and answered each with a specific number and a clear priority order, your system is better understood than most. That's genuinely rare.
If one of the three stopped you, that's the gap. The question that you couldn't answer confidently is where the audit starts.
This is the framework the Udder Optimization Audit is built on. We go into ATS and HRIS configurations and produce answers to all three questions: what the gap is, what it's costing, and what to do about it first. The output is a findings report with ROI attached and a roadmap ordered by business value.
If one of these questions didn't have a clear answer, it's worth finding out what an audit would uncover.