The Multi-State Handbook Problem
By VICKY BROWN
Most small business owners don’t think about their employee handbook very often. You had one written (or downloaded one, or inherited one from a previous job), everybody signed the acknowledgment page, and it went into a folder. Done. And for a company where everyone works in the same state, that can honestly hold up for a good long while.
Then you hire someone remote. Maybe they’re in Texas. Maybe they’re in New York. And somewhere along the way, somebody, your accountant, your payroll provider, a well-meaning friend who runs their own business, asks whether your handbook actually covers them. That’s usually the first time a founder hears the phrase multi-state employee handbook, and it tends to land with a thud.
So let’s walk through what it means, what it doesn’t, and how to set one up without drowning in paperwork. Just so we’re clear up front, I’m not an attorney, and state laws change often, so get an employment lawyer or a qualified HR professional to look at your specific situation. But the structure itself? That I can absolutely explain in plain English.
How a Simple Handbook Quietly Stops Fitting
Here’s how this usually unfolds. Nobody decides to become a multi-state employer. It creeps up on you. A long-time employee’s spouse takes a job across the country and you don’t want to lose them. A great candidate lives two states away. A manager says yes to someone working from their parents’ place “for a few months,” and a few months turns into a year.
Each of those decisions made sense at the time. But each one also quietly changed your legal obligations, and your handbook didn’t change with it. That’s the gap. Your document was written for one set of rules, and now your people are living under several.
When founders realize this, they usually swing to one of two extremes. Some go looking for a massive fifty-state handbook that tries to cover everything. Others decide it’s all too complicated and just keep using what they have. Both reactions are understandable. Neither one is a great plan.
The Question That Actually Drives Compliance
If you remember one thing from this article, make it this. Employment law generally follows the employee. It doesn’t much matter where you’re incorporated or where your office sits. What matters is where the person physically does their work.
So an employee working from their kitchen table in California is typically covered by California’s rules on paid sick leave, meal and rest breaks, and expense reimbursement, even if your company is based somewhere else entirely. Someone in New York City may be covered by federal law, New York State law, and city rules, all stacked on top of each other.
That’s why hiring remotely isn’t only a recruiting decision anymore. Every time you approve someone to work in a new location, you may be taking on a new set of obligations. Are you registered to employ people there? Is payroll withholding the right state taxes? Are there required notices? Does this person need additional policies? Somebody has to ask those questions before the start date, and that goes for current employees who want to move, too. A relocation should go through an approval step, rather than showing up three months later as a new address on a pay stub.
What Belongs in Your Core Handbook
The good news is that a big chunk of your handbook doesn’t need to change from state to state at all. Your core handbook is really a description of how your company runs. Your values, how people are expected to treat each other, what you consider confidential, how company laptops and accounts should be used, how attendance and communication work, how performance gets managed.
Your anti-harassment policy belongs here too, and it should be the same everywhere. The Equal Employment Opportunity Commission, the federal agency that enforces workplace discrimination laws, expects employers to have a clear policy, share it, give employees more than one way to report a problem, and make it plain that nobody gets punished for speaking up. That’s a company-wide standard. It shouldn’t look different in Ohio than it does in Oregon.
One piece of advice while you’re in there. Take out the promises you don’t need to make. Language like “every employee receives a verbal warning, a written warning, and a final warning before termination” feels fair when you write it. But it can tie your hands the day someone does something serious enough that three warnings would be absurd. A handbook should explain expectations clearly.
“… A manager says yes to someone working from their parents’ place “for a few months,” and a few months turns into a year.“
Layering State and Local Policies on Top
This is where a multi-state employee handbook actually earns its name. Instead of rewriting the whole document for every state, you keep your core handbook intact and add a state addendum for each state where you actually have people. An addendum is simply a supplement, a few pages that say, in effect, “if you work in this state, here’s what’s different for you.”
What goes in it? Anything where the law materially differs. Paid sick leave is the big one for most small businesses, since states disagree about how much time employees get, how it builds up, and what it can be used for. Final paycheck timing is another, because some states want that check in the employee’s hand on their last day and others give you more room. Meal and rest breaks, pregnancy and lactation accommodations, and state-specific complaint rights often land here too. That’s not a complete list, just the usual suspects.
And sometimes there’s a third layer. Certain cities and counties have their own rules on top of the state’s, and some require employers to hand out specific written notices. Not all of that belongs inside the handbook. Some of it works better as a standalone notice, a payroll setting, or a note in your manager guide. What matters is that someone on your team knows which layer applies to which employee.
So picture it this way. One core handbook for everybody. A state addendum only for the states you actually employ in. Local notices only where a city or county requires them. If you have people in three states, you have three addenda, and that’s it.
Why Generous Isn’t the Same as Compliant
There’s a shortcut that sounds really smart, and I understand the appeal. Just pick the most generous version of each policy and give it to everyone. If one state requires five sick days, give everybody seven. Problem solved, right?
Well, sort of. Generosity can help, and in some areas it works fine. But these laws care about more than the number of days. They care about who counts as family, when you’re allowed to ask for a doctor’s note, whether unused time carries over, how it has to show up on a pay stub, and what notice you have to give. You can beat the number and still miss a detail. So compare your actual policy wording against each state’s requirements, rather than trusting the spirit of it.
The opposite extreme, fifty fully separate handbooks, creates its own mess. Change your IT policy or your reporting hotline and now someone has to update every single version. Miss one and you’ve got employees working from rules that are years out of date, which is exactly how companies end up with three “official” handbooks and no idea which one is real.
Whether you’re an entrepreneur jumping into a leadership role, a seasoned business pro with new HR responsibilities, or just starting your HR career – we’ve got the right path to guide you through your HR hurdles.
Check out the Leaders Journey Experience.
A Handbook Only Works If Someone Owns It
Here’s the part founders tend to skip. Having the right words on paper doesn’t mean your company is actually following them. If your harassment policy names two people who left last year, it isn’t really working. If your addendum describes sick leave perfectly but payroll is calculating it wrong, the document won’t save you.
So assign an owner. One person responsible for the current core handbook, the approved addenda, collecting signed acknowledgments, and knowing where every employee actually works. For a small company, that can be a simple spreadsheet with each employee’s name, work state and city, which handbook version and addendum they received, when they signed, and when it’s due for another look.
Then update it when something changes, and don’t wait for the annual review. A hire in a new state, an employee who moves, a new law, a new benefit, a new payroll system, all of those are reasons to open it back up. And give your managers one simple rule. When a question comes up about leave, pay, accommodations, a complaint, or a move, they don’t guess. They escalate.
You don’t need a fifty-state handbook on day one. You need a solid foundation, the right add-ons for the places your people actually live, and a clear process for keeping it current as you grow. Get that in place, and your handbook goes back to doing its real job, which is making your company easier to run.
And if setting all of that up sounds like more than you want to take on alone, that’s what IDO On Call is for. You get a dedicated HR expert who can help you build the core handbook, draft the addenda you actually need, and put a process in place that keeps up with your team.