A field inspection app should preserve a usable record even when its user has no mobile connection, and it should explain how confidently that record identifies the asset inspected. Better positioning helps, but it does not replace asset identifiers, photographs, inspection context, or a controlled synchronisation process.
New Zealand has a timely opportunity to test that distinction. In July 2026, LINZ invited organisations to trial SouthPAN-capable equipment in their own workflows. The offer describes an initial four-week equipment loan, subject to suitability and availability. It encourages practical evaluation before changing equipment or processes.
Start with the decision a location supports
Imagine an illustrative maintenance crew inspecting drainage assets beside a rural road. Two assets sit close together. A point on a map may suggest the right area while leaving the asset identity uncertain. The useful question is whether the evidence allows the next person to find the exact asset and understand its condition.
Ask what action follows the inspection. Scheduling a return visit, ordering a replacement, and making a survey-grade boundary determination have different evidence requirements. A general field app should not imply that its location record is suitable for every engineering or legal purpose.
Define the required outcome with the operational specialists. That decision determines which positioning equipment, identifiers, photographs, and review steps belong in the first release.
Test the complete positioning chain
SouthPAN is a satellite positioning augmentation service. LINZ’s compatible-device guidance makes equipment compatibility a practical consideration. The existence of the service does not mean every phone or receiver automatically uses it.
Test the receiver, its configuration, the device connection, and the field application together. Check which location source the app actually records. A paired external receiver is not useful if the application silently records the phone’s internal location instead.
Repeat observations in representative settings, including obstructions and difficult working positions. Record the conditions and compare outcomes against a reference appropriate to the task. Treat any reported accuracy indicator as information to assess, not a universal guarantee that an asset has been identified correctly.
Capture an evidence bundle, not a loose photograph
Link each inspection to an explicit asset identifier or a clearly marked proposed new asset. Record the form version, observation time, operator, location source, and relevant quality information supported by the device. Attach photographs to that inspection record rather than relying on a filename that someone must interpret later.
Let users flag uncertainty. They may be unable to locate an asset, distinguish two nearby objects, or obtain a useful position. A clear “needs review” path is better than forcing an invented value to satisfy a required field.
For a new asset, retain the original field observation when an office reviewer later approves a corrected location. The system should explain the correction and its reason without silently rewriting what the crew recorded.
Make the offline experience visible before departure
Before a crew leaves, show whether assignments, forms, reference records, and necessary map areas are available on the device. Downloading an app does not mean its working data is ready for a disconnected site.
Design an explicit readiness check:
- ▸The assigned work and required reference data are present.
- ▸The map coverage needed for the route is available.
- ▸The user can open and save the intended inspection forms offline.
- ▸Available storage is suitable for the expected photographs.
- ▸Device and receiver power arrangements have been considered.
- ▸The user understands which actions require a later connection.
Protect locally stored information according to its sensitivity and the organisation’s device policy. Explain what happens when a shared device changes hands or a user loses access while work remains unsynchronised.
Give synchronisation a business owner
Reconnection can reveal conflicts. Two crews may inspect the same asset, an office user may change an assignment, or a photograph may upload after its form. Decide which changes can merge automatically and which require review.
Keep a durable local queue and show what remains pending. A retry should continue the same inspection rather than create another copy. Users need to distinguish “saved on this device” from “received by the office.”
For conflicting observations, preserve both until the agreed resolution occurs. A blanket last-write-wins rule can erase the information that explains an asset’s condition. Our repeatable processing guide provides a related integration principle.
A field trial should include an inconvenient day
Test the workflow with gloves, glare, interrupted power, unavailable connectivity, a mistaken asset selection, and a delayed return to the office. Ask someone who did not design the application to recover an interrupted inspection using the interface and runbook.
Compare an extension of existing GIS tools with a custom application. The development opportunity may be a specialised form, an asset-system connector, or a review queue rather than replacing the mapping platform. Define acceptance outcomes using the MVP acceptance checklist.
TuniCyberLabs can help scope custom field and operations software. Describe your field task, devices, GIS platform, and the evidence that currently gets lost or disputed to discuss a practical offline workflow and integration pilot.