Offline Mode
The LiteLog app also works without an internet connection — in underground garages, basements, halls, or on remote sites your employees simply keep working. All captured data is stored locally on the device and synchronized automatically as soon as a connection is available again.
What works offline
| Feature | Offline |
|---|---|
| Running patrols — scanning checkpoints via QR code or NFC | ✅ |
| Capturing incident reports — including photos | ✅ |
| Time tracking — start, pause, and stop working time; shift sign-in/sign-out | ✅ |
| Filling in forms — e.g. shift reports and checklists | ✅ |
| Status reports — including check-ins via the status reporter | ✅ |
| Completing tasks | ✅ |
| Viewing documents — PDFs already downloaded | ✅ |
To make this possible, the app keeps the required data locally: properties and checkpoints, patrol tasks, and documents are loaded onto the device while working with a connection.
The buffer zone (geofencing) and beacon checks also apply offline: both are evaluated locally on the device — no server connection is needed for them. The timestamp is always the moment of capture — not the time of the later synchronization.
Automatic synchronization
As soon as the device is back online, the app automatically transfers all not-yet-synchronized records to the server — tag scans, time tracking entries, attendance, incident reports including images, form responses, status reports, and task completions. Nothing needs to be triggered manually.
- Failed transfers are stored and retried automatically.
- Depending on the amount of data (e.g. many photos), the transfer can take a while after a long offline period — keep the app open for it.
Limits of offline mode
- Signing in requires internet — Login (and thus the first start after installation) needs a connection. Once signed in, the app remains usable offline.
- Data must have been loaded once — Properties, checkpoints, patrols, and documents are only available offline if they were previously loaded with a connection. Ideally open the app once with internet before heading into a dead zone.
- Patrols that were not loaded — If a planned patrol cannot be loaded (e.g. because it is not available offline or was deleted in the meantime), the app deliberately aborts the start and shows a notice — so no scans get assigned to the wrong patrol. Details: Running a patrol.
- Rotating kiosk QR — Checking in via the kiosk screen requires a connection, because the rotating code is generated and validated server-side. Static QR codes and NFC tags, on the other hand, work offline.
- Form drafts with media — Drafts containing photos or a signature are best continued on the same device; across devices the answers are carried over, but media attachments are not.
- Live features — Chat, live views, and loading new tasks or changes from the portal naturally require a connection.
If synchronization gets stuck
If entries remain marked as "not synchronized" permanently, the guided recovery in the app's help area can assist: it first uploads all pending data and then resets the app cleanly — without data loss. See Help — Recovery.
Good to know
:::tip Note
- Offline mode works silently in the background — your employees do not need to switch anything.
- Timestamps are set at capture time, not at synchronization time: a checkpoint scanned offline carries the actual scan time.
- The electronic guard book benefits as well: evidence is captured without gaps even when the site has no reception. :::