VisitsTracker › Product
One record. Everything else comes off it.
What the product records, what it derives from that, and what you can hand to somebody else afterwards.
9 pagesAndroid, iOS and web
The shape of it
One record, and everything that comes off it.
The product does one thing at the bottom: it works out that somebody was at a place, for how long, without asking them to say so. Everything on this page is either how that record is made, or something derived from it afterwards.
Made, then derived
Nothing here is a separate product
Timesheets, mileage, attendance and customer proof are not four systems that need reconciling. They are four readings of the same day, which is why they cannot disagree with each other.
- The visit is the atom: a stay inside a boundary, with a start, an end and a trust verdict.
- Hours, distance and attendance are computed from visits, never typed alongside them.
- Correct a reading and every figure drawn from it moves with it, in one place.
Four numbers, one source. There is no second place where any of them could be entered by hand and drift.
All 9 pages
The whole product, one page at a time.
Separate pages rather than one long scroll, because these are genuinely different subjects and the person evaluating attendance is rarely the person evaluating the API. Every one of them ends with what it does not do.
A map of dots is the easy half. The useful half is knowing which of those dots you should believe.
Read VisitsHow a stop becomes a visitThe 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.
Read TimesheetsHours, and the week you sign offHours are the number that has to survive payroll and, occasionally, a tribunal.
Read EvidenceWhy the record holds upMost 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.
Read CustomersWhat you send the customerThe same record that settles an argument also renews a contract. The customer opens it themselves rather than waiting for you to assemble something.
Read SitesSites, zones and coverageEverything downstream depends on the geography being right, and the product should tell you which pins it does not believe.
Read ReportsThe artifacts you hand to someone elseA report is not a dashboard. It leaves the building and gets read by payroll, by a client, or by somebody's solicitor.
Read MobileThe app on the vanA tracking app that workers resent gets uninstalled, disabled, or left in the glovebox.
Read AdminRoles, fields and controlThe settings that decide what the product asks, who sees the answers, how long they survive, and how they leave the building.
ReadTwo other ways in
Or start from your trade, or from the alternative.
The same product described for guarding, facilities, cleaning, care, waste and lone working, with the vocabulary and the evidence each one is actually asked for.
15 pages Against the fieldComparisonsAgainst Hubstaff, When I Work, Deputy, Badger Maps, SPOTIO, Repsly, ServiceM8, BigChange, Housecall Pro and more, each one leading with where the alternative is the better buy.
13 comparisonsTry it on one van for a week.
Put it on one phone, run a normal week, and see what comes out the other end. That answers more than any page here.
No card needed. Set up in an afternoon.