Sync & Field Readiness
The Field Readiness panel on each trip plan gives you a real-time view of whether your team's mobile devices are properly prepared before heading into the field. It checks each linked survey individually and surfaces any issues before they become problems — such as a device that hasn't downloaded the latest survey package or a form template that is out of date.
What the panel shows
At the top of the panel, an overall indicator summarises the trip's readiness at a glance:
- Ready for field (green) — all surveys have current packages and form templates, and there are no pending uploads blocking the team.
- Some surveys need attention (amber) — at least one survey has an outdated package, pending uploads, or a minor issue that should be addressed before departure.
- Not ready — missing packages (red) — one or more surveys are missing their package entirely on a field device. Field researchers will not be able to collect observations for those surveys until the package is downloaded.
Below the overall indicator, each linked survey is listed as a row showing:
- Survey name — the name of the linked survey.
- Package status — whether the survey package on the device is Current, Outdated, or Missing.
- Forms status — whether the form templates associated with the survey are Current or Missing.
- Pending uploads — the number of observations or media items queued for upload but not yet synced to the server.
- Issues — any specific problem messages for that survey, shown in small text below the badges.
If there are trip-level issues (for example, unresolved sync conflicts affecting multiple surveys), these appear at the bottom of the panel.
What each status means
Package status
| Status | Meaning | What to do |
|---|---|---|
| Current | The device has the latest survey package | Nothing — you're good to go |
| Outdated | A newer package version has been bundled on the server | Ask the field researcher to open the app while connected and let it sync |
| Missing | No survey package has been downloaded to this device | The field researcher must sync before going offline — see below |
Form template status
| Status | Meaning | What to do |
|---|---|---|
| Current | The device has the latest form templates | Nothing required |
| Missing | Form templates were not downloaded | Sync the device before leaving mobile coverage |
What to do if a survey shows "Missing"
A missing package means the field researcher's device never completed a sync for that survey. This must be resolved before the team loses mobile coverage:
- Open the TerraSitu mobile app on the affected device.
- Ensure the device has an active internet connection (Wi-Fi recommended for large packages).
- Navigate to the survey list — the app will automatically detect and download any pending packages.
- Wait for the download to complete and the status to update to "Current".
- Refresh the Field Readiness panel in the web portal to confirm.
Do not allow field researchers to depart for remote areas until all surveys show "Current" in both Package and Forms status.
How sync works in the mobile app
The TerraSitu mobile app is designed for offline-first work. Once a survey package is downloaded, field researchers can collect observations, photos, GPS tracks, and field session data without any connectivity for days at a time.
When the device reconnects to the internet — even briefly — the app automatically queues and uploads all collected data in the background. You do not need to manually trigger a sync. The mobile app handles this continuously whenever a connection is available.
The Field Readiness panel reflects the latest sync state known to the server. Because sync is automatic, the panel should update within minutes of a device reconnecting. The panel auto-refreshes every 30 seconds, so you can leave it open and watch readiness improve as the team syncs up before departure.
Pending uploads and conflicts
If a survey shows pending uploads, it means the field researcher has collected data that has not yet reached the server. This is normal during active fieldwork when devices are offline. Before marking a trip as complete, ensure all pending uploads have cleared.
If the panel reports pending sync conflicts, it means two devices submitted conflicting data for the same record (for example, the same sampling unit was updated on two devices while offline). Conflicts must be reviewed and resolved in the Sync Dashboard before the trip can be finalised.