---
title: "Write a weekly status report for leadership from team updates"
description: "AI prompt and skill that turn raw team updates, goals and blockers into a one-page weekly status report, with checks before you send."
url: https://atulsingh.co.in/ai-playbooks/weekly-status-report-from-updates
skill: https://atulsingh.co.in/ai-playbooks/weekly-status-report-from-updates/SKILL.md
function: operations
roles: ["Operations manager", "Team lead", "Department head", "Founder or business owner"]
industries: ["manufacturing", "logistics", "professional-services"]
published: 2026-11-14T20:49:16.858+00:00
updated: 2026-11-15T15:16:16.124346+00:00
---

# Write a weekly status report for leadership from team updates

Paste your team's raw weekly updates, goals and blockers into this prompt and get a one-page report for leadership. It covers progress against each goal, risks, decisions needed and next week's focus, using only what the updates say. A 'Check before sending' list shows gaps and conflicts, so you chase only those, check every line against the notes and send it under your name.

**Time saved:** about 30 to 45 minutes per weekly report

## What to gather

- The raw team updates for the week: bullets, chat messages or short emails, pasted as they are.
- The goals or KPIs for the period, with targets where you have them. Say if a goal is monthly or quarterly.
- Last week's stated priorities, so progress can be compared with what was planned.
- Current blockers and open issues, with who owns each one if known.
- Who reads the report and what format they prefer, for example a managing director who reads it on a phone.

## Steps

1. Collect the updates in one place by the end of the working week. Paste them in raw. Do not tidy them first.
2. Remove anything the report does not need, such as customer names, phone numbers, or staff health or pay details. Use your company's approved AI workspace.
3. Fill in the fields in the prompt. If a field has nothing to report, write 'none this week' so the model does not guess.
4. Run the prompt in ChatGPT, Claude or Gemini. Read the 'Check before sending' section first.
5. Ask the team member concerned to fill any gap or settle any conflict the check section lists. Then re-run the prompt or edit by hand.
6. Go through next week's focus line by line. The prompt asks for at least three items, so the model may add some that no one mentioned. Keep only items your team named or agreed, and add owners yourself.
7. Check every status label and every 'because'. If the report links two updates, for example late pickups causing a dispatch drop, keep the link only if a team member said so.
8. Read the report against the original updates. Fix any line you cannot trace back to an update, then send it under your own name.
9. Keep the final report. Next week, its 'Next week's focus' section becomes the 'last week's priorities' field.

## The prompt

```text
You are helping an operations manager write a weekly status report for leadership. Use only the information I provide below. Do not add facts, numbers, reasons or promises that are not in my notes.

Team: {{team_name}}
Reporting period: {{reporting_period}}
Who will read it and how they like it: {{reader_and_format}}

Goals and KPIs for this period:
{{goals_and_kpis}}

Last week's stated priorities:
{{last_week_priorities}}

Team updates (raw bullets and chat messages):
{{team_updates}}

Blockers and open issues:
{{blockers_and_asks}}

Task: Write a one-page report of no more than 350 words with these headings:
1. Headline: two sentences on where the team stands overall.
2. Progress against goals: one line per goal with its status (On track, At risk, Off track or No update), the figure or fact from the updates, and a short reason.
3. Risks and blockers: each with its impact, the owner and the action under way, where my notes say so.
4. Decisions needed: the decision, who must make it and by when.
5. Next week's focus: three to five items, each with an owner if one is named.

Rules:
- Take each status from what the updates say. If you are judging the status yourself, add '(my reading)'.
- If a goal has no update, write 'No update'. Do not guess.
- Do not create new figures. Simple arithmetic on figures I gave is allowed, but show the working in brackets.
- Use short, plain sentences and keep names as written.
- If two updates conflict, do not choose between them. List the conflict in the check section.

After the report, add a section called 'Check before sending'. List every assumption you made, every unclear or conflicting update, every goal with no update, and every blocker or decision with no owner or date. Write 'None' for any list that is empty.
```

### Fill in

- `{{team_name}}`: Name of your team or department (for example: Dispatch and Warehouse Operations, Pune)
- `{{reporting_period}}`: The dates the report covers (for example: Monday 9 November to Friday 13 November 2026)
- `{{reader_and_format}}`: Who reads the report and how they like it (for example: Managing director Sunil Rao and the finance head. They read on their phones and want the headline first.)
- `{{goals_and_kpis}}`: Goals or KPIs for the period, with targets (for example: 1. Dispatch confirmed orders within 24 hours (target: at least 90 per cent of orders).
2. Finish the stock count for Zone B by 20 November.
3. Keep damaged-goods claims under 5 for the month.)
- `{{last_week_priorities}}`: What you said the team would focus on last week (for example: Clear the backlog of 40 pending orders. Start the Zone B stock count. Agree a new pickup slot with Shree Logistics.)
- `{{team_updates}}`: Paste the raw updates from your team (for example: Ravi: backlog cleared by Wednesday. Dispatch within 24 hours was 86 per cent this week, 92 per cent last week. Late pickups by Shree Logistics on Tuesday and Thursday.
Meena: Zone B count is about half done, 6 of 12 aisles. Two aisles had mismatched stock, still being checked.
Imran: 3 damaged-goods claims raised this week, 2 from one pallet type. Packing team briefed on new wrapping method.)
- `{{blockers_and_asks}}`: Blockers, open issues and anything you need from leadership (for example: Shree Logistics pickups are late and no new slot is agreed yet. New barcode scanners were promised for 16 November but the vendor has not confirmed. Imran asks for approval to hire 2 temporary packers for year-end orders.)

