How do I set up environmental survey software for phase II site investigations with custom forms and offline sync?

To set up environmental survey software for Phase II site investigations with custom forms and offline sync, think in terms of 5 parts: data model, form design, offline-first mobile workflow, sync/conflict handling, and reporting/GIS export.

1) Define the Phase II workflow first

Phase II investigations usually include:

• soil borings and samples
• groundwater wells and sampling
• field screening readings
• photo logs
• chain-of-custody / sample IDs
• borehole logs and stratigraphy
• QA/QC observations
• GPS coordinates and site metadata

Map these into your software before building forms.

2) Choose an offline-capable platform

Use software that supports:

• custom field forms
• mobile app with offline data capture
• data sync when back online
• file attachments (photos, PDFs)
• role-based access
• API / export to GIS and LIMS

Common options:

• Esri Survey123 + ArcGIS Field Maps
• Fulcrum
• KoBoToolbox / ODK for highly customizable forms
• Microsoft Power Apps with offline patterns
• Custom app using Flutter/React Native + backend sync

If you need strong GIS integration, Survey123 or Fulcrum are usually quickest.

3) Build the custom forms

Create separate forms for each field activity, for example:

Site Recon / General Form

• project name
• site address / parcel ID
• date/time
• crew members
• weather
• access notes
• GPS location
• photo upload

Soil Borings Form

• boring ID
• depth intervals
• lithology
• PID / LEL readings
• sample collection flags
• refusal depth
• drilling method
• casing notes

Groundwater Wells Form

• well ID
• installation depth
• screened interval
• purge volume
• water level
• sample time
• field parameters
• decontamination notes

Sample Log Form

• sample ID
• matrix
• container type
• preservatives
• lab destination
• cooler ID
• chain-of-custody status

QA/QC Form

• field duplicate
• trip blank
• equipment blank
• calibration results
• anomalies / deviations

Tips for form design

• use drop-downs for controlled vocabularies
• use conditional logic to hide irrelevant questions
• add validation rules for required fields, ranges, and formats
• generate unique IDs automatically
• include photo and signature capture
• use repeatable groups for multiple samples or soil intervals

4) Set up offline sync

Offline sync is usually the main requirement for field work.

Required behavior

• users download assigned site data before going to the field
• forms work without cell service
• records are stored locally on device
• when online, app uploads changes automatically or manually
• attachments sync too
• users can see sync status and error messages

Best practices

• store local drafts in an encrypted local database
• sync using a queue so failed uploads retry later
• timestamp every record and edit
• assign each record a globally unique ID
• support attachments as separate sync objects
• preserve an audit trail of edits

Conflict handling

Decide what happens if two users edit the same record:

• last write wins for simple cases
• field-level merge for some fields
• lock records after submission
• require supervisor approval for corrections

For Phase II work, a good rule is:

• field crews create records offline
• supervisors review/approve after sync
• locked records require an amendment record instead of overwriting

5) Connect to reporting and GIS

You’ll likely want:

• PDF field logs
• Excel export
• shapefiles / GeoJSON / feature service sync
• sample summary tables
• chain-of-custody reports
• dashboards for progress and missing data

Useful integrations:

• GIS: ArcGIS, QGIS, GeoJSON
• Lab: LIMS via CSV/API
• Documents: SharePoint, S3, Google Drive
• Reporting: Power BI, Tableau, or built-in dashboards

6) Security and compliance

Because these are project and site records:

• enforce user logins and role permissions
• encrypt data in transit and at rest
• keep an audit trail
• back up daily
• allow read-only exports for regulators/clients
• if handling sensitive site data, restrict offline exports and device access

7) A practical implementation pattern

If you want a straightforward setup:

Option A: Low-code, fastest

• Survey123 / Fulcrum
• design forms
• enable offline mobile app
• create sync groups by project/site
• connect exports to GIS and reporting

Option B: Custom app, most flexible

• mobile frontend: Flutter or React Native
• local offline DB: SQLite
• backend: PostgreSQL/PostGIS
• sync API: REST/GraphQL
• file storage: S3-compatible object store
• form schema: JSON-based form definitions
• conflict resolution and audit logs in backend

Option C: Open-source field data stack

• ODK Central
• ODK Collect mobile app
• forms in XLSForm
• offline by default
• server sync when connected

8) Minimum checklist to launch

• define inspection/sampling workflows
• create form templates for each activity
• test offline entry on phones/tablets
• verify sync with photos and GPS
• test conflict handling
• set up user roles
• validate exports to GIS/LIMS
• train field staff
• run a pilot on one site first

9) Example recommended architecture

A solid setup for most environmental consulting teams:

• Mobile app: Survey123 or custom Flutter app
• Local storage: encrypted SQLite
• Backend: PostgreSQL + PostGIS
• File storage: S3
• Sync: API with delta updates and retries
• Reporting: Power BI / PDF generator
• GIS: ArcGIS or QGIS export

If you want, I can also help you with one of these next:

1. a sample Phase II field form template
2. a database schema for soil/groundwater/samples
3. an offline sync design
4. a Survey123/ODK setup guide
5. a custom app architecture for Flutter or React Native