Leave · Leave Desk
Keep balances, approvals and rosters in step.
A leave approval is not complete if the balance changes but the roster and attendance do not.
This is a capability inside Lightning Pharos, not a separate product.
Apply, approve or cancel leave.
01 · What ships
The complete working surface.
Balances that are computed, not remembered.
- 01
Leave types and policies with monthly accrual, rollover, and carry-expiry rules
- 02
Balances accrued automatically and visible to the employee
- 03
Apply, approve, and cancel with the roster and attendance kept in step
- 04
Holiday calendars per location
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
Apply, approve or cancel leave.
- 02 / 03
Governed event
The balance and dated approval update together.
- 03 / 03
Connected result
Scheduling, attendance and payroll see the same absence.
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.
There is no encashment calculation or payment workflow. Attendance synchronisation can be blocked by a locked period.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system