
SimpliGov |
September 28, 2026
What happens between application and day one in government hiring.

In this article
A candidate submitted background check paperwork three weeks ago. It's sitting somewhere between the reviewer's desk and the next verification step, in that stretch of the process nobody's specifically responsible for checking on, and nobody has, not since it arrived. Meanwhile, a candidate who applied to a neighboring agency at almost the same time got an offer in less than half the time it's taken this one just to clear the first two steps, and took it, understandably. Nobody made a mistake here. The process simply has more places for someone to go quiet than most people realize until they're the one trying to explain the delay.
This isn't isolated to one office. A 2026 report from Work for America, based on interviews and surveys with more than 70 government HR leaders, found that even where candidate interest is strong, it's internal system performance, not a shortage of applicants, that holds public-sector hiring back. In a related survey of 16 jurisdictions, 69% named slow time-to-hire as a top challenge, and 45% pointed specifically to approval bottlenecks and inconsistent workflows.
A government hire that requires licensing, certification, or a public trust background check isn't a simple application-review-offer process. It's an application, a background check, sometimes a medical or fitness-for-duty review, sometimes a licensing or credential verification step, an HR onboarding process, and a training or orientation seat. In some agencies, the background process alone involves dozens of pages of disclosure, employment history, and reference verification, with a reviewer flagging anything that doesn't match the record before a candidate can move forward, and in some cases escalating a discrepancy to a review board before a final decision gets made. Each of those steps is typically owned by a different person, sometimes a different office altogether, and nothing forces them to talk to each other automatically. So nobody ends up with one view of where any single candidate actually stands, only a series of separate views, each accurate for its own piece and silent about everyone else's.
Background check, medical or fitness review, credential verification, HR setup, training scheduling, each lives with a different person, and nobody's watching all of them at once. A stall at any single step looks, from everywhere else in the process, exactly like normal progress, because there's no way to distinguish "this is taking a while" from "this has actually stopped moving" until someone happens to ask.
The same gap shows up once someone's already hired. A promotion, a transfer, or a disciplinary action often needs a division supervisor, HR, and sometimes legal or a compliance office to weigh in, and discipline in particular tends to be more layered than it looks on paper. A case involving something like repeated absenteeism might stay entirely within HR, while one touching a more serious allegation moves into an entirely different office, one HR may not have visibility into once it's handed off. There's rarely one record showing where any of this is actually stuck, so checking on it usually means checking with two or three offices separately, and hoping each one remembers to mention it if something changes.
It shows up again in the recurring work nobody schedules time for. Licensing renewals, continuing education requirements, and other annual credentialing get tracked person by person, sometimes against a roster that has to be built and updated manually for every cycle. A compliance report at the end of a cycle usually means someone sitting down to figure out who actually finished, who's only partway through, and who never started, discovered at the deadline rather than flagged earlier when there was still time to do something about it.
And underneath all of it is a simpler problem: none of this usually has backup. Forms coordination, applicant tracking, personnel actions, telework requests, policy acknowledgments, reimbursement paperwork, in a lot of agencies this is one person's responsibility layered on top of another full job entirely, procurement, records management, whatever landed on their desk first. When priorities compete, and they compete constantly, whichever process has no immediate deadline attached is the one that waits, which over time tends to be exactly the process most in need of steady attention.
What people in this role actually want isn't a bigger applicant tracking system layered on top of the ones they already have. It's a single place that shows a candidate's actual status, background check, medical or credential review, HR setup, together in one view, so a stall becomes visible the moment it happens instead of being discovered weeks later, usually right around the time the candidate has already accepted an offer somewhere else.
A lot of what keeps an HR process moving, which exceptions are normal, who to escalate a stalled background check to, where a particular kind of request always seems to get stuck, exists only in the head of whoever's handled it the longest, often someone who's been doing this specific job for years and has simply absorbed all of it without ever writing it down. When that person moves on, the process doesn't just get harder to run. In some cases, it stops being documented anywhere at all, and whoever inherits it has to rebuild that knowledge from scratch, usually by making the same mistakes the process used to quietly absorb.
Those three checks won't close the gap. They're diagnostic, and they'll show exactly where a candidate or a case is most likely to go quiet next, which is usually the part that's hardest to see from inside the process itself. What they can't do is replace a system that watches every handoff automatically, because that's not something a checklist can do on its own, no matter how honestly it's answered.
That's not hypothetical. The same Work for America research found real examples of agencies closing this exact gap: the City of St. Louis cut its hiring timeline from more than nine months to roughly three by simplifying its workflows, and the Commonwealth of Pennsylvania closed a persistent bottleneck by fixing how its interview stage was scheduled and tracked. Neither required adding staff. Both required rethinking how the process itself moved.
None of this gets fixed by replacing your HRIS or your broader personnel system. It gets fixed by giving every step in the process, background check, medical or credential review, HR, division sign-off, one shared record instead of several separate ones that only talk to each other when somebody remembers to pick up the phone. That's the work SimpliGov does.
It's built to be configured by the people who already run this process, not handed off to an outside developer every time a step changes, and it keeps a record of how the process actually works, so it doesn't depend on one person's memory.
One county's public health department saw this play out directly: onboarding new hires used to take seven or more business days, split across HR, IT, and departmental sign-off, mostly coordinated by email. After connecting those steps into one shared workflow, that dropped to two business days or less, a reduction of more than 70%. Read the case study →
If the checks above turned up something real, it's worth ten minutes to see what closing that gap actually looks like. See the platform →
See how the workflows you're running by hand right now can run themselves.