> 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/transit-post.md).
# Transit Post
## Overview
The **Transit Post mode** enables front-line workers to record vaccination or intervention data in dynamic, high-footfall locations (e.g., bus stops, railway stations, parks) where individuals are not pre-enumerated. Instead of individual records, the system captures aggregate counts linked with location details, ensuring data traceability without adding complexity to the delivery flow.
***
## **Key Features**
* **Introduction of Temporary Outreach Posts**: Create temporary immunisation posts at strategic public locations (e.g., bus stops, railway stations, parks) to efficiently reach unvaccinated individuals.
* **Geolocation Capture**: Record the name, type, and nearby landmarks of the transit post, with the option to add precise geolocation data.
* **Quick Data Capture**: Enable swift recording of beneficiary counts with minimal inputs.
* **Flexible Setup**: Configure different types of temporary posts in the system, whether pre-known or added on the spot.
* **Aggregate Counts**: Capture beneficiary numbers without linking to households or facilities.
* **Reduced Field Friction**: Simplify tasks for front-line workers operating in mobile or fluid environments.
* **Support for Large Campaigns**: Optimised for high-volume interventions such as polio campaigns and outreach drives.
* **Coverage Insights**: Gather data from otherwise hard-to-track delivery points, improving visibility of outreach efforts.
## User Roles
Role
Scope of action
Role description
Distributor
Distributor sets up transit posts in high foot fall areas.
Distributors identify areas to set up transit posts and deliver interventions to eligible beneficiaries.
\
---
# 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/transit-post.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.