How far in advance should I publish the schedule?

Aim for two weeks; treat one week as the floor. The exact lead time matters less than picking a cadence and hitting it every time, so staff can plan around a reliable date. Predictability is most of the fairness — a schedule that's sometimes two weeks out and sometimes two days out feels arbitrary even when the assignments are balanced.

Is it unfair to give senior staff the shifts they prefer?

Not inherently. Seniority can reasonably earn a lighter share of the undesirable shifts and stronger consideration on preferences. It crosses into favoritism when it becomes a zero share — a senior person who never takes a single hard close, or who gets hours ahead of what they declared while junior staff come up short. The test: can you state the seniority rule out loud and would the team accept it as reasonable? "Fewer bad closes" passes; "never any bad closes" doesn't.

What's the difference between availability and preference, and why does it matter?

Availability is what someone can work — hard constraints like a second job or childcare. Preference is what they'd like — soft wishes like "I prefer mornings." You honor availability as a firm constraint and weigh preference only as a tie-breaker. Blurring the two is where most "you're playing favorites" complaints come from: the moment you break one person's hard "can't" to satisfy another's soft "want," the whole team learns some people's real lives count for less.

How do I handle someone who always lobbies for the good shifts?

Anchor hours and desirable slots to declared availability and a rotation, not to who asks most. When the loud person pushes, you have a written answer: "Hours track the availability everyone submitted, and the good weekend rotates — here's where you are in it." That protects the quiet, reliable people who assumed fairness without campaigning for it. Genuine merit still earns more — but state it openly as a merit decision, don't let volume of complaint pass itself off as merit.

How do I keep two locations fair when different managers build each schedule?

Standardize the rules, the availability format, and the publish cadence across both sites, and keep availability in one shared place rather than in each manager's phone. Most cross-location "favoritism" is really two managers applying two different unwritten standards. Write the standard down once, apply it everywhere, and audit monthly for drift.

Blog

How to Build a Fair Shift Schedule Across Multiple Locations (Without Playing Favorites)

To build a shift schedule your staff actually perceive as fair, apply four rules in order: rotate the undesirable shifts instead of defaulting them to the newest hire, honor stated availability before you consider preferences, distribute hours proportionally to how much each person said they can work, and publish far enough ahead that people can still swap.

Most "fair scheduling" advice stops at "be consistent." Consistency about the wrong thing is still unfair. The difference between a schedule staff trust and one they resent is whether you can point to a written rule for every decision — especially across multiple locations, where "favoritism" is usually just two managers applying two different unwritten standards.

This guide turns fairness into something you can audit. Each rule is a question you can answer with a yes or no when someone challenges the roster.

Why "be consistent" isn't enough

Consistency only helps if the underlying rule is fair. A manager who consistently gives every Friday night close to the last person hired is being perfectly consistent — and perfectly unfair. Staff don't experience your intentions; they experience the pattern in the schedule. If the pattern always dumps the worst slots on the same people, no amount of "I treat everyone the same" will land.

Fairness that staff believe has two properties:

It's rule-based, not mood-based. Every assignment traces back to a stated rule, not to who you like or who complained.
It's the same rule at every location. Two sites, two managers, one standard. Otherwise the person working across both learns that fairness depends on which manager built that week.

The four rules below give you that. Write them down, post them where staff can see them, and apply them in order.

The four rules of a fair shift schedule

Rule 1: Rotate the undesirable shifts — don't default them to the newest hire

Every roster has slots nobody wants: the Sunday double, the closing shift before an early open, the holiday-adjacent Monday. The lazy default is to hand them to whoever has the least standing to object — usually the newest or most junior person. That's the single most common source of "this place plays favorites."

Do this instead: keep a running rotation of the undesirable shifts and cycle them through everyone who's qualified and available for that slot. When you assign a bad shift, mark whose "turn" it was, so next time the same slot goes to the next person in the rotation.

