VisitsTracker › Product › Visits
How a stop becomes a visit
The mechanism the rest of the product rests on. A visit is derived from the trail, not declared by a worker, which is why it can disagree with what somebody remembered.
VisitsEvidence
01 · Two steps, kept apart
Stay-point detection, then matching
Finding the stop and naming the site are separate jobs, and keeping them separate is the point.
- Detection works on the fixes alone and knows nothing about your sites.
- Matching then asks which site that stop belongs to.
- So a stop at a place you never mapped is still recorded, which is how you find the sites you forgot.
02 · Honest uncertainty
When two sites both fit
Neighbouring units, a shared estate, two floors of one building. The product says so rather than choosing.
- The visit is marked ambiguous and the runner-up is kept on the record.
- In the app's own words: another site was in range, so the match is a claim and not a fact.
- A confident guess is what loses an argument later. An honest maybe survives it.
Both candidates stay on the record, and both print in the evidence pack.
03 · Matched nothing
A stop just outside a fence
Unmatched stops get an address and a distance, so they read as an administrative fix rather than a mystery.
- Reverse-geocoded to a street address and measured against your nearest known site.
- How long a stop must run before it is worth asking about is yours to set.
- Most are a pin in the wrong place or a site nobody added.
04 · Forwards, not only back
Scheduling a visit before it happens
The same object works as dispatch: a title, a site, an assignee, a window and a checklist.
- A checklist gates completion. An unfinished list cannot be marked done.
- A visit closes when the work is finished and a stop at that site backs it up the same day.
- Assign to the nearest available person from trusted fixes, or order a set into a driving route.
05 · Fixing the past
Changing your mind about a boundary
Sites move and radii turn out too tight. Fixing a pin should repair the history, not only improve the future.
- Visits can be recomputed against corrected geography.
- The underlying fixes are never rewritten. Only the interpretation changes.
- And the change is visible rather than silent.
Honest limits
What it does not do.
Worth knowing before you buy, not after
Ten minutes is the dwell threshold for a stop. Genuinely brief calls, a two-minute delivery drop, sit below it by design, because the alternative is every traffic light becoming a visit. If your work is short stops, test that first.
Straight answers
Questions people ask.
Does anyone have to tap anything?
No. The visit is derived from time spent inside the boundary, so nobody clocks in at the door and nobody can forget to.
What if a site has no boundary drawn?
It works from a pin and a radius. A drawn or imported boundary is more accurate, especially for long thin sites where a circle covers the wrong ground.
What happens to a stop somewhere I have not mapped?
It is kept as an unmatched stop with its address and its distance from your nearest site, so you can add the site or move the pin.
Can a faked position create a visit?
No. Readings flagged as coming from a mock-location tool are excluded from the dwell that creates a visit, while staying visible in the record.
Keep going
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.