stakeholder-comms

Weekly Status Pack

Shapes weekly progress notes into a concise status pack for leadership and cross-functional stakeholders.

Open this workflow

Version 1.1.0

Inputs

- Project Updates
- Reporting Period
- Audience and Tone

Output schema

- Overall Progress
- Completed
- In Progress
- Risks
- Blockers
- Next Week
- Leadership Summary

Downloadable assets

- Prompt pack (Markdown)
- Template definition (JSON)
- Leadership summary checklist

Overview

How this module works

Weekly Status Pack

Shape rough weekly project notes into a concise stakeholder-ready status report.

Best for

Before leadership review
At the end of each delivery week
When consolidating updates from multiple owners
When weekly status updates are inconsistent across the team

Source material

Progress notes
Jira summaries
Bullet updates

What this workflow produces

Overall progress
Completed
In progress
Risks
Blockers
Next week
Leadership summary

Why teams use it

It turns scattered updates into a consistent reporting format. Instead of manually rewriting several project notes into one leadership update, the team gets a clear weekly pack with the right signal.

Instructions

Usage guidance

Instructions

Recommended workflow

Paste the raw update notes first
Keep risk and blocker notes explicit
Edit tone after generation if the audience is highly executive
Use the leadership summary as the email or Slack header

What good output looks like

Overall progress is concise and does not overstate progress
Completed and in-progress items show meaningful movement
Risks and blockers are explicit and easy to escalate
The leadership summary can be reused with minimal rewriting

Customization tips

Add portfolio or program labels
Add a metrics section if your team reports KPIs weekly
Tailor the summary tone for leaders, peers, or project sponsors

Common mistakes

Hiding blockers inside the narrative summary
Mixing risks with completed work
Overwriting the source material so much that the status loses credibility

Assets

Export and packaging notes

Downloadable Assets

Markdown prompt pack
JSON template definition
Leadership summary checklist

Recommended channel adaptations

Email: place the leadership summary first and keep the rest of the output scannable
Slack: shorten the overall progress section and prioritize blockers and next steps
Notion: add milestone or owner context if your weekly update lives in a shared program page

Notes

The plain-text export is useful for email drafts, Slack recaps, and copied status templates.

Examples

Production examples built into this workflow.

Platform migration status

Balances progress, blockers, and leadership framing without sounding vague or overly optimistic.

standardFlagship workflow example

Source input

Completed API dependency mapping and finalized migration plan for checkout services. In progress: sandbox validation for payment routing and regression pass for refund flows. Risk: one partner sandbox is unstable. Blocker: finance sign-off on settlement reporting is still pending. Next week we plan to close regression and complete production readiness review.

Structured output

overall progress

The migration remains on track with planning complete and validation actively moving forward.

completed

API dependency mapping; Migration plan finalization

in progress

Sandbox validation for payment routing; Regression pass for refund flows

risks

Partner sandbox instability may slow validation

blockers

Finance sign-off on settlement reporting is pending

next week

Close regression pass; Complete production readiness review

leadership summary

Execution is progressing, but finance sign-off and sandbox stability need attention to protect the readiness timeline.

Onboarding refresh status

A realistic delivery update where the team needs to balance product progress with instrumentation and reporting caveats.

standardOperational scenario

Source input

Delivered the updated onboarding checklist prototype and aligned with support on handoff copy for stalled accounts. Engineering is implementing account activation states and checklist persistence. Risk remains around instrumentation completeness for stalled-user reporting because some checklist steps still do not emit events. No major blocker this week, but support reporting quality depends on the event coverage. Next week includes design QA, metric validation, and a review of support-facing dashboard requirements.

Structured output

overall progress

The onboarding refresh is moving from design into implementation with good progress, but reporting quality still depends on instrumentation coverage.

completed

Updated onboarding checklist prototype; Support handoff copy alignment

in progress

Implementation of account activation states; Checklist persistence work

risks

Instrumentation may be incomplete for stalled-user reporting; Support-facing reporting quality depends on event coverage

blockers

next week

Design QA; Metric validation; Review support-facing dashboard requirements

leadership summary

Momentum is healthy, but the team still needs full checklist event coverage before support reporting can be considered reliable.

Procurement workflow status

standard

Source input

Completed UAT fixes for procurement review flow and updated release notes draft. In progress on rollback validation and support enablement material. Risk: training content still needs legal review. Blocker: none. Next week target is release sign-off and staged rollout prep.

Structured output

overall progress

The procurement workflow release is in late-stage preparation with UAT fixes complete and sign-off work underway.

completed

UAT fixes for procurement review flow; Release notes draft update

in progress

Rollback validation; Support enablement material

risks

Training content still needs legal review

blockers

next week

Release sign-off; Staged rollout preparation

leadership summary

The release is close to sign-off, with legal review of training content as the primary remaining risk.

Messy update notes

messy

Source input

some work done on alerts and maybe dashboard. qa had issues. leadership wants cleaner update. maybe blocked by data? next wk maybe fix and review.

Structured output

overall progress

There was some movement on alerts and dashboard work, but the update lacks detail and confidence.

completed

Some progress on alerts and dashboard work

in progress

Issue investigation with QA

risks

Data dependency may be affecting progress; Source update is too vague for confident reporting

blockers

Potential data-related blocker is unclear

next week

Clarify completed work; Resolve QA issues; Review status with leadership

leadership summary

The team needs a sharper status update and clearer blocker framing before leadership can assess progress confidently.

Incomplete bullet summary

incomplete

Source input

Met with team. Progress okay. Need follow-up.

Structured output

overall progress

The update indicates acceptable progress but does not provide enough detail for a reliable weekly status pack.

completed

in progress

Follow-up planning

risks

Insufficient source detail

blockers

next week

Collect clearer status inputs from owners

leadership summary

A more detailed update is needed before this can support a useful leadership report.

Weekly status adapted for executive email

Shows how the weekly status workflow can support an executive-ready update pack, not just an internal report.

channelLeadership email adaptation

Source input

Completed pilot onboarding for three procurement customers and resolved the top two setup blockers. In progress on admin analytics and rollout documentation. Risk: one pilot customer still lacks SSO configuration. Blocker: legal review of updated implementation guide is pending. Next week focus is go-live readiness and internal enablement.

Structured output

overall progress

Pilot onboarding has moved into go-live readiness with the major setup blockers resolved for most participants.

completed

Pilot onboarding for three procurement customers; Resolution of the top two setup blockers

in progress

Admin analytics; Rollout documentation

risks

One pilot customer still lacks SSO configuration

blockers

Legal review of the updated implementation guide is pending

next week

Finalize go-live readiness; Complete internal enablement

leadership summary

The pilot is progressing well, but SSO readiness for one customer and legal review of the guide remain the two items most likely to affect go-live timing.