It's Friday at 4pm.
You open a blank doc. Subject: "Weekly Status Update." You stare at it. What did you even do this week? Monday feels like a month ago.
So you open Slack. Scroll through channels trying to find evidence of your existence. Check Jira for tickets you closed. Skim your calendar for meetings that might jog your memory. Piece together a narrative about your week that nobody will actually read.
Here's what that looks like:
Open blank doc, stare — 5 min
Scroll through Slack for context — 10 min
Check Jira/Asana for completed tickets — 10 min
Write something coherent — 15 min
Second-guess it, add filler, rewrite — 10 min
50 minutes. For a doc your manager will skim in 30 seconds.
And you do this every week. That's 40+ hours a year spent reconstructing what you already did.
You're not alone. Asana found that 60% of knowledge worker time goes to "work about work" — coordination, status checks, documentation. A Flexjobs survey showed 58% of workers say status meetings could be replaced by written updates. And the average manager spends 8 hours per week on reporting alone.
The information already exists. It's in your Slack messages, your closed tickets, your calendar. You're just manually re-typing it into a different format.
Here's the fix.
✂️ The Prompt
Open Claude or ChatGPT. Gather your raw inputs — Slack messages you sent this week, Jira tickets you worked on, calendar events, or just rough notes from memory.
Then paste this:
You are a senior professional writing a weekly status update. I'll give you raw inputs from my week — Slack messages, Jira tickets, calendar events, rough notes, whatever I have. Turn them into a clean, professional status update.
Format:
WINS THIS WEEK
[2-4 bullets. Concrete accomplishments. Shipped features, closed deals, finished projects, resolved issues. Quantify where possible.]
PROGRESS
[2-4 bullets. Things that moved forward but aren't done yet. Include current status.]
BLOCKERS
[Anything slowing you down. Be specific about what's blocked and what would unblock it.]
[If nothing is blocked, write "None — moving smoothly."]
NEXT WEEK
[2-4 bullets. What you're focusing on. Be specific enough that someone could check if you did it.]
Rules:
Keep the entire update under 200 words. Dense, not padded.
No filler language. No "continued to make progress on various initiatives."
Wins first — start strong.
If I mention meetings, extract what RESULTED from them, not that they happened.
If my raw inputs are messy or incomplete, do your best — ask clarifying questions only if something is truly ambiguous.
If I didn't do anything noteworthy, find the signal in the noise. Maintenance work, keeping things running, preventing problems — that's work too.
My raw inputs from this week:
[PASTE YOUR SLACK MESSAGES, JIRA TICKETS, CALENDAR EVENTS, OR ROUGH NOTES HERE]
That's it.
Paste whatever you have — Slack exports, ticket titles, meeting notes, or just "finished the API integration, met with Sarah about Q2, dealt with that production bug, lots of meetings." The messier your input, the more time the prompt saves you.
2 minutes instead of 50.
Copy the output. Paste into email or Slack. Quick skim, maybe tweak one line, send. Done.
Why this works (and why "write my status update" doesn't)
If you just ask AI to "write a status update," you get corporate fluff. "Made significant progress across multiple workstreams." That's useless.
The trick is raw inputs + structured output. When you give AI the actual evidence of your week — messages, tickets, notes — it has real material to work with. And when you enforce a specific format — wins, progress, blockers, next week — it produces something useful instead of vague.
The "Wins first" rule is the killer feature. Status updates bury the lead. Your manager has 15 direct reports sending updates. They skim. If your accomplishments are in paragraph three, they're invisible. Wins at the top means your value is the first thing they see.
Try it right now
You've done work this week. You have evidence somewhere.
Open Slack. Search "from:me" for the last 7 days. Copy a few messages.
Check your task board. Copy the titles of things you closed.
Or just write 3-4 bullet points from memory — rough is fine.
Paste the prompt above. Add your raw inputs.
Hit enter.
Then compare that to what you would have written in 50 minutes of staring at a blank doc.
If that worked, you'll want what's below.
Next week
My expense reports used to take 45 minutes. Now they take a photo.
Claude Vision reads the receipt so you don't have to. Merchant, amount, category, business justification — all from a photo you took in 3 seconds. Next Tuesday's kit.
⚡ The Full Kit
The prompt above handles one status update. The full Status Update Ghost kit handles every format, every edge case, and automates the input gathering.
📦 What's in the kit:
1. The 3-Prompt Chain
Not one prompt — three, each solving a different problem:
Prompt 1: The Week Scanner — Raw inputs (Slack, Jira, calendar, notes) → extracted data: what completed, what progressed, what's blocked, decisions made, meetings attended
Prompt 2: The Narrative Writer — Extracted data → polished status update in multiple formats (Slack-native, email to manager, standup script)
Prompt 3: The Priority Setter — From your week's data, generate next week's priorities + flag anything at risk
2. 3 Format Templates
Different contexts need different outputs:
Slack-native format — Emoji-rich, scannable, under 10 lines. Perfect for #team-updates channels.
Email to manager format — Professional, asks/blockers prominent, suitable for weekly 1:1 prep.
Standup/status meeting script — "What I did, what I'm doing, what's blocking me." Ready to read aloud.
3. Edge Case Prompts (3 variants)
Not every week is the same:
"I did nothing noteworthy" — Finds the signal in the noise. Reframes maintenance, firefighting, and keeping-things-running as legitimate progress.
Manager writing a TEAM status update — Aggregates multiple people's updates into one cohesive summary.
Monthly/quarterly review — Same concept but larger timeframe, more narrative, suitable for performance reviews or exec updates.
4. Automation Guide
Stop copy-pasting from Slack manually:
Slack API script to export your messages for the week
Jira JQL query to pull your completed/in-progress tickets
Calendar export for meetings attended
How to schedule this as a Friday 4pm recurring task (Zapier, Make, or cron)
5. Team SOP
The 1-page doc you hand your team:
Standard format for team status updates
When to use bullet format vs narrative format
How managers should read status updates (what to look for, red flags)
⏱️ Time to implement: 10 minutes (manual) or 15 minutes (with automation)
💰 Time saved: 2-3 hours per week
📎 Paid subscribers get the full Status Update Ghost kit →
Subscribe to One Less Thing to read the rest.
Become a paying subscriber of One Less Thing to get access to this post and other subscriber-only content.
UpgradeA subscription gets you:
- Full prompt chains, templates & SOPs for every kit
- Notion kit pages with copy-paste resources
- Edge case prompts for tricky scenarios
- Automation blueprints (Zapier, n8n, scripts)
- New kit every Tuesday