How to Eliminate Clopening Shifts in Hospitality Without Losing Coverage

Key takeaways

• A clopening shift — closing one night and opening the next morning — leads to burnout, turnover, and potential Fair Workweek violations in seven United States (US) jurisdictions.

• Deputy data shows 31% of hospitality workers already want to leave; clopening accelerates that attrition.

• You can eliminate forced clopens by setting minimum rest-period rules, using demand forecasting, and opening a shift marketplace for voluntary coverage.

• Scheduling software like Deputy can help flag clopening conflicts before you publish a schedule.

Table of contents

• What is a clopening shift?

• Why clopening is a bigger problem than most managers realize

• Where clopening is regulated: a US jurisdiction guide

• Five steps to eliminate clopening without losing shift coverage

• How Deputy helps you stay ahead of clopening compliance

• Frequently asked questions about clopening

What is a clopening shift?

A clopening shift is when an employee closes a business one night and opens it the next morning, leaving fewer than 11 hours of rest between shifts. The term blends "close" and "open" — and if you manage a hospitality team, you've probably seen it happen more often than you'd like.

Picture this: your hotel front-desk agent finishes their closing shift at 11 p.m. and walks back through the door at 6 a.m. to open. Or a restaurant server wraps up at midnight after a busy Saturday and returns at 7 a.m. to set up for brunch. That's a clopen — and it's rough on the person working it.

Hospitality gets hit harder by clopening than most industries. Late-night service hours, early-morning prep, thin staffing during off-peak windows, and seasonal surges all push managers toward scheduling the same reliable people to close and open. When you're short-staffed and trying to keep things running, clopens can feel like the only option.

But they come with real costs — to your team's wellbeing, your turnover rate, and increasingly, your legal exposure. Several US cities and one state now regulate minimum rest periods between shifts, and the list is growing. We'll break down exactly where those laws apply later in this article.

The good news? Clopening is a solvable problem. With the right hospitality staff scheduling practices, tools, and a little culture change, you can protect your team's rest without leaving gaps on the floor.

Why clopening is a bigger problem than most managers realize

Clopening doesn't just make your team tired. It drives your best people out the door — and the data backs that up.

According to The Big Shift Report 2025, 31% of hospitality workers are considering leaving their jobs. That's the highest rate across all shift-based industries. Even more alarming, 22% are actively looking to resign — seeking opportunities at a different company, in a different industry, or leaving the workforce entirely.

The same report found that 20% of hospitality workers report feeling "Stressed," "Frustrated," or just "Okay" after their shifts. That sentiment has stayed largely unchanged through years of cost-of-living pressure, which means the problem isn't getting better on its own.

Now connect those dots to clopening. When your team doesn't get enough rest between shifts, fatigue builds up fast. Fatigued workers call off more often, make more mistakes on the floor, and deliver worse guest experiences. They're also far more likely to look for a job that respects their time. In an industry where over a million roles already sit unfilled, you can't afford to push your existing staff toward the exit. The staff retention challenge in hospitality is already steep enough without making it worse.

There's a safety dimension too. A bartender running on four hours of sleep is more likely to slip on a wet floor, mishandle a knife, or make an error during a rush. A front-desk agent who can barely keep their eyes open at 6 a.m. isn't going to catch a booking mistake or handle a guest complaint well. Clopening doesn't just burn people out — it creates real operational risk.

Here's the thing — money alone won't fix it. The Big Shift Report 2025 found that every $1 per hour wage increase makes hospitality workers 13% more likely to report positive sentiment after their shift. That's meaningful. But schedule quality is the non-wage version of that same lever, and it costs you nothing to pull.

If you're operating in a city with Fair Workweek laws, clopening carries another risk: premium-pay penalties. Let's look at exactly where those rules apply.

Where clopening is regulated: a US jurisdiction guide

Fair Workweek laws — sometimes called predictive scheduling laws — are active in several US cities and one state. These regulations require covered employers to provide minimum rest periods between shifts and pay premiums when they violate those rules. For a comprehensive overview, see the US Department of Labor's fact sheet on scheduling law penalties.

Here's a breakdown of where clopening-related regulations currently apply:

A few things to keep in mind as you review this table.

These laws evolve. New jurisdictions are considering similar legislation, and existing ones update their rules. Always consult local counsel for your current requirements. Deputy's Fair Workweek compliance features help surface potential scheduling conflicts before you publish, but they don't replace legal advice.

