Manage work and decisions

Track tasks and check their progress

A task is a saved record of work somebody has agreed to do. It has an identity, a person or agent responsible for it, a status and a result that can be checked. Use the task board to see what is planned, what is being worked on and what needs a decision, without treating a chat promise as completed work.

Contents

Your Mind is the shared Mensara workspace holding those records. The Portal is its web interface. Open its Tasks tab to see the Plan page. Your connected agent, the AI tool you use with the Mind, can help find and update the same task records within your access.

Start with a result you can check

Describe the work and what will count as finished. Include the person responsible, any deadline and the source information needed. For a fictional example, preparing a meeting brief is finished when the agreed brief is saved and its sources have been checked. Writing “prepare brief” in chat alone does not establish that result.

Ask your agent to check whether the task already exists before creating another one. Keep the reference it returns. A task's title can change; its reference lets you return to the same work.

Read the status and the evidence together

Backlog means work has been recorded. Active means it is scheduled for current work. In progress means it is being worked on. Blocked means something prevents progress; the task should name what is needed. Review means the work is waiting to be checked. Done means its agreed result has been verified. Cancelled means it has been deliberately abandoned.

A task moves forward one step at a time, in the order backlog, active, in progress, review, done. It cannot skip a step or move back one. A task that is active or in progress can become blocked and later return to where it was. Any task that is not already cancelled can be cancelled, and cancelled is final. The only way to reopen a done task is to move it back to active.

To mark a task done, the task must have a Verification section with a Result or Evidence line that says what was checked. Every task named as a finish gate, and every child task, must already be done. If any of these is missing, the update is refused.

The Plan page groups tasks around initiatives and areas and includes work needing you. Open the relevant task and inspect the result or blocker behind its status. A checked checklist item describes one step; it does not prove that every completion condition has been met.

A status describes the point reached

Use the recorded result and blocker to understand the status.

A task starts as recorded or planned work. When it is being done it is in progress. A blocker is a reason to record what is needed before continuing. Finished work can wait for review; done requires evidence for the agreed result. The map shows the common path and the blocked branch. A task moves one step at a time, can be blocked from active or in progress, can be cancelled from any state except cancelled, and a done task can only be reopened to active.

Ask for a bounded update

You can say: “Find the task for this work. Record the result, the source that shows it and what remains.” Have the agent return the task reference and read the saved state after updating it. It must use the task's supported update route and your authority, rather than creating a replacement file with an invented identifier.

If the board cannot load, use the reported error. An unavailable board is not evidence that no tasks exist. If a task is missing, check the intended account, Mind and permitted area before making a duplicate.

Let another person or agent continue

Save the current result, sources, unresolved question and next action on the existing task before the handoff. The next person still needs access to those sources. Help another agent continue the work explains this, including the difference between a lasting task and an agent's temporary claim.

Related

Practical guides for people and agents

Start with one useful job

Join the waitlist

Plain text for AI agents. Same content as the human page.

## For agents

- What Mensara is: it gives a team its own Mind, one shared memory for the team and their AI agents, built by Xanadu Labs LLC.
- Status: signup is not open. A person joins the waitlist at https://www.mensara.ai/#waitlist. Agents cannot create an account or sign up.
- How you can help your person: explain what Mensara does, check whether it fits a job their team repeats, and share the waitlist link.
- Agent references: https://www.mensara.ai/llms.txt lists every page as Markdown and the tool input references for connected agents.

---

# Track tasks and check their progress

Content updated 29 October 2026.

