> 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/functional-specifications/campaign-setup.md).

# Campaign Setup

<table><thead><tr><th width="183">Name of the field</th><th width="247">Description</th><th width="182">Mandatory</th><th width="100">Input</th><th width="131">Validation</th><th width="166">Comments</th><th>Need data from program/state</th></tr></thead><tbody><tr><td>Address </td><td></td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td>Door number </td><td>House number or door number.</td><td>O</td><td>User</td><td></td><td></td><td></td></tr><tr><td>Latitude</td><td>Latitude of the address.</td><td>O</td><td>System</td><td></td><td></td><td></td></tr><tr><td>Longitude</td><td>Longitude</td><td>O</td><td>System</td><td></td><td></td><td></td></tr><tr><td>Location accuracy</td><td>Accuracy of the address, latitude and longitude, in metres.</td><td>O</td><td>System </td><td></td><td></td><td></td></tr><tr><td>Type</td><td>Type of address: Permanent, correspondence, other.</td><td>R</td><td>User</td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Address Line 1</td><td>Apartment, block, street of the address.</td><td>O</td><td>User</td><td></td><td></td><td></td></tr><tr><td>Address Line 2</td><td>Locality, area, zone, ward of the address.</td><td>O</td><td>User </td><td></td><td></td><td></td></tr><tr><td>Landmark</td><td>Additional landmark to help locate the address.</td><td>O</td><td></td><td></td><td></td><td></td></tr><tr><td>City</td><td>City of the address. This can be represented by the tenant ID itself.</td><td>R</td><td>User</td><td></td><td></td><td></td></tr><tr><td>Pincode</td><td>Pin code of the address.</td><td>R</td><td>User</td><td></td><td>Indian pin codes will usually be all numbers.</td><td></td></tr><tr><td>Building name</td><td>Name of the building.</td><td>O</td><td>User</td><td></td><td></td><td></td></tr><tr><td>Street</td><td>Street name.</td><td>O</td><td>User</td><td></td><td></td><td></td></tr><tr><td>Locality</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Start date</td><td>Campaign start date.</td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td>End date</td><td>Campaign end date.</td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td>Targets</td><td></td><td></td><td></td><td></td><td>Targets will be provided after the micro-planning exercise</td><td>Yes</td></tr><tr><td>Beneficiary type</td><td></td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td>Baseline</td><td>The total number of individuals/ households.</td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td>Target number</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Department</td><td>Project department</td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td>Description</td><td>Description of the project.</td><td>Mandatory</td><td>User</td><td></td><td></td><td>Yes</td></tr><tr><td></td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Set up tasks to be carried out as a part of the campaign</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Tasks</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Resources [ ]</td><td>Array of resources that are a part of the campaign.</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Task resources</td><td></td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Delivery comment</td><td>Capture comments regarding the delivery of campaign resources.</td><td>Mandatory</td><td>User</td><td></td><td>The final list of reasons to be given by the state/programme during impel</td><td>Yes</td></tr><tr><td>Status</td><td>Status of the task. For example, delivered, not delivered, partial delivery, refused, insufficient, etc.</td><td>Mandatory</td><td>User</td><td></td><td>The final list of tasks' status to be given by the state/program during impel.</td><td>Yes</td></tr></tbody></table>


---

# 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/functional-specifications/campaign-setup.md?ask=<question>&goal=<user_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.
