> For the complete documentation index, see [llms.txt](https://docs.elkyc.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elkyc.com/home/review-data/review-process.md).
# Review Process
This section provides detailed steps on how compliance officers can manage and review applicant profiles, either manually or automatically through flow auto-approval.
### Manual Review
As a compliance officer, you have the ability to manage the applicant review process effectively. Here's how to manually handle the review process for an applicant:
* After the system assigns a `Completed` status to the Applicant, a reviewer must be assigned to finish the verification process.
{% hint style="info" %}
A reviewer should also be assigned earlier if manual intervention is needed before the user has provided all the data and the system has performed all the checks. \
It may be necessary if the system completes the verification with the status **"On Hold,"** indicating that a decision cannot be made automatically due to **suspicious data or requiring additional manual review**. In this case, the reviewer must analyze the flagged step and determine the appropriate action.
{% endhint %}
* Navigate to the `Applicants` section from the Sidebar Menu.
* Select a `Reviewer` from the context menu in the applicants table:
*
```
```
* Select a reviewer from the drop-down list and click `Assign`:
* You can also assign a reviewer from the Applicant's Profile.
* Open the applicant's profile.
* Locate the reviewer section, select a reviewer from the drop-down list and click `Assign` :
* The reviewer must review and either Approve or Decline the applicant's data:
* A system user with the necessary [permissions](/home/get-started/work-with-the-team/user-roles-and-permissions.md) can change the reviewer if required.
***
### Automatic Review
If flow [auto-approval](/home/build-verification-flows/flow-builder-overview.md#flow-auto-approval) is enabled, the review process is fully automated.
* Nevertheless, a reviewer can be assigned if manual intervention is needed before the user has provided all the data and the system has performed all the checks.
* Also, a manual review may be required in case of system warnings or if the face matching result is less than 85%.
---
# 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.elkyc.com/home/review-data/review-process.md?ask=&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.
