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

# Attestation Log

> How to review your confirmation history in the Forager app

The Attestation Log shows every confirmation your team has recorded — matches, mismatches, and new assets discovered. Use it to verify that your scans were recorded, review what happened during a session, or look up when a specific device was last confirmed.

## Opening the Attestation Log

From the Forager home screen, tap **Attestation Log**.

## Reading the log

Each entry shows:

| Field         | Description                                                 |
| ------------- | ----------------------------------------------------------- |
| **Asset tag** | The barcode that was scanned                                |
| **Type**      | Match, mismatch confirmed, mismatch dismissed, or new asset |
| **Location**  | The room recorded at the time of the confirmation           |
| **Tech**      | Who performed the scan                                      |
| **Time**      | When the confirmation was recorded                          |

Entries are sorted with the most recent at the top.

## Searching

Type in the search bar to find entries by asset tag or location. Results update as you type. Tap **✕** to clear the search and return to the full list.

## Filtering

Tap a filter chip at the top of the screen to narrow the list by result type:

* **Match** — confirmed in expected location
* **Mismatch** — asset found in unexpected location
* **New asset** — first time this asset tag was seen by Forager

The type filter and search work together — for example, filter to **Mismatch** and search for a room name to find all mismatches in a specific area.

## When to use the Attestation Log

* **Verifying a scan was recorded** — After completing a round, tech checks the log to confirm a specific scan was captured before clocking out. Look for the asset tag with the matching timestamp.
* **Mismatch follow-up** — A mismatch was flagged during scanning. Tech reviews the log entry to see exactly what was recorded — the asset tag, the room, and whether it was confirmed or dismissed.
* **Pre-audit self-check** — Tech knows an auditor will ask about a specific device. They find the entry and note the timestamp to reference in the review rather than trying to recall it from memory.
* **Discrepancy investigation** — Admin gets a report that a device's location doesn't match what was reported on the floor. The log shows which scan created the record and who performed it.
* **Confirming a result from a previous session** — Tech scanned a device yesterday but can't remember what result it returned. The log shows the entry with the type and location.

<Note>
  The in-app log shows recent records. For full historical reporting, filtered by date range, location, or tech, use the **Reports** page at [dashboard.harbinge.rs](https://dashboard.harbinge.rs).
</Note>