> 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/statuses.md).

# Statuses

### Overview

Statuses standardize workflow state across work items. Consistent meanings improve reporting and reduce execution confusion.

### Key Concepts

* **Status Type**: reusable set of allowed statuses
* **Status meaning**: shared definition of what each status represents
* **Workflow alignment**: keeping statuses consistent across Projects

### How It’s Used

Use status standards during rollout. Use them when teams report inconsistent progress tracking.

### Benefits

* Cleaner reporting across Projects
* Faster reviews through consistent signals
* Reduced rework from ambiguous state definitions

### Setup Steps

1. Define status meanings at Account scope.
2. Apply status types consistently across Projects.
3. Review status usage quarterly and remove unused states.

### Best Practices

* Keep the status set small and stable.
* Document meaning and entry criteria in an internal SOP.
* Avoid repurposing a status for a new meaning.

### Summary

Statuses standardize workflow state and reporting. Meanings should be consistent and governed.

Related:

* [Status Types and Meanings](/transformations/status-types-and-meanings.md)
* [Custom Status Creation](/transformations/custom-status-creation.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)


---

# 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/statuses.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.