Define the outage you need to handle
A remote pickup, patchy venue Wi-Fi and a completely disconnected device create different conditions. Identify the devices, expected outage duration and information staff must access. Do not assume a web page that opened earlier will continue to support every action.
Test collection and retrieval separately
Confirm whether a new participant can complete a form offline and whether staff can find previously signed records. Check what must be downloaded in advance. Use a test booking to inspect the data available before disconnecting and the record created after signing.
Inspect the return to connectivity
Reconnect and verify that records sync once, remain associated with the correct participants and show an understandable state to staff. Test an interrupted sync and a changed booking. Ask the provider how conflicts, failed uploads and device storage are handled.
Keep a practical operating fallback
Train staff to recognise unsynced records and avoid assuming that a locally completed task is visible elsewhere. Document device preparation, charging and end-of-day checks. Choose a fallback consistent with your approved safety and document process for a device that fails completely.
A concrete example
Disconnect the supported test device, complete a sample record, reconnect and verify where it appears. Staff should be able to distinguish collected, queued and synced states without guessing.
Put it to work this week
Rehearse the actual device and network conditions of your departure point before relying on offline collection.