My employee says he visited the site. How can I verify it?
Open his route history for that day: the path travelled, the exact time he entered the site's geo-fence, how long he stayed, and when he left — with a face-verified check-in. 'I went there' becomes a record you can export.
Geo-fenced check-in · face match · route replay · exportable proof
A client calls at 4 PM: nobody came to the site today. Your engineer says he was there in the morning for an hour. He even sends a selfie with a timestamp. You still can't tell the client anything definite — the selfie could be from last week, from outside the gate, or from his terrace.
Verifying a site visit means checking presence, not a photo. Bazat Tracker logs a visit only from inside the site boundary, with a live face match and spoofing checks, and stores arrival, duration and departure — so you can answer the client with a fact.
Why the usual proof doesn't hold up
Selfies, call reports and messages all rely on trust, and all of them can be produced from anywhere.
The timestamped selfie
A photo can be taken from the road outside, or on another day, and its metadata edited. It proves a camera fired, not a visit.
The call report
A visit report is written at day-end from memory. It records intent and recollection, not attendance.
The WhatsApp update
'Reached site' in the group chat is a message, not a location. It can be sent from the tea stall.
No duration
Even a genuine visit with no record of how long it lasted can't tell a two-minute stop from a full inspection.
How Bazat Tracker verifies a site visit
Every visit carries the four things a dispute actually needs: where, who, when, and how long.
Geo-fenced check-in
The visit logs only from inside the site boundary — the road, the gate and a spoofed location all fail.
Face verification
The check-in is matched to the employee's face, so it can't be logged by a colleague.
Spoofing checks
Mock-location apps and rooted devices are detected, so coordinates can't be faked to stage a visit.
Arrival, duration, departure
Time inside the boundary is recorded per visit, so a quick stop and a real inspection look different.
Route replay
See the full day as a path with every site entered in order and the distance between them.
Exportable visit record
Site, date, in/out time, duration and verification method export as a tamper-evident document.
An MEP subcontractor was in a payment dispute — the main contractor claimed the commissioning engineer had visited the site twice, not the eight times invoiced. The subcontractor exported the route history: eight geo-fenced, face-verified visits over three weeks, with arrival times and durations from 40 minutes to three hours. The invoice was cleared without further argument.
How to verify visits going forward
- 1
Geo-fence the sites
Add every client and project site with a boundary that matches the location.
- 2
Assign the visitors
Attach engineers, supervisors and managers to the sites they're expected to visit.
- 3
Require face on check-in
Make a live face match mandatory so a visit can't be logged for someone else.
- 4
Enable auto-logging
Let crossing the boundary record the visit, so it's captured even without a manual tap.
- 5
Pull the record when asked
When a visit is questioned, export that day's route and visit log and share it.
Selfie vs call report vs Bazat Tracker
| Capability | Timestamped selfie | Call / visit report | Bazat Tracker |
|---|---|---|---|
| Confirms the person was inside the site | |||
| Confirms who made the visit | |||
| Records how long the visit lasted | |||
| Resists editing / staging | |||
| Shows all visits in a day as a route | |||
| Exports as proof for a dispute |
Verifying site visits — FAQs
Open his route history for that day. You'll see the path he travelled, the exact time he entered the client site's geo-fence, how long he stayed, and when he left — plus a face-verified check-in, so 'I went there' becomes a record.
A selfie can be taken from anywhere and its timestamp edited. A Bazat Tracker visit is logged only from inside the site boundary, with a live face match and mock-location detection, so it can't be staged from the road outside.
Export the visit record: site name, date, arrival and departure time, duration inside the boundary, and the verification method. It's a tamper-evident document you can attach to an email or a bill.
Crossing the site boundary can auto-log the visit, so it's captured without a manual tap. If auto-logging is off, the employee can raise a regularisation with a reason for supervisor approval.
Yes. The day replays as a route with every site geo-fence entered, in order, with stop durations — so you can confirm each assigned visit actually happened.
Tracking runs during working hours to record site entries, exits and the route between them. It stops outside shift hours.
See a site visit that can't be staged
On a 15-minute demo we'll log a real visit, try to fake one from outside the boundary, and export the record you'd send a client.