Daily Standup Summarizer
The Daily Standup Summarizer takes raw, unstructured standup notes or transcripts and produces a clear summary with categorized updates, highlighted blockers, dependency maps, and tracked action items. It turns the chaotic output of a 15-minute standup into a document that actually serves its purpose: keeping the team aligned and surfacing problems early.
Engineering managers, scrum masters, project managers, and team leads who run daily or weekly standups use this template. It solves the problem that standups generate useful information that immediately evaporates because nobody writes it down in a structured way, and meeting notes are typically too messy to scan quickly.
The prompt is effective because it does more than transcribe. It cross-references updates to identify dependency conflicts ("Alice is waiting on the API endpoint that Bob says is delayed"), flags risks that no individual mentioned but that emerge from the combined picture, and maintains a running action item list that carries forward between standups. This analytical layer is what separates a useful standup summary from a simple meeting transcript.
This prompt is just the starting point
Score it with AI, optimize it with one click, track versions, and build your prompt library.
The Prompt
Analyze the following standup notes and produce a structured team summary: **Team Name**: [TEAM NAME] **Date**: [TODAY'S DATE] **Sprint/Iteration**: [CURRENT SPRINT NAME OR NUMBER, e.g., "Sprint 14" or "Week of March 24"] **Raw Standup Notes**: ``` [PASTE THE RAW NOTES, TRANSCRIPT, OR CHAT LOG FROM YOUR STANDUP. This can be messy. Include each person's update in whatever format they gave it, e.g., Alice: Finished the login page redesign yesterday. Today working on the password reset flow. Blocked on the API spec from backend team, pinged Bob about it. Bob: Still debugging the payment retry logic, found a race condition. Should be done by tomorrow. Will send Alice the API spec after lunch. Carlos: Reviewed 4 PRs yesterday. Today starting the database migration script. Worried about the 2-hour maintenance window, might not be enough. Diana: Out sick yesterday, catching up on Slack. Will pick up the notification service work today. Need access to the staging environment, not sure who to ask.] ``` **Previous Action Items** (optional): ``` [LIST ANY OPEN ACTION ITEMS FROM PREVIOUS STANDUPS, e.g., - Bob to share API spec with Alice (from Monday) - Carlos to estimate migration window (from last Thursday)] ``` Produce the following: ### Team Status Summary A 3-5 sentence executive summary covering: overall team velocity (on track, slowed, blocked), the biggest risk or blocker, and any notable progress. ### Individual Updates For each team member, a structured entry: - **Completed**: What they finished (if anything) - **In Progress**: What they are working on today - **Blocked/Waiting**: Any blockers, with who or what they are waiting on - **ETA**: Estimated completion for current work item (if mentioned or inferable) ### Blockers and Dependencies A table or list showing: | Blocker | Who is Blocked | Depends On | Status | Impact if Unresolved | For each blocker, assess: is this being actively worked on, or is it stuck? ### Risk Flags Issues that no single person flagged as a blocker but that emerge from the combined updates: - Dependency conflicts (person A needs something from person B who is delayed) - Timeline risks (estimates that seem optimistic given current progress) - Resource gaps (someone missing access, knowledge, or availability) - Scope concerns (work items that seem larger than originally planned) ### Action Items A numbered list of specific actions with owners and deadlines: 1. [OWNER]: [ACTION] by [DEADLINE] Mark which items are new today and which are carried over from previous standups. Flag any carried-over items that are more than 2 days old. ### Suggested Follow-Ups Questions or conversations the team lead should initiate based on today's standup (e.g., "Check with Carlos whether the migration window can be extended before he starts the script").
Usage Tips
- Paste raw notes, not polished summaries: The prompt's value comes from analyzing messy input. If you clean up the notes first, you lose the signals (hesitation words, vague timelines, unstated concerns) that reveal hidden risks.
- Include previous action items every time: The carried-over action items section is where accountability lives. Without it, the same blockers recur for days without visibility.
- Share the output with the team: Post the structured summary in your team channel after each standup. It creates a searchable record and ensures everyone, including those who missed the standup, has the same picture.
- Use the risk flags to guide your 1:1s: The risks section often surfaces issues that team members are not comfortable raising in a group standup. Follow up privately using the specific flags as conversation starters.
- Batch multiple days for async teams: If your team does async standups (posting updates in Slack or a tool), paste a full week of updates and ask for a weekly summary instead. The cross-referencing becomes even more valuable over longer time periods.
Get more from this prompt
Save it, score it with AI, optimize it, and track every version. Free to start.