How to Rotate Closing Shifts Fairly Among Store Managers

Every store manager has had the conversation. An ASM pulls you aside and says some version of "I have closed three Saturdays in a row." You pull up last month's schedule to check, and either they are right and you feel bad, or they are wrong and now you have to prove it. Either way you have lost twenty minutes and some trust. This post is about building a closing rotation for your leadership team that removes that conversation entirely.

Why closing rotations go wrong

Closing is the shift nobody wants. It runs late, it eats the evening, and on a Saturday it wrecks the weekend. When the person building the schedule is also one of the people on it, the temptation to protect a few nights is real, and even when you are scrupulous, memory is bad at this. You remember who closed last week. You do not remember who closed the second Saturday of the month before last.

Three patterns show up again and again in unfair closing rotations. The first is week-by-week thinking: each week looks balanced on its own, but the same manager keeps landing the Saturday close because of how the weeks line up. The second is PTO drift: someone takes a week off, misses their closes, and never makes them up, so everyone else quietly absorbs the extra. The third is the reliable-closer trap: one manager is good at closing, so they get more of it, and that becomes the rotation by default.

The rules of a fair closing rotation

A rotation your team will accept needs a handful of explicit rules. Write them down and share them. The point is not the exact numbers, it is that everyone knows the numbers exist.

• Count closes over a rolling window, not a week. Three months is long enough to smooth out PTO and short enough that people can remember it. Every manager should land within one or two closes of everyone else over that window.
• Weekend closes are their own count. A Tuesday close and a Saturday close are not the same shift. Track Friday, Saturday and Sunday closes separately and balance those first.
• Cap closes per week. Two or three mid-or-close shifts per person per week is a common ceiling. More than that and you are scheduling burnout.
• No clopens unless someone asks for one. A close followed by an open is the fastest way to lose a good manager. If your solver or your spreadsheet allows it by default, change the default.
• PTO comes out of your closes, not your teammates'. If you take a week off, your close count should catch up over the following weeks. The rotation should remember.

A simple manual system

If you are running this in a spreadsheet, you can get most of the way there with one extra tab. List each manager down the left. Across the top, one column per week for the last twelve weeks. In each cell, record two numbers: total closes and weekend closes. At the bottom, a rolling twelve-week sum for each. When you build next week's schedule, start by assigning the Saturday close to whoever has the lowest weekend-close total, then the Friday close, then the Sunday close, then fill in weekday closes from the lowest overall total up.

This works. It also takes an honest hour a week and falls apart the first time someone else builds the schedule while you are on vacation, because the tab does not get updated and the history is lost.

Letting software do the counting

The reason we built Schedule Maker is that this specific problem, a fair open, mid and close rotation for a store's leadership team, is not what the big scheduling apps solve. They schedule hourly associates against labor hours. They do not know or care that Naz closed the last two Saturdays.

Schedule Maker keeps three months of rotation history per manager and uses it when it generates the next month. Weekend closes are balanced as their own category. Clopens are blocked. Locked shifts and PTO are respected, and a manager coming back from PTO is not punished with a pile of makeup closes in one week. When it is done, the schedule gets a fairness grade, so when someone asks "why me again," you can show them the number instead of arguing about it.

Handling the exceptions

Some managers want more closes. A parent who does school drop-off may prefer closes to opens. Someone in school may only be able to close on certain days. A fair rotation is not a rigid one; it is one where the exceptions are visible and agreed on. Set the preference once, lock the shifts that are fixed, and let the rotation balance everything else around them. The people who did not ask for an exception should not be able to tell it exists by looking at their own schedule.

What to do this week

Pull the last three months of schedules and count closes and weekend closes per manager. If the spread is more than two or three, you have the conversation coming whether you know it or not. Share the rules with your team, start the rolling count, and if the spreadsheet gets old fast, try generating next month with a tool built for the job.