A weekly status report, or weekly update, tells the people around a team what changed this week. It goes to the team's manager, the teams that depend on it and often the team itself. Readers want three answers: did anything ship, are the numbers moving, and do you need something from me. Everything else is detail they will skip.
This template follows the progress, plans, problems format (often called PPP), with a short block of numbers in the middle. The example above is week 41 of a fictional mobile team at a budgeting app: a release shipped, signups up 9%, a dip in the app rating, and two blockers with a named person who can clear each one.
What goes in each section
The headline
The week and the one thing worth knowing: "iOS 4.2 shipped, signups up 9%." Under it, the dates, the team and one line on what it works on, for readers from outside the team. Mistake to avoid: "Weekly update, week 41" and nothing else. A reader who stops at the headline should still learn something.
01 · Shipped
Two to four small cards, each a finished thing and what users or the business get from it. "Faster first sync: bank accounts connect in 40 seconds, down from 2 minutes." Mistake to avoid: listing work in progress here. If it is not done, it belongs in next week's plans.
02 · Numbers
Three or four big numbers, marked green when they went well and orange when they went the wrong way, then a small table of this week against last week and the goal. Use the same metrics every week so trends show. Mistake to avoid: hiding the bad number. One honest orange tile makes the green ones believable.
03 · Next week
Three plans in priority order, each with an owner and a day. Lead with the fix for whatever went wrong this week. Mistake to avoid: ten items. If everything is a plan, readers cannot tell what matters.
04 · Blockers
What is stuck, since when, and the exact help you need from whom: "Need: Sam to escalate with the partner." If nothing is blocked, write "none this week". End with a one-line shout-out for someone who helped. Mistake to avoid: a blocker with no ask. Readers cannot help if they do not know what to do.
How often, and how long
Every week, on the same day; Friday or Monday morning both work. Aim for ten to fifteen minutes to write and five to read. The trick is to keep one note open during the week and drop a line in it when something ships or gets stuck, so Friday is editing, not remembering. If the update regularly needs a timeline, a budget and a risk log, the work is a project and deserves a project status report for its sponsor. A founder writing to investors rather than a manager wants the monthly investor update instead.
How to use this template
- In Obsidian: install the free myone.page plugin, run New page from template and pick Weekly update.
- With AI: paste the week's notes, a changelog or a tracker export into ChatGPT or Claude with the prompt from myone.page/ai and ask for this week's update.
- By hand: copy the Markdown of the example above. It is a plain note, so last week's update is the start of this week's.
Where myone.page helps
A weekly update shared as a link is one page people come back to, not another long email. Teammates can add their own line in the browser before it goes out, without Obsidian, and the edits land in your note. If your team already writes weekly updates in Slack threads and nobody outside the team reads them, a thread is fine. Use a page when other teams or your manager need to scan it in a minute.