Weekly Status Update Template

A weekly status update template should help people coordinate, not perform busyness.

The best weekly status update is short enough to read quickly and specific enough to show progress, blockers, and next priorities. AI can help compress rough notes, but you still need to decide what matters.

Use this template for async updates in Slack, email, Notion, or a team doc.

Weekly status update template

Weekly status update: [name/team/project]
Week of: [date]

Progress:
- [Completed outcome or meaningful progress.]
- [Completed outcome or meaningful progress.]

Current focus:
- [What you are working on now.]

Blocked or at risk:
- [Blocker/risk, owner, and what is needed.]

Next week:
- [Priority 1]
- [Priority 2]

Help needed:
- [Decision, review, approval, or dependency. Write "none" if there is no ask.]

The "help needed" line prevents a common failure: people hide the real ask inside a paragraph and nobody acts on it.

Short async version

Use this when the team sends lightweight weekly updates in a channel.

This week:
- [Main outcome]
- [Second outcome]

Next:
- [Next priority]

Blocked:
- [Blocker or "none"]

Ask:
- [Decision/review needed or "none"]

This version is better than a long report when the update is for coordination, not formal reporting.

Manager update version

Use this when the reader needs risk and decision context.

Weekly update: [project/team]

Status: [on track / at risk / blocked]

What moved forward:
- [Outcome with evidence.]

Risk or blocker:
- [Risk, impact, owner, next step.]

Decision needed:
- [Decision needed by date.]

Next priority:
- [Priority for next week.]

For managers, the most important line is usually not what you finished. It is what needs a decision before work slows down.

What to send where

Channel	Best update length	Use when
Slack or Teams	4-8 bullets	The team needs quick async coordination.
Email	One short sectioned note	The reader may forward or archive the update.
Project doc	Structured status block	The update becomes the weekly source of truth.
Client report	Use a fuller weekly report	The update needs outcomes, metrics, and decisions.

AI rewrite prompt

Use this prompt when your weekly notes are too long.

Rewrite these rough notes into a concise weekly status update.

Rules:
- Keep it under 120 words.
- Separate progress, next focus, blockers, and asks.
- Do not invent completed work.
- Do not hide blockers.
- If there is no blocker or ask, write "none."

Rough notes:
[paste notes here]

Do not let AI make the update sound smoother than the work actually is. A clean update that hides risk is worse than a rough update that tells the truth.

Skip this template if

Skip a weekly status update when:

• Nobody reads or acts on it.
• The team already reviews work in a live planning rhythm.
• The update repeats the same dashboard everyone already sees.
• It creates status theater instead of decisions.

Use a weekly update only when it improves coordination.

Best next step

Use the weekly report template when the update needs more detail, metrics, or stakeholder context. To turn scattered tasks and meeting notes into a repeatable update process, follow automate weekly report with AI. If meeting notes are part of the source material, use the meeting summary template.