> For the complete documentation index, see [llms.txt](https://docs.takadao.io/takadao-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.takadao.io/takadao-docs/part-b.-takadao-the-daos/06-benefits-payout-protocol/decentralized-benefit-payout-management-dbpm-a-multistage-process/stage-one-document-review/manual-verification.md).

# Manual Verification

Subsequently, each document is divided into sections (or sections redacted) and provided to Verifiers who are working independently and without knowledge of who the other Verifiers are. Documents are provided to Verifiers via a secure platform (the “Verifier Dashboard”) that can only be accessed by that specific verifier in a defined period of time.&#x20;

Each document is evaluated on the following criteria

* Information matches original KYC information provided at the time of underwriting
* Correct/official format used
* Information on document provides evidence that the protected event occurred &#x20;

The number of Verifiers who will engage in Stage One is at least 3. The maximum number of Verifiers who will engage in Stage One depends on the type of protected event and the number of documents required.&#x20;


---

# 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.takadao.io/takadao-docs/part-b.-takadao-the-daos/06-benefits-payout-protocol/decentralized-benefit-payout-management-dbpm-a-multistage-process/stage-one-document-review/manual-verification.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.
