Platform · Field & movement
The work happens away from the office. So does the record.
Location-aware timekeeping, work-site geofences, authorized movement and a field app that keeps working when the signal does not — built so that visibility never costs the worker their trust.
The operational problem
Field work is where operational truth is usually lost.
A visit happens in someone’s living room, a job site, a car, a basement with no reception. By the time it reaches a system, it has been through a phone, a memory and a form. Timestamps drift toward whenever somebody got around to entering them. Mileage becomes an estimate. “Were you there?” becomes an argument nobody can settle with evidence.
The common response is to track harder — and to hand workers a system that treats them as suspects. That solves the record and destroys the relationship. The interesting problem is producing an operational record that is genuinely trustworthy while remaining something a worker would defend.
How Phibian handles it
Honest states beat confident guesses.
Phibian records what it actually knows about where and when work happened, including when it does not know. Uncertainty is a first-class state, not a gap to be quietly filled.
Location states that never overclaim
A clock-in carries an explicit verification state — at a work site, away from work sites, couldn’t confirm, no reading, location off, not collected by policy, or attested by the worker. A weak fix is never rendered as “outside”.
Time that cannot quietly change
Punches are immutable events. A missing clock-out is auto-closed and flagged at the threshold — never backfilled with a plausible eight-hour day. Device time and server receipt time are both recorded.
Offline is a supported mode, not a failure
Actions taken with no connection are queued encrypted on the device and uploaded later carrying their real occurrence time. Every event carries an identifier, so a retry can never create a duplicate punch.
Movement only while on shift
Breadcrumbs are captured during an open session and only under the organization’s policy — never while clocked out. Retention is bounded and enforced by deletion, not by convention.
Gaps are reviewable, not accusations
A coverage gap raises an exception for a human to look at. Phones lose fixes for ordinary reasons, and the product says so rather than implying misconduct.
Raw history is a separate privilege
Viewing a raw location trail is its own permission, granted to no role by default, and viewing it writes an audit event. Work sites are organizational sites — client residences are not turned into geofences.
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
Check-in verification gives a supervisor the evidence and the uncertainty together, so review is a judgement made with context rather than a verdict handed down by an algorithm.
- Verification states summarised, then opened record by record
- Work-site geofences with accuracy gating built in
- Policy modes from record-only through to requiring a geofence
- Correction requests reviewed against the original, which is kept
For the Worker
The worker sees exactly what is being recorded, while it is being recorded — and what happens when their phone cannot answer the question.
- Location collected while clocked in only, and stated plainly
- Attest to a punch when GPS cannot get a fix, without being blocked
- Offline actions visible in a queue, with their real times intact
- Their own record, and a way to ask for it to be fixed
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.
Time flows into approvals
Field punches are the raw material of the weekly timesheet, so approval means approving something that was actually observed.
Exceptions flow into attention
Missing clock-outs, coverage gaps and unconfirmed check-ins become ranked items in the operational queue rather than silent data.
Movement will become mileage
Mileage workflows are being built on this same authorized breadcrumb record, so trips derive from the operational trail instead of being reconstructed from memory. That capability is in development and is not available today.
Evidence supports compliance
When an organization has to demonstrate what happened, the evidence and its uncertainty are already attached to the record.
Keep exploring
Compliance & evidence
Rules, exceptions, corrections and the audit trail that make field activity defensible later.
Explore Compliance & evidenceWorkforce & scheduling
The assignments and schedules field activity resolves against.
Explore Workforce & schedulingSecurity & trust
How location, permissions, tenant isolation and audit are actually enforced.
Explore Security & trust