The Cities Where Your Boss Can't Call You In With No Notice

Six U.S. jurisdictions currently regulate predictive scheduling in some form: New York City, San Francisco, Seattle, Chicago, Philadelphia, and the state of Oregon. Most require advance notice before a shift and extra pay when an employer changes it late. Whether any of them actually stop a “clopening” turnaround, a closing shift followed by an early opening the next day, is a narrower and messier question than the phrase “Fair Workweek law” implies, and the answer depends heavily on which city a worker happens to be standing in.

What these laws are actually responding to

Predictive scheduling emerged as a legislative category in the 2010s in response to a particular complaint from retail and food-service workers: not that hours were too long, but that they were unknowable. Scheduling software built to match staffing to real-time demand, a genuine efficiency gain for the employer, pushed the cost of that flexibility onto workers who couldn’t plan child care, a second job, or a class around a shift they might not learn about until two or three days out. San Francisco passed the first of the Formula Retail Employee Rights Ordinances in 2014, aimed at large chain retailers, and that early wave of organizing also gave voice to a closely related but separate complaint: workers who did get plenty of advance notice still sometimes closed a store at 11 p.m. and opened it again at 6 or 7 a.m. the same week. That pattern earned its own nickname among restaurant and retail workers well before most of the ordinances existed, and it’s the pattern this piece is about.

The laws that followed, Seattle’s Secure Scheduling Ordinance, New York City’s Fair Workweek Law (with separate provisions for fast food and retail), Oregon’s statewide predictive scheduling law, Philadelphia’s Fair Workweek law, and Chicago’s Fair Workweek ordinance, share a general shape without sharing exact numbers. Each requires employers to post schedules a set number of days ahead, commonly discussed as somewhere around two weeks, though the exact figure and the penalty for missing it differ by city and by whether it’s a first or repeat violation. Each requires some form of “predictability pay,” extra compensation owed when a covered employer adds, cancels, or shortens a shift after the notice deadline has passed. And in most of these ordinances, rest between shifts gets addressed as its own separate provision, not folded into the notice rule, because the two problems aren’t the same problem.

Why notice and rest are different problems

These two protections get filed under one banner, but they solve different problems. A notice requirement solves for unpredictability: a worker who knows their schedule two weeks out can arrange child care, a second job, or a class around it. A rest requirement solves for something else entirely: even a schedule known two weeks in advance can still put a closing shift directly against an opening shift with ten hours between clock-out and clock-in, once a commute and a wind-down are subtracted. An employer can comply fully with a notice provision and still clopen someone. Predictability and adequate rest are separate legislative asks, addressed by separate provisions where they’re addressed at all, and a city that’s strong on one is not automatically strong on the other.

An original comparison: what each jurisdiction actually protects

There’s no single published table anywhere that lines these six jurisdictions up on the clopening question by itself, because most coverage of Fair Workweek law is organized around the notice-period and predictability-pay provisions that draw the political attention, with rest-between-shifts treated as an afterthought. The comparison below is built for that gap. It’s a synthesis of the general shape of each law’s public provisions, not a legal citation for any single figure. Treat the notice-period numbers as commonly cited approximations: exact day counts and penalty structures shift with amendments, and a worker in a given city should confirm the current ordinance text rather than take a number from any one article, this one included.

Jurisdiction	Advance notice	Rest-period / clopening provision	Predictability pay	Covered industries (general)
New York City (Fair Workweek Law)	Commonly cited around two weeks for fast food and retail	Yes. Fast-food workers generally must be given at least 11 hours between the end of one shift and the start of the next, or the employer owes extra pay	Yes, for late changes to a posted schedule	Fast food chains, retail employers above a size cutoff
Seattle (Secure Scheduling Ordinance)	Commonly cited around two weeks	Yes. Workers can decline a shift starting less than roughly 10 hours after the previous one ended, and are owed extra pay if they accept it anyway	Yes	Large retail and food-service employers above employee-count minimums
Oregon (statewide)	Commonly cited around one week minimum, with longer notice generally encouraged	Yes. Workers have a right to roughly 10 hours of rest between shifts and can decline without retaliation, with a premium owed if they consent	Yes	Retail, food service, and hospitality employers above an employee-count minimum
San Francisco (Formula Retail Employee Rights Ordinances)	Advance posting required; commonly discussed in the one-to-two-week range	Addressed less directly than in NYC, Seattle, or Oregon. The original ordinances lean more heavily on notice and predictability pay than on a stated rest-hour minimum	Yes	Formula (chain) retail employers above a store-count minimum
Philadelphia (Fair Workweek law)	Commonly cited around two weeks	Yes. A stated rest period between shifts, with the right to decline a shift that doesn’t provide it and a premium if the employee agrees anyway	Yes	Retail, food service (including fast food), and hospitality, above employer-size minimums
Chicago (Fair Workweek ordinance)	Commonly cited around two weeks, shorter for newer employees	Yes. A stated rest period between shifts, generally in the same range as the other city ordinances, with premium pay if the worker agrees to a shorter turnaround	Yes	Retail, food service, hospitality, health care, warehouse services, building services, and manufacturing, above size minimums

Read that table for shape, not for exact hour counts. What it should communicate is the pattern: most of these six jurisdictions do address clopening directly, most describe the protection the same way (a right to decline, or a premium if the worker accepts anyway, rather than an outright ban), and San Francisco’s original ordinances lean more heavily on the notice side of the problem than on a stated rest-hour floor. That last part matters for anyone assuming “my city has a Fair Workweek law” automatically means “my city has solved clopening.” It might. It might also mean the city solved a different, related problem and left this one mostly alone.

