> 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/task-status-tracking.md).

# Task Status Tracking

### Overview

Task status communicates intent and progress.

Consistent status use keeps reporting reliable.

### Key Concepts

* **Status**: current state of execution work
* **Status type**: reusable workflow definition
* **Blocked**: explicit signal that work cannot proceed

### How It’s Used

Update status during daily execution.

Review status distribution during weekly governance.

### Benefits

* Clear execution signals for stakeholders
* Faster escalation of risk
* Cleaner reporting across Projects

### Setup Steps

{% stepper %}
{% step %}

### Set a starting status

1. Create or open a task.
2. Set status to the correct starting state.
3. Avoid moving work to **In progress** without active execution.
   {% endstep %}

{% step %}

### Use Blocked as a high-signal state

1. Set status to **Blocked** when progress cannot continue.
2. Add a comment with the unblock condition.
3. Add an owner for the unblock action.
   {% endstep %}

{% step %}

### Close tasks cleanly

1. Set status to **Complete** only when acceptance criteria are met.
2. Add evidence links or notes when required.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep statuses simple and stable.
* Use the same meanings across Projects when possible.
* Review blocked and overdue work weekly.

### Summary

Status is a shared contract for progress reporting.

For status definitions and governance, see [Status Types and Meanings](/transformations/status-types-and-meanings.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/task-status-tracking.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.