Weekend Close Rotation: Why Your ASMs Think It Is Unfair (and How to Fix It)
Ask any assistant store manager which shift they track, and it is the Saturday close. Not total hours, not opens, not how many mids they pulled. Saturday close. It is the one that costs them a night with their family, and it is the one they will count on their fingers when they think the rotation is off. If your weekend closes are not visibly fair, nothing else about your schedule will feel fair either.
Why week-by-week scheduling breaks weekend fairness
Most managers build the schedule one week at a time. Each week has one Friday close, one Saturday close, one Sunday close. With five managers and three weekend closes, two people get the weekend off every week and it feels balanced. The problem is that the pattern across weeks is invisible. If the same two managers happen to get the weekend off in weeks one, three and five because of how PTO and opens fell, the other three carried every weekend close for a month and nobody noticed until one of them said something.
Weekend fairness is a quarter-level property, not a week-level one. You cannot see it unless you count it across the quarter.
Count weekend closes as their own thing
The fix starts with one change in how you count. Keep two tallies per manager: total closes, and weekend closes (Friday, Saturday, Sunday). Balance the weekend count first, every time. A manager who is one close behind on the weekend tally gets the next Saturday, even if their overall close count is fine. Only after weekend closes are assigned do you balance weekday closes.
Some stores go further and weight Saturday above Friday and Sunday, so two Fridays do not equal two Saturdays. That is reasonable if your Saturday close is meaningfully worse. Most teams find that a single weekend count with a rolling window is enough.
Key takeaway
If you only balance one number, balance weekend closes. It is the number your managers are already counting.
Use a rolling window
A month is too short. One week of PTO knocks a manager's count off by a full weekend and it takes the rest of the month to catch up. A quarter is about right: long enough that PTO and holidays average out, short enough that people remember it. Keep the last twelve or thirteen weeks in the tally and drop the oldest week as each new one is added.
Publish the tally. Put the weekend close count for each manager at the bottom of the schedule. When the numbers are public, the argument mostly stops, because everyone can see they are within one of each other. When one person is two or three ahead, you can see it before they do and fix it in the next schedule.
Handle PTO without punishing anyone
A manager who takes a week off misses a weekend close. There are two bad ways to handle it: ignore it, so everyone else absorbed an extra close for free, or make it up all at once, so the returning manager closes the next three Saturdays. The fair version is to let the rolling tally catch them up gradually: they are one behind, so they get priority for the next open weekend close, and then the rotation continues normally.
How Schedule Maker does it
Schedule Maker keeps a separate weekend-close history for each manager across three months and balances it as its own objective when it generates the month, ahead of weekday closes. Managers returning from PTO get caught up over time rather than in one week. The fairness grade on each schedule includes the weekend spread, so a schedule where one manager is carrying too many Saturdays will not grade well, and you will see it before you post it.
Start with this
Count weekend closes per manager for the last twelve weeks. If the spread is more than one or two, you already have a fairness problem, whether or not anyone has said it out loud yet. Balance the next schedule from that count, publish the tally, and keep it rolling.