Create your first job

Some work is too big for one conversation: it has parts, it needs more than one skill set, and it will outlast the chat you asked it in. This guide hands work like that to a team and follows it to a result.

Before you start

Know what done looks like: the outcome, the form you want it in, and the constraints that matter, such as a deadline, a length or the sources you trust. A job is only as good as its brief, which is the whole instruction the coordinator works from.

Choose a concrete project first: the name sits at the top left of every page, and in All projects nothing can be created, because a job belongs to one project at a time.

Start it in a conversation you will come back to, because that is where the job asks its questions and reports its result.

1. Ask for the work as a job

Describe the outcome to your assistant and say you want a team on it, not an answer.

Research what our four main competitors charge for their mid-tier plan, work out where our pricing sits, and write me a report I can take to the board on Friday. Use their public pricing pages, quote the source for every figure, and flag what you could not confirm. Plan it with me before the writing starts.

Your assistant confirms it is setting a team on the work, and you have the conversation back straight away.

2. Find the job

Automations > Jobs (/jobs) lists your jobs, each with a badge saying what it is doing, under tabs that group them by state. Open yours: you land on the Team tab, which fills with the coordinator and each specialist as they join.

3. Read the plan

The Plan tab holds the coordinator's plan: the phases, what each produces, and a count of what is planned, pending, active, done and failed. It is rewritten as the work goes, so return to it.

Read it as you would a colleague's proposal. If a phase is missing or the order is wrong, say so in your chat and it is adjusted.

4. Approve or send back a gated phase

Because you asked to see the plan first, the work waits. On the Tasks tab the held task carries a Review Plan button, which opens the submitted plan with Approve and Reject beneath it.

Rejecting needs a reason. Write what was wrong in a sentence or two: it goes back to the coordinator, and the next version answers it. Approving releases the phase and the board starts moving.

5. Answer its questions

When a job reaches a decision only you can make, it stops rather than guessing. An amber card headed Job needs your input appears in your chat with a summary, the questions numbered and an Open job link. Reply there in plain words and the coordinator resumes on its own.

If you missed the card, the Needs input tab of the jobs list gathers every job waiting on you, and the job's page carries the same question in a banner. Where else Player One chases you is set on Admin > Alerts (/admin/alerts).

6. Watch it work

Two tabs tell you where things stand. Tasks is a three-column board of Pending, In Progress and Finished, grouped by phase, with every finished task carrying its outcome. Team lists everyone on the job, and opening one opens that agent's own conversation, so you can read what a specialist did.

Both update live. Automations > Active (/automations) is the wider view of everything running at once.

7. Collect the result

The Files tab is the job's own shared folder, where the drafts, the notes and the finished report are. It stays there after the job ends.

The coordinator also writes its result into the chat the job is talking to. That message is your signal the work is finished.

8. Close it

Read the deliverable first. When you are satisfied, say so: "close the competitor job". It is marked done and stops asking anything of you. Close job on the job page does the same.

To tidy the list, use the actions menu beside the tabs: Archive tucks the job away and keeps everything, and Delete job removes the record, though the team's files are kept.

Stopping and resuming

"Stop the competitor job" and "resume it" are enough, said in the chat. Stop and Resume are also buttons on the job page, and Stop asks you to confirm first. Stopping is a pause, not a delete, and nothing is destroyed.

Resuming picks the job back up with its phases, tasks, team and workspace as they were, and takes about half a minute to get going. Stopping returns before the team has downed tools, so trust the board rather than the confirmation.

If something goes wrong

Nothing has moved for a while. A job that looks frozen is often waiting on capacity from your AI provider rather than stuck; it resumes itself when the limit resets.

The badge says Needs attention. It tried to sort itself out, could not, and wants a decision from you. Ask in the chat: "what is the competitor job waiting on?" Your assistant reads the board and tells you what the page cannot.

One task failed. It sits in the Finished column with a Failed badge and a Retry control on its card.

You cannot find the job. Switch the project picker to All projects and look again.

Where next

• Jobs for every tab, badge and state in one place.
• Give it work for when a job is more than the work needs.
• Agents, delegation and team chat for why side work belongs off your main thread.
• Research, deck, send for this shape carried through to a finished presentation.