---
name: weekly-status-report-from-updates
description: Turns a team's weekly updates, goals and blockers into a one-page status report for leadership. Use when asked to write or draft a weekly status report that must report only what the updates say.
---

# Weekly status report from team updates

## When to use
Use this skill when a manager or team lead wants a weekly report for leadership and has raw material: bullets, chat messages, goals and blockers. It suits operations, project and support teams. Do not use it to invent progress, to report on a team with no updates, or to write about performance reviews or individual staff issues.

## What to ask for
Ask for each item below. If the user has not given one, ask for it before writing. If they have nothing for an item, record it as 'none provided'.
- Team name and the reporting period (dates).
- Who reads the report and how they like it (length, phone reading, headline first).
- Goals or KPIs for the period, with targets where they exist, and whether each goal is weekly, monthly or quarterly.
- A running total for any monthly or quarterly goal, if the user has one.
- Last week's priorities, if available.
- The raw team updates, pasted as they are.
- Blockers, open issues and anything needed from leadership, with owners and dates if known.

If the updates contain customer personal data or staff personal details, tell the user to remove them first, unless the report truly needs them.

## Steps
1. Read all the updates once. Note which goals each update relates to.
2. Match every goal to the updates. If a goal has no matching update, mark it 'No update'.
3. Set each status from what the updates say. On track: the figures meet the target or the work is on schedule. At risk: behind, but the target or deadline can still be met. Off track: the figures miss the target or the deadline will be missed. No update: nothing reported. If you have to judge it yourself, add '(my reading)'.
4. For a monthly or quarterly goal with no running total, report the week's figure and add 'period total not given' to the check section.
5. List risks and blockers with impact, owner and action, only where the updates give them. Do not link two updates as cause and effect unless someone said so.
6. List decisions needed: the decision, who decides, and by when. If the owner or date is missing, say so in the check section.
7. Draft next week's focus with up to five items taken from the updates and blockers only. Name an owner only if the updates name one. Do not add items to reach a number.
8. Write the headline last: two plain sentences on where the team stands.
9. Compile the check section: assumptions, conflicting or unclear updates, goals without updates or period totals, and blockers or decisions without an owner or date.

## Output format
Give the report in this order, in no more than 350 words, using short sentences and no extra header block:

```text
Weekly status report: <team>, <period>

Headline
<two sentences>

Progress against goals
- <goal>: <status>. <figure or fact from the updates>. <short reason, if stated>.

Risks and blockers
- <risk>: impact, owner, action under way.

Decisions needed
- <decision>: from <who>, by <date>.

Next week's focus
- <item> (owner, if named)

Check before sending
Assumptions: ...
Conflicting or unclear updates: ...
Goals with no update or no period total: ...
Blockers or decisions missing an owner or date: ...
```

Write 'None' under any check line that is empty.

## Quality check
Before replying, confirm that:
- Every figure and fact traces back to the user's input.
- Every goal has a line and a status that matches the figures.
- No cause or explanation appears that no one stated.
- New figures appear only where simple arithmetic was possible, with the working shown.
- Conflicting updates are listed, not settled.
- Next week's focus holds nothing the user did not mention.
- The report fits on one page and the headline stands on its own.

## Watch-outs
- Do not fill gaps with likely reasons or invented dates. Write 'No update' or 'not stated'.
- Do not make the week sound better or worse than the updates do. Keep status labels honest.
- Keep names, product names and figures exactly as the user wrote them.
- Remind the user that a person must read the report against the source updates before it goes to leadership.
- If the updates hold sensitive personal or commercial details, suggest removing them or using the company's approved workspace.