The gap even the strongest version of these laws leaves open

Even where a rest-period provision exists and is enforced well, it’s addressing a number on a clock, not the actual physiology of the turnaround. A worker who closes at 11 p.m. and is legally guaranteed 11 hours before the next shift starts at 10 a.m. has technically cleared the bar in a city like New York. But 11 hours on paper isn’t 11 hours of sleep. Subtract a 40-minute commute each way, half an hour to decompress and eat something, and the time it actually takes an adult to fall asleep after a stressful closing shift, and the realistic sleep window on a fully compliant schedule can land closer to eight or nine hours: survivable, but short of what a body recovering from a full closing shift needs, at an hour when its own alerting signals are working against a fast, clean sleep onset in the first place. That’s a distinction the political success story tends to blur. These ordinances were fought for and won as real worker protections. They were also built to regulate a number on a schedule, not the lived experience of a body trying to fall asleep fast enough to make that number mean anything. A law guaranteeing 10 or 11 hours between shifts is a genuine floor. It is not the same claim as “enough rest,” and no jurisdiction’s ordinance language actually claims otherwise once you read past the headline notice-period figure.

There’s a plainer limitation too, and it shouldn’t get glossed over: enforcement of these ordinances varies by city, self-reported violation rates are hard to verify independently, and a worker’s practical ability to use a “right to decline” a shift isn’t the same thing as that right existing on paper. A worker in a covered industry, at a covered employer, in one of these six places, who’s offered a clopening shift without adequate rest before it, generally has three moves available: decline the shift outright, accept it and collect the premium pay the ordinance requires, or raise the pattern with a manager under the ordinance’s protection against retaliation for asking. Whether any of those three is realistic for a given worker, at a given store, on a given week, is a question the law doesn’t answer. It depends on things no ordinance can legislate directly, like whether asking to decline quietly costs someone the good shifts the following month.

Where coverage runs out

Zoom out from these six places and the picture shrinks fast. There’s no federal predictive-scheduling law. A handful of other cities and a couple of additional states have considered similar bills without passing them, and coverage even inside the six places above is generally capped to a short list of industries and to employers above a size minimum, meaning a worker at a small independent restaurant in the same city as a covered chain may have no statutory protection at all for the identical clopening pattern. For a worker whose real legal exposure is less “am I scheduled fairly” and more “can I be fired outright for the morning after,” that’s a related but different question, and it’s covered in what employment law actually says about getting fired for oversleeping. A bad clopening turnaround and a missed alarm the next morning can turn into the same conversation with a manager, but the protections that apply to each aren’t the same protections.

For most workers outside these six places, and for plenty of workers inside them whose employer sits under the size minimum, the plain state of the law is that nothing stops a schedule from being built this way. A restaurant line cook’s account of what actually gets her out of bed on a five-day-a-week opening schedule is a useful companion here for exactly that reason: her schedule is at least consistent, which researchers studying shift transitions generally treat as easier on the body than an irregular rotation, but consistency and adequate rest between a close and an open aren’t the same thing either, and no ordinance guarantees both. Workers dealing with rotating patterns more broadly, not just the close-to-open turnaround alone, may find the broader rundown of shift-work sleep strategies useful for the parts of the problem that sit entirely outside anything a city ordinance touches.

What an app can and can’t do about any of this

This is not a problem DontSnooze, or any accountability app, can fix. An app doesn’t set notice requirements, doesn’t create a rest-period floor, and can’t make an employer schedule an opening shift with enough runway after a close. That’s a policy fight, decided city council by city council and legislature by legislature, and it’s being decided unevenly on purpose. Some places have chosen to regulate this. Most haven’t. No product changes that math, and it would be dishonest to pitch one as though it could.

Where the idea behind DontSnooze has a real, if narrow, use for someone actually living through a clopening pattern is smaller than fixing the schedule. On the mornings when the body clock has been wrecked by a tight or unpredictable turnaround, waking up on the first alarm gets harder, and that’s exactly the situation where a person is most likely to hit snooze half-asleep and not fully register doing it. DontSnooze’s model, thirty seconds to record video proof of actually being up, or an embarrassing photo goes out to friends automatically, doesn’t touch the scheduling problem that created the exhaustion. It only addresses one narrow piece sitting after that problem: whether the alarm that does go off actually gets answered. For a retail or restaurant worker whose schedule this month is legal, compliant, and still brutal, that’s real but limited help. It is not a substitute for the rest a fairer schedule would have provided in the first place.

The short version

Predictive-scheduling law in the U.S. is real and spreading slowly, and where it exists it generally does more for a worker’s ability to plan than for the physiology of a fast close-to-open turnaround. New York City, Seattle, Oregon, Philadelphia, and Chicago each build some form of rest-period protection into their ordinances, typically structured as a right to decline plus a premium if the worker agrees anyway rather than an outright prohibition. San Francisco’s original ordinances lean more toward notice and predictability pay than a stated rest-hour minimum. Everywhere else, in most American cities and every state without its own version of this law, there’s currently no statutory floor on the close-to-open turnaround at all. A worker checking whether their own schedule is protected has to check three things separately: their city or state, their industry, and their employer’s size, because any one of the three can put someone entirely outside coverage even while a coworker two towns over, doing the identical job, is protected.