How do I know how long my engineer stayed at each site?
Bazat Tracker measures the time between entering and leaving each site's geo-fence, per visit, per engineer. A two-minute stop and a six-hour shift look completely different — and both feed payroll and client billing correctly.
Duration inside the fence · per site · feeds payroll & billing
Your engineer's day sheet says: Site A morning, Site B afternoon. Payroll pays a full day. The client on Site B is billed for six engineer-hours. Nobody actually knows he spent 20 minutes on Site A and left Site B by 3 PM — the check-in tap looks the same whether he stayed an hour or the whole day.
Time-on-site is the duration inside the boundary, not the check-in. Bazat Tracker records entry and exit for every site visit, so working hours are based on real presence and a client is billed for the hours the engineer was actually on their site.
Why check-in taps don't tell you duration
A punch records a moment. On its own it can't distinguish a passing visit from a full day.
Check-in only
If the app records the arrival tap and nothing else, a 10-minute visit and a full shift are identical in the data.
The early exit
The engineer checks in, does an hour, and leaves. Without an exit event, the system assumes he stayed all day.
Self-entered hours
Asking staff to write their own site hours turns payroll and billing into a negotiation.
Split days guessed
An engineer on two sites gets a rough 'half and half' split, so both clients are billed on an estimate.
How Bazat Tracker measures time on site
Entry and exit are both captured, per site, so duration is a fact rather than an assumption.
Entry and exit events
Crossing the site boundary logs an arrival and a departure, so every visit has a real start and end.
Duration per visit
Time inside the fence is calculated for each visit and shown against the engineer and the site.
Per-site totals
A day split across sites shows each site's hours separately, and a combined total for payroll.
Feeds working hours
Verified in and out times flow into shift and overtime rules automatically — no manual timesheet.
Billing export
Export time-on-site per engineer for one project as a report for a running-account or T&M bill.
Seen in context
Durations sit inside the day's route replay, so you can see the travel time between sites too.
A design-and-build firm billed clients for interior site supervision by the day. After switching on time-on-site, the data showed supervisors averaged 3.5 hours per client site, not the 8 being billed. The firm moved those clients to hourly billing backed by the exported records — invoices got smaller per visit, disputes disappeared, and two clients signed longer contracts because the billing was now transparent.
Setting up time-on-site tracking
- 1
Geo-fence each site
Add every site with a boundary tight enough that entry and exit are meaningful.
- 2
Turn on auto entry/exit
Let boundary crossings log arrival and departure so duration is captured without taps.
- 3
Set shift and OT rules
Define working hours and overtime so verified durations compute pay automatically.
- 4
Choose billing units
Decide which projects bill by the hour and which by the day, and map the export to each.
- 5
Review durations weekly
Watch for sites with unexpectedly short average presence and act early.
Check-in tap vs day sheet vs Bazat Tracker
| Capability | Check-in tap only | Self-entered day sheet | Bazat Tracker |
|---|---|---|---|
| Distinguishes a short stop from a full day | |||
| Records an exit, not just an arrival | |||
| Per-site duration for split days | |||
| Feeds payroll hours automatically | |||
| Client-billing export by project | |||
| Resistant to self-reporting bias |
Time spent on each site — FAQs
Bazat Tracker measures the time between entering and leaving each site's geo-fence, per visit, per engineer. A 10-minute stop and a 6-hour shift look completely different in the record.
No. Time-on-site is the duration inside the boundary, not the check-in tap. Someone who touches the site for two minutes and leaves can't have a full day attributed to them.
Yes. Verified in and out times per site feed working-hours and overtime rules automatically, so pay is based on real presence rather than a register.
Yes. Export time-on-site per engineer for a single project as a report you can attach to a running-account or time-and-material bill.
Each site shows its own duration. The day totals across all sites for payroll, while each site's hours stay separate for billing.
Entry and exit events are recorded on the device offline and synced when signal returns, so the duration is preserved.
See time-on-site turn into a payroll and billing report
On a demo we'll log a visit with entry and exit, split a day across two sites, and export the per-site hours.