> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/facial-recognition/work-offline.md).

# Work Offline

## Overview

Everything after enrollment works without a network connection. Face matching runs on the device, and events are held locally until the device reconnects.

## Details

<table><thead><tr><th width="165.2890625">Action</th><th width="143.421875">Works offline?</th><th>Notes</th></tr></thead><tbody><tr><td>First-time face enrollment</td><td>No</td><td>Requires an active internet connection. Do not start enrollment offline — the behaviour is untested in this release and the page may hang.</td></tr><tr><td>Face login / check-in</td><td>Yes</td><td>Matching runs on the device. The attendance event is stored locally.</td></tr><tr><td>Re-verification</td><td>Yes</td><td>Prompts trigger and scans complete normally.</td></tr><tr><td>PIN fallback</td><td>Yes</td><td>The PIN is validated on the device.</td></tr><tr><td>Helper verification</td><td>Yes</td><td>Helper enrollment, however, needs the system user present and is not supported offline mid-campaign.</td></tr><tr><td>Sync to backend</td><td>On reconnection</td><td>Stored events sync automatically with no user action. Duplicate event IDs are prevented on sync.</td></tr></tbody></table>

{% hint style="info" %}
**Protect your unsynced data:**

Do not clear the app storage or uninstall the app while you have unsynced events. Anything not yet synced will be lost.

You can see unsynced records and the time of the last sync from the app. Check this before handing a device back or wiping it.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/facial-recognition/work-offline.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
