> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/enumeration-checklist/enumeration-checklist-user-manual.md).
# Enumeration Checklist User Manual
## Steps
* Click on the Beneficiaries card to begin creating and adding beneficiaries.
* Enter the household details on the Household Location page.
* Fill in the details of the house structure and number of rooms.
* Enter the required details in the Household Details screen.
|  |  |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
* On the success acknowledgement screen, click on the View Household Details button to fetch information.
* Click on the Add Child button to append child details.
* Enter the child details in the Individual Details screen as prompted.
* Provide the relevant responses to the questions on the screen related to the child's health.
* Click on the Submit button once the child details are entered. You can add multiple child records in the same way.
---
# 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.digit.org/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/enumeration-checklist/enumeration-checklist-user-manual.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.