exodus field

How it works

What we can prove, and what we cannot.

The full method, stated plainly.

At the punch

Location is required to clock in

A location fix at the punch, measured against the job site. No fix, no shift.

Distance, not a yes or no

Metres and device accuracy are both stored. A weak fix is labelled weak.

Away punches are explained, not blocked

Outside the geofence, the tech states why and it stamps the punch.

Location at the punch, not all day

One fix at clock in, one at clock out. Nothing in between, nothing in the background.

During the shift

Photos carry their own capture time

Timestamp and location come from the camera, so Tuesday cannot become Thursday.

Checklists timestamp as they are ticked

A sheet finished in one burst at 4:58pm shows as one burst.

Verification grades

Verified

Accurate, inside the geofence, at both ends.

Weak

Inside, but poor device accuracy. Never promoted to verified.

Away

Outside, with the tech’s stated reason attached.

Getting it to the client

A link you can revoke

Read-only links. Revoking one also cuts off forwarded copies.

Printable by design

One clean sheet for the invoice. No login at the other end.

Nothing about your crew leaks

Pay rates, other clients and other techs never appear on a shared record.

What it can't prove

We prove a device was at a place at a time and that work was recorded there. We do not judge quality, and we record nothing outside a running shift.