How to write a weekly status update
A weekly status update should tell a busy reader what moved, what is stuck, and what you need — without a chronology of the week.
Goal
The reader should finish the note able to act. Give them three answers, in this order:
- What is the status in one sentence (on track, at risk, or blocked).
- What actually moved, slipped, or changed.
- What you need from them, if anything — a decision, a review, or nothing.
Include outcomes, dates, and blockers that affect someone else. Cut the play-by-play, the full backlog, and work that did not change the plan.
One screen on a phone is enough for most weeks. A second screen usually means you are writing a report.
Method
The week was busy, so the first draft tries to prove that. Remembering what happened is easy. Choosing what the reader must know is the work.
Keep a stable format:
- One-line status
- What moved (three items or fewer)
- Risks / blockers
- Ask, or “no ask this week”
That is the skeleton. The writing pattern depends on how much context the reader is missing.
If they already sit in the same project, lead with the point. If this week's status only makes sense after a change — a slipped dependency, a new constraint, a decision that reversed last week — set the situation first, then the ask.
Keep those two shapes in separate paragraphs. Either the point can stand alone, or it cannot.
Steps
1. Dump, then cut
List everything that happened. Keep only items that change a date, a risk, or a decision. Everything else is optional color.
2. Write the one-line status before the rest
Useful shapes: “On track for Friday's beta.” “At risk: design sign-off is still open.” “Blocked on legal until Thursday.” If you cannot write this line, you do not have a status yet.
3. Fill a four-block template
- Status: [on track / at risk / blocked] — [one sentence]
- Moved:
- - [outcome + date]
- - [outcome + date]
- Risks / blockers: [one line, or “none”]
- Need from you: [decision / review / nothing]
4. Choose the writing pattern
If the one-line status is understandable without a backstory, use PREP (point, reason, one example, restated point). If the reader would misread the status without knowing what changed, use SCQA (situation, complication, question, answer). See Frameworks.
5. Send, then stop
Do not attach a second narrative “for context” below the template. If they need the full method, they can ask, or you can link the Library page.
Frameworks
How each framework helps with this problem.
Primary
PREP Framework
State a conclusion first, support it with one reason and one example, and restate the same point so a short spoken answer stays followable.
Alternative
SCQA Framework
Structure a message so the audience gets a shared situation and a real complication before the question and the answer.
Example
Week type: PREP (reader already knows the launch plan)
Status: At risk for Friday's beta — we still need design sign-off on two screens.
Moved:
- Checkout happy path is in QA.
- Error-state copy is drafted; waiting on design.
Risks / blockers: Checkout error state is unsigned. Without it, QA cannot finish.
Need from you: 30 minutes tomorrow morning to close the two screens.
Point: We miss Friday if design does not sign off tomorrow. Reason: two screens are still in review, and QA is gated. Example: the checkout error state. Point: please hold a 30-minute review tomorrow morning.
Week type: SCQA (the plan only makes sense after a change)
Situation: We were targeting Friday's beta with design sign-off by Wednesday. Complication: the payment vendor pushed their sandbox outage into Thursday. Question: do we still hold Friday, or slip QA? Answer: propose slipping the beta to Tuesday so QA has a clean sandbox; need your yes/no by end of day.
The facts could sit in one paragraph. SCQA puts the vendor move before the status line, because the reader cannot use the status until they know that.
Mistakes
- Starting with Monday → Friday chronology
- A task list with no status line
- Hiding the ask in the last sentence of a long paragraph
- Using SCQA every week “to be thorough”
- Using PREP when the reader does not share last week's picture
- Pasting screenshots instead of one proof in the example slot
- Writing to prove effort instead of to change a decision
Next step
Write the one-line status first. If it stands alone, draft the rest as PREP. If it does not, name the change in one sentence and use SCQA. The full patterns are on PREP and SCQA.
Apply this to your own context
Bring your situation into Advisor. It helps you choose a framework and work through the next step.