What we learned from 300 HR teams
Three hundred conversations later, the operational gaps in HR document workflows look strikingly similar across industries.
We expected wide variance across industries. We found the opposite: the operational pain in HR document workflows looks remarkably similar from a 40-person SaaS startup to a 4,000-person manufacturer. The details differ; the failure modes don't.

How we ran the research
Over eight months, we conducted structured interviews with 300 HR practitioners across SaaS, healthcare, manufacturing, financial services, and professional services. Participants ranged from solo HR generalists at early-stage startups to VPs of People at public companies. We asked the same 22 questions to each, then followed up on anomalies.
Three patterns that held everywhere
1. The "one-off exception" is never one-off
When we asked teams how often they deviate from a standard template, the most common answer was "rarely — maybe a few times a year." When we asked them to pull the last 30 documents they'd issued, the actual deviation rate was closer to 40%. The gap between perceived and actual exception rates was consistent across every segment we studied.
Once a template is bypassed once, it gets bypassed roughly 11 times per quarter. The first exception creates a precedent; the precedent creates an expectation; the expectation becomes the de facto policy. The written policy and the practiced policy drift apart quietly, over months.
2. Teams underestimate their template count by 3–4×
We asked: "How many active document templates does your team maintain?" The median answer was 8. When we helped teams do an actual inventory — including templates living in personal Google Drives, old email attachments, and department-specific folders — the median actual count was 27. Several teams discovered templates they'd forgotten existed, some of which contained outdated legal language or benefit terms that were no longer accurate.
The templates you don't know about are the ones that create liability. You can't update what you can't find.
3. Audit prep takes 4× longer than predicted
When asked to estimate how long it would take to produce all signed employment documents for a given employee during an audit, the median estimate was two hours. The median actual time, when we observed the process, was eight hours — and that was for teams who considered themselves well-organized. The bottleneck was almost never access; it was locating the definitive signed copy versus drafts, superseded versions, and unsigned originals.
What the best teams do differently
The 20% of teams that performed consistently well on document operations shared three practices that the others didn't:
They treated document storage as a records system, not a file system. Every document had a status, an owner, and a defined retention period.
They ran a quarterly template audit — a structured review of every active template against the current version of each relevant policy.
They tracked exceptions explicitly. Every deviation from a standard template was logged, with a reason and an approver. The log was reviewed monthly.
None of these practices required specialized software. They required process discipline and the organizational will to maintain it. The software made the discipline easier to sustain — but the discipline came first.
What this means for your team
If your team is in the majority — managing documents in a shared drive, with exceptions handled informally and templates that haven't been reviewed in over a year — the risk isn't catastrophic today. The risk is that it compounds. Each month of template drift makes the eventual reconciliation harder. Each exception that isn't logged is a policy gap that can't be defended.
The good news is that the fix is modular. You don't have to solve everything at once. Start with the template inventory — knowing what you have is the prerequisite for everything else.