Define which shifts count as "undesirable" up front and in writing — late closes, split shifts, the graveyard, whatever your team actually dreads. Don't decide after the fact.
Rotate within the pool of people qualified for that role and location. You can't rotate a bar close onto someone who isn't trained on the till.
Seniority can earn a lighter share, not a zero share. It's reasonable that a five-year veteran draws fewer bad closes than a three-week hire — but "fewer" is not "never." A senior person who never takes a single hard shift is exactly the favoritism staff smell.

Honest tradeoff: rotation sometimes puts a slightly less experienced person on a harder shift than pure optimization would. That's a real cost on the busiest nights. Cap it with a qualification floor — rotate only among people who can actually run the shift — and accept a small efficiency hit in exchange for a roster nobody can call rigged.

Rule 2: Honor stated availability before you consider preferences

Draw a hard line between two things people tell you:

Availability — the hours someone can work (hard constraints: a second job, childcare, a class, a standing commitment).
Preference — the hours someone would like to work (soft wishes: "I'd rather do mornings," "I like Saturdays for tips").

Availability is a constraint you honor. Preference is a tie-breaker you weigh. Never schedule someone outside their stated availability to satisfy someone else's preference. The moment you break one person's hard "can't" to grant another person's soft "want," you've told the whole team that some people's real lives matter less than others' wishes.

Practical guardrails:

Collect availability in a structured, dated way — not scattered across texts and hallway conversations you'll misremember. A record of "here's what everyone said they can work" is your evidence when a decision is questioned.
Require notice for availability changes (e.g. by a set day for the following week). Fairness runs both ways: staff commit to a cutoff, you commit to honoring what they gave you before it.
When two people are equally available for a good shift, then preference and rotation decide. That's the correct place for "who asked first" or "whose turn for the good Saturday" — not for overriding a constraint.

Honest tradeoff: honoring availability strictly means you'll sometimes be short on a shift everyone constrained themselves out of. That's a hiring, cross-training, or availability-expectation conversation — not a reason to quietly override one person's stated limits. Solve the gap openly.

Rule 3: Distribute hours proportionally to declared availability — not to who complains loudest

When hours are scarce, the person who lobbies hardest often wins them. That feels responsive in the moment and is corrosive over time, because it rewards squeaky wheels and punishes the quiet, reliable people who assumed you'd be fair without being asked.

The fair anchor: distribute available hours in proportion to how much each person said they could work. Someone who marked themselves open for 30 hours should get roughly twice the shot at hours as someone who marked 15 — not because they emailed you three times, but because they offered more availability.

Convert availability into a share, not a promise. "You told me you're open 30 hours, the location has capacity for X, so your proportional target this week is roughly Y" — adjusted for qualifications and legitimate business need (you still need a trained closer on).
Track hours over a rolling window (a few weeks), not a single week. One lumpy week isn't unfair; a month where the same people always come up short is.
Business need is a legitimate override — but name it. "You're the only one certified for X, so you're carrying more of it this week" is a fair, stated reason. "I gave Sam the hours because Sam kept asking" is not.

Honest tradeoff: proportional distribution can leave your single best worker slightly under-scheduled relative to what pure performance would justify. If someone is genuinely carrying the location, reward that transparently — more hours stated as a merit decision everyone can see — rather than by quietly letting the loudest voice win. The rule isn't "ignore performance"; it's "don't let volume of complaint masquerade as merit."

Rule 4: Publish far enough ahead that swaps are still possible

A schedule posted the night before is unfair even if every single assignment is balanced — because staff can't do anything about the parts that collide with their lives. Lead time is fairness. It's what converts a top-down roster into something people can adjust.

Publish on a predictable cadence. Two weeks out is a strong target; one week is a workable floor. The exact number matters less than that it's the same every time, so staff can plan around it.
Give swaps a clear path. State who approves a swap, and that both people plus the manager sign off. A published schedule with no swap mechanism just relocates the unfairness — now it's frozen in.
Same cadence at every location. If Site A posts two weeks out and Site B posts on Fridays for Monday, the cross-site staff learn that one manager respects their time and the other doesn't. Standardize the calendar, not just the rules.

