> 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/hcm-console/functional-specifications.md). # Functional Specifications

Field Name	Description	Mandatory/Optional	Input	Need Data from programme/state?
Campaign type	Specific campaign run by the system admin.	Mandatory	User	Yes
Campaign name	Name given to the campaign being created.	Mandatory	User	Yes
Beneficiary type	Specify the beneficiaries for the campaign. For example, household, individual, structure.	Mandatory	Auto Selected by the system	No
Start and end dates of the campaign	This will define when the campaign starts and ends.	Mandatory for moving to the next step.	User	Yes
Number of cycles in the campaign	This will set the number of cycles in the campaign.	Mandatory for moving to the next step	User	Yes
Number of deliveries in each cycle in the campaign	This will set the number of deliveries in each cycle of the campaign.	Mandatory for moving to the next step	User	Yes
Dates for each cycle	This will set the dates of cycles in each cycle of the campaign.	Mandatory for campaign creation, non mandatory to move to the next step	User	Yes
Selecting parameters for delivery rules	These are the parameters basis which a user can create the delivery rules.	Mandatory for moving to the next step	User	Yes
Selecting operators for delivery rules	These are the operators basis which a user can create the delivery rules.	Mandatory for moving to the next step	User	Yes
Configuring resources for delivery	These are the products/resources that are going to be delivered to the beneficiary during the campaign.	Mandatory for moving to the next step	User	Yes
Selection of the boundary information	The user will select boundaries where the user wants to select the boundary.	Mandatory for moving to the next step	User	Yes
Setting of targets	The user will enter boundary-wise targets in an Excel template.	Mandatory for campaign creation, non mandatory to move to the next step	User	Yes
Creating facility data	The user will enter the facility data in an Excel template.	Mandatory for campaign creation, non mandatory to move to the next step	User	Yes
Creating user data	The system admin will enter the user data in an Excel template.	Mandatory for campaign creation, non mandatory to move to the next step	User

--- # 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/hcm-console/functional-specifications.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.