Daily Standup Meeting Template
The daily standup was invented to kill meetings. Somewhere along the way it became one.
Fifteen minutes, three questions, everyone back to work. That was the deal when standups spread through software teams in the late 1990s and 2000s. What actually happens in most companies today: nine people on a call, the first four minutes spent waiting for someone to find the right link, then a parade of "no blockers" while three people check email with their cameras off.
A standup isn't broken because your team is lazy. It's broken because nobody gave it a shape. Here's the template that gives it one back, plus an async version for teams that don't share a timezone.
What a daily standup is (and isn't)
A daily standup is a short, time-boxed check-in where each person answers three questions: what did I finish since yesterday, what am I doing today, and what's blocking me. The rule that made it famous: keep it to 15 minutes, and stand up so nobody gets comfortable enough to ramble.
The Scrum Guide put the 15-minute cap in writing, and the "stand up" part was literal at first — teams gathered around a board and stayed on their feet. Both rules existed for the same reason: a standup that runs long stops being a check-in and becomes a status meeting nobody needed.
What a standup is not: a place to solve problems, a demo, a planning session, or a way for a manager to take attendance. Problems get a name in the standup and a separate conversation right after. Everything else waits.
The problem with the classic three questions
The three questions are fine. The way most teams run them isn't.
"Yesterday I worked on the dashboard. Today I'll keep working on the dashboard. No blockers." That's a real standup update you've heard a hundred times. It contains zero information. Nobody learns what "worked on" means, nobody can offer help, and nobody can tell whether the work is on track.
The fix isn't to drop the three questions. It's to make the answers commit to something specific. The template below does that.
The 15-minute standup template
Copy this, paste it into your meeting notes, and run it unchanged for a week before you tweak anything.
| Who | Question | Time |
|---|---|---|
| Facilitator | Open, restate today's focus, read the board | 2 min |
| Each person | What did I finish since yesterday? | ~30 sec each |
| Each person | What am I doing today, and what does "done" look like? | ~30 sec each |
| Each person | What's blocking me, and who can unblock it? | ~30 sec each |
| Facilitator | Park issues, assign owners, close | 2 min |
A few rules make the template hold together:
One answer per question, no narration. "Finished the checkout flow, it's in review" beats "so basically I was looking at the checkout and there was this one edge case...". If the story matters, it goes to the parking lot.
"Done" needs a shape. "Working on the dashboard" tells nobody anything. "Shipping the dashboard filter today — done means it's live for the beta group" gives the team something to hold you to, and a reason to flag you early if it slips.
Blockers name a person. "Blocked on the API" is a complaint. "Blocked on the API, need 20 minutes from Priya this morning" is something the facilitator can act on before the meeting ends.
The facilitator parks, doesn't solve. When two people start problem-solving, the facilitator says "park it, you two sync after" and moves on. The standup's job is to make the problem visible, not to fix it live.
The agenda, minute by minute
If your team keeps running over, run the agenda on a visible timer:
- 0–2 min — Open and orient. Restate the sprint goal or today's focus in one sentence. Read the board so everyone's starting from the same place.
- 2–11 min — The round. Each person gets their 30-second answers. Speak in a fixed order — the board order, not whoever unmutes first. No cross-talk until the round is done.
- 11–13 min — Park and assign. The facilitator names every blocker that surfaced and assigns an owner. "Priya, you and Marcus sync on the API — put a time in the calendar now."
- 13–15 min — Close. One line on what changed, one line on what to watch today. Done.
The timer isn't theatre. A standup that respects its own clock is a standup people will actually attend.
Async standup: same questions, no call
Not every team shares a timezone, and not every team needs a live call to sync. An async standup runs the same three questions in a shared channel or doc, with a deadline instead of a meeting time.
The template, async version:
Done: one thing you finished since yesterday. Today: one priority, and what "done" looks like. Blocked: nothing, or one blocker with a named person.
Post your answers by, say, 10:00 in your timezone. Read everyone's before you start your day. If a blocker needs a human conversation, that conversation is a five-minute call between two people — not a 15-minute meeting for nine.
Async standups die from vagueness faster than live ones, because nobody's in the room to ask a follow-up. "Making progress" is a null answer. If every update is one finished thing, one next thing, and one blocker, the thread stays readable and the team stays honest.
Standup formats for different teams
The three questions fit engineering. Other teams need a slightly different lens:
Sales. "Deal I moved yesterday, deal I'm moving today, deal that's stuck." Blockers are things like "need a security review before the contract goes out" or "waiting on the buyer's procurement."
Customer success. "Account I saved or expanded, account at risk today, renewal that needs a decision." The blocker is usually a customer going quiet — and the standup is where someone else on the team knows why.
Cross-functional and leadership. Replace the round with a board review: "what's red, what moved, what needs a decision today." Fewer personal updates, more triage.
Same shape in every case: finished, next, blocked. The words change; the discipline doesn't.
Why standups fail (and the fix)
It turned into a status report for the manager. If the only person who learns anything in a standup is the person in charge, it's a reporting ritual, not a team sync. Fix: updates are for teammates to act on, not for a manager to hear. If the manager wants status, they can read the notes.
Nobody writes anything down. A standup where blockers and owners live only in the moment is a standup that happens again tomorrow because nothing was resolved today. Fix: every action gets an owner and a note, written down before the meeting ends. If the note has no owner, it isn't an action — it's a hope.
It's a meeting about the meeting. Ten minutes of "wait, who's speaking next?" and "sorry, you go first" is not a standup. Fix: a fixed order, a timer, and a facilitator who isn't afraid to say "park it."
Where a notetaker earns its keep
A standup is short, which is exactly why its notes matter. The three answers, the blockers, the owners — that's the whole record of the day, and if it disappears when the call ends, tomorrow's standup starts from scratch.
This is the one place an AI notetaker pays for itself without getting in the way. Because the meeting is time-boxed, nobody wants to be the person typing. A notetaker that sits in the call captures the round and — the part that actually matters — turns every blocker into an action item with an owner attached. No bot joins the call, so the standup stays a standup: nine people, fifteen minutes, nobody transcribing.
Meetbook records your meetings from the browser tab, with no bot in the call. When the standup ends you get the three answers, the blockers, and the action items with owners, every one backed by the quote and timestamp it came from. Summaries can land in Slack or Notion, so the record of what everyone committed to is already where the team reads it.
The point of a standup was never the meeting. It was always the follow-through. Write down the owners, and the standup stops being a ritual and starts being the reason work moves.