The rules around voluntary clopens also vary. In some jurisdictions, an employee can consent to a shorter rest period — but the documentation requirements differ. New York City requires written consent. Oregon doesn't allow waivers for covered employers at all.

Even if you operate outside these seven jurisdictions, eliminating clopens is still smart business. The retention and safety risks exist everywhere. The legal requirements just add financial penalties on top.

If you're unsure whether your operation is covered, start by checking employee count thresholds and industry classifications for your locations. And keep an eye on your state legislature — more jurisdictions are considering similar bills each year. The National Women's Law Center's fair scheduling fact sheet and your state labor department's website are reliable starting points.

Five steps to eliminate clopening without losing shift coverage

You don't have to choose between rested workers and a fully staffed floor. Here are five steps you can act on this week.

Audit your current schedules for hidden clopens

Most managers don't realize how often clopening happens because it's buried in shift patterns. Start by running a report that filters for any shifts with fewer than 11 hours between an employee's end time and their next start time.

Look for patterns. Who gets clopened most often? Is it concentrated on certain days — like Friday close to Saturday open? Is it hitting specific roles harder, like bartenders or front-desk agents? You might be surprised to find that a handful of your most dependable team members are absorbing the majority of clopens simply because they never say no.

Once you can see the problem clearly, you can start fixing it. Document what you find — you'll need that baseline to measure progress.

Deputy's reporting tools make this audit straightforward. As Hazel de los Reyes, co-founder of Gumption Coffee, explains: "The more I use Deputy, the more it becomes an oracle for my staffing issues. If there are gaps in your talent mix or shifting hours, Deputy will show that very clearly."

Set minimum rest-period rules in your scheduling system

Once you've identified where clopens are happening, build a guardrail to prevent them going forward. Configure your scheduling tool to enforce a minimum gap between shifts. Eleven hours is the safest default — it meets or exceeds the rest-period requirement in every current US jurisdiction.

Deputy's scheduling rules let you set rest-period minimums that block clopening conflicts before a schedule is published. You can choose between two approaches:

• A hard block

  that prevents the schedule from publishing if a clopening conflict exists

• A soft alert

  that warns you about the conflict but allows an override with documentation

The right choice depends on your jurisdiction and how strictly you need to enforce rest periods. If you're in New York City or Oregon, a hard block is the safer path. In jurisdictions without formal Fair Workweek laws, a soft alert still gives you visibility — you can track how often managers override the warning and address the pattern.

The key is making the default the right behavior. When your scheduling system flags clopens automatically, managers don't have to remember to check every shift gap themselves. The tool catches what a tired manager at 10 p.m. on a Sunday might miss.

Use demand forecasting to staff smarter, not thinner

Clopening often happens because managers are short-staffed and default to scheduling the same reliable closers to open. The root cause isn't bad intent — it's not having enough visibility into when you actually need people.

Demand forecasting fixes that. It uses historical sales data, foot traffic patterns, and seasonal trends to predict your busy and slow periods. With that information, you can match staffing levels to actual need rather than guessing — and stop relying on the same overworked closers to fill morning gaps.

With over a million hospitality roles still open across the US, operational efficiency isn't optional — it's a necessity. You need every shift to count.

Ariana Korman, chief operating officer of Juice Press, says: "Deputy helps us with projecting where sales will be and where we should allocate labor to accommodate that."

AI-powered scheduling tools like Deputy's auto-scheduling can account for rest-period rules, employee availability, and demand forecasts all at once. Instead of building a schedule and then checking for conflicts, the system builds a conflict-free schedule from the start. Learn more about how AI shift planning can help you address staffing shortages.

This matters most during seasonal surges — think holiday weekends, summer tourist season, or New Year's Eve — when the temptation to clopen your strongest team members is highest. Forecasting helps you plan ahead so you're not scrambling the night before.

Open a shift marketplace so coverage is voluntary, not forced

Instead of assigning the same person to close and open, post the open shift to your team. Let someone who's rested and available pick it up. This keeps your coverage intact without forcing a clopen on anyone.

Deputy's open-shift feature sends notifications to qualified, available employees when a shift needs filling. Your team members can claim the shift from their phone in seconds. You keep coverage; they keep their rest. And because the system only notifies people who are qualified for the role and available based on their set preferences, you don't end up with an unqualified fill.

