Fair scheduling for a small team: rotating closes, weekends and availability

Nothing in a small restaurant gets talked about more than the schedule. Who got the Saturday off, who's closing again, why the new hire got the good shifts. Most of the time it isn't anyone being unfair on purpose. The schedule gets built in a hurry on Sunday night from last week's copy, and the same patterns repeat until somebody quits over them.

Fairness on a schedule isn't about everyone getting the same shifts. It's about the hard shifts being shared, the rules being known, and people being able to plan their lives.

This is the fifth post in our series on leading your first team. If you're building a schedule for the first time, start with your first restaurant staff schedule and our weekly schedule template; this post is about keeping it fair once it's running.

This is general information, not legal advice. Updated October 5, 2026: the fair workweek coverage on the city and state pages linked below was checked against those pages.

Write the rules down

Most schedule arguments come from rules that live only in the scheduler's head. Write a short set, share it with the team, and stick to it:

• When the schedule is published, and how far ahead (two weeks is a good target).
• When availability is due, and how far ahead time-off requests need to come in.
• How closes and weekends are shared (more below).
• How holidays are decided, and how they rotate from year to year.
• How swaps work: who can swap with whom, and who approves.
• How hours are cut in a slow week, and how extra hours are offered.

A rule doesn't need to be perfect. It needs to be the same for everyone, and changed openly when it changes.

Rotate the closes

Closing is usually the least popular shift: late, physical, and the one that gets blamed when the opener finds something undone. If the same two people close every night, you'll lose them, or they'll stop closing properly.

A simple rotation for a small team:

1. List everyone who's trained to close. If that's only two people, training a third is your first job (our delegation ladder works for the close too).
2. Give each person a target, for example "two closes a week, no more than three."
3. Keep a tally. A sheet with names down the side and weeks across the top, with the number of closes in each cell. Look at it before you build next week.
4. Swap who gets the "easy" closes. A Tuesday close isn't a Saturday close.

Some people genuinely prefer closing, because of school, a second job or because they're not morning people. That's fine. Fairness is about nobody being stuck with a shift they don't want, not about forcing everyone to do every shift.

Don't schedule the close-then-open

A close followed by the next morning's open, sometimes called a "clopening", leaves someone with a short night's sleep and a long commute in between. Even where no law forbids it, avoid it. Make it a written rule: a set number of hours between the end of a close and the start of the next shift, and only by the person's own choice if it ever happens.

Some cities make this a legal rule for the employers they cover; see the fair workweek section below.

Share the weekends and holidays

Weekends are when people's friends and families are off, and when you need the most staff. Both are true, so share them openly:

• A weekend rule everyone knows, such as "everyone gets at least one full weekend off a month," or "every other Sunday off."
• Holidays by rotation. Whoever worked Thanksgiving this year gets first pick of time off next year. Write it down so you remember in twelve months. Our guide to holiday and event staffing covers planning the holiday week itself.
• Time off approved in order. First come, first served, by the date the request came in, within your limits on how many people can be off at once.

Track weekends the same way as closes: a tally of weekend shifts per person per month.

Keep availability current

Availability goes stale fast. A school term starts, someone takes a second job, a parent's schedule changes. Ask everyone to update theirs on a schedule, every three months and before the summer and fall changeovers (our back-to-school scheduling guide covers the fall switch).

Treat availability in two layers:

• Can't work: school, another job, childcare. Respect it every time. If you schedule someone in their "can't" hours, you're scheduling a call-out.
• Prefers not to: "I'd rather not close on Fridays." Respect it when you can, and say so when you can't.

Ask people to keep their "can't" list honest. Someone who's available "any time except evenings, weekends and mornings" isn't really available, and that's a conversation for a check-in, not for the schedule.

Cut and add hours fairly

In slow weeks, cuts usually go to whoever complains least. Instead:

• Ask for volunteers first. Some people are glad of a day off.
• Then rotate the cuts, and keep track, so the same person doesn't lose hours every slow week.
• Offer extra hours the same way, to people who've asked for more, before you hire. A new hire taking hours an existing employee wanted is a quick way to lose that employee.
• Explain it. "Sales are down this month, so everyone loses one shift, and here's the order."

Our slow-season guide has the step-by-step version.

Fair workweek laws: where they apply

A handful of cities, and the state of Oregon, have "fair workweek" or "predictive scheduling" laws that turn some of the habits above into legal requirements: posting schedules in advance, paying extra for changes after posting, and protecting rest between a close and an open. They generally cover large employers and chains, not an independent café, but check if you're part of a franchise or a larger group.

Each page summarizes the notice period, the pay owed for changes and the rest rule, and links the city's or state's own source. Los Angeles has a fair work week law too, but it covers retail, not restaurants (Los Angeles pay rules). Laws and thresholds change, so read the official source for your city before you rely on any summary.

Even if none of them reaches you, they're a useful benchmark. Two weeks' notice, few changes after posting, and real rest between shifts are what a fair schedule looks like anyway.

Check the schedule before you post it

A two-minute fairness check before you publish:

• Did anyone get more closes than their target? More than one close-then-open?
• Does everyone have their weekend this month?
• Is anyone scheduled in their "can't work" hours?
• Did the cuts land on the person who had them last time?
• Are approved time-off requests honored?

Then publish on your usual day, and change as little as possible afterwards.

Where Mays fits

• Availability in writing. Staff set their own in the app under Schedule → Availability: a Recurring week, or a Temporary pattern for a date range like a school term, with each day Available or Not available, all day or between set times. Managers review it under Scheduling → Availability. For a "prefers not to," add a scheduling note: the note icon next to a name on the schedule (Add a scheduling note), visible to managers only.
• Time off in order. Requests come in with dates and get approved or declined under Scheduling → Time Off, where you can also set Blocked Days and Advance notice for time off.
• Swaps and extra hours. Staff offer a shift with Hand off or Swap in the app, and a manager always approves. Open shifts let anyone at the location claim extra hours, with your approval.
• An even first draft. The web Auto-schedule respects approved time off and availability and the weekly overtime threshold, and evens out the number of shifts so people end up close to last week's count. It doesn't look at rest time between a close and the next open, so check that yourself.
• The numbers for your tally. Scheduling → Reports → Scheduled Hours & Wages gives each person's shifts and hours for any date range, and Shift Pool shows who offered up, picked up or traded shifts.
• Fewer surprises after publishing. Notify only affected people tells just the people whose shifts changed.

Mays doesn't count closes or weekend shifts per person, so keep the close and weekend tally on your own sheet. It also doesn't track fair workweek rules: it doesn't check how far ahead a schedule is posted, calculate pay for changes after posting, or warn about a close followed too soon by an open. If a fair workweek law covers you, keep those records yourself.

Your fair scheduling checklist

• Written schedule rules, shared with the team
• Two weeks' notice as the target, and few changes after posting
• A close rotation with targets and a tally
• No close-then-open unless the person chooses it
• A weekend rule, and holidays by rotation
• Availability updated every three months, with "can't" and "prefers not to" kept apart
• Cuts and extra hours rotated, and offered to the existing team first
• A check of whether a fair workweek law covers you

Build a fairer schedule with Mays

Collect availability and time off in one place, build the week around it, and tell only the people whose shifts changed.

Start your free trial: 30 days, every module, no card needed. Next in this series: handling conflict between staff.