Weekly Project Status Digest to Stakeholders
Every Friday, turn Jira/Asana activity into an exec summary doc (Notion or Google Docs) and email it to stakeholders — approved before it sends.
This recipe replaces the Friday-afternoon scramble of chasing boards and copying numbers into a status update. It pulls completion, movement, and blocker data from the connected PM tool, pairs it with upcoming milestones from the calendar, assigns a grounded RAG status per workstream, and writes an audience-correct executive summary into the doc-of-record — a Notion page by default, or a Google Doc when your org bridges Google Docs through Composio. Recipients are resolved from your CRM or a saved list and cleaned of anyone who opted out, every metric is cited back to its source task, and the whole package is held at a one-click approval gate — idempotent, so a re-run for the same week never duplicates a doc or an email.
How it runs
Multi-agent orchestration — here's the flow, step by step.
Resolve stakeholder recipients and run the suppression gate first — exclude any unsubscribed / do-not-contact / suppression-list contact with a named reason.
crm scannerClassify each surviving recipient into executive vs. working audience tier for the right level of detail.
triage routerPull the week's completed/opened/blocked tasks from Jira (JQL) or Asana per in-scope project, capturing each provider record ID.
pm scannerPull upcoming milestones, deadlines, and standing project meetings from Google Calendar / Outlook for the next 1-2 weeks.
calendar scannerNormalize and dedupe by provider record ID, then compute completion counts, velocity, carry-over, and week-over-week delta.
data analystMap work against milestones/OKRs and assign each workstream a grounded RAG status with named risks/blockers.
okr trackerAssemble the full status document structure — metrics, RAG table, highlights, blockers, upcoming milestones — in memory.
report generatorDistill the executive layer: overall RAG, the number that matters, top risk, and any decision leadership must make.
executive briefing writerDraft the stakeholder email — tiered subject, inline summary, doc link, sign-off — matched to brand voice, staged not sent.
email writerCompute and persist the idempotency key digest:{project}:{iso_week} before any outbound action; reuse on re-run, resume partial runs.
workflow orchestratorOn approval, create the doc-of-record with the staged body and return the shareable URL — a Notion page via notion_create_page, or a Google Doc via the Composio GOOGLEDOCS_* bridge (composio_search_tools then composio_execute); once per week.
docs managerOn approval, stage/send the email per surviving recipient, optionally post to Slack, and write outcomes + snapshot back to the ledger.
distributorRequired Agents
12- crm-scanner
- triage-router
- pm-scanner
- calendar-scanner
- data-analyst
- okr-tracker
- report-generator
- executive-briefing-writer
- email-writer
- docs-manager
- distributor
- workflow-orchestrator
Connections
Required
Optional
What it does
- Pulls task completion & blockers from Jira or Asana
- Real week-over-week velocity & delta computation
- Grounded RAG status per workstream (Green/Amber/Red)
- Executive summary auto-drafted into a Notion page or Google Doc
- Suppression gate — excludes opted-out stakeholders first
- Audience-tiered digest (executive vs. working detail)
- Idempotent weekly key — never duplicates a doc or send
- One-click approval before any doc or email is created
Example prompt
Every Friday, pull this week's completed tasks from our Asana projects, write up an executive status summary in a Google Doc, and email it to our project stakeholders.
Ready to deploy Weekly Project Status Digest to Stakeholders?
Start free. One click, full agent orchestration.
Get Started Free →