This approach also respects what hospitality workers actually want. Research shows that 44% of US shift workers value the ability to meet other commitments, and 48% say they appreciate schedule flexibility. Having a clear shift swap policy alongside a shift marketplace gives your team more control — which makes them more likely to stay.

Gonzalo Aurelios-Solis, cafe manager at Partners Coffee, says: "By managing our labor costs and scheduling better, we've been able to retain more staff. Baristas are getting the schedules they needed and I'm able to provide the business what it needs as well."

Build a no-clopening culture from the top down

Policy alone doesn't fix clopening — manager behavior does. If shift leads keep swapping or reassigning shifts without checking rest gaps, all your scheduling rules fall apart.

Train your shift leads to verify rest periods before approving any shift swap or reassignment. Make your no-clopening policy visible: post it in the break room, include it in onboarding materials, and explain the "why" to your team. When people understand that adequate rest makes them better at their jobs, they're more likely to support the policy.

Remember the $1-per-hour wage data from earlier? Every dollar increase makes workers 13% more likely to report positive sentiment. Schedule quality is the zero-cost version of that same lever. You're giving your team something they value — predictable rest — without spending an extra dollar on payroll.

Use scheduling reports to monitor how well your team follows the policy over time. Flag managers who consistently override rest-period rules, and coach them on why it matters. When clopening stops being the default, your team notices — and your retention numbers will reflect it.

How Deputy helps you stay ahead of clopening compliance

If you're ready to eliminate clopening from your operation, the right scheduling software makes the difference between a policy that sticks and one that falls apart within a week. Here's how Deputy's features specifically address clopening prevention and Fair Workweek requirements.

Auto-scheduling builds schedules that respect the rest-period rules you set, along with employee availability and demand forecasts. Instead of creating a schedule and then manually checking for clopening conflicts, Deputy's auto-scheduling factors in those constraints from the start.

Compliance alerts flag potential Fair Workweek violations — including clopening — before you publish a schedule. You see the issue while you can still fix it, not after a team member has already been assigned a back-to-back close and open.

Open shifts let employees voluntarily pick up shifts that need filling. When someone calls off or you're short for an opening shift, you don't have to default to the person who just closed. Post the shift to your available team and let someone rested claim it.

Break and attestation tracking documents that employees took their rest periods and breaks. If you're in a jurisdiction that requires audit trails for scheduling compliance, this feature keeps your records organized without adding admin work to your managers' plates.

Scheduling reports give you visibility into patterns over time. You can see which locations or managers are generating the most rest-period conflicts and take corrective action before small issues become systemic problems.

Dennis Novak, head of showrooms at Proper Cloth, says: "Deputy definitely helped us stay on top of compliance because we also have the attestation where somebody marks off that they have actually taken their breaks. From a liability standpoint, that puts us at ease."

Hazel adds: "Fair Workweek is about the principle of people not being overworked. I like the fact that Deputy enables me to monitor workload and stress."

Deputy won't replace your legal counsel, and it doesn't guarantee compliance outcomes. But it gives you the tools to spot issues early, enforce rest-period rules consistently, and keep documentation that supports your compliance efforts.

Ready to see how it works for your team? Try Deputy for free and start building schedules that protect your team's rest without sacrificing coverage.

Frequently asked questions about clopening

Is clopening illegal?

It depends on where you operate. Seven US jurisdictions — including New York City, Oregon, Chicago, Seattle, Philadelphia, and Los Angeles — have Fair Workweek laws that regulate minimum rest periods between shifts. Outside those areas, clopening isn't explicitly illegal but still carries retention and safety risks. Deputy's scheduling rules help you stay compliant regardless of your location.

What is an example of a clopening shift in a restaurant?

A server closes the restaurant at 11 p.m., finishes side work by midnight, then returns at 6 a.m. to open — getting fewer than six hours of sleep. Deputy flags these conflicts automatically when you build your schedule.

Can an employee volunteer for a clopening shift?

In some jurisdictions like New York City, yes — but you need written consent and documentation. Oregon's law doesn't allow waivers for covered employers. Deputy can log consent acknowledgments and track rest-period exceptions so you have an audit trail.

How does Deputy help prevent clopening?

Deputy's auto-scheduling respects minimum rest-period rules you set, flags conflicts before publishing, and lets you open unfilled shifts to available team members — so you maintain coverage without forcing back-to-back closes and opens.