> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/core-concepts/manual-review-and-manual-capture.md).

# Manual Review & Manual Capture

***

### Overview

1Kosmos IDV supports two fallback mechanisms for when a user cannot complete automated document scanning.

Manual Capture is triggered when users who are unable to scan their ID automatically after repeated scan failures. The user does not need to select this mode manually, the system transitions them.

| Fallback mode      | Description                                                                                                                                                                                                 |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Manual Capture** | Share the identity verification session link from the Manual Capture workflow. The system automatically switches to Manual Capture mode, and the user takes still photos of the front and back of their ID. |
| **Manual Review**  | After images are submitted (via auto or manual capture), a 1Kosmos agent reviews the session and approves or rejects it manually. The user sees an **Under Review** status screen.                          |

**Alternate device.** If a user cannot complete scanning on their current device, advise them to use an alternate device (for example, a smartphone with a better camera) and re-initiate the IDV link. Try this before escalating to Manual Capture.

### Supported documents

The 1Kosmos IDV platform accepts a defined set of document types. Advise users to have one of these ready before starting the verification journey.

See the [Supported Document List](/identity-verification/supported-documents.md).

**Alternate ID (if primary fails).** If a user's primary ID cannot be scanned or is not accepted, advise them to try an alternate accepted document from the list. For example, if a driver's license fails, a passport may scan more reliably due to its flat, high-contrast layout.

{% hint style="info" %}
Worn, heavily laminated, or damaged documents may fail automated scanning. In these cases, Manual Capture is the recommended fallback — not a different document.
{% endhint %}

### Alternate device guidance

If a user's primary device cannot complete the scan, advise them to switch to an alternate device before escalating further.

**Recommended steps:**

1. Ask the user to open the IDV link on a second device (smartphone preferred, tablet acceptable).
2. Confirm the alternate device has a working rear camera.
3. Re-send the IDV link, or have the user copy it, to the alternate device.
4. The user restarts the journey on the new device. Manual Capture will be available again if auto-scan fails.
5. If the alternate device also fails, escalate to Manual Review.

### Manual Review: what happens after submission

Once a user completes Manual Capture (or any IDV session that requires additional verification), their session may be placed into Manual Review. The user sees:

*"Under Review, Images submitted. Our team is reviewing your session."*

#### What happens during Manual Review

* A 1Kosmos reviewer (or designated agent) examines the submitted ID images and selfie.
* The reviewer verifies document authenticity, legibility, and face match against the selfie.
* The session is then approved or rejected in the AdminX.

#### AAMVA check during Manual Review

During the manual review process, 1Kosmos agents can run a database check to validate a driver's license or state ID.

| AAMVA check detail     | Description                                                                                                                                  |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **What it verifies**   | Confirms that the name, date of birth, license number, expiration date, and address on the submitted ID match the DMV record for that state. |
| **When to run it**     | During manual review, when the reviewer needs additional confidence in the document's authenticity.                                          |
| **When NOT to run it** | When the issuing state is not in scope for AAMVA. Check with your 1Kosmos admin for the current in-scope state list.                         |

### Common issues

* **Image quality** — Without automated quality gates, users may submit blurry, poorly lit, or cropped images, increasing IDV0001 failures and hard stops.
* **OCR extraction** — Poor image quality leads to misread or missing fields (DOB, document number, name), driving Data Match and Format check failures and inflating manual review volume.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.1kosmos.com/identity-verification/core-concepts/manual-review-and-manual-capture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
