1. Scheduled tasks
Write the task first
State the work to run, the sources, the delivery location, and the review boundary. Use a successful manual run as the basis for a schedule. A recurring task should not depend on a person remembering an unstated step.
Set time and timezone
Choose the frequency and the timezone explicitly. A date range such as 'last complete week' is different from 'the previous seven days.' Check the next scheduled run against the intended business calendar.
Inspect a run
Review the first run's output and its tool activity. Confirm that sources were read at the expected time and that the output went to the correct location. Report a missing source instead of silently using old data.
2. Automation templates
Choose a relevant template
Browse the automation catalog for a workflow that matches your desired output. Read the required applications and source fields. A template is a starting instruction, not permission to act on every connected system.
Fill in the team's context
Replace account names, date ranges, channels, and source locations with your own. Identify the person who will review the first results. Leave explicit instructions for missing or contradictory information.
Run it once
Try the workflow manually with a small, representative input. Check its output against the source material. Change the template where your team's process differs from its assumptions.
3. Proactive updates
Choose what deserves attention
A useful check has an observable condition: an overdue item, a new blocker, or a missing confirmation. Define that condition instead of asking for a general update about everything.
Keep unchanged state quiet
Include what should happen when nothing has changed. This prevents a recurring workflow from sending the same summary every time and helps the team notice the updates that need action.
Give the update a destination
Use a channel or task output your team already reviews. Include source links and an owner for the next step. External outreach and record changes still follow approval and access rules.
Try a brief you can review
Use the last complete reporting week. Prepare a sourced update with wins, blockers, owners, and next steps. Ask for review before posting. Report unavailable sources.Try the hands-on practice to check your instruction before using it in a real workspace.
Review before repeating
Inspect the draft and confirm its sources. Correct one specific part of the process when the result falls short. Save a reliable instruction as a skill and assign a teammate to maintain it.
