> 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/v1.5/hcm-product-suite/health-products/digit-hcm-app/user-manual/single-round-campaigns/registration-and-delivery.md).
# Registration & Delivery
An illustrative guide to using the Single-Round Registration & Delivery module
This enables frontline workers to register households and individuals using the HCM application.
## Key Features
* Register households
* Add/Delete members to/from the households
* Edit household/individual details
* Delete household
* Record delivery of an intervention
## User Roles
| User Role | Scope of Action | Role Description |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Frontline workers | - Register households
- Add members
- Deliver intervention
- SBCC
| Provide direct healthcare services, communicate SBCC information, and support to communities. Usually operate in teams and within a specified boundary. |
| Field Supervisors | - Train and monitor the field teams
- Provide on ground support
- May have authority for registration and distribution to support the teams
| Organize and direct the activity of frontline staff in health initiatives. Offer direction, assistance, and coordination for effective service delivery, adherence to protocols, and high-quality results. |
## Using Registration & Delivery
When field and district supervisors navigate to the home screen, the beneficiaries button is visible to them.
On this page, the following actions can be performed:
* You can register a new household only after attempting a search.
* Click on the "Register New Household" button to register a household.
* After the user clicks on "Register New Household", the page navigates to the "Household Location" page.
* The "Administrative Area" is the only mandatory field. "Address Line 1", "Address Line 2", 'Landmark' and "Postal Code" are optional fields.
* Clicking on the 'Next' button will take the user to the "Household Details" page where the number of members living in the household can be registered.
 
* Clicking the 'Next' button will take the user the "Individual details" screen.
* The first individual added will be the "Head of Household" by default.
* The name, ID type, and ID number fields are mandatory. You can enter the date of birth or their age. The date birth will take precedence over age.
* When the user clicks on the submit button, a popup appears asking for confirmation.
* If the user clicks on ‘Submit’, the household is registered and a confirmation screen is displayed.
* The user can click on the "Back to Search" button for editing the household or register new household fields.
* Click on the open card to navigate to the detailed page of the household.
* There is an "Edit Household" button for editing household details, which navigates the user to the household location screen. The service delivery status is present below the household’s name followed by the administrative area and the number of members.
* There are cards for each member, starting from the household head. The card consists of the ‘Edit’ button for individual-level actions.
* For adding new members to the household, there is the "Add Member" button below the member cards, which navigates the user to the "Individual Details" screen.
* At the bottom, the "Deliver Intervention" button is present which navigates the user to the update delivery screen.
---
# 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/v1.5/hcm-product-suite/health-products/digit-hcm-app/user-manual/single-round-campaigns/registration-and-delivery.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.