Honest tradeoff: publishing earlier means committing before you have perfect information — a late call-out or a demand spike will force edits. Accept that. An early schedule you occasionally amend, with changes communicated clearly, beats a "perfect" schedule posted too late for anyone to respond to.

Worked example: the same headcount, two ways

Take two locations, same owner, same total staff, one week. Watch how the rules — not the headcount — decide whether the week lands fair or lopsided. (The people and numbers below are an illustrative scenario, not data from any real business.)

The setup (both scenarios identical):

Location A and Location B, each needing coverage across mornings, evenings, and weekend closes.
Six staff who can flex across both sites. Call them Ava, Ben, Cara, Dan, Eve, and a new hire, Noah (two weeks in).
Availability as declared: Ava and Ben are open ~30 hours each; Cara and Dan ~25; Eve ~20; Noah ~30 (he wants hours).
Three "undesirable" slots this week: two weekend closes and one Sunday double.

Before — the lopsided week (no written rules):

All three bad slots go to Noah, because he's newest and won't push back. He works both weekend closes and the Sunday double.
Ava lobbied hardest for hours, so she lands ~34 — above what she even declared — while Eve, who quietly declared 20 and said nothing, gets 11.
Ben mentioned in passing he "can't really do Thursdays" (a hard constraint), but a preference-swap for Cara's preferred Friday pushed a shift onto his Thursday anyway.
The schedule goes up Sunday evening for the week starting Monday. Noah can't find anyone to take even one of his three bad shifts in time.

The headcount was fine. The week is still unfair — and every person can feel exactly why.

After — the balanced week (four rules applied):

Rule 1: the two weekend closes and the Sunday double rotate. Noah takes one weekend close (his turn in the rotation, and he's qualified for it); the other close goes to Dan; the Sunday double goes to Ava, whose turn it was. Noah carries one hard shift, not three.
Rule 2: Ben's Thursday constraint is honored — nothing is scheduled against it. Cara's Friday preference is granted only where it doesn't override anyone's stated availability.
Rule 3: hours track declared availability. Ava and Ben land near 30, Cara and Dan near 25, Eve near 20 — Eve is no longer punished for being quiet, and Ava no longer rewarded for lobbying. Noah gets his ~30 because he declared them, not because he absorbed the bad slots.
Rule 4: the schedule posts two weeks ahead on the standard cadence, both locations. When Noah wants his weekend close covered, there's a week-plus and a defined swap path to arrange it.

Same six people, same coverage need. The only variable that changed is that decisions traced to written rules instead of to who pushed, who was newest, and who happened to be top of mind. That's the entire difference between a roster staff trust and one they quietly count grievances against.

Making the rules stick across multiple locations

The rules only produce fairness if every manager applies the same ones. A few things that hold the standard together across sites:

Write the rules down once, for all locations. One document: what counts as an undesirable shift, the availability cutoff, the publish cadence, the swap-approval path. Managers apply a shared standard instead of improvising per site.
Keep availability in one structured place, not in each manager's texts. Cross-site fairness is impossible if Site A's availability lives in one manager's phone and Site B's in another's memory.
Audit after the fact. Once a month, glance at who's been carrying the bad shifts and how hours track declared availability over the rolling window. Drift is normal; catching it early is the whole game.

Once the rules are written, keep applying them consistently

The rules above are the hard part, and they're free — you can apply all four with a spreadsheet and the discipline to stick to them. The tedious part is doing it identically week after week, across every location, without quietly slipping back into "whoever's newest takes the close."

That's the repetitive work a tool can take off your plate. Zentru's scheduling includes Ask Amil: you describe next week in plain language — coverage needs, who's available, which slots to rotate — and it returns a validated draft schedule for you to review, edit, and approve, instead of dragging shifts around a grid by hand. It's a deterministic planner, so the same inputs give you the same, checkable output across all your sites. The rules still matter more than any tool — but once they're written down, this makes applying them consistently a lot less manual.

If you want to try it on your own roster, Zentru offers a 30-day no-card trial with no automatic charge. Starter supports single-location teams, and scheduling plus clock-in are included in every tier. Bring your four rules; let the draft handle the repetition.