Scheduling · Air Traffic Control
Publish a roster people can actually work.
Coverage plans fail when overlap, leave, rest and competency rules are checked after publishing.
This is a capability inside Lightning Pharos, not a separate product.
Build a versioned roster and run compliance preflight.
01 · What ships
The complete working surface.
Versioned rosters checked before they are published.
- 01
Shift patterns and templates per site and per role
- 02
Schedule versions, diffs, publishing, locking, and late amendments
- 03
Compliance preflight for overlap, leave, rest, consecutive days, and competency
- 04
Coverage warnings and governed overrides before publication
- 05
Notifications through a configured delivery path
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Build a versioned roster and run compliance preflight.
- 02 / 03
Governed event
Conflicts, coverage, overrides and the published version stay on the schedule.
- 03 / 03
Connected result
Attendance, open shifts and payroll begin from the approved plan.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
Employee self-service availability is not yet consumed by scheduling, and there is no roster-acknowledgement model. Shift swaps are handled in Marketplace.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system