Field notes · July 16, 2026 · 4 min read
Why "just check the ATS" doesn't work
> Editorial Note (August 2026): This post was written during an earlier phase of Voco, when our exploration focused heavily on building software for recruiting teams. While the observations about friction in those workflows remain true, Voco now operates more broadly to build custom AI systems for operational teams. You can read more about why we stopped starting with software.
Every staffing team has an ATS, and almost every staffing team still has someone chasing status by phone, Slack, or a walk over to another desk. That's not a training problem. It's a trust problem, and it's usually earned.
Why the ATS stops being trusted
The ATS is supposed to answer "where does this candidate stand right now." It can only do that if every status change gets entered the moment it happens, by whoever is closest to it, every single time. In practice, status updates happen in whatever channel is fastest for the person who has the news — a text to the recruiter, a comment on a shared doc, a verbal update in a hallway — and the ATS gets updated later, if at all, by someone reconstructing what happened after the fact.
Once that gap opens once, it doesn't close on its own. A recruiter who got burned by stale ATS data once stops trusting it by default, and starts double-checking through the same manual channels that created the problem in the first place. The system that was bought to eliminate status chasing becomes one more place status might be, alongside three others that are actually faster to check.
The same trust gap breaks search, not just status
Status chasing is the visible symptom. The quieter one shows up when a recruiter opens a new role and asks "have we talked to anyone like this before?" If answering that means digging through a system they've already learned not to trust, most recruiters skip the question and go straight to sourcing from scratch — not because the right candidate definitely isn't in there, but because finding out costs more than it feels worth. Candidate data that's been re-typed at every handoff makes this worse: a record that's drifted out of sync is even harder to trust than one that's simply missing.
That's the real cost of "just check the ATS" as advice. It assumes checking is cheap. For a recruiter staring down a live search, digging through inconsistent notes and half-updated statuses on the chance something useful turns up rarely feels cheap — so the search that should start with "who do I already know" starts with a blank sourcing list instead.
This isn't a re-training problem
This is why simply mandating "update the ATS" rarely works — it asks people to add a step to a process that's already working for them in the moment, for a payoff (someone else finding accurate data later) that they don't personally feel. The fix that actually holds is structural, not behavioral: make the fastest way to communicate a status change be the ATS update, not a parallel step on top of it. That usually means connecting whatever channel people already default to — a form, a message, an existing tool — directly into the record, so the update and the communication are the same action instead of two.
Before you assume the candidate isn't in there
Three questions worth asking before a search defaults to sourcing from scratch:
- Did I actually search, or did I glance and give up? A keyword search on a job title misses people filed under an old role, a different spelling, or a recruiter's shorthand notes.
- Am I searching the ATS, or every place a candidate might actually be? Notes docs, old email threads, and a previous recruiter's spreadsheet often hold context the ATS never got.
- Would I recognize the right person if their record were stale? A candidate who went quiet six months ago for a reason unrelated to this role can still be worth a second look.
Fixing the ATS itself is a five-day problem, not a re-training problem: find the one status transition that gets chased the most, and make updating it the path of least resistance instead of the extra step.
Fixing the search problem doesn't require touching the ATS at all. That's what Voco is for: give it the role you're working on and the candidates you already know — a CSV export is enough — and it shows you who's worth another conversation before you assume you have to start over. Ask Voco.