How to Write a Weekly Project Summary People Can Scan

A weekly summary should reduce the number of questions the team asks next week. A diary of everything you did rarely achieves that. Readers need movement, risk, and ownership.

Use The Same Five Headings Every Week

Keep the structure predictable:

• Outcome this week
• Next milestone
• Decisions made
• Blockers and dependencies
• Help needed

Under each heading, write only changes since the previous update. “Continued working on onboarding” is weak. “Completed account creation; email verification remains for the 24 July milestone” shows state.

Write For Decisions, Not Activity

Executives and collaborators scan for exceptions. Lead with changed dates, new risks, scope choices, and requests. Routine activity belongs in the task system.

If you manage several workstreams, Axtio presents each project as a row and separates work by who currently owns it. That visual state can become the source for your written summary, while the summary explains why anything moved or stalled.

End With Named Requests

Do not close with “let me know if you have questions.” Ask for the specific help the project needs:

Decision needed: Nina to select pricing option A or B by Tuesday, 12:00.

Use this Wrivio Context to shape raw notes:

Rewrite these notes as a weekly project summary with Outcome, Next Milestone, Decisions, Blockers, and Help Needed. Lead with changes and exceptions. Preserve owners, dates, metrics, and uncertainty. Do not invent progress.

Compare the result against your notes, then remove any section that says nothing. Consistency helps readers scan; brevity rewards them for doing it.

See also how to write a status update executives read.