When two locations share employees, a roster that looks workable at each store can still collide when the schedules are combined. In a public r/restaurantowners post, an operator said the same person was scheduled at both locations at seven on a Friday; the post does not say whether that was 7 a.m. or 7 p.m. That is a useful reminder: shared-staff planning needs a cross-location check, not just two separate grids.
A practical sequence
- Keep each location’s needs explicit. Define its shifts, roles, operating days and minimum coverage. Do not assume the two stores run the same pattern.
- Record known unavailability before generating. Time off and availability constraints belong in the inputs, not in a manager’s memory after the roster is built.
- Confirm one location before planning the next. When both stores have enabled cross-store operations and the employee is linked as shared staff, EasyShiftPlan treats that employee’s confirmed shifts at the other store as unavailable while generating a schedule. Unconfirmed drafts are not reserved, so managers should review drafts together before confirming either one.
- Check combined hours as well as overlapping times. Where the shared employee has a weekly maximum configured, the other store’s confirmed hours count toward that limit. A person can avoid a same-time collision and still need a manager’s review if no combined plan fits.
- Review the result before sharing it. If a later change affects a confirmed shift, revisit the other location’s plan too.
What EasyShiftPlan does across stores
With cross-store operations enabled at both stores and shared staff linked, EasyShiftPlan treats an employee’s confirmed shifts at another participating store as unavailable and counts those hours against the configured shared-employee weekly limit while generating a schedule. Stores are still generated one at a time. This is sequential conflict avoidance—not a simultaneous, joint or globally optimal multi-store schedule—and unconfirmed drafts are not coordinated.
That boundary matters. If both schedules are still drafts, managers should review them together before confirming either one. A solver can make constraints visible, but it cannot decide which store should get priority when the combined requirements do not fit.
A separate illustrative solver run
In a separate fictional restaurant demo—not the two-store case above—the production CP-SAT scheduler assigned all 14 required four-hour shift slots across five sample employees for a four-day partial week: 56 scheduled hours, zero uncovered slots and zero hard-constraint violations. No wage cost was calculated because no wage data was entered. This is one illustrative run, not a customer result, savings claim, labor-law determination, or proof of a global optimum.
Try the fictional restaurant scheduling demo. Use sample details only; the demo is isolated from other visitors. The current pricing page lists one-store plans at CA$20/month or CA$199/year, each with a 14-day trial. Payment details are required, and the selected plan renews automatically after the trial unless canceled; review the current terms and confirm the first charge in Stripe before enrolling. The demo is not a joint multi-store optimization test.
Source note
This is an EasyShiftPlan-published practical guide informed by a public discussion. It is not an independent review, endorsement or case study. The poster has not been contacted and is not represented as an EasyShiftPlan customer.