Weekly status report template: what to include, with examples

What should a weekly status report template include?

Copy this into a doc, an email or a Slack post and replace the brackets:

Weekly status report: [team or project], week of [date]

Summary (2 sentences): [overall health: on track / at risk / off track] and the one thing a reader must know.

Shipped this week
- [outcome, past tense, with a link]
- [outcome]

In progress (with dates)
- [item]: [what is left], expected [date], owner [name]

Blocked or at risk
- [item]: waiting on [person or decision], needed by [date]

Decisions or help needed
- [the specific ask, and from whom]

Numbers (this week vs last week)
- [metric]: [value] (last week [value])

Next week
- [top 3 priorities]

Each section earns its place. The summary is for readers who stop after two lines. "Shipped" proves progress. Dates on in-progress items turn vague statuses into commitments you can check next week. "Blocked" is the section that saves projects, because it names who has to act. "Decisions or help needed" is the only part that asks the reader to do something, so keep it specific. Numbers with last week's value beside them show a trend, which a single snapshot cannot.

What does a good weekly status report look like?

Three short examples, with invented placeholder details, show the same template in different teams.

Product team lead to a founder:

Summary: On track for the November release. One risk: the billing migration depends on a vendor reply.
Shipped: new onboarding checklist (live to all users); fixed CSV export timeout.
In progress: billing migration, 60% of accounts moved, rest expected Thu, owner Priya.
Blocked: tax settings, waiting on the vendor's API key, needed by Wed.
Help needed: approve the revised pricing page copy by Tue.
Numbers: signups 212 (last week 190); open bugs 14 (last week 19).
Next week: finish migration, release notes, start usage analytics.

Agency account lead, internal update:

Summary: Two of three clients on track. Client B campaign launch slipped one week.
Shipped: Client A landing page; Client C October report sent.
In progress: Client B ads, creative in review, launch moved to Nov 6, owner Sam.
Blocked: Client B needs final logo files from their team.
Decisions needed: agree whether to bill Client B for the extra revision round.
Next week: Client B launch, Client A A/B test readout.

Operations lead:

Summary: Hiring and payroll on schedule; laptop orders delayed.
Shipped: payroll run completed; new expense policy published.
In progress: two offers out, answers expected Fri, owner Dana.
Blocked: laptop order backordered, supplier ETA Nov 10.
Numbers: open roles 3 (last week 4).

What are the most common weekly report mistakes?

• Activity instead of outcomes. "Worked on the migration" tells the reader nothing. "Moved 60% of accounts, the rest by Thursday" does.
• One section per person. Five mini-reports stapled together are hard to scan. Group by project or outcome and put the owner on each line.
• No dates. An in-progress item without a date cannot slip, so nobody notices when it does.
• Hiding the blocker. If something has slipped twice, move it to Blocked and name what it waits on.
• Changing the format every week. Readers learn where to look. Keep the sections fixed and put extra detail in a linked doc.
• Too long. If it does not fit on one screen, most people skim the summary and stop.

How do you collect weekly updates without chasing people?

Most of the effort in a weekly report is gathering inputs, not writing. Three approaches work for small teams:

1. A shared tracker. Keep one sheet with item, owner, status, date and last update, and set the expectation that it is current by Thursday. The report becomes a copy of the sheet's changes. Our guide to posting weekly KPIs from Google Sheets to Slack covers the numbers section.
2. A check-in bot or a Workflow Builder form. Ask each person the same three questions on Thursday and collect answers in one thread. Standup tools such as Geekbot do this; see AI tools for Slack standups and status updates.
3. Drafting from the tools themselves. If the work already lives in Linear, GitHub, Jira or Google Sheets, a draft can be assembled from what changed, and the team lead edits instead of starting from a blank page. How to automate weekly status reports in Slack compares Workflow Builder, ChatGPT and an AI coworker for this.

How is an internal weekly report different from a client status update?

An internal report can name blockers inside the team, show rough numbers and ask for decisions from a manager. A client update leads with progress against what was agreed, frames blockers as what the client needs to provide, and avoids internal debates. If you send both, write the internal one first and derive the client version from it. We keep separate copy-ready versions: the client status update template and the weekly client report template, plus a free weekly client report generator.

Can an AI coworker draft the weekly status report for you?

Yes, if the inputs are in tools it can read. Geniusly is an AI coworker for your team in Slack. It reads the accounts you connect (Gmail, Google Drive, Google Sheets, Slack, GitHub, Linear, and Google Ads) and prepares a brief, report, status update, or handoff for a person to review. Connected apps are read-only by default, except Google Sheets edits you explicitly ask for, and Slack messages beyond its reply are posted only after your approval. Anyone in a channel it has been invited to can ask it for work, it can run a task once, daily, or weekly, and it has a Free plan.

A typical request is "Every Friday at 3 PM, draft this week's status report for the product team from Linear and GitHub, using our template, and post it here for me to review." You still check the summary, the health call and anything in Blocked before it goes out, because those are judgment calls. See the weekly operations brief use case or get started with Geniusly free.

Frequently asked questions

What is a weekly status report?

A short written update, usually sent at the end of each week, that tells a manager, team or stakeholders what was completed, what is in progress, what is blocked and what help is needed. It replaces or shortens a status meeting.

How long should a weekly status report be?

One screen. A two-sentence summary plus five short sections is enough for most teams. Put extra detail in a linked doc or tracker instead of the report.

Should a weekly status report use red, amber and green?

A single overall health call at the top (on track, at risk or off track) is useful. Color-coding every line tends to start arguments about what amber means, so many teams use shipped, in progress and blocked instead.

What is the difference between a weekly status report and an end-of-day report?

An end-of-day report covers one person's day and is mostly for the immediate team. A weekly status report covers a team or project, rolls up a full week, and is written for a manager or stakeholders.

Who should write the weekly status report?

The team lead or project owner, using inputs from the people doing the work. If inputs come from a shared tracker or the tools themselves, writing it takes minutes instead of an afternoon.

Can I send the weekly status report in Slack instead of email?

Yes. Post it in a fixed channel at the same time each week, pin the template, and keep follow-up discussion in the thread so the decisions stay attached to the report.