Start with the outcome that changed this week. Then list what is on track, what needs a decision, and what will happen next. Give each next action an owner and date. Keep supporting detail behind links.
Start with the outcome, not the activity list
A reader needs to know whether the work is moving toward its goal. Lead with a one-sentence outcome and, when available, one meaningful measure. The number of meetings held is activity; what changed because of them is the update.
Use four short sections
A repeatable structure makes it easier to write and scan the update. Use the same headings each week and leave a section out when there is nothing to report.
- Progress: state the result achieved and how it compares with the plan.
- Blockers: name the obstacle, its impact, and who can remove it.
- Decisions needed: state the choice, options, decision owner, and deadline.
- Next week: list the next two or three actions with owners and dates.
Make the update actionable
Avoid vague phrases such as 'working on it' or 'awaiting feedback'. Say who is waiting for what, by when, and what happens if the answer does not arrive. Link to the task board, evidence, or decision log for readers who need detail.
A weekly update should also say when a plan changed. That keeps a reader from treating an outdated target as the current commitment.
A weekly update you can adapt
Outcome: the onboarding guide is ready for a five-customer pilot next Tuesday. Progress: the team completed the guide and resolved three of four support issues found in review. Blocker: the final issue needs a product decision by Monday; Priya owns it. Decision needed: whether to pilot with the current manual workaround or delay one week; the product lead will decide by Monday at 2 pm. Next week: run the pilot, record where customers pause, and publish a short findings note on Friday.