What you will learn
- What field crews need from an app, and what slows them down
- How field codes turn raw measurements into usable features
- How offline capture and sync should work on real sites
- How photos, sketches, and notes attach to the right job and point
- What the office handoff looks like when it works well
What the project is
Field data collection is the moment a survey is made or lost. The crew records measurements, feature codes, monument conditions, sketches, and photos, and every gap or ambiguity in that record becomes office guesswork later. An app built for crews replaces the field book with structured forms tied to the job, the instrument, and the point being measured.
The app is a capture tool, not a drafting tool. Its job is to make the record complete, consistent, and immediately usable, so the office can start drafting while the crew is still on site or on the way home.
Core features
Job-based forms are the core: when a crew opens a job, they see its parcel, its control points, and the forms for that job type, pre-filled where possible. Field codes matter enormously: a short code entered at the point should expand into the right feature, symbol, and layer in the office, with a code list the firm controls. Photos attach to points and to the job, with automatic timestamps and a note field for what the photo shows.
- Job-based forms pre-filled with parcel, control, and crew details
- Custom field-code lists that map codes to features and layers
- Offline capture with queued sync and a visible sync status
- Photos and sketches attached to points, lines, and the job
- Monument condition records: found, disturbed, reset, or not found
- End-of-day summary the crew reviews and signs off before sync
How it is built
Build with crews, not for them in the abstract. The first version should be tested on real jobs by the people who will use it daily, because a form that looks clean in the office can be unusable with gloves on, in sun glare, or with one hand free. Two rounds of field testing beat a month of extra features.
- Shadow real crews for several jobs and list every record they actually make.
- Build job forms and field codes for one job type, with offline sync.
- Test on live jobs, fix the friction points crews report, then widen job types.
- Add photos, sketches, and the end-of-day summary.
- Build the office import so field data lands in drafting without retyping.
Technology considerations
Offline-first design is non-negotiable. The app must store everything locally, queue uploads, and resolve conflicts without losing data when two devices record the same job. Battery life matters too: constant GPS polling and camera use drain a device, so location capture should be deliberate rather than continuous.
Device choice is a practical question. Rugged devices survive sites better but cost more, while ordinary phones are cheaper and easier to replace. The app should work on both, with large touch targets and high-contrast screens for outdoor use.
Challenges to plan for
Adoption is the main challenge. Crews with years of paper habit will run the app and the book in parallel unless the app is clearly faster, and parallel records are worse than either one alone. The fix is a cutover per crew, with support on the first jobs, not a firm-wide launch day.
- Parallel paper and app records that disagree and double the office work
- Sun glare, gloves, and rain making small controls unusable
- Sync conflicts when two devices edit the same point
- Code lists that drift between crews unless one person owns them
Who it is for, and its limits
This app fits survey firms with field crews doing boundary, topographic, or construction survey work, especially firms where office retyping currently delays drafting. It also fits engineering firms running their own survey teams.
It does not replace the instrument or the surveyor's observation. Measurements still come from the total station or GNSS receiver, and the app records what the crew observed, including uncertainty where it exists. Costs and timelines vary with job types and device strategy, so confirm with a quote before budgeting.
Frequently asked questions
Does the app replace the field book completely?
It can, once crews trust it and the office import is proven. Until then, a planned cutover per crew works better than asking everyone to drop paper on the same day.
What happens when there is no signal on site?
Nothing is lost. The app stores everything on the device and syncs when signal returns, showing what has synced and what is still queued.
How do field codes work?
The crew enters a short code at each point, and the office system expands it into the right feature, symbol, and layer. The firm controls the code list, so it matches its drafting standards.
Can photos be tied to specific points?
Yes. Photos attach to points, lines, or the whole job, with timestamps and a note field, so the office knows what each photo shows and where it belongs.
What devices does it run on?
It should run on ordinary phones and tablets as well as rugged devices, with large touch targets and high-contrast screens for outdoor use.