The work behind the work
Draft weekly project updates from Slack, Notion and Google Drive
Writing the weekly update often starts with catching up on the week. Messages, decisions and documents are spread across different places. Use one repeatable process to gather progress and make blockers visible.
The result
What you’ll get
A weekly update covering progress, blockers and next steps, ready to review.
Website refresh · Weekly update
- Progress
- The new onboarding screens are ready for review.
- Blocker
- The billing flow still needs a decision on the trial experience.
- Next step
- Review onboarding on Tuesday, then agree on the billing scope.
The method
A process your agent can follow.
3 stepsRead this week’s updates in the selected project channel.
Limit the search to the chosen channel and reporting period. Link back to the messages that matter.
SlackCheck the project notes and shared documents for changes.
Compare decisions and documents with the channel updates. Mark conflicting information for review.
Notion
Google DriveDraft a short update with progress, blockers and next steps.
Group the draft into progress, blockers and next steps. Include owners only when the sources identify them.
Make it fit your work.
Choose your sources, adjust the instructions and decide what your agent can do. Keep the method in your Upsy setup so a compatible agent has a clear starting point next time.
See how to create your ownA few things to know
Can each project use a different update format?
Yes. Change the instructions to match the project’s sections and reporting cadence while keeping the same source-gathering process.
Does the update get posted to Slack automatically?
This example creates a draft for review. Publishing it would require a separate action and permission.
Can I use this Playbook today?
This page previews the proposed Playbooks feature. You can copy and adapt the instructions now. The Get started link opens the current Upsy product; it does not install this example.
