> 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/create-and-assign-tasks.md).

# Create and Assign Tasks

Turn requirements and action items into owned, trackable work.

### Overview

Tasks turn approved scope into owned execution work.

They create accountability and progress tracking at the work-item level.

### Key Concepts

* **Task**: unit of delivery work with an owner and status
* **Assignee**: single Teammate accountable for completion
* **Linked requirement**: scope traceability from task to requirement
* **Due date**: scheduling signal for planning and escalation
* **Dependency**: sequencing constraint across tasks

### How It’s Used

Create tasks during planning.

Update tasks during daily execution and weekly reviews.

### Benefits

* Clear ownership for execution work
* Cleaner progress reporting
* Better traceability from requirements to delivery evidence

### Setup Steps

{% stepper %}
{% step %}

### Create a task from the Tasks area

1. Open the Project.
2. Navigate to **Tasks**.
3. Select **Create task** (or **New task**).
4. Enter a short, verb-based task name.
5. Select **Create** (or **Save**).
   {% endstep %}

{% step %}

### Create a task from a requirement (recommended)

1. Navigate to **Requirements**.
2. Open a requirement.
3. Select **Create task** (or equivalent action).
4. Confirm the requirement link is created.
   {% endstep %}

{% step %}

### Assign an owner and set intent

1. Set **Assignee** to one Teammate.
2. Set **Status** to the correct starting state.
3. Set a **Due date** when sequencing requires it.
4. Add acceptance criteria in the description when needed.
   {% endstep %}

{% step %}

### Organize execution (optional)

1. Add subtasks for multi-step work.
2. Add dependencies for true sequencing constraints.

Related: [Task Dependencies](/transformations/task-dependencies.md)
{% endstep %}
{% endstepper %}

### Best Practices

* Keep one assignee per task.
* Keep tasks small enough for weekly reporting.
* Link tasks to requirements for traceability.
* Use **Blocked** only with an unblock condition.
* Record decisions and changes in comments for auditability.

### Summary

Tasks provide the execution backbone for delivery work.

Next actions:

* Track status cleanly: [Task Status Tracking](/transformations/task-status-tracking.md)
* Build repeatable lists: [Task Views and Organization](/transformations/task-views-and-organization.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/create-and-assign-tasks.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.