How to Automate a Daily Standup Summary with AI: A Prompt Workflow

Daily standups are supposed to take ten minutes and almost never do. The real cost is the follow-up: someone has to turn a messy thread of updates into a clean “done / doing / blocked” summary and chase the blockers. AI can do the boring part in seconds, provided you give it the raw material and a fixed output format.

This workflow turns a pile of standup notes or a chat log into a structured summary that you can paste into Slack, a project tracker, or an email.

What You Will End Up With

A consistent daily summary that separates completed work, in-progress work, and blockers, with owners attached — produced in under a minute from whatever raw notes you already have.

Step 1: Capture the Raw Material

Paste the actual notes, chat log, or transcript. Do not clean it up first — cleaning is the job.

Below is today's raw standup chat log. Do not summarise yet. Just confirm you understand it, and list any items that are ambiguous or missing an owner.

<paste raw notes here>

You get an early warning about gaps before the AI invents anything. Fix or flag those gaps now.

Step 2: Extract Done, Doing and Blocked

Force the three-bucket structure that makes a standup useful.

From the notes above, produce three sections: Done today, In progress, Blocked. For each item give: the task, the owner, and one short line of status. Use only information present in the notes. If an owner is unknown, write "unassigned".

You now have a clean, factual summary with no hallucinated progress.

Step 3: Format for Slack

Match the output to where it will live. Slack rewards brevity and scannability.

Reformat the summary for Slack: use short bullets, bold section headers, no more than 8 bullets per section, and put blockers first. Keep it under 200 words.

You get a post you can drop into a channel without editing.

Step 4: Flag Risks and Owners

The value of a standup is surfacing problems early, so extract them explicitly.

List every blocker as a separate line in this format: [Risk] description -> owner -> suggested next action -> urgency (high/medium/low). Do not add blockers that are not in the notes.

You now have an action list, not just a status report.

Step 5: Draft the Next-Day Plan

Close the loop by turning open items into tomorrow’s starting point.

Based on the in-progress and blocked items, write tomorrow's top three priorities, each with an owner. Keep each priority to one sentence.

You end the day with a plan the team already agrees with, because it came from their own updates.

Final Deliverable Checklist

• Three buckets: Done, In progress, Blocked.
• Every item has an owner (or is explicitly “unassigned”).
• Blockers formatted as risk -> owner -> next action -> urgency.
• Summary is under 200 words and pasted into the team’s real channel.
• Top three priorities set for tomorrow.

Common Pitfalls

Pitfall 1 — letting AI invent progress. Always instruct it to use only the provided notes; otherwise it fills gaps with plausible fiction.

Pitfall 2 — no output format. Free-form summaries drift. Lock the buckets and the character limits in the prompt.

Pitfall 3 — summarising instead of triaging. A standup that only reports status is a missed chance to unblock people. Always extract risks separately.

If your team runs longer meetings, combine this with our meeting notes summary workflow. To plan the week around these updates, use the weekly work plan prompt, and pull more routines from our productivity prompts collection.

Worked Example: From Notes to Slack Post

Input is a messy log; output is something a channel can read in ten seconds.

Input:
"ana finished the login fix, still waiting on design for empty states; sam blocked on API keys from vendor; QA reran the payment flow, 2 fails left; I updated the changelog"

Output:
Blocked
- Vendor API keys not received -> Sam -> escalate to vendor today -> high
In progress
- Empty states waiting on design -> Ana -> chase design -> medium
- Payment flow: 2 failing cases -> QA -> retest after fix -> medium
Done
- Login fix shipped -> Ana
- Changelog updated -> (unassigned)

Notice the output invents nothing and marks the changelog item unassigned — exactly what you want.

Tooling Options

Edge Cases to Handle

Watch for updates that are really opinions (“should be done soon”), items with two owners, and repeats across days. Tell the model to preserve verbatim any item it cannot classify, and to merge duplicates rather than listing them twice.

Quick FAQ

What if my team does not use Slack? Ask for the same three buckets as plain text or an HTML table. The format is what makes a standup scannable; the tool is interchangeable.

Should I include every tiny task? No. Instruct the model to keep only items that changed state today or that need someone’s attention tomorrow. A summary that lists everything summarises nothing.

Can I run this on a recorded call? Yes. Paste the transcript and add “ignore small talk, greetings, and off-topic side conversations” so the summary stays on work.

How do I stop it from guessing? Repeat the line “use only information present in the notes” in every prompt. If an item is unclear, require it to be preserved verbatim rather than interpreted.

How do I keep it short? Put an explicit word limit in the prompt every time. Without one, summaries creep toward a full recap that nobody reads — the opposite of what a standup needs.

Sources & Notes

The three-question standup format (done / doing / blocked) is a widely used agile practice; the phrasing here is our own, reviewed on 2026-10-09. Output conventions such as word limits and Slack formatting are suggestions — adjust to your team’s norms. Always review AI summaries for accuracy before sharing them with stakeholders.