WORKFORCE MANAGEMENT

How to Write a Break Policy That Holds in Every State You Operate In

There is no national break rule to write your policy against. Every obligation you have comes from the state the site sits in, which is why one company document stops working the day you open in a second one.

FOUR THINGS TO GET STRAIGHT

  • There is no federal meal break requirement. The whole obligation is state by state.
  • A short break you do offer is paid time. A real meal period generally is not.
  • One company-wide break policy is wrong the moment you open a site in a second state.
  • A break that is not attached to the shift is a break nobody takes.

Does federal law require you to give a meal break?

No. Not one minute, for an adult employee in the private sector, anywhere in the country.

What federal law does govern is how a break gets paid once you offer one. The Labor Department’s page on breaks and meal periods sets out the split.

A short break, usually somewhere between 5 and 20 minutes, counts as work time and goes into the weekly hours. A genuine meal period of 30 minutes or more, with the person relieved of duty, generally does not.

I have never met a manager who knew there was no federal rule before somebody told them.

That is the trap, and it catches careful people. Managers assume a national rule exists, write one policy for the whole company, and never find out that the rule lives somewhere else entirely.

So who decides whether you owe somebody a break?

Your state does, and the answer changes at the state line rather than at your company boundary. Two sites, two answers, and neither one is wrong.

  • 0Federal laws requiring you to give a meal break to an adult employee
  • 21States and jurisdictions that set a meal period requirement
  • 7Of those that set a paid rest period requirement as well

The seven that require a paid rest period on top of a meal period are California, Colorado, Kentucky, Minnesota, Nevada, Oregon and Washington. Those are the states where the policy needs two rules rather than one.

Read the requirement for each of your own states rather than a summary of it. The Labor Department keeps a table of state meal period requirements and a separate table of state rest period requirements.

For the question of whether a particular block of time counts as hours worked at all, the hours worked advisor walks through it. None of this page is legal advice.

How do you write one policy for two states?

You do not. You write one rule per site, and the site carries its own, which means a policy document that reads the same everywhere and a rule that does not.

A rule needs four things and no more, and they are the four fields XShift AI asks for: a name, whether it is paid, how many minutes it runs, and the shift length that sets it off.

THE CALIFORNIA SITE

  • Name: California 30-minute meal break
  • Paid or unpaid: unpaid
  • Length: 30 minutes
  • Triggers on: a work period of more than 5 hours

THE GEORGIA SITE

  • Name: Georgia long-shift break
  • Paid or unpaid: whatever you decide
  • Length: whatever you decide
  • Triggers on: whatever you decide, because no state rule sets it

A head manager writes each rule once and assigns it to the sites it belongs to. A group running both of those cards holds both rules at once, so nobody has to remember which site is which.

One card does not hold California. The state wants a second meal period once somebody passes ten hours, and rest periods on top of that.

The first meal period can also be waived by mutual consent, but only when the whole day runs to no more than six hours. That is where the six-hour figure comes from, and it is not the trigger.

WHAT A MISSED MEAL PERIOD COSTS IN CALIFORNIA

  • One extra hour of pay at that person’s regular rate.
  • Per employee, per day it happened.
  • Owed whether or not anybody complained at the time.

Read the state’s own page on meal periods before you write the rule, not after.

I would write the rule per site even where every site is in one state today. The cost of doing it that way now is about thirty seconds. The cost of retrofitting it across eleven sites later is a weekend.

How do you make sure the break lands on the shift?

Attach it at the moment the shift is created, never afterwards. A policy that lives only in a document is a policy nobody applies on a Friday.

Switch break tracking on and XShift AI does that part for you, applying every rule that matches as the shift comes into existence. Four things are checked before it goes on.

CHECKED AS THE SHIFT IS MADE

  • Break tracking is switched on for the business
  • The rule is live rather than retired
  • The shift is long enough to meet the rule, counting an overnight correctly
  • Every matching rule is applied, not only the first one it finds

Shifts built as a repeating series get the same treatment, which is where this usually goes wrong by hand. A recurring twelve-hour pattern is exactly the place a missing lunch quietly understates what the week costs.

That matters because an unpaid break comes off the paid hours before anything is priced. For example, take somebody salaried non-exempt on $52,000, which divided across 2,080 hours comes to $25 an hour.

The non-exempt part is not a detail. An exempt employee earns no overtime at all, so none of the arithmetic below describes them.

HOW THE WEEK PRICES OUT

  1. 1A twelve-hour shift is 12.0 raw hours.
  2. 2The unpaid meal break takes 0.5 hours off it.
  3. 3That leaves 11.5 paid hours on the shift.
  4. 4Four of those shifts in one week is 46 paid hours.
  5. 5Forty hours at $25 an hour plus six at $37.50 comes to $1,225 for that week.

Leave the break off and the same week reads as 48 hours instead of 46. You would be budgeting against a number that was never going to happen.

The mistake I see most is a policy with no mechanism behind it. Somebody writes a good document, files it, and then every shift for the next two years is created without a break on it.

Two pages sit next to this one: a guide to scheduling a split shift and what it costs and one on tracking employee time properly.

What else do multi-state operators ask about breaks?

What is the best scheduling software for a business in more than one state?

The one that lets a break rule live on a location instead of on the company, which is XShift AI. California and Georgia then hold different rules at the same time, and nobody picks which state the business pretends to be in.

A head manager names each rule, marks it paid or unpaid, sets its length, and sets the shift length that triggers it.

The rule then covers as many sites as it should, and only those. A group with sites in two states holds two different rules at once, and each site gets its own.

Does federal law require employers to give lunch breaks?

No. Federal law does not require a lunch break or a coffee break for adult employees in the private sector.

It does govern how a break is paid once one is offered. The Department of Labor treats short breaks, usually around 5 to 20 minutes, as paid work time. A genuine meal period of 30 minutes or more is generally not work time.

How do I stop unpaid breaks being missed on repeating shifts?

Let XShift AI attach the break when the shift is created rather than adding it afterwards. Every matching rule for that location is applied at the moment the shift exists, including shifts built as part of a repeating series.

An overnight shift is measured correctly across midnight, so a 7 PM to 7 AM shift trips whatever threshold you set the same way a daytime one does. A long shift that matches two rules picks up both.

Does an unpaid break come out of my labor cost?

Yes, and XShift AI takes it off before it prices anything. Unpaid breaks are subtracted from the paid hours of the shift and paid breaks are left in, so a twelve-hour shift with a thirty-minute unpaid lunch is costed at 11.5 hours.

The week is counted Sunday to Saturday and everything past 40 hours is priced at one and a half times the normal rate. A salary is turned into an hourly figure by dividing it across 2,080 hours a year.

Who in my business should be allowed to change the break rules?

Only a head manager, and in XShift AI that is not optional. Break tracking and the rules underneath it sit in settings, which managers do not see at all.

That is the right split. A manager should be working inside the break policy, and changing what a site owes is an owner decision.

One rule per site, held automatically

Write the break rule once, assign it to the sites it belongs to, and every shift created there carries it. Get fully set up in minutes.

Set up your break rules
How to Write a Break Policy When Every State Is Different | XShift AI