ChatGPT Prompt to Write a Weekly Status Update for Your Manager
A weekly status update prompt turns a scattered list of tasks, wins, and blockers into a short, readable report your manager can skim in under a minute. It's built for anyone who sends a recurring update — individual contributors, team leads, project managers, freelancers reporting to a client — and who would rather spend five minutes filling in a template than staring at a blank doc every Friday.
The prompt works by asking ChatGPT, Claude, or Gemini to take your raw notes (what you finished, what's in progress, what's blocked, and what's coming next) and reshape them into a consistent structure: a short summary line, grouped accomplishments, open risks, and next week's priorities. Because the structure stays the same every week, your manager starts recognizing the pattern and can spot changes fast, instead of re-reading a wall of unstructured text each time.
If you're not sure how to phrase the raw inputs so the model doesn't flatten everything into generic bullet points, running your draft notes through Prompt Builder first can turn a rough description of your week into a properly structured prompt before you hand it to the model.
Prompt template
Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.
Example input
Example output
Summary: Research and testing wrapped this week; onboarding redesign and vendor contract are the two active threads moving into next week.
Completed
- Finished user research synthesis for the onboarding redesign
- Shipped the pricing page A/B test
- Closed 4 customer feedback tickets
In Progress
- Onboarding redesign wireframes — 60% complete
- Vendor contract review — submitted to legal Monday, awaiting response
Blockers/Risks
- Vendor contract has been with legal for 5 days with no response; this is at risk of delaying the vendor kickoff if not resolved by early next week
Next Week
- Finalize onboarding wireframes
- Present pricing test results to leadership
- Follow up with legal on the contract review
When to use it
- You send a recurring weekly or biweekly status report to a manager, client, or stakeholder group
- You have scattered notes, Slack messages, or a to-do list and need them turned into a coherent summary quickly
- You manage a project with multiple workstreams and need a consistent format that highlights changes week over week
- You want to flag a blocker or risk clearly without burying it under routine updates
Best practices
- Feed the model your actual raw notes (tasks completed, in progress, blocked) rather than asking it to invent content from a vague prompt
- Specify the audience and their technical depth so the model avoids jargon your manager won't recognize or, conversely, over-simplifies for a technical stakeholder
- Ask for a fixed word or bullet-count limit per section so the report stays skimmable instead of growing longer every week
- Always review the output for accuracy before sending — the model can misread vague notes and state a task as 'done' when it was only started
Common mistakes
- Pasting an entire week of Slack messages with no instruction on what to extract, producing a report that's just a reformatted chat log
- Letting the model guess at task status instead of explicitly stating what's done, in progress, or blocked
- Skipping the 'next steps' section, which is usually the part a manager cares about most
- Reusing the exact same prompt every week without updating the context, so the model repeats last week's priorities verbatim
FAQs
How do I write a status update that doesn't sound robotic?
Give the model your actual notes in your own words rather than a generic request, and ask it to keep your tone — it mirrors the phrasing you provide, so vague input produces generic, robotic-sounding output.
Should I use ChatGPT, Claude, or Gemini for a weekly status report?
Any of the three works well for this kind of structured summarization task; the prompt template above is written to work across all three without vendor-specific syntax.
How long should a weekly status update be?
Most managers prefer 150-250 words that can be read in under a minute — set an explicit word limit in the prompt so the model doesn't let the report grow longer each week.
What should I do if I have no progress to report on a task?
State that explicitly in your raw notes (e.g., "no movement this week") rather than omitting it, so the model reports the status accurately instead of guessing or skipping it.
Which Cuelara tool can help me check this prompt's quality before sending it off every week?
Intelligence Score — grades your filled-in prompt for clarity and specificity, which is useful for a recurring report where small ambiguities compound week after week.