Prepare for offline fieldwork

Prepare the device while connected, then test the work under the same disconnected conditions you expect in the field.

Before you start

Use an approved Android installation when you need dependable startup without internet. The web application can use available local data after loading, but a browser shortcut is not an offline installation guarantee.

Confirm the project, intended collection layers, forms, reference data, and your team’s handover method.

1. Load the project and maps

1. Open the correct workspace and project on each field device.
2. Load the layers, forms, controlled lists, and reference polygons the workflow uses.
3. Download offline map tiles for the work area and the zoom levels you need.
4. Check storage and battery capacity, especially if you will capture attachments.

See Settings & offline maps and Layers.

2. Test without internet

1. Disconnect internet access on the test device.
2. For the approved Android installation, close and reopen the app to test disconnected startup.
3. Open the prepared project and inspect the basemap.
4. Collect a sample record with the intended form, position, and evidence.
5. Reopen the saved record and confirm that its values and attachments remain available.

Keep the test record identifiable so your team can remove it through its normal review process when appropriate.

If you use separate related visits, test that exact action with the field user's role. Hosted table and relationship editing require connectivity, and offline new related records depend on a valid short-lived authorization. Opening the project beforehand does not grant indefinite offline access. See Record repeated inspections.

3. Agree how the data comes back

Handover	What to prepare
Cloud synchronization	A signed-in workspace, appropriate access, and an opportunity to reconnect and inspect pending synchronization
Nearby device transfer	Compatible mobile builds, the same Wi-Fi or hotspot, a host device, and its current session details
File handover	An enabled export format and a receiving tool that can open the result

For supported nearby transfer, the host shares its address, port, and short-lived session code with the intended team. Verify receipt on the host and stop the session when finished. Follow the current Data & Sync instructions.

4. Reconnect and confirm delivery

For hosted projects, reconnect and open Sync Inspector from the sync status control. Send eligible changes, review the remaining queue and any attention state, and confirm that the receiving user sees the expected records and evidence.

If a save or delivery is uncertain, keep the original device data and use Check sync and recover saved work. It explains paused retries, pending related-data requests, and recovery of an already submitted update or archive.

Expected result

Each device can complete the planned local collection task, and the team has tested how to return and review the records. A saved local record and a completed cloud synchronization are separate states.

If something does not work

• Blank basemap: check the downloaded area and zoom coverage while connected.
• Missing choices or reference values: reload the required form, lists, or reference data before leaving.
• Transfer cannot connect: check the hotspot, supported build, host status, address, and current session code.
• Pending cloud changes remain: reconnect, open the correct project, and inspect synchronization status before assuming delivery is complete.

See the offline readiness checklist for the full deployment reference.