Field notes · July 16, 2026 · 3 min read
Where staffing teams actually lose the week
> 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.
Ask a staffing-agency owner where their week goes and you'll usually get "recruiting" as the answer. Ask where it actually goes, hour by hour, and the real list looks different. It's rarely one big broken process. It's six small ones, repeated daily, that never got fixed because none of them were ever bad enough on their own to stop and rebuild.
The six places the week disappears
Candidate intake. The same details — name, contact info, availability, certifications — get typed into an intake form, then a notes doc, then the ATS. Three keystrokes for one fact. (Add up what that actually costs and it stops looking small.)
Resume processing. A resume arrives as a PDF, an image, or a forwarded email. Before anyone can act on it, it gets opened, read, and manually reformatted or retyped into whatever the ATS or client template expects.
Internal candidate updates. A recruiter doesn't read status — they chase it. Slack, a phone call, a "just checking in" email, because the one place that's supposed to have the answer — the ATS — is either stale or nobody trusts it.
Client submissions and feedback. A submission goes out by email, feedback comes back by email or in a call, and someone copies it into a spreadsheet so it doesn't get lost — a third copy of information that already existed twice.
Interview scheduling. Availability gets collected, proposed, confirmed, and rescheduled by hand, usually across three or four back-and-forth messages per interview.
Placement and onboarding handoffs. The moment a candidate is placed is also the moment the paper trail gets messiest — documents, start dates, and next steps moving between people with no single source of truth.
Why none of these get fixed on their own
None of these are dramatic. That's exactly why they survive. A workflow that's obviously broken gets fixed fast; a workflow that's merely annoying gets tolerated for years, because it never quite crosses the threshold that justifies a "real" software project.
The right test for what's worth fixing
That threshold is the wrong test. The right question isn't "is this bad enough to justify a platform migration" — it's "is this one specific, repeatable thing costing us real hours every week, with one person who owns it and could tell you exactly how it works." If the answer is yes, it doesn't need a quarter and a vendor evaluation. It needs five days.
The candidate-side friction on this list — intake, resume processing, status chasing — shares a root cause: nobody trusts the record enough to search it first, so a search that could start with "who do I already know" starts from zero instead. That's the specific gap Voco is built to close, one search at a time. Ask Voco.