A regional bar group ran the same tip pool policy at every location — kitchen included, split evenly across front-of-house by hours worked. It worked fine for two years. Then a location in California got a demand letter, because California bans tip credits and restricts pooling with back-of-house staff in ways the head office’s one-size-fits-all policy didn’t account for. Nobody had done anything maliciously wrong. The policy was just written for one state and applied everywhere. That gap is exactly where tip-pool lawsuits live.
Why this is genuinely harder than it looks
The federal tipped minimum wage has sat at $2.13 an hour for decades, with the rest made up through tips under the federal tip-credit system — except California, Washington and Oregon ban tip credits entirely, and several other states layer on their own rules about who can legally be included in a pool. A policy that’s fine in Texas can be a violation in Seattle. And tip-pool disputes aren’t a rare or theoretical risk — they’re a live, recurring category of wage-and-hour litigation, often triggered by exactly the kind of thing that sounds minor until a lawyer’s involved: a manager who dips into the pool, a back-of-house split that wasn’t allowed in that state, or simply no clean record of who worked which shift and how the pool was split that night. Owners rarely find out about the gap until a former employee, or a state labor department, asks a question the paperwork can’t answer.
What actually needs to happen
Asky doesn’t give legal advice, and no software replaces checking your specific state’s rules. What it can do is remove the most common failure point underneath most of these disputes: nobody can produce a clean record when it’s asked for.
Know who worked, and in what role, down to the shift
Tip-pool rules almost always hinge on role — who’s eligible, who isn’t, and whether back-of-house can be included at all. Asky’s role-based permissions mean the system already knows who was working as a bartender, a barback or a server on a given night — not a distinction that lives only in a manager’s memory.
Make the hours and the split itself auditable
Shift tracking that has staff start, pause and close their own shifts gives you sales, hours and cash per team member in real time — not reconstructed after the fact from a schedule and a guess. When a dispute does surface, “what were the hours and the split that night” is a report you can pull, not a question you have to reconstruct from memory three months later.
Close the books the same way, every night
End-of-day reports — sales by item, staff hours, variance — finalize the moment you close, with no spreadsheet assembled by hand on Sunday morning. A spreadsheet someone builds after the fact is exactly the kind of record that falls apart under a lawyer’s questions. An itemized report generated automatically, the same way every night, is the opposite.
Run each location on its own state’s rules, inside one system
A multi-location bar group doesn’t get to run one national tip policy — the whole problem is that Texas rules and California rules aren’t the same rules. What each location needs is its own configured tip-pool policy that matches its own state, while still reporting into the same dashboard the head office actually looks at. That’s the difference between “we have a company policy” and “we have a policy that’s actually legal everywhere we operate” — the second one requires knowing what’s different location to location, not assuming they’re all the same.
Closing
None of this replaces actually knowing your state’s rules — check them, and check them again if you operate in more than one state, since $2.13 an hour and a banned tip credit are not the same starting point. What clean, itemized, role-based records do is make sure that when the question gets asked, you have an answer instead of a shrug. Most tip-pool lawsuits aren’t won on the policy. They’re won on whoever kept the better records.