The whole product, one page at a time
Nine pages rather than one long scroll, because these are genuinely different subjects and the person evaluating attendance is rarely the person evaluating the API. Each one ends with what it does not do.
Where everyone is, right now
A map of dots is the easy half. The useful half is knowing which of those dots you should believe.
How a stop becomes a visit
The mechanism the rest of the product rests on. A visit is derived from the trail, not declared by a worker, which is why it can disagree with what somebody remembered.
Hours, and the week you sign off
Hours are the number that has to survive payroll and, occasionally, a tribunal.
Why the record holds up
Most days nobody asks. The record only has to be good on the day a customer refuses to pay, and that is a different standard from looking tidy in a dashboard.
What you send the customer
The same record that settles an argument also renews a contract. The customer opens it themselves rather than waiting for you to assemble something.
Sites, zones and coverage
Everything downstream depends on the geography being right, and the product should tell you which pins it does not believe.
The artifacts you hand to someone else
A report is not a dashboard. It leaves the building and gets read by payroll, by a client, or by somebody's solicitor.
The app on the van
A tracking app that workers resent gets uninstalled, disabled, or left in the glovebox.
Roles, fields and control
The settings that decide what the product asks, who sees the answers, how long they survive, and how they leave the building.
Looking for your trade instead?
The solution pages describe the same product for guarding, facilities, cleaning, care, waste and lone working. The comparisons put it against Connecteam, Jibble, Timeero and scanning guard tour systems.