The team for this work
Which workers to hire, which Marketplace worker templates start them, and the order they need each other in.
✦ Guide · Intermediate
Agents for operations
Status reporting, meeting actions, invoices, deadlines and policy questions as a team of flexible workers that runs the week.
Start guideYOUR OUTCOME
You will run an operations pod that reports weekly, captures actions from every meeting, files invoices and answers policy questions from approved documents.
Reporting on a routine, actions on every meeting Invoices monthly, deadlines weekly Policy answers only from approved files
4 min
Hire the first wave
Import, rename, and give a goal with the deliverable, the sources and the finish line.
The team and the second wave
Run the team in one room; hire the rest once the first deliverable exists.
The routine that keeps working
One recurring job on a schedule, then a status round and a grade.
What each lesson covers
The guide, lesson by lesson.
The team for this work
Which workers to hire, which Marketplace worker templates start them, and the order they need each other in.
Start from the work, not the tool: Status reporting, meeting actions, invoices, deadlines and policy questions as a team of flexible workers that runs the week. The team is Sol · Status (Weekly status reporting), Ada · Actions (Meeting notes and actions), Ivy · Invoices (Invoice and expense organisation), Pol · Policy (Document and policy Q&A). Each starts from a Marketplace template, imported as your own copy, renamed and re-goaled on the setup card; nothing personal and no creator credentials come with a template.
Practice. Open Marketplace, Worker templates, and read the Instructions and Integrations of each template on this list before you import anything. Note which sources each one will ask you for.
Marketplace → Worker templates → open Weekly status reporting. Read Instructions, then Integrations.
Hire the first wave
Import, rename, and give a goal with the deliverable, the sources and the finish line.
Import worker creates your copy as a flexible worker and opens the setup card. Rename it, replace the goal with yours, and choose When to work. Status reporting is the first hire because it reads what everyone else produces and shows the week at a glance.
Practice. Import Weekly status reporting, rename it Sol · Status, and paste your goal on the setup card. Choose Now, once, and Continue. Check its first deliverable in Doc Manager before the next hire.
Name: Sol · Status. Goal: Every Friday, read the project board and this week's updates in the workspace, and write a one-page status note as a document: what moved, what slipped, who owns each next step, and one risk. Use only the board and the updates; flag anything you cannot verify. Draft only. When to work: Now, once.
The team and the second wave
Run the team in one room; hire the rest once the first deliverable exists.
Click New team, name it Ops pod, add Sol · Status, and post what the team is for. Then hire the second wave with goals that start by reading the first wave's document. @Name directs one member, @everyone the room, and Work in the member row opens what that member did in the team. Actions come from meetings; invoices from the inbox; policy answers from approved files only.
Practice. Create Ops pod, add each hire as it joins, and ask every member to post what it made and the one thing it would flag.
@everyone Welcome to the ops pod. Ada: turn Tuesday's transcript into an action register with owners and dates. Ivy: file September's invoices into the expense sheet and flag duplicates. Pol: answer questions only from the approved policy folder and say when the answer is not there. Post what you made and what you'd flag.
The routine that keeps working
One recurring job on a schedule, then a status round and a grade.
Deadlines are the operations job that a routine does better than a person. Each run shows on its worker's Runs tab. Close each cycle with a status round, "@everyone one line each", and a grade against the acceptance checks each worker wrote first.
Practice. Add the time in When it runs, use Run now to get today's first report, then run one status round in Ops pod.
When it runs → Add a time. Name: Deadlines. What should it do? Read the contracts folder and the task records, list every deadline and renewal in the next 30 days with its owner, and flag any without a next step. Say nothing if the list is empty. Repeats: Every week, Monday, 07:00.
Keep going
Make the learning stick
Start with one real piece of work.
Open Oppermind beside the lesson, apply each step, and leave with something you can use.