Running one site is a scheduling problem. Running three is a different problem wearing the same clothes. The grid looks familiar, but almost every assumption baked into a single-site schedule quietly stops holding, and the failures show up as small repeated frustrations rather than one obvious break.
The staff who belong to more than one place
The first thing that breaks is the idea that a person belongs to a location. In practice a handful of people float: the supervisor who covers two sites, the trained keyholder everyone borrows, the part-timer who takes whatever is going. If each site keeps its own schedule, those people are double-booked by construction, because neither schedule can see the other.
This is the case for one schedule with locations inside it rather than several schedules side by side. Availability, hours already worked and overtime thresholds are properties of the person, not of the site, and they have to be checked against everything that person is doing, everywhere.
Travel between sites is the detail that catches people out. If somebody closes one site and opens another the next morning, a rest gap that looks compliant on paper may not survive the journey, and two schedules that can't see each other will never raise it.
Rules stay local even when the schedule doesn't
The opposite mistake is to flatten everything. Sites differ in ways that matter: opening hours, break rules, minimum staffing at a given hour, and the positions that exist at all. A kitchen has a role a kiosk doesn't. A site in another region may sit under different rest requirements entirely.
- Operating hours, and the shape of the busy period inside them
- Minimum coverage per position, per hour
- Break and rest rules, which can vary by jurisdiction
- The local time zone, which is not a display preference
That last one causes more trouble than the rest combined. If your sites span time zones, the moment a shift is stored as nine in the morning without recording nine where, every total downstream becomes negotiable. Store the instant, carry the location's time zone with it, and render it locally. Do that and a shift is unambiguous. Skip it and you'll spend a payroll period arguing about which numbers are right.
Who is allowed to change what
With one shared schedule, the next question is authority. A site manager should be able to run their own week without being able to quietly reassign somebody else's staff, and a regional manager needs a view across all of it. Get this wrong in the permissive direction and you get silent cross-site poaching. Get it wrong in the restrictive direction and everything funnels through one person, which is slower than the three separate spreadsheets you were trying to replace.
Compare like with like
The reward for a single schedule is that the sites become comparable. Coverage, overtime and cost can be read side by side rather than assembled by hand from three sources at the end of the month.
That comparison is only worth something if the underlying rules are recorded per site, because a site that looks expensive may simply be open longer, or staffed to a standard the others aren't held to. So the useful question isn't which site is cheapest. It's whether each site is staffed to what it was asked to deliver, and that's a question you can only ask once the requirements live next to the results.
“Three schedules make three local optima. One schedule with three sets of rules makes a business you can actually read.”