Platform · Time
Time should reflect the work that actually happened.
Phibian connects timekeeping to operational context instead of treating a punch as an isolated event. Correctable records. Visible states. Human review.
The operational problem
A punch without context is just a number to argue about.
Timekeeping systems are usually built to produce hours, and only hours. When something looks wrong — a shift with no end, a punch from an unexpected place, a week that does not add up — the system has no way to explain itself. Somebody reconstructs the story from memory, and the correction overwrites whatever was originally recorded.
That is how organizations end up unable to demonstrate their own diligence. The original observation is gone, so the only remaining evidence is the corrected number, which looks exactly like a number somebody typed in.
How Phibian handles it
Simple for workers. Structured for supervisors. Connected to the operation.
Time in Phibian carries the context it was created in — the session, the location state, the device conditions — and every change to it is an addition to the record rather than a replacement of it.
Simple for workers
Clocking in and out is obvious, fast and trustworthy. One open session at a time, and no way to accidentally create an overlapping one.
Structured corrections
An adjustment is a request with a reason, reviewed by someone authorised to approve it. The correction supersedes the original; the original is kept.
Context, not just hours
A punch carries its location verification state and its session, so a supervisor reviews an event with evidence rather than a bare timestamp.
Honest handling of the unusual
A missing clock-out is auto-closed and flagged at the threshold — never quietly filled in with a plausible eight-hour day. Offline punches keep their real occurrence time.
Approval that means something
Approving a week captures an immutable snapshot. If an underlying value changes afterwards, the week reopens rather than silently diverging from what was approved.
Payroll-ready, not payroll
Approved time is snapshotted and exportable. Phibian stays the time-of-record; your payroll system stays the money-of-record.
In the product
One model, two surfaces.
What the worker records is what the supervisor reviews. There is no second entry, and no reconciliation step between the two.
In Admin
Supervisors work an exception queue rather than a timesheet grid: what needs review, why it was flagged, and what evidence supports it.
- Missing clock-outs and unsubmitted timesheets surfaced automatically
- Adjustment requests reviewed beside the original record
- Weekly approval with a locked snapshot and automatic reopening
- Every hour traceable to the session that produced it
For the Worker
The worker can see their own time as the system holds it, including anything captured offline, and can ask for a fix without a phone call.
- Clock in and out in one action
- Today’s and this week’s recorded time
- Offline punches visible in a queue with their real times
- Request a correction; the original stays on the record
How it connects
Nothing here is a standalone product.
The value is not the capability on its own — it is what happens when this record is continuous with the rest of the operation.
Field activity produces the events
Location verification states arrive attached to punches, so review has context from the start.
Scheduling gives them meaning
Recorded time is compared against planned work, which is what makes unmatched activity visible.
Compliance keeps them defensible
Corrections, approvals and audit events make a week explainable months later.
Payroll consumes the snapshot
The approval snapshot is the artefact that leaves Phibian, which is why approving is a deliberate, attributable act.