> 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/review-verification-history.md).

# Review Verification History

## Overview

Verification History is the record of everything that has happened on the device. Use it to confirm that a check-in was recorded, to check a match score, or to see whether a worker checked in by face or by PIN.

## Steps

{% stepper %}
{% step %}

### Open the history

From the home screen, tap History on the Active Session card, or open Verification History from the menu.
{% endstep %}

{% step %}

### Use the Verification tab

Lists every verification event: login verification, re-verification, and helper verification. Each entry shows the user ID, the event ID, the verification type, the method (Facial Recognition with a match percentage, or Enrollment PIN Verification), the date and time, and the GPS coordinates with accuracy in metres.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FXQlc5EkDbFLKDsRWKFO7%2Fimage.png?alt=media&amp;token=12fc5a2c-0250-4853-aa42-184e24fa018b" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Read the status chips

Verified in green for a successful face match, Failed in red for a failed attempt, and PIN Used in amber where the worker fell back to the PIN.
{% endstep %}

{% step %}

### Use the Enrollment tab

Lists enrollment events rather than daily verifications, with the same identifying details.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FrlrGRcz2V2Sx5Oh4lsNH%2Fimage.png?alt=media&amp;token=3324a6a4-aeca-44e4-a500-cc43a979c306" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Search for a worker

Use the search field at the top of either tab to filter by user. Refer to the table below for details.
{% endstep %}
{% endstepper %}

<table><thead><tr><th width="174.0703125">What you see</th><th>What it means</th></tr></thead><tbody><tr><td>Verified (green)</td><td>The face scan passed. The match percentage is shown next to Facial Recognition.</td></tr><tr><td>Failed (red)</td><td>The face scan did not reach the configured match threshold. Check the attempt sequence around it.</td></tr><tr><td>PIN Used (amber)</td><td>The worker fell back to the enrollment PIN. Shown as Enrollment Pin Verification rather than a match score.</td></tr><tr><td>Login Verification</td><td>The morning check-in event.</td></tr><tr><td>Re-verification</td><td>A scan completed in response to a random prompt during the day.</td></tr><tr><td>Face Enrollment</td><td>The original enrollment, shown under the Enrollment tab.</td></tr><tr><td>Coordinates with (±Nm)</td><td>The GPS position recorded with the event and its accuracy in metres. A large figure means the fix was poor.</td></tr></tbody></table>


---

# 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/review-verification-history.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.
