Marketplace · Exchange
Fill an open shift with someone eligible to work it.
Broadcasting a vacancy to everyone creates overtime, skill and rest conflicts for supervisors to untangle.
This is a capability inside Lightning Pharos, not a separate product.
Offer an uncovered shift to qualified, available people.
01 · What ships
The complete working surface.
Open shifts the right people can pick up.
- 01
Publish unfilled shifts to the workers qualified and available for them
- 02
Claims, offers, withdrawals, swaps, bids, auctions, and gigs
- 03
Eligibility and rule-based recommendations using skills and readiness
- 04
A history of who was offered a shift and who took it
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
Offer an uncovered shift to qualified, available people.
- 02 / 03
Governed event
The claim is checked and approved against workforce rules.
- 03 / 03
Connected result
The roster updates with a trace of who was offered and who accepted.
03 · What it needs
Connected by design.
Pharos requires these modules first because the workflow depends on their records. The dependency is enforced in the product.
04 · Where it stops
The boundary is part of the product.
Matching is deterministic and rule-based, not AI. Readiness depends on Team data.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system