> 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-management.md).

# Task Management

### Overview

Tasks represent executable delivery work. Tasks provide ownership and progress tracking for requirements.

### Key Concepts

* **Task**: unit of work assigned to a Teammate
* **Task status**: workflow state for execution tracking
* **Due date**: planning signal for sequencing and reviews
* **Save View**: repeatable task review list

### How It’s Used

Use tasks to execute requirements. Use Save Views for daily triage and weekly delivery reviews.

### Benefits

* Clear ownership and accountability
* Faster execution tracking through consistent statuses
* Better planning through due dates and views

### Setup Steps

{% stepper %}
{% step %}

### Create and assign tasks

* [Create and Assign Tasks](/transformations/create-and-assign-tasks.md)
  {% endstep %}

{% step %}

### Standardize task views

* [Task Views and Organization](/transformations/task-views-and-organization.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Link tasks to requirements when traceability is required.
* Keep status meanings consistent across Projects.
* Use Segments and Processes for reporting consistency when configured.

### Summary

Task Management supports execution tracking for requirements. Views and statuses provide repeatable review workflows.

Related:

* [Requirements](/transformations/requirements.md)
* [Working with Views](/getting-started/working-with-views.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-management.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.