> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/custom-status-creation.md).

# Custom Status Creation

### Overview

Custom statuses support delivery workflows that vary by Organization.

They standardize reporting and approvals when defaults do not fit.

### Key Concepts

* **Status type**: workflow definition for an item type
* **Status**: state label within a workflow
* **Default status**: starting state used for new items

### How It’s Used

Use custom statuses when governance needs differ across Projects.

Keep workflows stable to protect reporting continuity.

### Benefits

* Consistent execution signals
* Cleaner governance reviews
* Better alignment across delivery teams

### Setup Steps

{% stepper %}
{% step %}

### Open status configuration

1. Navigate to **Project Settings**.
2. Open **Statuses** (or equivalent area).
   {% endstep %}

{% step %}

### Create or edit a status type

1. Select an item type, such as Tasks or Requirements.
2. Select **Create status type** (or **Edit**).
3. Name the status type with intent.
   {% endstep %}

{% step %}

### Add statuses and order

1. Add the required statuses.
2. Order statuses in the expected progression.
3. Set a default starting status.
   {% endstep %}

{% step %}

### Validate reporting impact

1. Confirm Save Views and dashboards reflect the new statuses.
2. Update team guidance for meaning changes.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep workflows minimal.
* Use the same status meanings across Projects when possible.
* Avoid frequent changes after delivery begins.

### Summary

Custom statuses should support governance and reporting.

They should not be used for one-off exceptions.


---

# 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://help.transform.ai/transformations/custom-status-creation.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.