> 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/status-types-and-meanings.md).

# Status Types and Meanings

### Overview

Statuses communicate intent and progress consistently.

Status types standardize those meanings across work items.

### Key Concepts

* **Status**: state label applied to a requirement, task, or test
* **Status type**: reusable workflow definition
* **Governance signal**: status meaning used in reviews and reporting

### How It’s Used

Use status types to standardize delivery across Projects.

Use consistent meanings to protect reporting comparability.

### Benefits

* Cleaner reporting signals
* Faster governance reviews
* Less rework caused by ambiguous status changes

### Setup Steps

{% stepper %}
{% step %}

### Select a minimal workflow

Use a small set of states with clear meaning.

For example:

* Draft
* Ready
* In progress
* Blocked
* Complete
  {% endstep %}

{% step %}

### Define meaning for each status

Define “entry criteria” and “exit criteria” per status.

For example, for **Blocked**:

* Entry: work cannot progress due to a constraint
* Exit: unblock condition is met and execution resumes
  {% endstep %}

{% step %}

### Apply consistently

Apply the same meanings across requirements, tasks, and tests when possible.

Document exceptions when a separate workflow is required.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep Blocked as a high-signal status.
* Avoid adding statuses for rare edge cases.
* Review workflow changes quarterly.

### Summary

Status types provide a shared contract for progress reporting.

For setup, see [Custom Status Creation](/transformations/custom-status-creation.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 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://help.transform.ai/transformations/status-types-and-meanings.md?ask=<question>&goal=<endgoal>
```

`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.