How do I know if my ATS is badly configured or if my recruiters just need more training?

Watch where the workarounds live. If your top recruiters keep candidate notes in spreadsheets, track submittals in their inbox, or skip required fields with junk data, the system is fighting them. Training fixes a knowledge gap. Workarounds signal a configuration gap. When your best people route around the tool, the tool is the problem.

We are PE-backed and just inherited an ATS we did not choose. Where do we start?

Start with the data, not the features. Pull a report on how many custom fields exist and how many are actually populated across the last 90 days. Then map your real recruiting workflow against the stages built into the system. The gap between those two things is your hidden tax. You can usually scope a fix in two weeks without ripping out the platform.

Is it worth fixing the configuration or should we just switch platforms?

Switching platforms is the most expensive way to fix a configuration problem, and most firms carry the same bad habits into the new system. Fix the setup first. If you reconfigure fields, workflow, and data mapping and recruiters still hit walls, then you have a real platform case. Order matters. Reconfigure, measure, then decide.

The Hidden Tax of a Badly Configured ATS

The worst ATS decisions get made on day one of implementation and cost you for years. Custom fields nobody uses, broken workflows, and bad data mapping quietly drain recruiter hours and margin. Here is how to audit the damage.

Most staffing firms think their ATS problem is a software problem. It is not. It is a setup problem, and the bill for it shows up years after anyone remembers making the decision.

Here is what actually happens. A firm buys a solid ATS. During implementation, someone makes a few hundred small choices about custom fields, workflow stages, and how data flows in and out. Then that person leaves, or moves on, and those choices freeze in place. Three years later your recruiters are working around a system that was configured for a business you no longer run.

The cost is real, and it is hiding in plain sight. Practitioner reviews across 2025 and 2026 keep flagging the same thing. The ATS itself is rarely the issue. The configuration is.

The Tax Nobody Put On The Budget

Bad configuration does not announce itself. There is no line item that says "recruiter time lost to a 14-field intake form." The damage is spread across thousands of small moments that never get measured.

A recruiter spends 90 seconds per candidate hunting for the right status because the workflow has 22 stages and only 6 are used. Multiply that by 40 candidates a day, across 15 recruiters, across a year. That is real money walking out the door, and it never hits a report.

Here is where the tax piles up:

Dead custom fields. Fields built for a client you lost in 2022 or a process you abandoned. Recruiters either fill them with junk or skip them, and now your data is half noise.
Workflow stages that do not match how you work. If your real process has 5 steps and the system has 18, recruiters guess. Guessing means inconsistent data and useless pipeline reports.
Bad data mapping. When candidate and job data does not flow cleanly between your ATS, your VMS, and your reporting tools, someone is rekeying it by hand. That someone is expensive.
Required fields that block instead of help. A required field with no clear answer trains your team to enter garbage just to move forward. Now you cannot trust your own database.

None of this is dramatic. That is exactly why it survives. It is a slow leak, not a burst pipe.

Why This Hits PE Portfolios Harder

If you run ops for a PE-backed staffing portfolio, you inherit these decisions whether you like it or not. You bought a firm, and you bought its tech debt with it. Most of the time nobody flagged the ATS setup during diligence because it looked fine on the surface. The platform was modern. The logins worked. Everyone moved on.

Then you try to roll up reporting across three portfolio companies and discover each one configured the same ATS differently. One firm tracks margin in a custom field. Another tracks it in notes. A third does not track it at all. Now your data does not roll up, and your portfolio dashboard is a fiction.

This is the part that catches ops leaders off guard. The cost of bad configuration is not just recruiter time. It is your ability to see the business clearly. You cannot manage what your system cannot report, and a badly configured ATS reports badly by design.

How To Audit The Damage

You do not need a consultant to find the leak. You need an afternoon and a few specific questions. Run this audit and you will see the tax within a day.

Count the fields nobody uses

Pull a list of every custom field in your ATS. Then check how many were populated in the last 90 days. If a field is empty or junk-filled more than half the time, it is not a field. It is friction. Flag it for deletion or repurposing.

Map your real workflow against the built one

Sit with two recruiters and have them walk you through what they actually do, step by step, from intake to placement. Write it down. Then compare it to the stages in your ATS. Every stage that does not match real life is a place where data gets sloppy and reports get unreliable.

Follow one candidate through the whole system

Pick one recent placement and trace the data. Where did it enter? Where did it get rekeyed? Where did someone copy and paste between tools? Each handoff is a place where bad mapping is costing you. You will find at least two you did not know about.

Ask where the spreadsheets live

Every recruiter who maintains a side spreadsheet is telling you the system failed them somewhere. Find those spreadsheets. They are a map of every gap in your configuration, drawn by the people who feel the pain daily.

The fix is rarely a new platform. It is usually a focused reconfiguration. Cut the dead fields. Rebuild the workflow to match how you actually work. Clean up the data mapping so nobody rekeys anything. Most firms can scope this in two weeks and execute it in a quarter without touching the contract.

The point is to stop paying a tax you never agreed to. Every month you leave a bad setup in place, you pay it again.

Do This Week

Block 60 minutes. Pull the list of every custom field in your ATS and check how many were populated in the last 90 days. That single number tells you how much of your system is working for you and how much is just sitting there charging rent. Bring it to your next ops meeting and make it the first thing you fix.

Your ATS Is Costing You More Than You Think: The Hidden Tax of Bad Configuration