VisitsTracker › Proof of visit
Proof of visit for service contracts
Ten minutes on a customer’s site becomes a visit on its own. Photos, signatures and your own notes attach to it — and the customer can see the lot.
No card needed. Set up in an afternoon.
Three check out. The fourth is on the timesheet with nothing behind it.
The record
What a visit actually consists of
Arrival, departure, time inside the boundary, who, and everything captured while there. One record, assembled without anybody being asked to prove it.
- Arrival and departure come from the boundary, not from a button.
- Photos carry the time and place they were taken, stamped at capture.
- Forms and signatures hang off the visit rather than off an email.
The seal
Evidence that survives being questioned
A record only matters when somebody disputes it. Each day is hashed and chained, so a later edit is detectable rather than deniable.
- Per-day hash seal, append-only, verifiable on demand.
- The worker can export their own record without asking permission.
- Change a reading afterwards and that day stops matching, visibly.
Verify recomputes the chain on demand rather than trusting a stored flag.
Handing it over
A link the other side can open
Most disputes end the moment somebody can look. A standing page per client shows their own visits, with nothing of anyone else's on it.
- Scoped to one client's sites, with a rolling window you choose.
- Expiring links for one-off questions, revocable the moment you want them gone.
- No account needed at their end, which is why it actually gets opened.
Also in the box
Evidence that arrives on its own
Photos, signatures and your own fields
Captured on site and kept with the visit. If a photo is later removed, the record says a photo was removed and by whom.
Monthly service statement
A branded PDF per customer covering the month’s visits, hours on site and photos. The thing you send when an invoice is queried.
A day report when someone asks
One file with the map of the day, every reading, the photos and every edit — for the times a summary is not enough.
When two sites are next door
If a stop could belong to two nearby sites, the visit says so and keeps the runner-up rather than picking one. A confident guess is what loses an argument later.
Straight answers
Questions people ask
How is a visit proven?
By dwell inside the site’s boundary, from readings we trust, with the arrival and departure times recorded. Readings flagged as fake do not count toward it.
Do my customers need a login?
No. A customer gets a link. The standing portal link lasts; share links expire within a day and can be cancelled.
What if two sites are next door to each other?
The visit is marked as ambiguous and the other candidate is kept on the record. You see that it was a close call rather than a decision made for you.
Can I brand what customers see?
Yes. Add your logo and colour once and the portal, share pages and monthly statement use them.
What if a customer disputes an hour?
Export the day report for that visit. It has the map, every reading with what we made of it, the photos, and every edit with who made it.
Also part of VisitsTracker
The rest of the product
Try it on one van for a week.
Put it on one phone, run a normal week, and see what comes out the other end.