At Hana Group I ran 21 franchise units across six states, embedded inside Walmart, Sam's Club, Whole Foods, and Target footprints. The P&L was $36M. The compliance surface area was enormous: six state labor codes, six state health codes, six unemployment insurance regimes, dozens of city-level ordinances layered on top, and four national retail hosts each with their own vendor compliance requirements sitting alongside the government ones.
Over the run we did not take a single meaningful labor fine. Not zero citations, that is not real. But no material fines, no class actions, no closed units. The reason was not luck. The reason was a system I want to describe here, because the system costs almost nothing to build and pays for itself the first time you avoid a fine you would otherwise have taken.
Why labor, not health, is the real risk
Most operators build their compliance program around health inspections because the health inspection is visible. The truck is in the parking lot. The corporate group chat lights up. The score gets printed and hung on the door.
The problem is that health is not where the meaningful dollars are. A failed health inspection costs you a day of revenue, a reinspection fee, and a hit to your online rating. That is real money but it is knowable money. Call it $3,000 to $12,000 per failed unit inspection, worst case.
A California meal break class action, by contrast, can settle in the six-figure range for one unit before legal fees. The private right of action in California turns a single missed meal period across a hundred employees over a year into a compounding exposure that a plaintiffs' firm will happily package and file for you. Same math, less flashy, in Oregon and increasingly in New York.
The compliance program that avoids fines is weighted toward labor, not health. Health you handle with a mock inspection program. Labor you handle with a system that will not let you build a schedule that violates the law in the state the unit sits in.
The six-state matrix
The core artifact is a one-page matrix per state. Each page names the four things that differ from federal baseline in that jurisdiction. Not everything. The four things that generate fines.
Fig. 1 · The compliance surface differs by state. The matrix names the differences.
California: the meal break machine
California requires a 30-minute unpaid meal break by the end of the fifth hour of work, a second one by the end of the tenth, and paid ten-minute rest breaks for every four hours. Miss one and you owe the employee one hour of pay at their regular rate as a premium, which sounds small until you multiply it across a hundred employees and 260 working days. The fix is not to remind managers to send people on breaks. The fix is to build the schedule so no shift crosses the fifth hour without a break already blocked in, and to have the POS enforce that the employee has punched to break before the fifth hour ticks over.
New York: predictive scheduling and spread of hours
New York City fast food operators face a 14-day advance schedule notice, a premium for shift changes inside that window, and access to hours rules that favor incumbent employees before new hires get shifts. On top of that the state has a spread-of-hours rule that requires an extra hour of pay when the workday spans more than 10 hours, even with unpaid breaks in the middle. Both rules are enforceable per shift and both trip operators who are running the same schedule template they use in states without the rule.
Texas: unemployment and the at-will trap
Texas has no state meal break law, no state sick leave law, and no predictive scheduling. The compliance risk in Texas is elsewhere. Unemployment is where operators bleed, because the state's system is easy to lose contested claims in when documentation is thin. The fix is documentation discipline: every write-up in writing, every final decision signed, every separation coded correctly at the moment it happens, not two weeks later when the claim arrives.
Illinois: Chicago Fair Workweek and sick leave
Illinois has the state sick leave law that accrues 40 hours per year, and Chicago layers Fair Workweek on top of that with 14 days notice and premium pay for schedule changes. The Illinois trap for out-of-state operators is that the state law and the Chicago ordinance interact, and running the Chicago rules in a suburban unit is safer than running the state rules in a Chicago unit.
Michigan: the wage law that keeps changing
Michigan has been through several years of minimum wage and tip credit legislation that has been amended, litigated, and revised. The compliance risk is not the current rate. It is that the current rate has changed twice in eighteen months and operators who ran the same tip credit calculation for a year quietly owe back wages. The fix is a quarterly wage rule review, not annual, in states with active legislative motion.
Florida: the quiet state
Florida is federal baseline on almost everything, which lulls operators. The trap is the state's tipped minimum calculation and its aggressive enforcement of workers compensation classification. Get the tipped calculation wrong for two years and you have a wage and hour audit that reaches back three.
The compliance calendar
The second artifact is the calendar. Every state has recurring dates: license renewals, sales tax filings, unemployment updates, workers comp audits, health inspection windows. Multiply those by six states and layer the four retail hosts on top and you have roughly 140 recurring compliance events per year across the region.
None of that can live in someone's head. The calendar is a shared, dated view with every recurring obligation, an owner, and a 30-day pre-alert. When the pre-alert fires, the owner is on the hook. When it goes overdue, the regional operator sees it the next Monday.
The calendar is the cheapest tool in the whole program. It runs in whatever shared calendar or project tool the group already uses. It exists because compliance work is not glamorous, does not get remembered under load, and generates a fine when it is forgotten. If it is not on the calendar, it will not get done.
The compliance calendar is not sexy. It also caught more late fees per dollar of effort than any other tool I ran, and late fees are the fines you take because you meant to file and forgot, not because you did anything wrong.
Health inspection prep by locale
Health inspections vary more by county and city than by state. Los Angeles County uses a letter grade system posted at the door. Chicago uses a pass/conditional/fail model. New York City has its own hybrid. The generalized health inspection prep does not work. Each unit has to know its own jurisdiction's form, its own inspector rotation, and its own commonly cited violations.
The mock inspection program does this work. Once a quarter, unannounced, one unit gets a full mock walk using the actual inspection form for that jurisdiction. The regional operator or an assigned area manager scores it. Corrections are walked with the general manager in the moment. The findings are shared across the region so the next unit in the rotation knows what to look for.
Rotate through every unit once per year. The purpose of the mock is that the real inspection produces no surprises. Boring real inspections are the goal.
The certifications that pay
Three ServSafe levels, distributed across the region:
- ServSafe Manager for every general manager. Baseline requirement in most jurisdictions. Do not run a unit without one.
- ServSafe Instructor for the regional operator. Lets you train the general managers in-house on the region's clock, on the region's material, at the region's cadence.
- ServSafe Proctor for at least one person in the region. Lets you test onsite rather than paying per seat at a National Restaurant Association test center.
The Manager plus Instructor plus Proctor combination is roughly $700 in fees to establish across the region and saves in the low four figures per year in training and testing costs. It also compresses the timeline from "we hired a new manager" to "they are certified" from six weeks to two. Speed of certification matters when the state requires a certified manager on site during operating hours.
The certification set is not a compliance program by itself. It is the credential that lets you run the program at cost.
When a fine happens anyway
They will happen. The program is designed to keep them small and rare, not zero. When one lands, three rules.
Debrief it as a system failure. Not a person failure. The system was supposed to catch this and did not. What did the system miss, what does the fix look like, how do the other units get the fix before the same auditor visits them next.
Pay small fines. Do not fight them. What you spend fighting a $1,200 fine is almost always more than the fine itself, and losing the fight teaches the region the wrong lesson. Pay it, fix the system, move on. Fight the ones that carry precedent or that would open the door to a class action if unchallenged.
Share the debrief with the whole region. The unit that got fined is not the only unit at risk. Publishing the debrief so every general manager sees it turns one fine into training for twenty units. That is the highest return anything about a fine will ever have.
Where the program actually lives
The compliance program is not a binder on a shelf. It lives in three places, and if any one of them is empty, the program is fiction. It lives in the compliance matrix, which is a single spreadsheet with every requirement, every state, every unit, every renewal date, and a named owner per row. It lives in the standing calendar, where every renewal appears on the regional director's Monday review at least 60 days before the due date. And it lives in the general manager's weekly report, where compliance items due in the next 30 days appear as a standing line item, not a special note.
When I audited the Hana compliance program in month one, all three existed on paper. Only the matrix was current. The calendar was six months stale, and the general manager reports had a compliance section that had been blank for a year because the template did not require it. Rebuilding the calendar took two weeks. Getting the weekly report line item to actually populate took a full quarter, because it required the general managers to change a habit, and habit change is slower than template change. That gap, template versus habit, is where most compliance programs quietly die.
The point
Multi-state compliance is not exotic work and it is not intellectually hard. It is the kind of steady, boring, calendar-driven, matrix-updating, mock-inspecting work that a regional operator has to do because nobody else will and because the cost of not doing it lands as a single fine that will pay for the entire program for a decade.
Twenty-one units across six states with no labor fines was not a heroic achievement. It was the output of a matrix, a calendar, three ServSafe certifications, a mock inspection program, and a debrief habit. Any regional operator can build that in a quarter. Most do not, because the reward for doing it is the fine that never arrives, and that is the hardest reward to see.
See it anyway. The system is cheap. The alternative is not.