> 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.md). # Stage One - Document Review The verification process begins with a review of evidentiary documentation that shows that an adverse event has occurred. For example, In the event of death, such documents may include a death certificate, accident report or medical report. In the event of credit default, such documents may include an official demand of restitution by a debt collector and bank statements evidencing no receipt of funds. #### Information segregation In order to protect the information privacy of the individual making the payout request, information is divided into chunks and provided to different verifiers such that no one verifier has all the pieces. --- # 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.md?ask=&goal= ``` `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.