Multi-site scheduling
A group with several sites is not several independent schedules. It is several schedules that share people, and the sharing is where things go wrong.
Each site administers itself
A site has its own units, shift templates, staff categories, rules and schedulers. A site administrator manages the sites they administer and sees nothing else — every list, every report and every change is scoped to those sites.
That scoping is strict rather than conventional. The permission to take an administrative action and the question of which rows that action may touch are separate decisions in the codebase, and conflating them is the defect class this product has been audited for most often. A site administrator is a customer with a boundary, not a reduced version of the operator.
Staff shared between sites
Someone working at two sites holds assignments in both. Everything about them has to be computed across both:
- Rest intervals. A night at one site and a morning at another is the turnaround that gets violated, because each site's schedule looks fine alone.
- Consecutive days. Five at one site and two at another is seven.
- Workload tallies. Their call and weekend counts are theirs, not each site's partial view.
All three are per person. There is no version of this that works per site.
What a group can see across sites
Where a group needs a view spanning its sites, that is available to an administrator of those sites — coverage, workload distribution, and where the same people are being leaned on at both ends.
A site administrator at one site still sees only their own.
Billing is a group concern
Billing is pooled at the group rather than charged per site, with one billing owner. Site creation and appointing another administrator are restricted to that owner, so adding a site is a deliberate commercial act rather than something any administrator can do.
Common questions
Can a site administrator see other sites?
No. A site administrator's access is scoped to the sites they administer, and every list, report and mutation is filtered to those. Platform-wide access is a separate role that belongs to the operator of the service, not to a customer.
How is a clinician who works at two sites counted?
Per person, across everywhere they work. Rest intervals, consecutive-day limits and workload tallies are computed from all of a person's assignments, which is the only way they can be correct for someone shared between sites.