Most TA leaders have already had some version of an ATS review done. The vendor ran an account health check, or the implementation partner did a post-go-live assessment.
Someone internally compiled a list of features the team wasn't using.
These reviews find things. Misconfigured pipeline stages, automation rules that were never turned on, integrations passing partial data. The list is usually longer than expected.
Most of them stop at the list.
A rigorous ATS audit is built around three questions, in sequence. Most vendor reviews and health checks get to the first one. The second and third are where the business value sits.
Each question requires a different type of work to answer properly. Most things that get called an audit only do the work for the first one.
What are you leaving on the table?
This maps the gap between what the system is capable of and what it's actually doing. For an ATS, that covers pipeline stages that don't reflect how the team works and automation rules configured at implementation and never revisited.
Integrations and reporting get particular attention. Job board connections that are live but not passing clean data, and reporting built around implementation defaults rather than how this business actually measures hiring performance, both sit here.
For an HRIS, the same question surfaces workflow automation that was deprioritised at go-live and data quality issues that have compounded since.
Answering this question well requires a proper configuration review. Someone has to go into the system and compare how it's set up against how the team is actually working.
What is that costing you?
This is where most audits stop short.
Identifying a gap is useful. Knowing that the gap is costing 15 hours per week in manual reconciliation, or that broken source-of-hire tracking has misdirected thousands of pounds in recruitment marketing spend: that's a business case. A list of things to fix becomes a prioritised argument for investment when the cost is attached.
Quantifying the cost requires more than a configuration review. It requires understanding how the team is working around the gaps: what manual processes have formed, how long they take, and what decisions are being made on incomplete data. That's the part that involves interviews and observation alongside the platform review.
For TA, the costs tend to show up in vacancy time and manual reconciliation hours. For HR, they sit in process duplication and workforce planning decisions made without reliable data.
What should you do about it, and in what order?
A good audit ends with a roadmap ordered by business value, with the cost of each gap made explicit. The highest-value, lowest-effort fixes go first. The more structural changes come with a clearer argument for why they're worth pursuing, and what the sequence should be.
This is a different output from a list of recommendations. A list puts the prioritisation work back on the TA or HR leader, usually without the cost data that would make the prioritisation defensible. A roadmap does that work and produces something they can take to leadership.
Vendor health checks are produced by people who know the platform well, they surface real gaps, and they cost nothing. Their brief is to help you use the platform more fully. Cost quantification, stakeholder experience, understanding roadblocks to adoption on the ground and the business case are a different scope of work entirely.
There's a structural reason for that: a vendor has an incentive to show you the value in the product you've already bought. An independent audit has an incentive to tell you the truth about what it's actually worth to you.
Internal reviews and post-implementation retrospectives have a similar boundary. They're useful for identifying operational friction. They rarely produce a quantified cost and almost never produce a prioritised roadmap tied to business value, because that's not what they're scoped to do.
Both are useful. The question they answer is narrower than what a proper audit covers.
A proper ATS or HRIS audit should leave you with a findings report where every gap has a cost attached. Each finding is linked to a business impact: time, money, risk, or a decision that can't be made without reliable data.
The roadmap that follows is ordered by that impact. The most useful versions also produce something boardroom-ready: a one-pager that translates the findings into language a CFO or CEO recognises, with the ROI case made explicitly. That's what converts an internal recommendation into an approved investment.
If an audit can't tell you what the gaps are costing and where to start, it's left the hard part undone.
For ATS reviews, we go into the configuration in depth: pipeline setup, automation rules, job board and HRIS integrations, reporting, data quality. For HRIS reviews, the scope covers configuration, workflow automation, self-service adoption, and process duplication. In both cases, we build out the cost of each gap we find.
We're independent. No incentive to sell you more software, no vendor relationship that shapes what we report. The output is a findings report with ROI attached and a prioritised roadmap your team can act on immediately.
The Essential Audit covers one set of stakeholder interviews and a full configuration review. The Strategic Audit adds observation sessions and cross-functional interviews, and produces a board-ready one-pager alongside the findings report.
If you've had a health check and walked away with a list of recommendations rather than a prioritised business case, that's the gap a proper audit fills. Start with a conversation.