> For the complete documentation index, see [llms.txt](https://ask.birdie.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ask.birdie.ai/~/revisions/imP4CTJ80lIhIX6zY2BL/admin-and-settings/initiatives.md).

# Initiatives

## Overview

The Initiatives settings page in Birdie provides tools to standardize project tracking across your organization. It allows administrators to define custom statuses and establish consistent timeframes for performance measurement and reporting.

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FVfh7dyfbqvbYe1rz0dsf%2Fss_settings-initiatives_full_v1.png?alt=media&amp;token=9cb1694e-a28e-411f-a5ab-016ba474ffe5" alt=""><figcaption></figcaption></figure>

## Viewing & Searching

The "Custom Statuses" tab displays a comprehensive list of all active initiative states. The table provides a clear view of:

* Status Label: The name assigned to the workflow stage.
* Color: The visual indicator used in dashboards and dropdowns.
* Triggers Release Date: A checkbox indicating if a status change logs a completion/release event.
* Default Tag: Identifies the starting status for new initiatives.

## Creating New Data

{% stepper %}
{% step %}

### Click the "+ Create new" button

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2F3zGPmjl1Y2euoLnhruGt%2Fss_settings-initiatives_create-headshot_v1.png?alt=media&amp;token=461e9503-536f-4508-b5e9-ebaf2549d423" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Fill in the form

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2F3yrMM1Rm7qseTny8ApeL%2Fss_settings-initiatives_edit-modal_v1.png?alt=media&amp;token=c44cdfc2-e752-4f4f-9567-bc28ee91993d" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Fields in the form

* **Status Label**, the name of the status.
* **Color,** to distinguish the status visually.
* **Triggers Release Date**, (Optional) if reaching this status signifies the initiative is finished.

## Modifying Existing Data

{% stepper %}
{% step %}

### Click the more menu ⋮

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FINt5jTZod35Z72sTDJuE%2Fss_settings-initiatives_more-menu_v1.png?alt=media&amp;token=6ef68450-a030-4628-b5f4-d44af94b0715" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Select Edit

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2F3yrMM1Rm7qseTny8ApeL%2Fss_settings-initiatives_edit-modal_v1.png?alt=media&amp;token=c44cdfc2-e752-4f4f-9567-bc28ee91993d" alt=""><figcaption></figcaption></figure>

### Fields in the form

* **Status Label**, the name of the status.
* **Color,** to distinguish the status visually.
* **Triggers Release Date**, (Optional) if reaching this status signifies the initiative is finished.
  {% endstep %}

{% step %}

### Save

Save the changes.
{% endstep %}
{% endstepper %}

## Removing Data

Statuses can be removed via the three-dot menu on the right of the specific row. However, please note that system-defined statuses like "To Do" are required for platform logic and cannot be deleted.

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FINt5jTZod35Z72sTDJuE%2Fss_settings-initiatives_more-menu_v1.png?alt=media&amp;token=6ef68450-a030-4628-b5f4-d44af94b0715" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
To maintain data integrity, a status can only be removed once it is no longer assigned to any active initiatives. If you wish to delete a status, ensure all associated initiatives are first transitioned to a different state.
{% endhint %}

## Advanced & Unique Features

### Reordering

Use the drag icon (six dots) on the left side of the table to move statuses up or down. This determines their order in the initiative dropdown menu.

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FNcp28V5CFVOi6eq2vHx9%2Fss_settings-initiatives_drag-status_v1.png?alt=media&amp;token=0a5328f5-03d9-4052-abed-e7a55255c189" alt=""><figcaption></figcaption></figure>

### Measurement Timeframe

Under the second tab, users can select the specific time interval used to compare initiative start and completion dates.

Timeframe setting is organization-wide; changing this window updates performance calculations across all reports and dashboards to ensure data consistency.

<figure><img src="https://2659701720-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN7EEIMhL4xEKWM6BDyEL%2Fuploads%2FO6IcQ0TrGgDKAiZ0pzBz%2Fss_settings-initiatives_measurement-timeframe_v1.png?alt=media&amp;token=62541f0d-f4e0-4581-ab66-adcd1e137e35" alt=""><figcaption></figcaption></figure>

## Troubleshooting & FAQs

* "Why is the delete option missing for "To Do"?\
  Solution: "To Do" is a system-required statfussf sthat serves as the default entry point for all initiatives; therefore, it cannot be removed.
* "Why did my dashboard metrics shift?"\
  Solution: If the Measurement Timeframe is changed, the platform recalculates the comparison window for all initiatives, which may update your performance data.


---

# 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://ask.birdie.ai/~/revisions/imP4CTJ80lIhIX6zY2BL/admin-and-settings/initiatives.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.
