Resource
Weekly Report Template for Work
Copy a weekly report template for outcomes, metrics, blockers, next steps, and AI-assisted work summaries.
- Focus
- AI Spreadsheets Reporting
A weekly report template should explain what changed, what is blocked, and what happens next.
Most weekly reports fail because they list activity instead of outcomes. AI can help draft the report, but it should not decide what was important or invent progress from vague notes.
Use this weekly report template when you need a clear update for a manager, client, project team, or remote stakeholder.
Weekly report template
Weekly report: [team/project/name]
Period: [start date] - [end date]
Report owner: [name]
Summary:
[Write 3-5 sentences: what changed, what moved forward, what is blocked, and what needs attention.]
Outcomes this week:
- [Outcome 1, tied to a result or deliverable.]
- [Outcome 2, tied to a result or deliverable.]
- [Outcome 3, tied to a result or deliverable.]
Key metrics:
- [Metric]: [value] ([change vs last week, if useful])
- [Metric]: [value] ([change vs last week, if useful])
Blockers and risks:
- [Blocker/risk]: [owner, impact, next step]
Next week priorities:
- [Priority 1]
- [Priority 2]
- [Priority 3]
Asks or decisions needed:
- [Decision, approval, review, or dependency needed.]
Source notes:
- [Task list, meeting recap, dashboard, or spreadsheet link used to build this report.]The "source notes" field matters. It keeps the report tied to real work instead of becoming a polished story with no evidence.
What to include
| Section | Include | Avoid |
|---|---|---|
| Summary | Outcome, risk, next action | A generic "busy week" paragraph |
| Outcomes | Completed deliverables or decisions | Every small task you touched |
| Metrics | Numbers someone can verify | AI-estimated metrics |
| Blockers | Owner, impact, next step | Vague complaints |
| Next week | Three priorities maximum | A long wish list |
AI drafting prompt
Use this prompt after you gather tasks, meeting notes, and metrics.
Draft a weekly report from the source notes below.
Rules:
- Do not invent completed work.
- Do not invent metrics.
- Separate outcomes from activity.
- Make blockers visible instead of softening them.
- Keep the summary under five sentences.
- If a fact is unclear, mark it as "needs confirmation."
Return this format:
Summary
Outcomes this week
Key metrics
Blockers and risks
Next week priorities
Asks or decisions needed
Source notes:
[paste tasks, meeting notes, and metrics here]This works best when the source notes are structured. If you paste a messy task dump into AI, you usually get a cleaner task dump back.
Short stakeholder version
Use this when the reader only needs the decision-level version.
Weekly update: [project/team]
What changed:
[One or two sentences.]
Done this week:
- [Outcome 1]
- [Outcome 2]
Blocked:
- [Blocker, owner, impact]
Next week:
- [Priority 1]
- [Priority 2]
Decision needed:
- [Decision or approval needed, if any.]This version is better for busy stakeholders. If someone needs detail, link to the longer report or spreadsheet.
Review checklist
Before sending the weekly report:
- Remove tasks that did not change an outcome.
- Confirm metrics against the source spreadsheet or dashboard.
- Name blockers plainly.
- Limit next-week priorities to three.
- Add an ask only when someone needs to make a decision.
- Keep the report shorter than the notes used to draft it.
Best next step
Use automate weekly report with AI when you want to turn this template into a repeatable workflow. If your report starts from spreadsheet rows, use the Google Sheets AI reporting workflow. For a shorter async update, copy the weekly status update template.