Attendance · Time Desk
Turn clock events into hours you can defend.
Paid days become an argument when roster, breaks, overtime and corrections are computed by hand.
This is a capability inside Lightning Pharos, not a separate product.
Capture clock events and approve an exception.
01 · What ships
The complete working surface.
Hours that survive an argument.
- 01
Clock and break events with source, location code, time, and actor
- 02
Late, early, and absent derived from the roster rather than judged by hand
- 03
Daily overtime and break-rule derivation
- 04
Regularisation requests with an approval trail
- 05
The paid-days feed payroll actually runs on
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
Capture clock events and approve an exception.
- 02 / 03
Governed event
Late, early, absent, break and overtime rules resolve against the roster.
- 03 / 03
Connected result
Payroll receives approved paid days with the evidence still attached.
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.
GPS or device attestation is not verified, weekly overtime is not fully applied, and manual paid-days overrides remain possible and visible.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system