How do I write a weekly update without listing every small task?
Quick answer
Group related tasks under the outcome they supported instead of reporting each action separately. For each group, say what changed, why it matters, and what remains or is needed. Include important decisions or blockers, then finish with next week's focus. Keep details that help someone understand progress or act; leave out routine steps that do not change the picture.
The question, the details, the next step.
I have to send a weekly update, but I did lots of little things: reviewed comments, fixed wording, checked a few numbers, and messaged people. How do I make it useful without listing all of that?
Start by asking what those actions added up to. The update is about the state of the work, not a time log. Put related actions together under a result or workstream, then describe the change they helped make.
For example, instead of listing “reviewed comments, fixed wording, checked figures,” you might write: “Prepared the draft for review by addressing feedback and checking key figures; it is now ready for the next review.” Use that only if it accurately describes what happened. If the figures are still being checked or the draft is not ready, say so plainly.
A useful test for every detail is: Would this help the reader understand progress, a decision, a risk, or what is needed next? If not, it probably does not need its own line.
How do I decide what counts as an outcome? Some weeks I don't finish a big deliverable.
An outcome does not have to be a finished launch or major milestone. It can be a meaningful change in status: a draft became reviewable, an open question was clarified, a recurring issue was narrowed down, or a handoff was prepared. Be precise about the degree of progress. “Draft ready for review” is different from “draft approved.”
Try this simple structure for each item:
- Work area or goal.
- What changed this week.
- Why that change matters or what it enables.
- Remaining step, decision, or help needed, if any.
If nothing changed beyond routine maintenance, you can say that briefly and name the next meaningful checkpoint. You do not have to inflate ordinary activity into a breakthrough.
Could you show me how to turn a messy task list into a short update? I want something I can adapt.
Assume, just for this example, that the notes are: “ask design about layout; revise draft; check two figures; send revised file to reviewer; wait for feedback.” First group them by the work they support. The layout question, edits, and figure check may all belong to preparing the draft. Sending it to a reviewer is the handoff. Waiting for feedback is a current status, not a completed task.
A compact version could be:
“Draft preparation: Revised the draft, checked two figures, and resolved the layout question. The file is now with the reviewer; feedback is pending. Next: incorporate comments once received.”
That wording assumes the layout question was actually resolved and the file was sent. If either assumption is wrong, change the sentence: for example, “Layout is still under discussion” or “The file is ready to send.” The update should distinguish completed work from work in progress and avoid implying a result that has not happened.
Should I mention blockers and decisions? And how can I keep the whole update brief?
Mention a blocker when it affects timing, scope, or someone else's next step. State what is blocked, what it depends on, and whether you need a decision or action. Keep the wording neutral: “Testing is waiting on the approved sample file; please confirm which version to use.” Avoid burying the request in a list of minor activity.
For a decision, record the decision and its practical consequence, if known: “We chose option B, so the next draft will use the shorter format.” Do not include a decision merely because a conversation happened; include it when it changes the work or helps readers stay aligned.
To stay brief, lead with the overall status, combine related work, and give each topic only the detail needed to understand progress or respond. A reusable template is:
“Overall: [on track / at risk / needs attention], because [short reason]. Progress: [work area] — [meaningful change and why it matters]. Decision or blocker: [what changed / what is waiting on whom], if relevant. Next: [priority or next milestone]. Needed from you: [specific action and date], or ‘None.’”
Delete a line if it only repeats an action without explaining a change, consequence, or useful next step.
A practical checklist
Group related actions under a work area or intended result.
Describe what changed, not every step you took.
Separate completed results from work that is underway or awaiting review.
Include decisions, blockers, and requests only when they affect progress or the reader's next step.
End with the next priority and any specific help or decision needed.
Remove details that do not clarify progress, impact, or action.
A few more useful answers
What if most of my week was routine work?
Summarize the routine work by its purpose or continuing result, then name any exception that affected progress. You do not need to make routine activity sound like a major milestone.
Should I include a task that is still unfinished?
Yes, when its status matters to the reader. Say what remains, what it depends on, and the next step; do not present it as completed.
How many topics should a weekly update have?
Use as many as needed to cover meaningful work, decisions, and requests—without forcing every small task into a separate topic. Group related items and follow any format your team already expects.