Where the work was logged

When a technician taps an action in the CleverTech app — on the way, arrived, started, a checklist step, a photo, sign-off — the app takes a single GPS reading at that moment and stores it with the action. CleverOps then works out how far that was from the site and shows you the trail.

The point is corroboration. A job's timestamps tell you when a technician said they did something; this tells you where they were standing when they said it.

What gets recorded

Every one of these actions carries a position (with one deliberate exception, marked below):

Action	Logged as
Mark on the way	On the way
I've arrived	Arrived on site
End visit — job not finished	Left site (plus the job's new status and any "what's left" note)
Start job / Resume	Started work / Resumed
Pause	Paused
Tick or answer a checklist step	Checklist step (with the step's name and answer)
Take a job photo	Photo
Add a note	Note
Ask the control room for help	Asked for help
Complete & sign off	Signed off
Open the job for the first time	Opened the job — no position is captured for this one; opening a screen is not a field action

Each entry records the coordinates, how accurate the reading was, the time the technician tapped, and — separately — the time the record reached us.

Nothing is recorded between taps. CleverTech does not follow a technician around; it takes one reading per action and asks the phone for nothing in between. There is no background tracking, and the app never records anything while it is closed.

Reading the trail

Open a job, go to the Activity tab, and look for Where the work was logged. Entries are newest first.

Each one carries a tag:

• On site — the action was logged within your on-site distance of the site's recorded position. The distance is shown once it's more than 50 m.
• Off site · 4.2 km away — the action was logged outside that distance. This is the flag worth acting on.
• 7.5 km from site — shown instead of "Off site" for On the way and Left site, where being away from the site is normal. The distance is still given (useful for sanity-checking an ETA), but it is not counted as a flag.
• No position — the phone gave no reading, with the reason: location switched off, permission refused, permission blocked, or no GPS signal at the time.
• Can't check — no site location — the site has no coordinates on file, so there is nothing to measure against.
• Mock GPS — the phone reported the position as coming from a mock location provider, meaning a fake-GPS app was supplying it rather than the satellites.

Some entries carry an extra line:

• "Logged offline — reached us 70 min later." The technician was out of signal; the action was saved on the phone and synced when they got a connection. The position is still from when they tapped, not from where they were when it synced.
• "Position: phone's last known position, not a fresh fix." No fresh reading was available, so the phone's last known position was used. It may be stale.
• "Position: fix taken moments earlier in the same burst." A run of quick actions (ticking several checklist steps) reuses one reading rather than pinging GPS for each.

The flag on the job

A job whose trail contains anything worth attention shows a chip in its header, so you don't have to open the Activity tab to find out:

• Mock GPS (red) — a simulated position was used on this job.
• 3 logged off site (amber) — that many actions were logged away from the site.

A job with a clean trail — or no trail at all — shows nothing.

Finding the flags — the Field integrity queue

The chip on a job only helps if somebody opens that job. Needs attention → Field integrity is where the flags come to you instead, across every job in the control room, and it is the section to work rather than hunting through the board.

It holds three lists:

• Signed off, but not closed — a technician completed the job on their phone and the completion never landed here. They think it's done; you're looking at unfinished work. The row says what was missing (open required steps, missing photos, no signature) so you know whether to chase the technician or fix the record.
• Work claimed away from site — the off-site and Mock GPS actions described above, gathered into one list, worst first. On the way and Left site are never counted here, for the same reason they aren't counted on the job.
• Started, not finished — jobs sitting In progress with nothing logged for over a day. This is deliberately separate from Overdue jobs, which only looks at the promised time: an abandoned visit and a job nobody has touched look identical there, and the fix is different — call the technician, not the customer.

Above the three lists, a banner names any technician the system can't fully reach: no CleverTech device registered against their account (so dispatch pushes land nowhere), or a phone that has reported location switched off, refused or blocked (so their proof-of-attendance records nothing). It shows how many open jobs they're carrying and how many messages never reached them.

What a flag does and doesn't mean

"No position" is not "off site." A phone with location switched off, a plant room with no view of the sky, or a permission the technician never granted all produce a blank. None of them say anything about where the technician was. These are shown neutrally, with the reason attached, and are never counted as off-site.

A site with no coordinates can't be checked. Roughly a quarter of sites have no location on file. That's an office data gap, not technician behaviour — the job says so plainly. Adding the site's coordinates makes the check work for future jobs.

Distance is not intent. A large plot, a phone that fixed on a cell tower rather than GPS, or a technician taking a call at the gate can all put a reading outside the radius. The trail is evidence to ask a question with, not a verdict.

Setting the distance

Settings → Service → On-site distance for technician actions.

The default is 250 m, which allows for a large plot, a farm gate, and normal handset GPS error. Tighten it for dense suburbs; loosen it for estates and farms where the site's pin is at the entrance but the work happens well inside.

Changing it only affects actions logged after the change. The on-site verdict is worked out once, when the action arrives — so tightening the distance never turns a job that was clean yesterday into a flagged one.

What the technician sees

If their phone can't produce a position for a reason they can fix — location switched off, or permission refused or blocked — CleverTech shows a Location unavailable banner on the job with a Fix this button that takes them to the right settings screen. Their actions still save either way; they just save without a position.

A missed reading for a reason they can't fix (no signal in a basement) stays quiet, because there is nothing for them to do about it.

Permissions and privacy

• CleverTech asks for "while in use" location only. It never requests background location and captures nothing while closed.
• The trail is append-only. Neither the technician nor the office can edit or delete where somebody was.
• A technician can see their own trail and nobody else's. The office (coordinators, supervisors, owners) sees the trail for their company's jobs.