Automate Daily Standup Meeting Notes With AI

Tested prompts for ai notes for daily standup meetings compared across 5 leading AI models.

BEST BY JUDGE SCORE Claude Opus 4.7 8/10

The prompt we tested

You are an expert meeting notes assistant specialized in daily standup meetings for agile teams. Transform the raw standup input below into clean, structured standup notes.

Follow these instructions exactly:
Format the output in Markdown with the date at the top, then a section per team member containing three bullet points: Yesterday, Today, and Blockers. After the per-person sections, include a '## Action Items' list with owners and a '## Blockers Summary' list flagging anything needing follow-up. Keep bullets concise (one line each), preserve names and ticket IDs exactly, and omit any section that has no content rather than writing 'N/A'.

Raw standup input:
Standup 10/28. Sarah: finished the login API PR-342 yesterday, today starting on password reset flow, no blockers. Mike: worked on the dashboard redesign but stuck waiting on Figma handoff from design team, today will pair with Sarah on auth if unblocked. Priya: shipped the analytics event tracking, today doing QA on staging, flagged that the staging DB is running out of space.

Produce the standup notes now.

Model comparison

ModelQualityCostLatencyTokens
Claude Opus 4.7 8 $0.0335 4.3s 369 / 373
Claude Haiku 4.5 7 $0.0013 1.9s 260 / 207
GPT-5.4 8 $0.0032 2.9s 232 / 175
Gemini 2.5 Pro 8 $0.0012 8.2s 235 / 179
Grok 4.1 Fast Reasoning 7 $0.0002 5.7s 382 / 152

Outputs

Claude Opus 4.7 8/10
# Daily Standup — 10/28

## Sarah
- **Yesterday:** Finished the login API PR-342.
- **Today:** Starting on the password reset flow.

## Mike
- **Yesterday:** Worked on the dashboard redesign.
- **Today:** Will pair with Sarah on auth if unblocked.
- **Blockers:** Waiting on Figma handoff from the design team.

## Priya
- **Yesterday:** Shipped the analytics event tracking.
- **Today:** Running QA on staging.
- **Blockers:** Staging DB is running out of space.

## Action Items
- Follow up with design team on Figma handoff for dashboard redesign — Mike
- Pair with Sarah on auth once Figma handoff is received — Mike
- Investigate and address staging DB disk space issue — Priya
- Continue password reset flow implementation — Sarah

## Blockers Summary
- **Mike:** Blocked on Figma handoff from design team — needs escalation to design.
- **Priya:** Staging DB nearing capacity — needs ops/infra follow-up.
Judge notes: The output is clean and production-ready, but the Action Items section adds low-value redundant entries (e.g., "Continue password reset flow — Sarah" was never flagged as an action item in the input) that dilute the list's usefulness.
Claude Haiku 4.5 7/10
# Standup Notes - 10/28

## Sarah
- **Yesterday:** Finished login API PR-342
- **Today:** Starting on password reset flow
- **Blockers:** None

## Mike
- **Yesterday:** Worked on dashboard redesign
- **Today:** Pairing with Sarah on auth if unblocked
- **Blockers:** Waiting on Figma handoff from design team

## Priya
- **Yesterday:** Shipped analytics event tracking
- **Today:** QA on staging
- **Blockers:** Staging DB running out of space

## Action Items
- Mike: Follow up with design team on Figma handoff
- Priya: Investigate and resolve staging DB storage issue

## Blockers Summary
- **Design handoff delay:** Mike blocked on Figma assets from design team
- **Infrastructure issue:** Staging DB capacity running critically low (Priya)
Judge notes: The output is clean and well-structured but violates the instruction to "omit any section that has no content" by including "Blockers: None" for Sarah, and the Action Items section adds inferred urgency language ("critically low") not present in the raw input.
GPT-5.4 8/10
# 10/28

## Sarah
- **Yesterday:** Finished the login API PR-342
- **Today:** Start on password reset flow

## Mike
- **Yesterday:** Worked on the dashboard redesign
- **Today:** Pair with Sarah on auth if unblocked
- **Blockers:** Waiting on Figma handoff from design team

## Priya
- **Yesterday:** Shipped the analytics event tracking
- **Today:** Do QA on staging
- **Blockers:** Staging DB is running out of space

## Action Items
- **Design team:** Provide Figma handoff to Mike
- **Priya:** Follow up on staging DB space issue

## Blockers Summary
- Mike is blocked waiting on Figma handoff from design team
- Priya flagged that the staging DB is running out of space
Judge notes: Excellent execution of all instructions—concise, correctly omits N/A sections, preserves ticket IDs and names—but Sarah's section silently drops the "no blockers" confirmation (which is fine per instructions) while the Action Items lack explicit owners with names/roles, slightly reducing production-readiness.
Gemini 2.5 Pro 8/10
## Standup 10/28

### Sarah
- **Yesterday:** Finished the login API (PR-342).
- **Today:** Start on the password reset flow.

### Mike
- **Yesterday:** Worked on the dashboard redesign.
- **Today:** Pair with Sarah on auth if unblocked.
- **Blockers:** Waiting on Figma handoff from the design team.

### Priya
- **Yesterday:** Shipped the analytics event tracking.
- **Today:** Perform QA on the staging environment.
- **Blockers:** The staging database is running out of space.

## Action Items
- **Priya:** Investigate the staging database space issue.

## Blockers Summary
- **Mike:** Waiting on Figma handoff from the design team.
- **Priya:** Staging database is running out of space.
Judge notes: Sarah's section correctly omits the Blockers bullet (per instructions), but the Action Items list only assigns Priya an item while Mike's Figma blocker—which likely requires escalation or follow-up with the design team—has no assigned owner or action.
Grok 4.1 Fast Reasoning 7/10
# 10/28

## Sarah
- **Yesterday:** finished the login API PR-342
- **Today:** starting on password reset flow
- **Blockers:** none

## Mike
- **Yesterday:** worked on the dashboard redesign
- **Today:** will pair with Sarah on auth if unblocked
- **Blockers:** waiting on Figma handoff from design team

## Priya
- **Yesterday:** shipped the analytics event tracking
- **Today:** doing QA on staging
- **Blockers:** staging DB running out of space

## Blockers Summary
- Mike: waiting on Figma handoff from design team (needs follow-up)
- Priya: staging DB running out of space (needs follow-up)
Judge notes: The output omits the "## Action Items" section entirely (a required deliverable per instructions), and retains "Blockers: none" for Sarah instead of omitting empty sections as instructed.

Related queries