Why one uniform policy set can't legally cover multiple states
Tip credit is the clearest example. Seven states (Alaska, California, Minnesota, Montana, Nevada, Oregon, and Washington) ban tip credits entirely; employers there must pay the full state minimum wage in cash regardless of tips earned. Other states allow a tip credit, letting a lower cash wage count tips toward the minimum. That list has been stable, and the two jurisdictions people assume have joined it are not states at all. Washington DC capped its tipped wage at 75 percent of the minimum rather than eliminating the credit, and Chicago pushed full elimination out to 2030 and beyond. Both slowed down rather than finished, so plan for the credit to persist in most places. Overtime is where the mismatch bites. For a tipped employee, the regular rate includes the cash wage plus the tip credit claimed, so overtime is computed on at least the full applicable minimum wage rather than the reduced cash wage, and the employer may then subtract the same per-hour tip credit from the overtime rate but never a larger one. In the seven no-credit states there is no reduced cash wage to begin with, so the calculation starts from a different place entirely. A single company-wide tip credit and overtime policy will be wrong in at least one direction in at least one state, systematically underpaying some employees and over-complicating payroll in others.
The same pattern shows up in overtime thresholds, meal and rest break requirements, and minimum wage itself, all of which vary by state and sometimes by city.
The structure that works: core plus addendum
The core handbook. Everything that doesn't vary by location: company mission and values, code of conduct, anti-harassment policy, benefits overview, standard operating procedures for the role itself. This is what gets standardized across every location and what manager training is built around.
State-specific addenda. A short, separate section per state covering exactly what varies there: minimum wage, tip credit rules if applicable, overtime calculation, meal and rest break requirements, and any state-specific leave laws. Each location's team receives the core handbook plus only the addendum for their state, not every state's addendum, which just creates confusion about which section applies to them.
This structure lets you standardize manager training (every manager learns the same core policies and SOPs) while keeping the compliance-sensitive details correctly scoped to where each location actually sits.
Manager training, standardized across the core
Once the core and addenda are separated, manager training can run identically everywhere for everything that doesn't depend on state law: how to use the scheduling system, how to handle a customer complaint, how to document a performance issue, how to run the hiring process for hourly roles. Build this once, train every manager the same way, and location-level customization becomes limited to the few genuinely state-specific items (how to calculate overtime correctly in that state, what the local meal-break requirement actually is).
Rolling this out without redoing everything from scratch
If a single uniform handbook already exists, don't scrap it. Split it: pull out everything that's genuinely state-dependent into addenda, and what's left becomes the core. This is usually a few days of careful review, not a rebuild, and it's worth doing before opening a location in a new state rather than after a wage-and-hour complaint surfaces the gap.