> 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/hcm-console/create-new-campaign.md).
# Create New Campaign
## Overview
This page explains how to create a new campaign in the HCM Console. Creating a campaign is the first step in setting up and running a health program.
A campaign defines the **campaign type, duration, and basic parameters** that will later be used to configure modules and the mobile application.
**Who Can Create a Campaign**
* Campaign Managers
* ICT4D team members
## Steps
#### Step 1: Select the Campaign Type
1. Click **Create Campaign** on the home page.
2. Choose the appropriate **Campaign Type**.
Campaign types are preconfigured templates that automatically apply default delivery rules and workflows.\
You can review and modify these configurations later if needed.
#### Step 2: Enter the Campaign Name
* In the **Campaign Name** field, enter a unique and descriptive name.
The campaign name:
* Helps identify the campaign throughout the Console
* Should follow recommended naming conventions
* Must be unique to avoid confusion
#### Step 3: Set the Campaign Duration
1. Select the **Start Date** of the campaign.
2. Select the **End Date** of the campaign.
The campaign duration defines the period during which campaign activities will be active. Ensure the dates align with your program plan.
---
# 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/hcm-console/create-new-campaign.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.
