> ## Documentation Index
> Fetch the complete documentation index at: https://help.terriqon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Offline Data Collection: How Terriqon Works Without Internet

> Terriqon's mobile app works in zero-signal zones. Field officers collect data offline and submissions auto-sync when connectivity is restored.

Many of the communities where field teams work have no reliable mobile signal, let alone broadband. Terriqon is built offline-first, which means the mobile app is fully functional with zero network connectivity — not as a fallback mode, but as the default design. Field Officers collect data exactly as they would online, and the platform handles synchronisation automatically the moment a connection becomes available. Your team never has to think about whether they have signal before opening the app.

<Warning>
  Ensure field officers have logged in and downloaded forms while online before heading into a zero-signal area.
</Warning>

## How Offline Mode Works

Terriqon is a Progressive Web App (PWA), which means it runs in a browser but behaves like a native app — including the ability to store data locally on the device.

<Steps>
  <Step title="Forms are cached on the device">
    When a Field Officer logs in and opens a project while online, the app downloads and stores the form schema locally. The form remains available even if the device is subsequently taken offline for days or weeks.
  </Step>

  <Step title="Submissions are queued locally">
    When a Field Officer fills in and submits a form with no connectivity, the submission is saved to the device's local storage queue. The app confirms the save with a visual indicator so the officer knows the data is secure.
  </Step>

  <Step title="Sync happens automatically">
    The moment the device detects connectivity — WiFi, mobile data, or satellite — the app uploads all queued submissions to Terriqon in the background. No manual action is needed.
  </Step>

  <Step title="Managers see synced data immediately">
    Once submissions land on the server they appear in the project's submission log and KPI dashboard in real time. Managers can start reviewing data as soon as the first Field Officer's device syncs.
  </Step>
</Steps>

## Installing the PWA

Install Terriqon on a device before going into the field so the app shell and cached forms are available offline.

**Android (Chrome)**

1. Open [terriqon.com](https://terriqon.com) in Chrome.
2. Tap the three-dot browser menu in the top-right corner.
3. Tap **Add to Home Screen** and confirm.

**iOS (Safari)**

1. Open [terriqon.com](https://terriqon.com) in Safari.
2. Tap the **Share** button at the bottom of the screen.
3. Scroll down and tap **Add to Home Screen**, then tap **Add**.

**Desktop (Chrome or Edge)**

1. Open [terriqon.com](https://terriqon.com).
2. Click the install icon (a small screen with an arrow) in the browser address bar.
3. Click **Install** in the prompt that appears.

<Note>
  Terriqon must be installed via the browser's native "Add to Home Screen" flow — it is not available through the Apple App Store or Google Play Store.
</Note>

## What Works Offline vs. Online

| Feature                                    | Offline | Requires connectivity |
| ------------------------------------------ | ------- | --------------------- |
| Filling in forms                           | ✅       |                       |
| Saving drafts                              | ✅       |                       |
| Viewing previously synced project info     | ✅       |                       |
| Initial login                              |         | ✅                     |
| Receiving form updates pushed by a manager |         | ✅                     |
| Submission sync to the server              |         | ✅                     |
| Viewing KPI dashboards                     |         | ✅                     |
| Generating or approving AI reports         |         | ✅                     |

## Conflict Resolution

If a submission is opened and edited on more than one device before either copy has synced — for example, a Field Officer edits a draft on a phone and a tablet while both are offline — Terriqon uses a **last-write-wins** strategy. The submission with the most recent save timestamp is kept, and the older version is discarded.

Managers can inspect the full timestamp history of any submission in the **Audit Log** tab of the submission detail view. If a Field Officer reports that data appears to be missing after a sync, the audit log is the first place to check.
