Planning & operations

Messy Week → Status Report

The problem

Writing the weekly update takes 45 minutes of reconstructing what happened, and it still reads like a list of activity rather than progress.

Who it's for: Managers, Freelancers, Consultants, Team leads
What it produces: A stakeholder-appropriate update: progress against goals, risks, decisions needed, and next week's focus.
What you need: Your task list, calendar or commits from the week; Last week's report; Who the report is for
Tools: ChatGPT · Claude · Notion
Level: Starter
Format: 5 steps · Starter

The workflow — 5 steps

Step 1

Dump raw activity without editing

Paste calendar entries, tickets, commits and notes unfiltered. Editing while you gather is what makes this take 45 minutes.

Here is my unfiltered activity for the week. Group it into themes and separate ACTIVITY (things I did) from OUTCOMES (things that changed as a result). Flag anything that looks like busywork with no outcome.

ACTIVITY:
"""
{paste}
"""

Step 2

Map outcomes to the goals that matter

Give the model the quarter's goals and have it map each outcome to one. Anything that maps to nothing is a signal worth reading.

My goals this quarter are: {goals}. Map each outcome to the goal it advanced, and rate the advance as significant / incremental / none. List separately anything that advanced no stated goal.

Step 3

Surface risks honestly

Ask for what slipped and why, as a separate step. Status reports that hide slippage cost more later than they save now.

Based on last week's report versus this week's outcomes, list what slipped, by how much, and the most likely cause. For each, give one sentence on impact if it slips again next week. Do not soften.

Step 4

Write for the specific reader

Same facts, different report. An executive wants decisions and risk; a peer team wants dependencies. State the reader explicitly.

Write the update for {reader}. Under 250 words. Sections: Progress (against goals, not activity), Risks, Decisions I need from you, Next week. Lead with the thing this reader most needs to know.

Step 5
Keep a rolling memory
Append each report to one running document and feed the last two in as context. The reports get faster and the trend becomes visible.
```
Compare the last three weekly reports. What is trending up, what is trending down, and what problem keeps appearing without being resolved?
```

What changes when you run it

Before

45 minutes reconstructing the week; a bulleted list of 14 activities with no visible progress.

After

A 220-word update tied to three quarterly goals, two named risks, one explicit decision request. Eight minutes.

Free prompts used in this workflow

Prompts are the ingredients; this workflow is the recipe. Each of these is free to copy.

Browse the full free prompt library →

This one is free — the system isn't just this

All 12 workflows, including the 7 Pro workflows in full
The complete 120-page AI Productivity Playbook
Reusable workflow templates and worked examples
The Notion Workflow Hub — duplicate it into your own Notion
Written Zapier and Make automation recipes

Get the AI Workflow System