---
url: /operate/task-cards.md
description: >-
  Step 5 of an engagement. What a Task Card holds, how people write them, and
  how you check them.
---

# 5. Task Cards

Built

A Task Card is one task, written by the person who does it. It is the smallest unit of the map and the thing an AI agent needs before it can do the work.

## What a complete card names

| Field | Question it answers |
| --- | --- |
| **Trigger** | What starts this task? |
| **What comes in** | What do you get, from which role or team, and how does it reach you? |
| **Steps** | What do you do, in order? Include physical work in physical detail. |
| **Who gets the result** | Which role or team, and how? |
| **Done means** | How do you know it is finished and right? |
| **How often** | How many times a week or month? |
| **How long** | How long does it take each time? |
| **Only I know** | What would a replacement not find written anywhere? |

How often and how long give the baseline. The hand-offs let the process map link one card to the next and find the gaps.

Task Cards cover manual work too. A card for loading a truck is as valid as a card for sending an invoice.

## How people write them

| Way | How it works |
| --- | --- |
| **Talk about your work** (client app) | The person talks or types about their work in any order. DutyGraph finds the tasks and opens each as a card with three parts: arrives, I do, leaves. It asks only for what is missing. **Lock in** puts the card in **My work** as a draft. |
| **In the client app, by questions** | Answer the task questions by voice or text. The answers become a draft card in **My work**. |
| **In their own AI chat** | Connect Claude or ChatGPT over MCP and say "Find my work". The assistant interviews them and saves each answer as it is given. See [Employee tools](../build/employee-tools.md). |
| **By rambling** | A person can send anything. If it cannot be drafted yet, it is kept as a note. |

A card is sent for review only when DutyGraph's check says it is complete and the person says yes to the preview. Cards that skip the interview are refused.

### Locked in and ready

| Level | Rule |
| --- | --- |
| **Draft** | A part has no words yet |
| **Locked in** | All three parts (arrives, I do, leaves) have words |
| **Ready** | Locked in, and it hands on to the next card with a named person |

## Task Card or workflow?

A Task Card is one person's job. When the same unit of work (an order, an invoice) passes through the cards of 2 or more people, that chain is a **workflow**. DutyGraph suggests workflows from the hand-offs, and you confirm them on **Work Map › Work flows**. See [Work Map and workflows](work-map.md).

## What you check

* Is each field something the person said or confirmed? Never fill a field with a guess.
* Does the card trace up to a duty and a responsibility in the person's role profile?
* Do the hand-offs match the cards of the people on the other side? The Work Map shows **Both sides agree** or **One side said it**, and the person on the silent side gets a one-tap **Mentioned you** check in their app.
* Is "only I know" filled in for work that depends on one person?

```sh
dutygraph coverage     # who has cards, and how many
dutygraph gaps list    # gaps in the map, such as a task with no owner
dutygraph agents list  # agent specs made from confirmed cards
```

## From card to agent

A confirmed Task Card can be exported as an agent spec for the AI tool the company uses. The export describes the agent. It does not run or deploy one. See [Build agents in the handbook](../handbook/agents/index.md).

## Related

* [Task Cards in the handbook](../handbook/discovery/task-cards.md)
* [Role AI task starters](role-ai.md)
* [Work Map and workflows](work-map.md)
