At peak, I was preparing three to five multi-state employee handbooks a week for PEO clients — more than 150 a year. Each one had to reconcile an approved template, the client's own policies, where their employees actually worked, and whatever source data we had on file, before it went to an HR business partner for review.
Writing the handbook was rarely the hard part. The hard part was everything that had to be true before the handbook could be right. Here's what that volume taught me.
1. The employee census is the real first draft
A multi-state handbook is only as accurate as the list of states it covers. If a client has picked up a remote employee in a new state and the records haven't caught up, the handbook will be missing that state's requirements no matter how carefully it's written.
So I started every handbook by confirming the employee population — which states, how many people, what types of roles — against what the client told us. When those didn't match, that was the first conversation, not the last.
2. Reconcile the inputs before you customize anything
Every handbook pulled from several sources that didn't always agree: the approved template, the client's existing policies, notes from the sales or onboarding handoff, and the HRIS record. Customizing on top of conflicting inputs just moves the conflict into the finished document, where it's harder to spot.
My habit became a quick reconciliation pass up front:
- Does the client's stated policy match what's in their current handbook?
- Do the states in the HRIS match the states the client described?
- Is anything in the client's policy language in tension with the approved template?
Anything that didn't line up got flagged and resolved before drafting — not buried in a comment for the reviewer to find.
3. One place for status, owner and revision history
At that volume, handbooks were always in motion — waiting on a client answer, in HRBP review, back for revisions, out for signature. While our CRM was still being implemented, there was no reliable way to see where every handbook stood.
I built a tracking spreadsheet that captured status, ownership and revision history in one place. It wasn't sophisticated, but it was consistent, and management ended up using it as the working source of truth until the CRM stabilized. The lesson: a simple tracker everyone trusts beats a better system nobody has finished setting up.
4. Hand reviewers something they can approve
HRBP review time is the scarcest resource in the whole process. If a reviewer has to chase down missing information or untangle a data mismatch, the handbook comes back and the cycle starts again.
The goal I held myself to was simple: every handbook that reached review should be review-ready — inputs reconciled, open questions answered, and any genuine judgment calls clearly called out. That's what kept downstream corrections low even at 150+ a year.
The throughline
None of this is specific to handbooks. Onboarding packets, benefits changes, LMS assignments — any multi-state HR process with a lot of volume rewards the same habits: confirm the population, reconcile the inputs, keep one trusted record of where everything stands, and don't pass problems downstream for someone else to catch.
I'm currently open to remote HR Operations, HRIS/LMS and Operations Coordination roles, as well as in-office opportunities within 10 miles of ZIP code 85375. If this is the kind of work your team needs, let's talk — or read more posts.