TL;DR
A weekly status update should take 15 minutes, not 90. The trick is splitting the work: AI handles the boring 80% (bucketing raw inputs, drafting a TL;DR, surfacing one under-discussed risk and win), and you keep the 20% only a human can write (the judgment call and the ask). This tutorial gives you the exact prompt chain, the tools that pull your raw data for you (Linear Agent, Slack AI recaps, Notion weekly digests), and a quality checklist that catches the two ways AI ruins a status update: inventing momentum and rounding numbers.
Who this is for
PMs, engineering managers, ops leads, and founders sending weekly or biweekly project updates — especially anyone who ships across more than one workstream and has an executive reader who only opens the first paragraph. It also works for individual contributors writing manager-readable updates, with the bucket labels shrunk to “did / blocked / next”.
Skip this workflow if the project is in crisis. In crisis you write the update by hand, daily, with a named owner per risk. AI is for steady state.
Which AI tool to use
Any of the big three frontier models handles this task well — the prompts are short and the reasoning is light. The real difference is which tool can also pull your raw inputs so you are not copy-pasting from five tabs. As of June 2026:
| Tool | Plan / price (USD/mo) | Best for status updates | Notes |
|---|---|---|---|
| ChatGPT | Plus $20, Go $8, Pro $100/$200 | Drafting + editing the prose | GPT-5.5 default; US Free tier shows ads and has tight limits |
| Claude | Pro $20, Max $100/$200 | Long inputs (paste a whole sprint) | Opus 4.7 / Sonnet 4.6 both 1M-token context, so a full week of tickets fits in one paste |
| Gemini | Google AI Pro $19.99 | Teams already in Google Workspace | Gemini 3.1 Pro, 1M context; pulls from Docs/Gmail if you grant access |
For the writing itself, any $20 tier is plenty — you are not running benchmarks, you are bucketing bullets. Where it gets interesting is the data-gathering layer:
- Linear Agent (shipped March 2026): mention
@Linearin any comment and it synthesizes project context, drafts updates, and now reasons over your actual codebase via Code Intelligence (May 2026). It also pulls external context through MCP (April 2026). If your team lives in Linear, this is the lowest-friction option — see Linear’s changelog for what shipped this quarter. - Slack AI recaps: summarize any channel, DM, or thread, with sources cited so you can verify. Note it is a paid add-on, not included in standard Pro/Business+/Enterprise plans.
- Notion AI weekly digest: a scheduled agent can query a tasks database for items completed in the last seven days and build a structured summary page automatically.
Our AI weekly report tutorial covers the data-pull setup in more depth; this article focuses on the prompt chain that turns raw data into a forwardable update.
Before you start
- Pick the single audience: skip-level manager, cross-functional partner, or exec. Each wants a different lead sentence.
- Gather raw inputs in one place: merged PRs, tickets closed this week (Linear/Jira), Slack threads worth surfacing, customer or support notes.
- Decide the format up front — Notion doc, Slack post, or email. The length cap is one screen on the reader’s device.
- Have last week’s update open so you can name what changed. The “delta” is what readers actually want, not absolute numbers.
- If you are in a regulated org, sanitize first: replace customer names with role tags. On ChatGPT Enterprise, admins set retention (90-day minimum) and deleted conversations are purged within 30 days; on the Free/Plus consumer tiers, assume your prompts may be used to improve models unless you opt out, so keep names and revenue figures out of the prompt.
The prompt chain
Run these as four separate messages in one chat so the model keeps context. Paste your raw bullets after Prompt 1.
Prompt 1 — bucket the raw data:
Here are my raw inputs for this week's status update: merged PRs, closed
tickets, Slack thread summaries, and customer escalations. Bucket every item
into exactly five lanes: Shipped, Blocked, On-track, At-risk, Next-week.
Deduplicate. Drop anything trivial (typo fixes, dependency bumps). Do not add
commentary yet — just the buckets.
[paste raw bullets here]Prompt 2 — draft the TL;DR:
Write a one-paragraph TL;DR from the buckets above: exactly 4 sentences, max
60 words, plain language. State what shipped, what is at risk, and what I need.
No buzzwords. If the draft contains "leverage", "synergy", "momentum", or
"unlock", rewrite that sentence.Prompt 3 — surface what the raw data hides:
From the same raw inputs, surface ONE risk that is under-discussed (mentioned
once or buried) and ONE win that is under-celebrated. One sentence each. Quote
the source line so I can verify it is real, not inferred.Prompt 4 — assemble:
Assemble the final update in this order: TL;DR on top, then the five buckets
as short bullets, then a blank line where I will add my own ask. Total length
must fit one phone screen. Cut the On-track section to one line.Then you do the only part AI cannot: add the human sentence. Format it as Ask: I need X by Y from Z and put it on the last line. That is the sentence your skip-level actually reads.
The two-minute first run
Run this on a low-stakes week first, so you can see where AI helps versus hurts before it matters. Take last week’s already-sent update and a fresh batch of raw inputs, run the full chain without editing, then diff the AI output against what you actually wrote last week. Mark each section: usable as-is, needs a light edit, or wrong.
Most teams find AI nails the bucketing and TL;DR but invents momentum that does not exist — that becomes the section you always edit. For your second run, change only one variable, usually the bucket labels or the audience tag.
Quality check before you send
- TL;DR test: read only the first paragraph. Does a reader who knows nothing understand what shipped, what is at risk, and what you need?
- Number audit: every metric, date, and percentage in the draft must appear in the raw inputs. AI rounds, smooths, and occasionally fabricates. This is the single highest-value check.
- Risk honesty test: would you say this sentence out loud in front of the at-risk team? If not, rewrite it.
- Length test: one screen on a phone. If it overflows, cut the On-track section first. Readers assume on-track if you do not mention it.
- Voice check: read it aloud. If it sounds like a press release, the human sentence is missing.
Make it reusable
- Save Prompts 1–3 as three separate saved messages (or a custom GPT / Claude Project). Each needs a one-line tweak per project.
- Keep a
status-update/folder with a dated copy of inputs and outputs. After four weeks, the deltas become your quarterly-review raw material. - If you use Linear, save the successful agent conversation as a reusable skill — Linear lets you replay it for recurring catch-ups.
- Every four to six weeks, rerun the chain without your edits and compare. If AI output is converging with yours, your prompt is mature; if diverging, the model or the project changed.
- Share the prompt with one peer. Their edits surface phrasing biases you cannot see in your own writing.
Common mistakes
- Sending AI’s draft verbatim. The cadence and word choice tip readers off within two sentences. The human sentence is the antidote.
- Burying the ask. Skip-level scrolls to the last line; put the ask there, never in the middle of a bucket.
- Omitting uncomfortable risks. A status update with no risks reads as either lying or asleep.
- Letting AI invent momentum. If your prompt was “make it sound positive,” you got fiction. Prompt 3 exists to pull real signal, not manufacture it.
- Writing for everyone. Pick one reader and write to them; cc the rest.
- Skipping a week because “nothing happened.” Cadence is the trust signal. Send four sentences and the ask anyway.
FAQ
- What if there is genuinely nothing to report? Send four sentences anyway: what shipped, what is blocked, what is next, and one ask. Skip-level reads the absence of an update as project death.
- Should AI write in my voice? No. Have AI draft factually and neutrally; you add voice in the human sentence and the ask line. That is enough to sound like you, and it sidesteps the AI-tell problem.
- My company blocks ChatGPT. What’s the workaround? Use your org’s enterprise tier (ChatGPT Enterprise/Business and Claude for Work do not train on your data by default), or run a local model on a sanitized inputs file. These prompts are short enough that a small local model handles them.
- How long should the TL;DR be? Four sentences, max 60 words. If it does not fit, the project is too broad for one update — split it into two.
- Which model is best for this? Any current $20 tier (ChatGPT Plus, Claude Pro, Google AI Pro) is more than enough. Reach for Claude only if you paste an entire sprint of raw data at once — its 1M-token context (Opus 4.7 / Sonnet 4.6) swallows a full week of tickets without truncation.
- Can I use this for an upward 1:1 update instead of a team-wide one? Yes, but shrink the bucket count to three: progress, blockers, asks. The TL;DR becomes a single sentence.