Guides
Daily Standup Meeting Template (Free) with Agenda, Questions and Example
A daily standup is a 15-minute meeting where each person answers three questions: what they finished yesterday, what they will do today, and what is blocking them. Copy the template below for live or async standups, and see real notes drafted from a sample standup.
Updated October 31, 2026.
Template 1: Daily standup agenda
For scrum teams and any team that meets briefly each morning.
DAILY STANDUP Team: [Name] Date: [Date] Facilitator: [Name] Timebox: 15 minutes [Name] - Yesterday: [What I finished] - Today: [What I will do] - Blockers: [What is in my way, or "none"] [Name] - Yesterday: - Today: - Blockers: BLOCKERS TO RESOLVE AFTER STANDUP - [Blocker] | Who helps: [Name] | By: [Time] REMINDERS - [Deadlines, releases, cut-offs]
Template 2: Async standup
For teams across time zones: post the answers in chat instead of meeting.
ASYNC STANDUP (post in your team chat by [time]) 1. What did you finish yesterday? 2. What will you work on today? 3. Is anything blocking you?
How to keep standups short and useful
- Stick to the three questions. Discussions move to after the standup.
- Give every blocker an owner and a time before the standup ends.
- Repeat deadlines at the end (release cut-offs, demos) so nobody misses them.
Real example: what Audio Notes AI wrote from a sample meeting
We wrote a short transcript of a fictional standup: three updates, two blockers (database access and missing copy), and a release reminder. We ran the transcript (a fictional meeting, plain text with no speaker labels, as the app produces it) through Audio Notes AI. This is the output, unedited, with key points shortened to the first 5.
Summary
During the fifteen‑minute standup, Lena reported finishing search filters and opening a pull request, and said she will address review comments and begin work on saved searches with no blockers. Marco explained he diagnosed a login bug caused by token refresh timing, will ship the fix and add a test today, but needs staging database access to reproduce an edge case, which he expects to receive immediately after the meeting. Aisha shared that she wrote onboarding emails, is testing them in the preview tool, but is waiting on final copy from marketing and will request it by noon. The facilitator reminded the team that sprint planning preparation was done yesterday, today the focus is on the release checklist for Friday, and the release cut‑off is Thursday at 5 pm. No other issues were raised.
Key points
- Lena completed search filters and opened a pull request yesterday; today she will address review comments and start work on saved searches, with no blockers.
- Marco investigated the login bug where sessions expire after an hour, identified the cause as the token refresh running in the wrong time zone; today he plans to ship the fix and add a test; he is blocked pending staging database access to reproduce an edge case and expects to receive that access immediately after the meeting.
- Aisha wrote the onboarding email content yesterday; today she is testing the emails in the preview tool but is blocked awaiting final copy from marketing, and will contact marketing to request the copy by noon.
- The facilitator noted that yesterday’s activity was sprint planning preparation and today’s focus is the release checklist for the upcoming Friday release; reminded the team that the release cut‑off is Thursday at 5 pm.
- No additional items were raised during the standup.
Action items
- Lena: address review comments on the search filters pull request and begin implementing saved searches.
- Marco: ship the login bug fix and add a test.
- Provide Marco with access to the staging database immediately after the meeting.
- Aisha: ping marketing to obtain the final onboarding email copy by noon.
- Facilitator: finalize the release checklist for Friday’s release.
One action item came out wrong: the lead offered to ping marketing, but the draft gives it to Aisha. Without speaker labels the app has to guess owners from what people say, so check owners before you share the notes.
Skip the typing: record the meeting on your phone or upload the recording in your browser, and Audio Notes AI drafts the summary, decisions and action items for you to paste into the template. Try it free in your browser (3 notes or 60 minutes) or get the iPhone app.
Honest limits
- Audio Notes AI does not label speakers. Owners come from names people say out loud; check them before you send the notes.
- Recordings can be up to 90 minutes each, and transcription needs an internet connection.
- Tell everyone you are recording, and follow your organisation’s rules and local law.
Related
Transcribe & Secure Your Audio
Record voice notes, generate instant summaries, and share them via secure expiring links with zero-knowledge encryption.
Download on App Store