> 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/managing-blocked-items.md).

# Managing Blocked Items

### Overview

Blocked items represent work that cannot progress.

They require explicit unblock ownership and sequencing decisions.

### Key Concepts

* **Blocked status**: explicit signal that work cannot proceed
* **Unblock condition**: what must happen to resume work
* **Owner**: Teammate accountable for progressing the item

### How It’s Used

Use blocked-item reviews during governance meetings.

Use them during daily execution triage.

### Benefits

* Faster escalation of risk
* Cleaner communication across teams
* Less hidden idle time in delivery plans

### Setup Steps

{% stepper %}
{% step %}

### Identify blocked work

1. Open **Requirements** or **Tasks**.
2. Filter for `Status = Blocked` (or equivalent field).
3. Save the view as a Save View for repeatable reviews.
   {% endstep %}

{% step %}

### Record unblock conditions

1. Open each blocked item.
2. Add a comment stating the unblock condition.
3. Add the accountable owner in the comment.
   {% endstep %}

{% step %}

### Clear blocked signals

1. Update dependencies when prerequisites are completed.
2. Update status from **Blocked** to the next valid status.
3. Record the reason for the change in a comment.
   {% endstep %}
   {% endstepper %}

### Best Practices

* Keep Blocked as a high-signal status.
* Require an unblock condition on every blocked item.
* Review blocked work at least weekly.

### Summary

Blocked items should be visible and managed actively.

Save Views keep the blocked review repeatable.


---

# 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/managing-blocked-items.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.