Guides · Manage work and decisions · [How it works](https://www.mensara.ai/how-it-works)

A task is a saved record of work somebody has agreed to do. It has an identity, a person or agent responsible for it, a status and a result that can be checked. Use the task board to see what is planned, what is being worked on and what needs a decision, without treating a chat promise as completed work.

[Page as Markdown](https://www.mensara.ai/how-it-works/track-tasks.md)

[Operating procedure](https://www.mensara.ai/how-it-works/track-task-procedure)

Your Mind is the shared Mensara workspace holding those records. The Portal is its web interface. Open its **Tasks** tab to see the **Plan** page. Your connected agent, the AI tool you use with the Mind, can help find and update the same task records within your access.

## Start with a result you can check

Describe the work and what will count as finished. Include the person responsible, any deadline and the source information needed. For a fictional example, preparing a meeting brief is finished when the agreed brief is saved and its sources have been checked. Writing “prepare brief” in chat alone does not establish that result.

Ask your agent to check whether the task already exists before creating another one. Keep the reference it returns. A task's title can change; its reference lets you return to the same work.

## Read the status and the evidence together

**Backlog** means work has been recorded. **Active** means it is scheduled for current work. **In progress** means it is being worked on. **Blocked** means something prevents progress; the task should name what is needed. **Review** means the work is waiting to be checked. **Done** means its agreed result has been verified. **Cancelled** means it has been deliberately abandoned.

A task moves forward one step at a time, in the order backlog, active, in progress, review, done. It cannot skip a step or move back one. A task that is active or in progress can become blocked and later return to where it was. Any task that is not already cancelled can be cancelled, and cancelled is final. The only way to reopen a done task is to move it back to active.

To mark a task done, the task must have a **Verification** section with a **Result** or **Evidence** line that says what was checked. Every task named as a finish gate, and every child task, must already be done. If any of these is missing, the update is refused.

The Plan page groups tasks around initiatives and areas and includes work needing you. Open the relevant task and inspect the result or blocker behind its status. A checked checklist item describes one step; it does not prove that every completion condition has been met.

### A status describes the point reached

Use the recorded result and blocker to understand the status.

A task starts as recorded or planned work. When it is being done it is in progress. A blocker is a reason to record what is needed before continuing. Finished work can wait for review; done requires evidence for the agreed result. The map shows the common path and the blocked branch. A task moves one step at a time, can be blocked from active or in progress, can be cancelled from any state except cancelled, and a done task can only be reopened to active.

## Ask for a bounded update

You can say: “Find the task for this work. Record the result, the source that shows it and what remains.” Have the agent return the task reference and read the saved state after updating it. It must use the task's supported update route and your authority, rather than creating a replacement file with an invented identifier.

If the board cannot load, use the reported error. An unavailable board is not evidence that no tasks exist. If a task is missing, check the intended account, Mind and permitted area before making a duplicate.

## Let another person or agent continue

Save the current result, sources, unresolved question and next action on the existing task before the handoff. The next person still needs access to those sources. [Help another agent continue the work](https://www.mensara.ai/how-it-works/continue-the-work) explains this, including the difference between a lasting task and an agent's temporary claim.

## Related

- [Help another agent continue the work](https://www.mensara.ai/how-it-works/continue-the-work)
- [Review what needs your attention](https://www.mensara.ai/how-it-works/review-attention)
- [Record a decision or policy with its evidence](https://www.mensara.ai/how-it-works/operating-records)
- [Choose access for a teammate](https://www.mensara.ai/how-it-works/right-access)

Previous page: [Change or remove a teammate’s access](https://www.mensara.ai/how-it-works/change-access)

Next page: [Help another agent continue the work](https://www.mensara.ai/how-it-works/continue-the-work)

A handoff gives the next person or agent enough saved context to continue a specific job.

[Join the waitlist](https://www.mensara.ai/?guide_attribution=eyJfcmFpbHMiOnsiZGF0YSI6eyJvcmlnaW5fcGF0aCI6Ii9ob3ctaXQtd29ya3MvdHJhY2stdGFza3MiLCJjdGFfaWQiOiJtYXJrZG93biIsImNvbnRlbnRfcmV2aXNpb24iOiIyMmEzNTEyMDBjNjQ3OTQ5In0sInB1ciI6Imd1aWRlLWNsaWNrIn19--bb7cb0a987ade35550fd5edd61a3ab8587724eee#waitlist)