> 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/access/public-health-product-suite/health-campaign-management-hcm/outside-household/add-a-missing-village-field-workers.md).

# Add A Missing Village - Field Workers

## Steps

Use this option to add a settlement that is not in the village list.

1\. On Choose your boundaries, under Didn’t find your Village? - click on Add Missed Village.

2\. Wait while Capturing Location runs, then select Save.

3\. Enter the Village name, and choose the Village type (Urban, Rural or Slum). Respond to the queries like - How safe is it to visit this settlement and how you reach this settlement. Check the GPS accuracy.

4\. Select Save. You will see a Village added, and the village is selected for you.

5\. Select Submit, then vaccinate there as in Section 2 or 3.

<div align="left"><img src="https://1852481771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAZdb5ZOhlbhsVhSVljzM%2Fuploads%2FIczNXm8vFLxJafxHzdAn%2FFigure%2015%3A%20Adding%20a%20missed%20village..png?alt=media&amp;token=4b77ef02-e87f-4f32-a010-399109c14bce" alt="Figure 15: Adding a missed village." height="336" width="480"></div>


---

# 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/access/public-health-product-suite/health-campaign-management-hcm/outside-household/add-a-missing-village-field-workers.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.
