Summarize a Daily Standup into a Shareable Update
Condenses raw standup notes into a scannable async update with blockers and at-risk items surfaced.
Standups are useful in the room and useless five minutes later, because the information evaporates the moment people stop talking. This prompt captures it. Paste your raw standup notes, however scrappy, and it produces an async summary the rest of the team can absorb in thirty seconds: per-person, what got finished, what's in flight today, and any blocker. The rollup is where it earns its place. It pulls every blocker into one section with a note on who can unblock it, flags what's at risk against your sprint goal, and surfaces decisions or asks the group needs to weigh in on, so the things that actually need action don't stay buried in individual updates. Blockers get bolded so nothing slips. It strips the filler and keeps each line to a sentence, which is what keeps people actually reading the daily post instead of tuning it out. Use it for distributed teams, async-first cultures, or any team lead who wants a written trail of progress without making everyone write their own update.
You are a team facilitator. Take the raw standup notes I paste and turn them into a clean async summary the team can read in 30 seconds. For each person, capture: what they finished, what they're doing today, and any blocker. Then add three rollup sections: Blockers needing help (with who can unblock), At-risk items against [SPRINT GOAL], and Decisions or asks for the group. Keep individual lines to one sentence each, strip filler, and bold any blocker. If someone reported no blockers, say so briefly. Team: [TEAM]. Raw standup notes: [STANDUP NOTES].
What you can expect back
Daily Standup - [Date] - Raj: Finished login fix. Today: checkout API. **Blocked: needs staging access.** - Elena: Testing checkout flow. Today: continue testing. No blockers (may want design input on error states). - Tom: Out sick. - Priya: Wrote release notes. Today: QA. No hard blocker, but flagged a timeline risk. Blockers needing help: Raj's staging access - DevOps (or Tom when back) can grant it. At-risk vs sprint goal: Error handling may not be done by Friday (Priya). The redesign can't ship to 100% without it. Decisions/asks: Does design need to weigh in on checkout error states before launch? Should we descope or extend to protect Friday?
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Paste notes raw and unedited; the prompt is built to clean up shorthand, so polishing first just wastes your time.
- 02Always set the sprint goal; the 'at-risk' section is only sharp when it has a finish line to measure against.
- 03Post the output in your team channel as the official record so people who missed standup stay in sync.
- 04Over a sprint, watch the recurring blockers; the same one showing up three days running is a process problem, not a daily one.
Adapt it for your case
Add 'collapse individual updates and give me only the blockers, risks, and a one-line progress read for my manager' for an upward report.
Add 'output only the blockers and who can unblock each' when you just need to chase down the stuck items fast.
Add 'estimate whether we're on track for the sprint goal and say why in one line' for a quick health read.
Common questions
What if half the team didn't report?
List who reported and mark the rest as 'no update.' Visible gaps are useful; they show who to follow up with rather than silently dropping them.
Can it work for an async standup people type into a channel?
Yes, that's an ideal fit. Paste the channel thread and it'll structure the scattered messages into the same clean summary, no live meeting required.
How is this different from just reading the standup notes?
Raw notes bury the signal. This pulls every blocker and risk into dedicated sections so the things needing action are impossible to miss, instead of scattered across ten individual updates.
You may also need
Build a Tight, Time-Boxed Meeting Agenda
Generates a time-boxed meeting agenda with owners, outcomes, and async/cut recommendations.
Turn Messy Notes into Clear Action Items
Extracts owners, due dates, decisions, and open questions from unstructured notes.
Write a Delegation Brief That Prevents Rework
Produces a clear delegation brief covering outcome, autonomy, deadline, and success criteria.
Summarize Meeting Notes Into Action Items
Turn messy meeting notes into a clean summary with decisions, owners, and follow-ups.