Daily standup meeting template (free, with example)

What’s in the template

The minutes open with these details:

• Team
• Date
• Time started / time ended
• Facilitator (rotating)
• Present
• Absent (and whether they posted an async update)
• Sprint / iteration and day number
• Sprint goal (one line, copied from sprint planning)

Then the body follows the meeting in this order:

1. 1. Goal check — Read the sprint goal aloud or paste it at the top. Thirty seconds. The updates that follow are about progress toward it, not about being busy.
2. 2. Updates, one block per person — Keep each person to a minute. Mention work by its ticket or item name so the board and the notes match.Name: · Yesterday: · Today: · Blockers:
3. 3. Board walk (optional) — Some teams walk the board right to left instead of going person by person: anything stuck in review, anything in progress for more than two days.
4. 4. New blockers raised today — Anything someone cannot move forward on without help. Give each one an owner for the unblocking, who is often not the person blocked.Blocker: · Who is blocked: · Who will unblock: · By when:
5. 5. Parking lot — Topics that came up and need a longer conversation. Note who needs to be in it and when it will happen. The standup ends on time regardless.
6. 6. Announcements — Absences, release times, a demo this afternoon. Facts only; questions go to the parking lot.
7. Blockers register (carried day to day) — One row per open blocker, copied forward until it is cleared. If a row survives a week, it belongs in the retrospective.Raised on: · Blocker: · Owner: · Status: · Cleared on:

At the end: blockers register and parking lot, as tables you can keep across meetings.

The template

Download it as a Word file, or copy the text version into your own document.

Daily Standup Notes

Team: 
Date: 
Time started / time ended: 
Facilitator (rotating): 
Present: 
Absent (and whether they posted an async update): 
Sprint / iteration and day number: 
Sprint goal (one line, copied from sprint planning): 

1. Goal check
   [Read the sprint goal aloud or paste it at the top. Thirty seconds. The updates that follow are about progress toward it, not about being busy.]

2. Updates, one block per person
   [Keep each person to a minute. Mention work by its ticket or item name so the board and the notes match.]
   Name:
   Yesterday:
   Today:
   Blockers:

3. Board walk (optional)
   [Some teams walk the board right to left instead of going person by person: anything stuck in review, anything in progress for more than two days.]

4. New blockers raised today
   [Anything someone cannot move forward on without help. Give each one an owner for the unblocking, who is often not the person blocked.]
   Blocker:
   Who is blocked:
   Who will unblock:
   By when:

5. Parking lot
   [Topics that came up and need a longer conversation. Note who needs to be in it and when it will happen. The standup ends on time regardless.]

6. Announcements
   [Absences, release times, a demo this afternoon. Facts only; questions go to the parking lot.]

Blockers register (carried day to day)
   [One row per open blocker, copied forward until it is cleared. If a row survives a week, it belongs in the retrospective.]
   Raised on:
   Blocker:
   Owner:
   Status:
   Cleared on:

Blockers register
Raised | Blocker | Blocked | Owner | Status

Parking lot
Topic | Who needs to be there | When

Example: filled-in daily standup

What the template looks like once it’s been used. The organisation and people are made up.

Action items

Tips for daily standup

• Rotate the facilitator weekly. It keeps the standup belonging to the team and stops one person from becoming the audience.
• Say ticket numbers out loud and write them down. "The payment thing" is unsearchable next week.
• Give every blocker an unblocking owner who is not the blocked person. Otherwise the register is a list of complaints.
• Start on time even if two people are missing. Waiting trains everyone to arrive late.
• If the same blocker is read out three days running, stop reading it out and escalate it in the parking lot instead.
• For async standups, post the three lines before 10:00 and reply in threads. Keep the main channel for updates only.

Related templates

• Sprint retrospective template — What went well, what didn't, ideas, and the one to three actions the team actually commits to.
• Sprint planning template — The sprint goal, the team's real capacity, the items pulled in, and what each of them depends on.
• Team meeting minutes template — The weekly meeting of one team: last week's numbers, blockers, decisions and this week's priorities.
• Meeting notes with action items template — Notes built around a running action register, for recurring meetings where last week's actions are this week's first agenda item.
• All meeting minutes templates

Or let the notes write themselves

A template helps when you’re the one typing. If you’d rather not be, an AI note taker can draft the summary and action items for you. Most send a bot into the call; QuietNote captures from your own computer instead, so nothing joins the meeting and you decide when capture starts. It’s in private beta. Whatever you use, read the draft before you send it, and tell attendees you’re recording where the rules require it.