Copyable workflow

Weekly Async Status Update

A bounded written update that surfaces change, risk, and requests without recreating a meeting transcript in text.

Use when

Projects need regular visibility but most updates can be understood independently and do not require immediate negotiation.

Avoid when

A live incident, sensitive conflict, or cross-team decision needs rapid interaction and a shared understanding now.

Copy the template

WEEKLY PROJECT UPDATE — [Project] — [Date]

STATUS
[On track / At risk / Off track] — [One-sentence reason]

CHANGED THIS WEEK
- [Material outcome or new information]
- [Do not list routine activity]

NEXT CHECKPOINT
- [Deliverable] — [Owner] — [Date]

RISKS / BLOCKERS
- [Risk or blocker] — impact: [what changes] — owner: [name]

DECISIONS / HELP NEEDED
- [Bounded question] — decision owner: [name] — respond by: [date/time]

LINKS
- [Source of truth, dashboard, or decision record]

Report change rather than activity

Readers need to know what became true, what is at risk, and what requires attention. A list of tasks performed creates volume without making the project easier to steer.

Make requests bounded

Name the decision owner, response deadline, and available options. ‘Thoughts?’ produces an open-ended thread; a specific question gives the update an operational next step.

Escalate exceptions

When written responses reveal conflict, ambiguity, or urgency, move that issue—not the entire update—into a short live conversation with the relevant people.

Before you use it

The status has a one-sentence reason
Only material changes are listed
Each action has one owner and date
Each request has a decision owner and response deadline
Readers know where to escalate a disagreement