Prompt Notebook

Status updates · Project management · Templates

How to write a weekly status update, with a full example

Last updated By T. Krause

A weekly status update tells the people around a project where it stands without a meeting. Here is what goes in each section, a complete example for an invented help centre migration, the mistakes that make updates useless and a free template.

A weekly status update opens with one line saying whether the project is on track, at risk or off track, and why. Below that it lists what got done this week, what happens next week, the risks, what you need from the reader and two or three numbers. Keep it to one screen, under 300 words, so a stakeholder can read it in about two minutes and know whether they need to act.

The rest of this guide goes through each section, then shows a complete update for an invented team so you can see one filled in. If you want a page with the sections already in place, copy our free weekly status update template.

Who the update is for

A status update is for people who need to know where the project stands but don't sit in its meetings: a manager, a client, a sponsor, the team next door that depends on your work. Write for the reader who has two minutes and five other projects. They want to know whether it will land when you said, and whether they need to do anything. Every line should help answer one of those two questions.

What to put in each section

The sections below follow our template: a status callout at the top, then five headings.

The status callout

The callout at the top holds the status and the reason for it. Pick one of three words: on track, at risk or off track. Then give one sentence on why, and what would change it. "At risk. Launch holds if finance confirms the refund policy by Friday" tells the reader what's wrong and what fixes it.

The callout colour helps a skimming reader: green for on track, yellow for at risk, red for off track. If the status changed since last week, say so. A reader who saw green last Friday may not notice it's now yellow.

Done this week

List outcomes, not activity. "Redirects for 180 old URLs written and tested" is an outcome. "Worked on redirects" is activity, and the reader can't tell how far along it is. Keep it to three to six items and leave out small tasks nobody outside the team cares about.

Next week

What the team will finish next week, with a name in brackets after each item. The reader will want to know who to ask, and next week's update checks these items off. If an item from last week's "next week" list didn't get done, it either appears here again or goes under risks with a reason.

Risks

Things that might go wrong, with what happens if they do. "Payment provider hasn't answered" is a worry. "If the payment provider hasn't confirmed the API limits by 6 November, card updates slip three weeks" is a risk the reader can do something about. Name the date it becomes a problem and the cost if it does.

Asks

This is the section people act on. Put a name first, say exactly what you need and give a date. "Rachel: can you ask Daniel in finance to confirm the refund policy by Friday 30 October?" works. "We need input from finance" will sit unread. If you have no asks this week, write "None" so the reader knows you checked.

Numbers

Two or three figures that show progress against the plan, such as work items done out of the total, budget spent against the total and days to the deadline. Keep the same numbers every week. A number without its total ("62 articles migrated") is hard to judge. "180 of 240" isn't. If the project exists to move one of the team's OKRs, add that key result's current value next to its target. Our guide to OKR examples for small teams shows how to write key results with a start and a target.

A complete example

The company, the people, the dates and the numbers below are invented. Spokewhistle is a small online bike parts shop moving its help centre to a new tool. The old help centre has 240 articles. Hannah Moss leads the project and writes the update every Friday. Owen Clarke writes and edits the help articles, Lukas Brandt does the technical work and Ines Duarte does design. The update goes to Rachel Lowe, head of customer support, who sponsors the project. Launch is planned for Monday 16 November 2026.

Status: help centre migration, week of 19 October 2026

Overall: at risk, down from on track last week. Launch on Monday 16 November holds if finance confirms the new refund policy by Friday 30 October. The 40 billing articles can't be finished until it does.

Done this week

  • 62 articles migrated, edited and checked, bringing the total to 180 of 240
  • Redirects from the old URLs written and tested for all 180 migrated articles
  • Search tested with the 20 most common support questions. 17 found the right article first time. The other 3 now have extra keywords

Next week

  • Migrate the remaining 20 general articles (Owen)
  • Set up the redirect for every old category page (Lukas)
  • Final design of the search results page (Ines)

Risks

  • The refund policy is still with finance. Owen needs a week to rewrite the 40 billing articles once he has it, and the week before launch is for final checks. Each day the policy arrives after Friday 30 October moves launch back a day.
  • The contract for the old help centre renews on 30 November. If launch slips past that date, we pay another month, €450.

Asks

  • Rachel: can you ask Daniel Price in finance to confirm the refund policy by Friday 30 October?

Numbers

  • Articles migrated: 180 of 240 (75%)
  • Budget used: €6,300 of €9,000 (70%)
  • Days to launch: 24

Why this example works

The status line names the one thing that decides the launch date and when it's needed. The ask repeats that date and names a person, so Rachel knows what to do. The second risk puts a price on a slip. The numbers add up: 240 articles minus the 180 done leaves 60, the 20 general articles for next week plus the 40 billing articles waiting on finance. And it says the status changed since last week, and why.

Common mistakes

Green until it's red. A project that reports on track every week and then misses its date by a month has been hiding the problem. Move to at risk as soon as you see it, while the reader still has time to help.

A diary instead of an update. Long lists of meetings held and tasks worked on bury the two lines that matter. If the reader has to dig for the status, they stop reading.

Asks without a name or a date. "We need a decision on the budget" gets nobody to decide. Name the person and the day.

A new format every week. Readers learn where to look. Keep the sections and the numbers in the same order so a change stands out.

Writing it for the team. Ticket numbers and internal abbreviations mean nothing to someone outside the project.

Where the update gets its material

If your team keeps daily standup notes, skim the week's pages first. They show what got finished and which blockers are still open.

Decisions and actions from the week's project meeting go straight into "done" and "next week" if the meeting has minutes. Our guide on how to write meeting minutes shows a format that records every decision and owner, so you can copy them across. A written update also answers the "where are we on X?" questions that would otherwise fill your one-on-ones. The guide to one-on-one meeting questions covers what to use that time for instead.

Writing it in Prompt Notebook

Prompt Notebook is ours, so read this part with that in mind. The weekly status update template opens with a coloured status callout, then Done this week, Next week, Risks, Asks and Numbers, filled in with a sample update for an invented customer portal project. Change the callout colour to match your status. Use @ to link the pages your reader needs, such as the meeting minutes or the plan. Once the first update looks right, save it as a template and create each week's update as a sub-page of the project page, so the whole series sits in one place.

Frequently asked questions

How long should a weekly status update be?

Short enough to fit on one screen. Aim for 150 to 300 words. If it runs longer, move the detail to a linked page and keep the link.

Who should get the weekly status update?

Everyone who needs to know where the project stands but isn't in its meetings: your manager, the sponsor, the client, teams that depend on your work. The project team can read it too, but don't write it for them.

What is the difference between a status update and a status report?

The terms overlap. A status update usually means the short weekly note described here. A status report is often longer and more formal, sent monthly or at a project milestone, with a fuller look at budget, schedule and scope. You can send both: the weekly update for the people who need to act, and a monthly report for a wider audience.

Should I send it by email or as a shared page?

Either works if people read it. A shared page keeps every week in one place and lets you link to the work. You can still post the link in email or chat so it arrives where your readers already look.

What if nothing changed this week?

Send it anyway, and say so. "No change. Still on track for 16 November. No asks" takes ten seconds to read and tells the reader nothing has gone wrong. A missing update makes people wonder.

Try it on your own notes

Prompt Notebook is free, with unlimited pages. Type one sentence and the AI drafts the first version.

Cookies and storage

Prompt Notebook needs one cookie to keep you signed in. Accepting turns on Google Analytics and Google's reCAPTCHA spam check on the contact form, and declining keeps the form working. Nothing optional runs until you choose.

Read the privacy notice