## Check the result

- Every figure in the report appears in the updates, goals or blockers you pasted. Nothing is rounded or recalculated without the working shown.
- Every goal you listed has its own line with a status, including 'No update' where the updates were silent.
- Each status label matches the figures. 'Off track' and 'At risk' are confirmed by you, not left as the model's reading.
- Every decision needed names who decides and by when, or the check section flags that this is missing.
- Next week's focus holds only items that your team named or agreed. Delete anything the model added to fill the list.
- No cause or reason is given for a problem unless a team member stated it, including links between two separate updates.
- The report is one page, about 350 words or fewer, with no extra header blocks, and the headline can be read on its own.
- The 'Check before sending' section is present and lists real gaps, or says 'None'.

## Watch out for

- The model may fill a gap with a plausible reason, such as blaming a delay on weather or on another team's problem. Check every 'because' against the updates and delete any that no one said.
- The prompt asks for three to five focus items. When the week was quiet, the model pads the list with sensible-sounding tasks. Cut them back to what your team actually plans.
- Monthly or quarterly goals reported mid-period are easy to misjudge. If you have no running total, give one in the goals field or expect the status to be a guess.
- Vague updates give a vague report. If an update says 'going well', ask the owner for a figure or a fact before sending.
- Status labels can make a week look better or worse than it was. Where the label and the figures disagree, change the label.
- Updates may hold customer names, phone numbers or staff personal details. Remove them or use your approved workspace, in line with India's DPDP Act or GDPR where they apply. This is general guidance, not legal advice.
- Do not paste confidential commercial terms, such as vendor prices, into a tool your company has not approved.
- A person must read and send the report. Leadership acts on it, so someone on your team must stand behind every line.

## Industry notes

- **manufacturing:** Updates usually mix output, quality and maintenance items. List them as separate goals so a machine breakdown does not bury a quality result.
- **logistics:** Delivery and pickup figures change daily. State the period each figure covers, and keep carrier delays and warehouse delays in separate lines so the owner of each is clear.
- **professional-services:** Updates are often about client deliverables. Use project names and deadlines as the goals, and keep client-sensitive detail out of the pasted text.

## Before and after

**Before:** The manager chases updates in chat, copies them into a document and rewrites them in a tone leadership will accept. The report goes out late on Friday evening and varies in shape from week to week.

**After:** The manager pastes the raw updates into the prompt and gets a draft in a fixed format. The check section shows what is missing, so the manager chases only those gaps, trims the focus list, checks the labels and sends a consistent report.

## FAQ

**Can the report be wrong if the updates are wrong?**

Yes. The prompt tells the model to use only what the updates say, so mistakes in the updates pass straight through. The check section flags conflicts and gaps, but the team lead still has to read the report against the source notes.

**Should I let AI decide whether a goal is on track?**

Take the status from the team's own updates where you can. If the model judges it, the prompt makes it add '(my reading)' so you can confirm or change the label. Anything that goes to leadership as 'At risk' or 'Off track' should be confirmed by a person.

**Does this work with updates in WhatsApp or Slack?**

Yes. Copy the messages and paste them as they are. Remove any customer details or private chat that has nothing to do with the report before you paste.

**How do I keep the report the same shape every week?**

Save the filled-in prompt and change only the dates, updates and blockers each week. You can also use the skill version, which holds the format and the rules so you only supply the week's inputs.

## Atul's note

I ask teams to agree one simple shape for their updates: done, in progress, blocked, needs a decision. That makes the AI draft much easier to check. I would rather the report say 'no update' than let AI fill a gap. The team lead should read every line against the source notes before it goes to leadership.

## Tested on

- Claude Sonnet 5.5, 2026-11-14: pass
- GPT-6, 2026-11-14: pass
- Gemini 4, 2026-11-14: fail

[This page](https://atulsingh.co.in/ai-playbooks/weekly-status-report-from-updates) · [Markdown copy](https://atulsingh.co.in/ai-playbooks/weekly-status-report-from-updates.md) · [SKILL.md](https://atulsingh.co.in/ai-playbooks/weekly-status-report-from-updates/SKILL.md)
