Explainer · Field teams
Use on-site mode as a field orientation aid
How to interpret device location against stored estate and plot geometry without presenting the result as survey verification.
- Category
- Field teams
- Best for
- Surveyors, marketers, site staff, and field supervisors
- Reading time
- 4 min read
- Content review
Scope of this guidance
On-site mode compares device location with stored geometry using a tolerance. It is not survey-grade measurement, legal boundary evidence, a safety system, or proof that map data is current.
Step 1 of 4
Prepare the field session
The comparison is only as useful as the device location and the stored geometry. Before relying on the result for orientation, confirm the selected estate, map revision, location permission, and reported device accuracy.
- Open the intended estate and confirm its boundary and plot data are available.
- Allow device location only when the field task requires it and follow the organization's privacy policy.
- Wait for a usable accuracy reading and keep an offline or unavailable state visible when location cannot be established.
Step 2 of 4
Interpret the location state
The boundary comparison can indicate that the device is inside a mapped plot, inside the estate but outside a mapped plot, or outside the stored estate boundary. Invalid or missing geometry should not be converted into a positive match.
- Read the plot number and operational plot state when a plot match is available.
- Treat an estate-only match as orientation context, not as identification of a specific plot.
- If the device appears outside the estate, check accuracy, selected estate, and map revision before drawing a conclusion.
Step 3 of 4
Use the result carefully
A tolerant point-in-polygon result helps a person understand nearby mapped context. It cannot resolve a close boundary, a disputed peg, an uncertain coordinate source, or a stale allocation record.
- Use the result to support navigation, inspection notes, and a client-site conversation.
- Use the plot record and current allocation episode for client or status questions.
- Escalate boundary uncertainty to the survey workflow instead of changing geometry from a device-location observation.
Step 4 of 4
Close the field feedback loop
Field observations become useful when they return to an owned record. Capture what was observed, when, by whom, which estate or plot was in view, and whether follow-up is required.
- Record an observation without presenting it as a committed map correction.
- Route suspected geometry or numbering errors to the responsible survey or operations role.
- Verify the approved correction in the record and map after the reviewed update is complete.
Final checks
Confirm these points before treating the workflow review as complete.
- The selected estate, map revision, permission, and device accuracy are visible.
- Inside plot, estate only, outside estate, and unavailable states are distinct.
- The result is described as orientation rather than survey verification.
- Field observations have an owner and a clear correction path.
Continue the review
Continue evaluating this workflow
Review the related Pole workflow, then request organization access when your organization is ready to begin the application. Access is reviewed by Platform and is not created immediately.