How to Brief an AI Team: Task Templates That Work

An AI team is several AI employees with different roles who share one job and work on it in the team's dedicated Windows workspace. They can research, write, fill in spreadsheets and work in the browser and desktop programs like people do. But like people, they can only be as good as the brief they get. This guide gives you a simple task structure, shows how to split work across roles, where to put checkpoints and which mistakes waste the most time, then finishes with six ready-to-use templates.

Why the brief matters more with a team#

A single employee who misunderstands a task wastes one afternoon. A team of four that misunderstands it wastes four afternoons in parallel and hands you a beautifully formatted wrong answer. The fix is not longer prompts. It is the same discipline a good manager uses with new staff: a clear goal, a concrete deliverable and an agreed way to say "this is done".

The eight parts of a good task#

Use these as headings in your task. Not every task needs all eight, but the first three are never optional.

Goal and deliverable#

Write the goal as an outcome, not an activity. "Research competitors" is an activity. "Decide whether to lower our entry price" is a goal, and it tells the team what to pay attention to. Then name the deliverable precisely: a file type, a table structure, a length, a language.

Done criteria#

This is the part people skip most often, and the one that matters most. List what must be true when the work is finished: the number of rows, the columns that cannot be empty, what has been checked twice, what format the dates use. If you can, attach one example of a good result.

Sources and access#

Point the team to where the information lives and say which logins it may use. Give each employee only the access its role needs. If a site asks for a two-factor code, the code goes to the person you nominate, and the employee does not try to get around CAPTCHAs.

Limits#

The employee asks on its own about payments, messages to strangers, posts in your name and deletions. Write your own limits explicitly, for example: any reply to an unhappy customer waits for me.

Splitting work across roles#

A team pays off when the job has parts that can be split by role and parts that feed each other. When you brief the whole team, describe the roles and the hand-offs:

• Who researches. A market researcher gathers raw information: companies, prices, contacts, sources.
• Who checks and structures. A data analyst or procurement specialist cleans the list, removes duplicates and adds the fields you need.
• Who writes. A content or sales role drafts emails, posts or summaries from the checked data.
• Who assembles the report. One employee is responsible for the final summary, so you get one answer instead of four.

You do not have to assign every step by hand. You can give the team the overall task and let the employees divide it, but naming the hand-offs ("the researcher passes the list to the analyst once it reaches 50 rows") makes the result more predictable. For an overview of how teams are put together, read AI team for business, and browse ready-made setups in solutions.

Checkpoints: correct early, not late#

Long tasks need a point where you look at partial results. Good checkpoints are cheap for you and decisive for the team:

1. 1After the first ten rows. Is the team looking in the right places and filling the right columns?
2. 2After the first drafts. Is the tone right? Are the facts correct?
3. 3Before anything costly or irreversible. The employee stops and asks on its own.

Between checkpoints you can look in on any employee in your dashboard: screenshots of its screen refresh every few seconds, and the action log shows what it opened and changed.

Common mistakes#

• One task, ten goals. "Run our marketing" is dozens of tasks. Split it, and start with the one that hurts most.
• No done criteria. Without them, the team stops when it thinks it is finished, which may not match what you meant.
• Too much access. Admin rights "just in case" add risk and no speed. Grant what the role needs.
• Unstated constraints. If you never contact competitors, never use a certain supplier region or always write in British English, say so.
• Report format left open. You get a long essay when you wanted a table. Specify it.
• No checkpoint. The first time you see the work is when it is complete and wrong.

Six ready-to-use templates#

Copy one, adjust the details and give it to your team. Each follows the structure above.

Choosing roles and plans#

Pick roles in the AI employee catalog. A paid team has its own Windows workspace and is billed per month: on the SUPER II plan one team costs 24 000 ₽ (≈ $255) per month, and the Several teams plan lowers the price per team from 5 teams. Details are on the pricing page.

Where to start#

1. 1Choose one recurring task that already has a clear result.
2. 2Write it with the eight parts above and add one checkpoint.
3. 3Sign up free and try the wording on the Start plan before giving it to a paid team.

For a worked example of a multi-role job, see how to source suppliers with AI.