Write a weekly status report for leadership from team updates
What this does
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.
On this page
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.
Saves about 30 to 45 minutes per weekly report

From my practice
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.
What to have ready
- 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 themSay 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.
Build your prompt
- 1. Gather your inputsHave the items above to hand.
- 2. Fill in the formYour prompt updates as you type.
- 3. Copy or open in your AIClaude, ChatGPT or Gemini.
- 4. Review before you sendCheck it against your notes.
Your prompt · 0 of 7 filled
Gemini cannot be filled from a link, so the prompt is copied first. Paste it with Ctrl+V or Cmd+V.
Use it as a skill
Add this playbook to your assistant once, then ask for it by name.
How to install
- Claude: download the zip and upload it as is under Settings, Capabilities, Skills.
- Other assistants: open SKILL.md, copy it, and paste it into the assistant's custom instructions or project.
- Ask for the playbook by its task, and give it your details when it asks.
The skill is plain text with no scripts, links or commands. Read SKILL.md before you install it, and use a company-approved AI workspace. Need help setting it up? Book a call.
See a real result
Sample input: Dispatch and Warehouse Operations, Pune · Monday 9 November to Friday 13 November 2026 · Managing director Sunil Rao and the finance head…
Monday 9 to Friday 13 November 2026
1. HeadlineThe backlog of 40 pending orders was cleared by Wednesday, and the Zone B count is 6 of 12 aisles done. Dispatch within 24 hours fell to 86 per cent against a target of at least 90, and Shree Logistics pickups were late twice.
2. Progress against goals- Dispatch within 24 hours (target at least 90%): Off track (my reading). 86% this week, 92% last week. That is 4 points below target (90 − 86 = 4). Late Shree Logistics pickups on Tuesday and Thursday were reported, but the notes do not say they caused the drop.
- Zone B stock count by 20 November: At risk (my reading). 6 of 12 aisles done, so 6 remain (12 − 6 = 6). Two aisles have mismatched stock, still being checked.
- Damaged-goods claims under 5 for the month: At risk (my reading). 3 claims this week, 2 from one pallet type. The month-to-date total is not given. If none were raised earlier this month, only 1 more claim fits under the limit (4 − 3 = 1).
- Shree Logistics late pickups, no new slot agreed. Impact: not stated. Owner: not named. Action: not stated.
- Barcode scanners promised for 16 November, vendor not confirmed. Impact: not stated. Owner: not named. Action: not stated.
- Damaged goods from one pallet type (2 of 3 claims). Owner: Imran. Action: packing team briefed on the new wrapping method.
- Approve 2 temporary packers for year-end orders. Requested by Imran. Decision maker: not named. Date: not given.
- Finish the Zone B count by 20 November and resolve the 2 mismatched aisles. Owner: not named.
- Agree a new pickup slot with Shree Logistics. Owner: not named.
- Bring dispatch within 24 hours back to at least 90 per cent. Owner: not named.
- Get the vendor's confirmation on the scanners due 16 November. Owner: not named.
- Keep damaged-goods claims under 5 for the month. Owner: not named.
Assumptions I made
- Statuses for all three goals are my reading. Your notes give none.
- I treated "under 5" as 4 or fewer claims.
- I assumed no damaged-goods claims were raised earlier in November. This only affects the "1 more claim" line.
- I treated the 90 per cent target as applying to each week.
- Next week's focus items are drawn from open issues and last week's priorities. Your notes do not list them.
- I assumed Zone B's 6 completed aisles may or may not include the 2 mismatched aisles. The notes do not say.
Unclear or conflicting updates
- Conflicts: none found.
- Unclear: whether the late pickups caused the 86 per cent figure. I did not link them.
- Unclear: the month-to-date damaged-goods count.
- Unclear: how many Zone B aisles are verified, given the 2 mismatches.
Goals with no update
- None. The damaged-goods goal has only a weekly figure, not a month total.
Blockers or decisions with no owner or date
- Shree Logistics pickups: no owner, no action stated, no date for a new slot.
- Barcode scanners: no owner, no action stated. The vendor date of 16 November is unconfirmed.
- Temporary packers: no decision maker and no date.
- All five next-week items have no named owner. Meena, Ravi and Imran each gave related updates, but your notes do not name them as owners.
The 40-order backlog was cleared by Wednesday, but dispatch within 24 hours fell below target. Zone B is half counted, while pickup arrangements and scanner delivery remain unresolved.
Dispatch and Warehouse Operations, Pune
Reporting period: Monday 9 November–Friday 13 November 2026
- 24-hour dispatch — Off track (my reading): 86 per cent against a target of at least 90 per cent; last week was 92 per cent.
- Zone B count — On track (my reading): 6 of 12 aisles counted towards the 20 November deadline; two aisles have mismatches still being checked.
- Damaged-goods claims — At risk (my reading): 3 claims this week against a monthly limit of under 5; the month-to-date total is not provided.
- Shree Logistics: Late pickups on Tuesday and Thursday; no new slot agreed. Dispatch impact is not specified. Owner and resolution date are not stated.
- Barcode scanners: Promised for 16 November, but the vendor has not confirmed. Operational impact, follow-up action and owner are not stated.
- Stock mismatches: Two Zone B aisles remain under checking. Deadline impact and owner are not stated.
- Damaged goods: Two of this week’s claims came from one pallet type. The packing team was briefed on a new wrapping method. Follow-up owner and date are not stated.
- Approve hiring 2 temporary packers for year-end orders, as requested by Imran. Decision-maker and deadline are not stated.
Proposed from the outstanding work; owners are not explicitly assigned.
- Improve 24-hour dispatch performance and agree the Shree Logistics pickup slot.
- Complete the Zone B count by 20 November and resolve stock mismatches.
- Confirm scanner delivery.
- Review damaged-goods claims and the wrapping-method briefing.
- Obtain a decision on Imran’s temporary-packer request.
Assumptions and judgements
- Dispatch is judged Off track because 86 per cent is below target.
- Zone B is judged On track based on half the count being complete; the notes do not confirm that the remaining work can finish by 20 November.
- Claims are judged At risk because 3 were raised this week against a monthly limit of under 5. This does not establish the actual monthly status.
- Next week’s focus is proposed from open work, not a confirmed team commitment.
Unclear updates
- Month-to-date damaged-goods claims are missing.
- The effect of late pickups on dispatch performance is not stated.
- The scanner delay’s operational impact is not stated.
- The effect of stock mismatches on the count deadline is not stated.
Conflicting updates
- None.
Goals with no update
- None. The claims goal has a weekly update, but no monthly total.
Blockers or decisions missing an owner or date
- Shree Logistics pickup issue: no assigned owner or resolution date.
- Scanner confirmation: no assigned follow-up owner or confirmation deadline; the promised delivery date is 16 November.
- Stock-mismatch checks: no assigned owner or resolution date; the overall count deadline is 20 November.
- Damaged-goods follow-up: no assigned owner or date.
- Temporary-packer approval: Imran is the requester; no decision-maker or decision deadline is stated.
Was this playbook helpful?
Want this set up for your team?
I can fit this playbook into your CRM, helpdesk or inbox and train your team to use it.
Book a 30-minute reviewReview before you send
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.
Tips for your industry
This playbook works for any business. These notes help you adapt it.
Updates usually mix output, quality and maintenance items. List them as separate goals so a machine breakdown does not bury a quality result.
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.
Updates are often about client deliverables. Use project names and deadlines as the goals, and keep client-sensitive detail out of the pasted text.
Questions people ask
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.
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.
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.
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.
Last checked · Updated