A site survey app that captures measurements, annotated photos and GPS offline, then hands estimating a structured record instead of a notebook.

Estimating works from a structured take-off with evidence attached, and the survey form itself becomes improvable, you can see which question keeps sending a van back.
Programme coverage becomes a live number with a location attached, and a site that was never visited stops looking the same as a site whose paperwork went missing.
Yes. The mobile app is offline-first. The form definition, any source lists it references and the compiled rule logic are downloaded to the device before the visit, and the completed submission including photographs, sketches and audio notes is stored locally and uploaded when the device reconnects. The surveyor is never blocked, and nothing is held on the server waiting for them.
They are different jobs and we keep them as separate forms. A site survey establishes what is there before work is designed or priced, so its output is measurements, constraints and a take-off. An asset inspection assesses the condition of something that already exists against a defined standard, so its output is a pass, fail or grade with follow-up actions. Both use the same builder, rules, dispatch and approval machinery, and a survey can spawn a work order or an inspection through a workflow node when it finds something that needs one.
In two ways. Dispatch carries a payload of field defaults, so an enquiry reference, customer name, address and target date can be populated when the survey is created, including in bulk, from an uploaded spreadsheet on a scheduled dispatch. Separately, the API question type calls an upstream endpoint from inside the form and writes the response back into fields, so a surveyor can look up the account or asset record on site. Credentials for those calls are encrypted at rest and never reach the device; the app only sends a small trigger payload.
Add a geo control question so position is captured on the record, and enable per-field geostamping and timestamping at dispatch so each individual answer carries where and when it was entered. A geo-proximity rule can warn or block when the captured position falls outside an expected radius of the site coordinates. Photographs taken through the camera question can also carry a GPS and timestamp watermark.
It can go either way. Submissions export as XLSX or CSV with one column per question, including the repeatable rows, and export can be triggered on demand or scheduled and emailed. For system-to-system handover, a workflow push-destination node maps individual form fields onto target fields in a structured connector such as SAP S/4HANA or Dynamics 365, or pushes a file over SFTP or a JSON payload to a webhook. Connector configuration is encrypted at rest and outbound calls pass a server-side egress allowlist.
Your own engineers or surveying leads, in the drag-and-drop builder, without a developer and without an app-store release. Forms are versioned: publishing creates an immutable version, every submission records the version it was captured against, and an earlier version can be restored as a draft if a change needs rolling back. You can also photograph an existing paper survey sheet and have the platform propose a draft form from it, then adjust it in the builder.
Usually one. Rules show, hide, require or clear questions as answers arrive and can target whole pages and sections, so a single published survey renders only the questions relevant to the type the surveyor selected. Where the same form is used for genuinely different passes, a quick screening visit and a detailed survey, tag the rules into rule groups and pick the active groups at dispatch, so both passes stay on one form definition instead of drifting into two.