What a good weekly report includes
The weekly report is the most-sent and most-padded document in working life, so the best advice is subtractive: Completed, In progress, Blockers is the whole spine, and half a page is the whole budget. Detail belongs in the monthly; the weekly is a pulse.
| Section | What earns a line | What doesn’t |
|---|---|---|
| Completed | Done things, with the outcome where it matters | Activity (“worked on…”) |
| In progress | Where it stands + expected done | Everything merely open |
| Blockers | What’s stuck + what would unblock it + who from | Complaints without asks; and if none, say “none” |
| Numbers (optional) | Up to 3 metrics, each vs last week | Dashboards in prose |
| Next week | The 2-3 things that will be true by Friday | A to-do list |
How to write a weekly status report in minutes
The trick is realising the report is already written; it is just scattered. Your sent messages know what shipped, your board knows what moved, your calendar knows what happened. Writing the weekly is a collection job, not a composition job: scan the week’s trail, sort it into the spine, translate activity into outcomes, and attach an ask to anything stuck.
Ten minutes if you do it while Friday is still describable; an hour of reconstruction if you leave it until Monday, which is why the recurring chore deserves automating more than almost any document on this site.
Weekly report example (filled in)
WEEKLY REPORT · Femi / studio · Week of 13 July For: Aldgate & Co COMPLETED - Checkout fix shipped Tues; failed-payment emails stopped - Autumn range photography brief signed off - Invoice run done; two overdue accounts chased IN PROGRESS - Landing page build → copy in, design QA Mon → done Wed - Supplier renegotiation → two quotes in, one to come → next week BLOCKERS - Product photography approval: with your team 9 days. Unblock: sign-off from Dana by Tue or the print date slips. NUMBERS Orders: 214 (vs 189) · Refund rate: 1.1% (vs 2.4%) NEXT WEEK - Landing page live by Wed - Supplier decision made and communicated
Free weekly report template (plain text, Google Docs, Notion)
Three ways to Friday’s half-page. The plain text pastes cleanly into Google Docs or Notion and reuses week after week.
The plain-text template
The Completed / In progress / Blockers spine, deliberately short.
WEEKLY REPORT · [Name / team] · Week of [date] For: [boss / client / team] COMPLETED - [Done thing, with the outcome where it matters] - … IN PROGRESS - [Thing] → [where it stands] → [expected done] - … BLOCKERS - [What’s stuck] → [what would unblock it, and who from] (None? Say “none”. The empty section is information too.) NUMBERS (optional, 3 max) [Metric]: [this week] (vs [last week]) NEXT WEEK - [The 2-3 things that will be true by next Friday] Keep it to half a page. The weekly is a pulse, not a chronicle.
The AI prompt
Prefer to use your own AI? Copy this into Claude or ChatGPT with the week’s raw notes, and it sorts them into the spine.
---
title: Weekly Report Generator
description: A prompt that turns your week’s notes and messages into a short Completed / In progress / Blockers report.
author: readywhen
source: https://readywhen.ai/weekly-report-template
homepage: https://readywhen.ai
license: CC BY 4.0 (free to use and share with attribution to readywhen)
version: 1.0
updated: 2026-07-18
keywords: [weekly report template, weekly status report, weekly update, end of week report]
---
# Weekly Report Generator
_By readywhen. Full guide + free template: https://readywhen.ai/weekly-report-template_
You are turning a week’s worth of raw material (messages, notes, a task list) into a short weekly report.
## Principles
- Completed / In progress / Blockers is the spine. Resist adding sections; the weekly is a pulse, not a chronicle.
- Half a page. If the reader wants more, they’ll ask, and that’s the report working.
- Completed items carry outcomes where they matter ("shipped the checkout fix; refund emails stopped"), not activity ("worked on checkout").
- Every blocker names what would unblock it and who from. A blocker without an ask is a complaint.
- If a section is empty, say "none". The empty section is information too.
- Numbers: three at most, each with last week’s value for contrast.
## What I need from you
Who the report is for · paste the raw material: messages, task list, notes, calendar highlights from the week · anything you know is stuck. I’ll sort it into the spine and cut the noise.
---
_Made by readywhen. readywhen writes the weekly from what actually happened in your tools, every Friday, so the recurring chore stops recurring. https://readywhen.ai/weekly-report-template_
Let readywhen do itRecommended
The template shortens one Friday; it can’t end the recurrence. readywhen writes the weekly from what actually happened in your tools, every week, waiting before your usual send time.
The week already wrote itself into your tools. readywhen sorts it into the report in ~45 seconds every Friday, and the 3:30pm dread retires.
Watch readywhen draft your weekly from Slack, Notion and your calendar
The pain of the weekly is not any single Friday, it is every Friday. A template shortens the writing; it cannot end the recurrence. readywhen can, because the raw material is already in your tools: it scans the week’s channels and threads for what shipped, checks the board for what moved, notices what has quietly stopped moving and turns it into a blocker with the ask attached, and has the half-page waiting before your usual send time. Same format every week, real contents every week, and the chore stops being yours.
Works with your existing tools
See all 100+ connectorsWeekly report FAQs
What should a weekly report include?
Three core sections: Completed (with outcomes), In progress (with where it stands and expected done), and Blockers (with what would unblock each and who from), plus optionally up to three numbers and a short next-week list. Half a page total.
How long should a weekly report be?
Half a page. The weekly is a pulse; if the reader wants more depth they will ask, and that is the report doing its job. Overloaded weeklies stop being read within a month, which defeats the entire cadence.
What is the difference between a weekly report and a project status report?
Scope and formality. The weekly covers a person or small team’s whole week in three sections. A project status report covers one project for stakeholders, with RAG health, milestones, budget and risks. Many owners send both: the weekly to the team, the status report to the client.
Should I send a weekly report if nothing got blocked?
Yes, and write “Blockers: none” explicitly. The empty section is information: it tells the reader nothing needs them this week, which is exactly what a status cadence exists to establish.
Is there a weekly report template for Google Docs or Word?
Yes. Copy the plain-text template on this page into Google Docs, Word or Notion, or download it as a file. All formats are free.
Can’t I just use ChatGPT or Claude to write my weekly report?
Yes. Paste the week’s notes and the prompt above, and it sorts them into the spine. readywhen is the version that gathers the week itself, from your channels, board and calendar, every Friday, which matters because the real cost of the weekly is not one report, it is fifty-two of them.
More templates for reporting on a cadence
Project status report
RAG health, milestones and risks, assembled from your project tools.
Board report
The monthly pack: numbers, narrative and asks, drafted from your tools.
Team meeting agenda
Next week’s agenda, pre-filled with carried-over actions and open decisions.
Retire the Friday 3:30 dread.
Get your weekly free with readywhen
About the author and editorial standards
About the author. Sançar Şahin is co-founder and CMO of readywhen. readywhen catches everything you say you’ll do and helps you move it forward: drafted, chased or flagged, ready when you are. He builds readywhen in public on LinkedIn.
Editorial standards. No paid placements. The Completed / In progress / Blockers convention reflects common team-reporting practice rather than a single authority. How this page was made: Sançar built the multi-agent research and drafting system behind it, checks its work at several phases, and approves the final page himself. To flag an error, email hello@readywhen.ai.
Last updated: 19 July 2026.