> ## Documentation Index > Fetch the complete documentation index at: https://docs.attensira.com/llms.txt > Use this file to discover all available pages before exploring further. # Delegation > How the Chief of staff hands work to your projects: one task per line, how each line finds its project, when you are asked to choose, and what approval mode changes. You set the direction; the agents do the work. When you ask for work rather than an answer, the Chief of staff does not do it inside the chat. It hands each piece to the **project** whose crew does that kind of work, and tells you where each one went. A project is a standing area of work with its own crew: the blog, a set of product pages, outreach. Each handed-off piece becomes a **task** in its project: a session of its own, started in your name and queued for the project's crew. Attensira guarantees the volume of work, not visibility. A task handed off is work we owe you; what an answer engine then does with the result is not ours to promise, and every change is measured [before and after](/measure/before-and-after) instead. ## Handing work off Write the work as lines, one piece of work per line, in your own words: ```text theme={null} Write an article comparing our plans with the two biggest alternatives Fix the meta descriptions on the pricing pages #outreach pitch us to the three directories that decide "best crm for startups" ``` * **In a chat**, the Chief of staff splits what you asked for into tasks and hands them off. Several lines typed into the message box on Home go to it as one message, and it does the splitting. * **Over MCP**, the same message sent to [`ask`](/mcp/recipes#hand-several-pieces-of-work-to-the-agents) reaches the same Chief of staff, which hands the lines off the same way. One hand-off takes up to **20 lines**, each up to **2,000 characters**. A line longer than that is a brief, and belongs in a chat. Handed off is not done. The Chief of staff says what went where and what happens next, and never describes a task as finished that a crew has only been given. ## How each line finds its project The rules run in this order, and the first that applies decides: 1. **The line names a project** with its `#slug`. Every `#token` in the line is checked against your projects, so "post it with #seo" is a hashtag, not a destination, unless you have a project called `seo`. A line that *starts* with a `#token` naming no project is treated as a typo and put to you. 2. **The hand-off names a project** for all its lines. 3. **The workspace has exactly one project taking work.** It goes there. 4. **Otherwise Attensira decides**, reading the line against each project's name and focus. When it is at least 60% sure, the line goes to that project. Below that, or when the line belongs to no project, or when the decision does not come back in time, the line is put to you. A wrong project files real work in the wrong place; a one-click choice costs you a second. A paused project, or one whose crew is still being set up, never takes a line. A line that names one is put to you with the reason. Routing only decides where a line goes. It never approves anything, never changes an approval mode and never decides that work is allowed. ## When you are asked to choose Lines waiting on a project come back as a question in the same chat: > **Project** ยท Which project should take "Fix the meta descriptions on the pricing pages"? * The options are your most recently active projects, up to four, each with its `#slug` and focus. Type a project's name to pick one that is not offered. * Up to three waiting lines get a question each. More than three share one question, and your answer applies to all of them. * Picking a project files the line straight away. If the project you picked has stopped taking work since it was offered, the Chief of staff sorts it out with you. * The question waits for up to **7 days**. Unanswered, the lines are not handed off, and the card says nobody picked a project in time. With **no projects** in the workspace there is nothing to choose from. The Chief of staff does the work in the chat instead, or offers to [make it a project](/agent/chats#handing-work-to-the-agents). ## The card Every hand-off draws a **Handed off** card with one row per line: | Row says | Meaning | | - | - | | **Queued** | Filed in its project for the crew. The line links to the task's own session, which is where to follow the work. | | **Waiting on you** | No project yet. **Choose a project** jumps to the question. | | **Not handed off** | Filing it failed, with the reason: the balance is spent, the project is no longer there, or "try again". **Retry** sends that line again. | The card is a record of the hand-off, not a progress bar: a filed row keeps saying **Queued** while its crew works. Open the task to see how far it has got. A placed row names its project. Where Attensira picked the project, hovering or focusing the name shows how sure it was, in words and as a percentage, and says **Attensira picked the project**: *Very sure* from 90%, *Fairly sure* from 75%, *Somewhat sure* from 60%. A project you named, or your only project, shows its name alone. The same line handed to the same project from the same chat is the same task. A retry, a double click or the agent repeating itself files it once. ## Approval Handing work off is an action, so it goes through your [approval mode](/agent/approval) like any other. | Mode | When the Chief of staff hands work off | | - | - | | **Ask** | An approval card first. Nothing is filed until you approve the hand-off. | | **Draft** | Filed without asking. A task stays inside the workspace and is undone by cancelling its session. | | **Act** | As Draft. | That is only the hand-off. The work each task then does is gated again in its own run, under the **stricter** of the workspace's approval mode and the project's own. A project can hold its crew tighter than the workspace, never looser. An article a crew writes is filed for your approval like any other article; see [what Attensira changes on its own](/agent/approval#what-attensira-changes-on-its-own-and-what-it-always-asks-about). ## Credits Deciding where lines go is charged as credits to the chat that handed them off, once per hand-off. Each task's work is metered in its own session, like any other run. A hand-off from a workspace whose balance is spent files nothing, and each row says why. Modes, questions, and what the Chief of staff can reach. What runs on its own, and what always waits for you. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.