Automations
Schedule recurring colleague work and keep every outcome reviewable.
Automations run colleague work on a schedule. They are appropriate for repeatable jobs with known inputs, a clear output and an accountable reviewer.
Before you schedule
Run the work manually first. Confirm that the colleague’s tools, rules, model budget and output format are appropriate. Scheduling an unclear job makes the uncertainty recur.
Define the recurring outcome
State what should be produced each time, where inputs come from and which changes matter. Include a date or period in the output when it helps reviewers distinguish runs.
Examples of bounded recurring work include preparing a periodic source summary, assembling a reporting pack from approved files, or checking a defined evidence set for exceptions.
Set the schedule
Add the schedule in the colleague configuration. Check the timezone and cadence shown by the product. Assign an owner who understands the job and can respond when it needs guidance.
Keep approval boundaries
Scheduling does not remove approval rules. If a run proposes a sensitive action, the item can still wait in Needs You. Design the workflow so a delayed approval does not create an unsafe or misleading outcome.
Review each result
Open the result from the workspace. Compare it with the previous period when relevant, inspect artifacts and verify important claims. A schedule makes execution repeat; it does not make the content automatically correct.
When to pause
Pause or revise the automation when inputs, ownership, connections, policy or expected output change. If a job repeatedly needs the same clarification, update the colleague’s instructions instead of answering the same question every run.
Next step
Read Approvals to design clear human checkpoints for recurring work.