> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monnet.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan

> The steps that take a motion from decision to done — how they're structured, who owns them, and how they advance.

Every open motion carries a **plan**: the work that has to happen. Monnet writes it, revises it as things move, and tracks whose turn it is. You'll find it in the **Progress** card on the motion page.

A plan is a tree, not a flat checklist.

## Groups and steps

A **group** holds other steps or groups, and says how they run:

* **Sequential** — one after another. The next step waits.
* **Parallel** — at the same time. Three people can be interviewed at once without any of them blocking the others.

A **step** is a unit of work with exactly one assignee. One assignee, always — if two people need to act, that's two steps.

## Step types

The type says what kind of thing is being asked of the assignee.

| Type | What it means |
| - | - |
| **Task** | Work to be done. The default. |
| **Approval** | The assignee has to explicitly approve before the plan moves on. |
| **Decision** | A choice between named options. The chosen one is recorded. |
| **Interview** | Monnet gathering something from the assignee, usually in their private chat. |
| **Closing** | The write-up that ends the motion. At most one, at the end. |

## Statuses

**Pending → In progress → Done**, plus **Skipped** for a step that was dropped rather than completed. Done and skipped are both terminal: the step no longer holds the ball.

Group status is derived from its children for display, but Monnet decides when a group is actually finished.

## Assignees

Each step names one human or one agent. Assignees get notified when a step becomes theirs, wherever they're reachable — in the app, Slack, Teams, or email.

Monnet never waits for you to announce that you're done. It infers completion from the deliverable: you answered the question, the pull request landed, the document is written.

## Dates

A step can carry a **due date**. Monnet checks dated steps daily and follows up on the ones slipping.

Dates are always absolute, and Monnet computes them from your workspace's timezone — set it in **Settings → General** under **Workspace**, because it's the clock Monnet reads when nobody's at the keyboard.

> [!NOTE]
>
> A due date and a check-in are different things. A due date says *when work is due* and drives a day-level nudge. A **check-in** is Monnet coming back at an exact moment: ask it to follow up Thursday at 2pm and it wakes at 2pm, in the same conversation you asked in. See [Ask Monnet to check in later](/product/discussion#ask-monnet-to-check-in-later).

## Approvals

If a step needs approval and you're the assignee, the motion shows a banner: **"This motion needs your review."**

* **Approve** — the step is done from your side.
* **Reject** — it goes back, with an optional reason.

When everyone required has approved, the step completes and the plan advances.

## Delegating a step to an agent

Assign an [agent](/product/agents) to a step like you'd assign a person. Monnet can only hand real work to an agent that is an assignee on a step that's **in progress** — that gate is what stops an agent writing code nobody asked it to write.

## Options versus the plan

Options capture **what you're choosing between**; the plan captures **what happens once you've chosen**. A motion can use either, both, or neither. See [Motion — Compare options and decide](/product/motion#compare-options-and-decide).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.