> 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/daily-check-in-face-scan-distributor.md).

# Daily Check-in Face Scan: Distributor

## Overview

Each morning, your face scan is what marks you as present. The scan creates the attendance event, so it must be done by you, on your own device, at your work location.

## Steps

{% stepper %}
{% step %}

### Log in

Open the app and log in. Enter your User ID and Password, accept the privacy notice, and tap Login. These are your existing HCM credentials.

<div align="left"><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FMh6ICViFUd8rxWNYMt94%2Funknown.png?alt=media&amp;token=462d5fc1-6368-49d0-b158-21b8414fb1e7" alt="" height="394" width="178"></div>
{% endstep %}

{% step %}

### Position your face in the frame

The face scan screen opens with the prompt Position your face to verify identity. When the app locks on, the prompt changes to Face detected — tap capture.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FAOugBl2UR4ZNxmUUht6p%2Fimage.png?alt=media&amp;token=cc02814a-b60d-42d8-bbdb-36a6983ac7af" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Tap the camera button

The app shows Scanning… and compares your face against your enrolled profile.
{% endstep %}

{% step %}

### Check the result

On success, you see Face Verified with your user ID and the match percentage. The attendance event is created with the timestamp and GPS coordinates.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FLRHykK7bQB8kHPXG7ago%2Fimage.png?alt=media&amp;token=b72425db-06e5-4253-a33f-90539fdf44aa" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Confirm on the home screen

The Active Session card at the top of the home screen shows Last verified with the elapsed time and a Face tag, confirming your check-in was recorded by face scan rather than PIN.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2F26brolh9MBCKoLIK9DFh%2Fimage.png?alt=media&amp;token=6c530b62-c3d8-4d84-8678-a3f7d4951e22" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Tip**

Wait for the location to resolve. Fetching location… appears while the app captures GPS coordinates. If you move indoors or under cover at this moment, the accuracy figure recorded against the event will be poorer.

The match percentage is shown on every result. A low score that still passes is worth noting — if your scores drop consistently, re-enrol rather than relying on the PIN.
{% 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/daily-check-in-face-scan-distributor.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.
