> 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/v2.0/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/view-dual-timeline.md).
# View Dual Timeline
Dual Timeline View for Campaign Creation
## **Steps**
The campaign creation process is structured with a dual timeline to manage different steps more effectively. The Horizontal Timeline at the top handles major campaign setup steps, while the Vertical Timeline on the left handles sub-steps within each major step.
### **Horizontal Timeline**
1. Click on Campaign Details.
2. Define campaign Type, Campaign Name, and Campaign Dates.
3. Review a summary of the campaign details.
4. Enter the Boundary Details. This step does not have a Vertical Timeline.
5. Enter the Delivery Details, such as the number of cycles and deliveries, including the cycle dates.
6. Set up rules for the delivery of resources.
7. Review a summary of the delivery details.
8. Upload Data for targets, facilities, and the creation of HCM app users sections.
9. Review the summary and the success screen before proceeding to app configuration.
10. App Configuration - Manage checklists and other configurations for the HCM mobile app.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.digit.org/health/v2.0/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/view-dual-timeline.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
