How ScheduleLord warns you about US labor laws while you schedule
Scheduling rules in the United States aren't one set of rules. They're 50 states, a few dozen cities, and a lot of exceptions. A schedule that's fine in Texas can break the law in California, and a closing shift followed by an opening shift can cost you a penalty in Seattle but not in Houston. ScheduleLord checks your schedule against the rules for each location as you build it, and tells you before you publish.
What you see
You don't turn anything on. When you add or edit a shift, ScheduleLord looks at the location, the employee, and the rest of that person's week. If the shift would break a rule, a warning appears right on the form, and the same warning shows up on the week calendar and in the staff view.
A warning says what the problem is and, where it matters, what it costs. For example:
- Daily overtime: Sam would exceed 8 hours worked today.
- Clopen conflict: Sam would have less than 11 hours of rest between shifts. This location requires written consent, or owes a $100 penalty per instance.
- Day of rest conflict: Sam would work all 7 days this week. California bars more than 6 days of work in a workweek without equivalent rest.
A "clopen" is when someone closes at night and opens the next morning without enough rest in between. More on that below.
Warnings never block you. You can save the shift anyway, because only you know whether you have a signed consent form, an exemption, or a good reason. A warning is a heads-up, not a gatekeeper.
What it checks
Overtime. Everywhere in the US, ScheduleLord flags anyone who would go past 40 hours in a week. A few states also count overtime by the day:
- California after 8 hours in a workday
- Colorado after 12 hours in a workday, or 12 consecutive hours, so an overnight shift that crosses midnight is still counted as one stretch
- Nevada after 8 hours, but only for employees earning under $18 an hour
- Alaska after 8 hours, but only at employers with 4 or more employees
Required breaks. Many states require a meal or rest break on longer shifts, and each one is a little different. Colorado wants 30 minutes on shifts over 5 hours. California wants a second break at 10 hours. Washington wants the break to start between the second and fifth hour. ScheduleLord checks the shift and its breaks against the rule for that state, including the timing rules, and the warning clears when you add a break that qualifies. Nineteen states are covered. The state-by-state guide lists each one.
Rest between shifts, known as clopening. A handful of cities and states require a minimum gap between a closing shift and the next opening shift, and charge a premium if you break it:
- New York City, 11 hours
- Berkeley and Emeryville, California, 11 hours
- Oregon, Seattle, Chicago, Los Angeles and Washington, D.C., 10 hours
- Philadelphia, 9 hours
These rules only apply to bigger employers, so ScheduleLord compares your organization against each rule's size cutoff first. A 12-person shop in New York City won't be warned about a rule that covers employers with 20 or more employees. The clopening guide has the details.
A day of rest. Texas, New York, California, Connecticut, Illinois, Massachusetts, Wisconsin, Maryland and New Hampshire each require a day off in a week, with different exemptions for short weeks, short days, and certain industries. ScheduleLord flags a seventh consecutive day and applies the exemptions it knows about. Kentucky and California also owe premium pay on a seventh consecutive day, so those show up as an overtime notice instead of a conflict.
Rhode Island Sundays and holidays. Rhode Island treats Sundays and a list of holidays as premium-pay days. A shift on one of them gets a notice naming the day, whether that's Labor Day or Victory Day.
The basics, too. Double-booked shifts, a second shift on the same day, and scheduling someone during time off you already approved get warnings as well.
It starts with the address
Most of these rules depend on where the work happens, not where your company is registered. ScheduleLord uses each location's address to find its state and city, so an organization with a Denver location and a Portland location gets Colorado's rules for one and Oregon's for the other. We even check whether a Los Angeles address is in the city or in unincorporated county territory, because the rules differ.
That means a location needs a full address before any of this works. If one is missing, ScheduleLord nudges you to finish it, on the schedule page and on the shift form, rather than quietly skipping the checks. See missing location address.
When ScheduleLord can't check a rule, it says so. If you schedule someone in Nevada and they have no hourly wage on file, you get a warning that Nevada's rule can't be checked, instead of silence that looks like "all clear."
It follows the schedule everywhere
The same checks run wherever a shift can change:
- The shift form and the plan page, including draft shifts you haven't published.
- Shift offers and swaps in the team chat. If a coworker taking a shift would put them over a limit, the change waits for a manager to approve it instead of going through quietly. We wrote about that in Team chat is now built into ScheduleLord.
What it isn't
ScheduleLord is not a lawyer, and the warnings are not legal advice. Labor law changes, and it has exceptions that depend on your industry, your size and your contracts. We research each rule from public sources and write it down, and we build the warnings from that research. They're a good way to catch the mistakes that are easy to make and expensive to find out about later. They don't replace someone who knows your business checking the rules that apply to you.
We also haven't covered every rule in every state. The list above is what ScheduleLord checks today. We've researched all 50 states and D.C., and we add rules as we work through them. If your state has a rule you'd like to see, tell us.
How we built it
This part is for the curious.
- Each rule is data, then a check. A rule is a small table entry: the state or city, the threshold, the penalty text and the size cutoff. One function reads the table and decides if a shift breaks it. Adding a state is mostly adding rows.
- Every rule has a "doesn't apply" case. The checks return nothing when you're under a rule's size cutoff, or when an exemption applies, and we test that as carefully as the warning itself. A false alarm teaches people to ignore the real ones.
- Time zones are the location's. A "workday" and the gap between a closing and an opening shift are measured in the location's own time zone, not the viewer's.
- The guides are generated from our tests. Every example in the scheduling warnings guides, screenshots included, comes from an automated test that runs the app. If a rule changes and the test fails, the guide can't quietly go stale.
Try it
Labor law warnings are included for everyone. ScheduleLord is free for up to 15 employees at one location, with no credit card needed. Head to schedulelord.com and click Get started free, then add your location's address and start scheduling.