VisitsTracker

Know every stop. Nobody taps a button.

No card needed. Put it on one phone and run a normal week.

Wednesday, 12 August J. Hartley 4 visits · 6h 41m on site
Abbey Retail Park08:12 – 09:05 · 53m
Northgate Depot10:20 – 11:48 · 1h 28m
Elm Court12:30 – 14:10 · 1h 40m
Harbour Works15:02 – 16:35 · 1h 33m
08:0011:0014:0017:00
1,204 readings sit behind this day. Every stop is derived from the trail, not from what somebody remembered at five o’clock.

The problem

Ask where the van went on Tuesday. The answer is whatever somebody remembers.

Every record of a field day was typed in by the person it describes, at the end of it. Clock-ins get forgotten on the busy days, durations get rounded, travel gets estimated, and the site nobody reached does not appear at all. Then a customer queries an invoice and the only thing you can send them is a screenshot.

A tracked day

Where they are, and where they have been.

Live positions, a visit for every stop with the time in and the time out, and the sites nobody has reached.

Live · Wednesday 12 August 4 of 5 sending
Abbey Retail Park Northgate Depot Harbour Works flagged reading Harbour Elm Park 500 m
4 of 5 sending3 on the clock 1 flagged0 gone quiet
Team
JHJ. Hartley
Harbour Works · 2 min ago
PSP. Sharma
En route · 40 s ago
NBN. Byrne
Fake location
flag
AWA. Whittaker
Off shift
off
SKS. Kaur
No reading for 2 h
quiet

When someone argues

The day holds up if it's questioned.

Most days nobody asks. When they do — a customer queries an hour, a worker queries a timesheet — you need more than a screenshot. Here is the same Wednesday with the checks turned on.

Same worker. Same Wednesday.
Wednesday, 12 August J. Hartley · 4 visits 6h 41m checked
Abbey Retail Park08:12 – 09:05 · 53m
Northgate Depot10:20 – 11:48 · 1h 28m
Weir Street no proof12:30 – 14:10 · claimed 1h 40m
Readings in that window41
Readings we trust0
Nearest trusted reading2.8 km away
Phone reportedfake location
Harbour Works15:02 – 16:35 · 1h 33m
08:0011:0014:0017:00
Three of these check out. The fourth is on the timesheet with nothing behind it.

Fake locations get flagged flagged

Some apps let a phone pretend to be somewhere else. We spot those readings and keep them, marked. A flagged reading never counts toward a visit, a mileage claim or an hours total.

Days are locked once written tamper-evident

Each day gets a fingerprint. Change a reading later and that day stops matching. You can show the record wasn't edited, rather than just saying so.

Close calls are marked as close calls

If a stop could be two nearby sites, we say so and keep both. A confident guess is worse than an honest maybe.

Edits are added, never overwritten

Fix a wrong note and the old value stays visible, with who changed it and when. That is what makes a correction believable.

One PDF settles it one click

One file with the map of the day, every reading, the photos and every edit. Hand it to a customer, to payroll, or to a tribunal.

Deleting a photo shows up

Remove a site photo and the record says a photo was removed, and by whom. A gap where evidence used to be is still information.

When a customer queries an invoice

One PDF answers it.

Instead of hunting through screenshots, you export one file with the whole day in it.

  • A map of the day, drawn from the saved positions. It won't expire or stop loading.
  • Every reading and what we made of it, flagged ones included, so nothing looks cherry-picked.
  • Every edit — who changed what, when, and what it was before.
  • Photos and signatures from the site, with anything deleted shown as deleted.
  • Whether each day still matches its fingerprint, so the reader can check rather than trust you.
Day report · Weir Street12 Aug · p.1/4
nearest trusted reading claimed site · 2.8 km away
Readings in that window41
Readings we trust0 none
Phone reported fake location41
Nearest trusted reading2.8 km
Day still matchesverifies
Edits2 entries

What your customers see

Send the customer the visit.

One link showing the visits at their site: when someone arrived, how long they stayed, and the photos. Your logo, not ours.

Customer portal standing link

One link per customer with their last 90 days of visits, photos and signatures. First names only.

Share links expiring

Send one day or one visit to anyone. It expires within a day, and you can cancel it sooner.

Monthly service statement

A monthly PDF per customer: visits, hours on site and photos. The thing you send when an invoice is queried.

Proof of completion

A PDF per job with the checklist, photos and signature. Made when the job closes, not chased on Friday.

Your branding, not ours

Add your logo and colour once. Customer pages and statements use them from then on.

Photos, signatures and notes

Taken on site and kept with the visit, alongside any fields you add yourself.

The difference

Two ways to track a visit.

Most tools show you a dot on a map. The useful question is what that dot leaves behind once the van has moved on.

A dot on a map

  • Shows where people are now, and little about where they were
  • A visit is whatever somebody remembered to tap
  • No duration: you can see the stop, not the 40 minutes
  • Travel time is typed in by the person claiming it
  • Quietly drops readings it doesn't like
  • Proof for the customer means a screenshot and an email

VisitsTracker a visit record

  • Live positions, plus every stop kept as a visit
  • Ten minutes on site becomes a visit on its own
  • Arrived, left, how long, and which site it was
  • Travel measured from the day, not entered by hand
  • Odd readings kept and marked, never dropped
  • One link the customer opens themselves

Questions about battery, no signal, faked locations or whether staff accept it: straight answers here.

The whole product

Nine pages, not one long scroll.

Each one ends with what it does not do, because the limits are the part you need before you buy rather than after.

Where everyone is now

Live, stale or not reporting, the trail behind them, unexplained time, and a link with an ETA you can send a customer.

How a stop becomes a visit

Stay-point detection, then matching. What happens when two sites both fit, and what happens when none of them do.

Hours and the week you sign off

Punches that carry their own evidence, automatic clock-in on zone entry, and a week that refuses late punches once approved.

Why the record holds up

Bad readings kept and marked, a per-day seal anyone can verify, edits that add rather than overwrite.

What you send the customer

A standing page per client, expiring links, monthly statements, and your branding rather than ours.

Sites, zones and coverage

Import from a spreadsheet or KML, draw real boundaries, and find the sites nobody has reached.

The artifacts you hand over

Payroll, dispute packs, speeding, mileage from trusted fixes only, and your own fields counted.

The app on the van

Bounded collection refused at the server, offline queueing, and a record the worker can export themselves.

Roles, fields and control

Who sees what, your own typed fields, retention, signed webhooks and an audit trail that appends.

Pricing

Simple pricing.

$19 a month for the workspace, plus $4 per tracked seat. Admins, managers and auditors are free.

Included, not metered

Every tracking hour and the full history. Dispute packs, timesheets, mileage and every export. Spoof detection and device health on every tracked seat. There is no evidence add-on and no tier that unlocks the record.

No card needed. A new workspace arrives with a sample crew that retires itself on your first real punch.

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. That tells you more than a demo.