Stand-up meeting: format, daily agenda, async variant — and what the channel does between stand-ups (2026)

A stand-up meeting is a short daily meeting of one team, held at the same time every working day, in which each person says three things: what they finished since yesterday, what they will do until tomorrow, and what is blocking them. Fifteen minutes is the ceiling, not the target. The name comes from the habit of standing for it so that nobody settles in — a stand-up that is comfortable has already run too long. It exists to surface blockers early, not to solve them, and not to report to a manager: the audience is the team, and the output is a short list of blockers with a name next to each.

This post is the format: what a stand-up is and what it isn't, the six rules that keep it one, the three questions and the version that works better, a daily agenda you can copy, three filled-in variants, and the asynchronous stand-up for a team that is never awake at the same hour. The last section is about the part most guides skip — the twenty-three hours and forty-five minutes between two stand-ups, where the blocker either gets cleared or gets repeated tomorrow — and what the tools a team already runs on do with that list.

What a stand-up is — and what it isn't

The two failure modes are the two columns to the right. A stand-up that drifts into a status meeting is the one where each person addresses the lead instead of the team, and the rest of the room waits for its turn. A stand-up that drifts into a team meeting is the one where two people start solving a blocker in front of six who cannot help — the first "let's take that offline" is the facilitator's whole job.

A related term: the daily scrum is the stand-up as Scrum defines it — a 15-minute event for the Developers of one Scrum Team, held every day of the Sprint to inspect progress toward the Sprint Goal and produce a plan for the next day. The 2020 edition of the Scrum Guide prescribes no format for it at all; the Developers choose whatever structure they want. "Stand-up" is the general form any team uses, Scrum or not; everything below applies to both.

The format: six rules

1. Same time, same place, every working day. The point of a daily meeting is that nobody has to schedule it. Pick the earliest hour everyone is reliably present and do not move it for a visitor.
2. Fifteen minutes is the ceiling. Eight people at one minute each is eight minutes; the rest is for naming who pairs on what. A team that regularly needs the full fifteen is too large for one stand-up, or is solving things in it.
3. One team. The people who can unblock each other. If half the room never has anything to say to the other half, it is two stand-ups.
4. Each person: since yesterday, until tomorrow, blocked by. Finished, not "worked on"; the next concrete thing, not the whole week; and the blocker with the name of who could clear it, if known.
5. Blockers are named, not solved. Two sentences to describe it, then it goes to the list with the two names who will talk after. Anything that takes more than two sentences is a conversation, and conversations happen after the stand-up.
6. It leaves a list behind. The blockers of today, with an owner each, somewhere the whole team reads — and the list of yesterday checked against it: cleared, still open, or dropped.

The three questions — and the version that works better

The classic three questions are What did I do yesterday? What will I do today? What is blocking me? They are a fine starting shape and they have one known problem: the first two are answered to the manager. "Yesterday I worked on the export, today I'll continue on the export" is a report, carries no information for anyone else in the room, and takes a minute of eight people's time.

Two adjustments fix most of it:

Anchor to outcomes, not activity. "Since yesterday I finished X; until tomorrow I will finish Y; I am blocked on Z by W." Finished and will finish force a concrete claim that is true or false the next morning; "worked on" is never false.

Walk the board, not the people. Instead of going round the room, go down the work items in priority order and let whoever holds each one say what it needs to be done. People with nothing on the board say nothing; the item that is stuck gets named by the work, not by who is embarrassed to raise it. For a team with a visible board this is the single most effective change; for a team without one, the round-robin with outcome wording is close enough.

A rule in either shape: the person speaking addresses the team, and the facilitator — rotating, one week each — stands at the side, not the front.

How to run one: before, during, after

Before (two minutes, the facilitator): the board is current, and the facilitator has yesterday's blocker list open. Not the whole backlog — the list from the last stand-up, so that each item can be checked in one word.

During (fifteen minutes, the team): start on time with whoever is there. Go round, or walk the board. One minute each; the facilitator says "and the blocker?" to anyone who finished without one and "offline" to any two people who start solving. Check yesterday's blockers: cleared, open, dropped — one word each. Parking lot for anything that is not a blocker but needs a slot: a decision, a question for someone absent. End by reading the list: blocker, who, who is helping, by when.

After (five minutes, the facilitator): the blocker list goes where the team reads, with an owner for each item and the parking-lot items given a time. The pairs talk. Tomorrow's stand-up starts from this list — which is why it has to live somewhere findable, not in the facilitator's head.

A daily stand-up agenda template

Copy the block, replace the brackets, and keep it to one screen — a stand-up agenda that needs scrolling is a team-meeting agenda.

Team stand-up — [day], [time] — 15 min — [facilitator this week]
Purpose: surface today's blockers; nothing else.
1. Yesterday's blockers — facilitator — 2 min
[blocker from yesterday] — [owner] — cleared / open / dropped
[blocker from yesterday] — [owner] — cleared / open / dropped
2. Round — each person — 1 min each — information
Since yesterday: [finished]. Until tomorrow: [will finish]. Blocked by: [what, and who could clear it].
3. Blockers that need two people — pairs named — 3 min — taken offline
[blocker] — [who has it] + [who helps] — [when they talk]
4. Parking lot — facilitator — 2 min
[not a blocker, needs a slot] — [when, where]
Leaves behind: today's blocker list with a name per item, posted in the team channel before [time + 20 min].

Three variants with the agenda filled in

1. A software team of eight, one time zone

Team stand-up — Tuesday 09:30 — 15 min — Priya
1. Yesterday's blockers — staging certificate (Tom) — cleared; design review for the export screen (Lena) — open, review moved to today 11:00
2. Round — eight people, walking the board from the top: three items in review, two in progress, one blocked
3. Blockers that need two people — the export screen cannot ship without the API change (Lena + Tom, 11:30)
4. Parking lot — release date for the mobile build, needs Marco back on Thursday
Leaves behind: two open blockers, two pairs, one parked item with a date.

2. A distributor's sales team in two countries

Daily huddle — 08:45 CET / 09:45 EET — 15 min — Ana
Purpose: surface what is stopping a deal or a delivery today.
1. Yesterday's blockers — the Bucharest warehouse confirmation (Radu) — cleared; price list for the new line (Ana) — open, finance promised noon
2. Round — six people: each names the one deal or delivery they will move today and what it is waiting on
3. Blockers that need two people — a client's customs paperwork is in a language only Radu reads (Radu + Sofia, 10:00)
4. Parking lot — the trade-fair stand, Friday's team meeting
Leaves behind: two open items, one pair, posted in the channel in each member's language.

3. A team across three time zones — the asynchronous variant

Async stand-up — every working day by 10:00 UTC — #team-daily
Purpose: the same three parts, written or spoken, one message per person.
1. Each person, by 10:00 UTC: since yesterday / until tomorrow / blocked by — one message, text or a one-minute voice note
2. Blockers: anyone who can help replies in the thread of that message, not in a new one
3. Yesterday's list: the facilitator checks it against the new messages — cleared / open / dropped — and posts today's list by 10:20 UTC
4. Twice a week, 14:00 UTC: a fifteen-minute live call for the blockers a thread could not clear
Leaves behind: the same list as the live version, in the same place, with the threads under it.

The asynchronous stand-up: written or spoken, by a set time

A live stand-up needs everyone awake, present and free at the same hour. A team across more than two time zones, a team with part-time members, field staff who are driving at nine, a clinic whose front desk cannot leave the desk — these teams either skip the stand-up or hold it with half the team. The asynchronous version keeps the format and drops the requirement of a shared hour.

The rules that keep an async stand-up a stand-up: one message per person, by a set time, in one agreed channel — not a form, not a document everyone edits, because a message has an author, a time and a thread. The same three parts in the same order, so that a message can be read in ten seconds. A thread per blocker, so that the offer to help lands under the problem and the rest of the channel stays readable. The facilitator closes it at the set time with the list — the one output a stand-up has — and checks yesterday's list in the same message. And a live call on a fixed cadence, twice a week or once, for the blockers that a thread did not clear: the async stand-up is a replacement for the hour, not for ever speaking.

Spoken works as well as written when the team allows it. A one-minute voice note from a phone, recorded on the way in, is often more honest than a sentence typed at a desk — people say the blocker they would have edited out — and a channel that transcribes the note keeps it searchable and lets the rest of the team read it rather than listen.

What the async version loses is the moment when someone hears a blocker and says "I had that last week". The thread-per-blocker rule and the fixed live slot are the two ways to get it back; a team that drops both has a daily report, not a stand-up.

Where the stand-up lives in the tools you already use

A stand-up is a recurring meeting on the calendar plus a place where the blocker list is posted. Documented behaviour only, from the vendors' own pages; each cell names the month its fact was checked.

Each of the four produces one document or one summary per meeting, in the language it was written or held in; none of the pages cited states that a reader gets it in a language of their own. Where that matters to the team, the next section is one way the job gets done; where it does not, the table above is the whole answer and any of the four will do.

What the channel does between stand-ups

In InterMIND a stand-up is a channel's meeting. A channel is a persistent room: its chat is kept between sessions, its meeting link is permanent, and the recurrence is set once, in Google Calendar or Outlook, on an event that carries that link — so the same room opens every morning, with its chat and its recaps. Today's blocker list is a message in the channel; yesterday's is one scroll up; the one from three Tuesdays ago is in search. And the whole space stays in each member's language: a message typed in Spanish is read in Romanian by the colleague in Bucharest and in Spanish by the sender, with the original one click away — the chat, the notes, the recap and the files, not one meeting at a time.

During the stand-up, the facilitator can put the list on everyone's screen: a note in the channel, Share to conference from its message menu, and it opens for every participant in their own language while the sharer edits it live — cleared, open, dropped, typed in as the round goes. The same works for a recap message from yesterday.

After the stand-up, the recap: a summary of what was said and the action items with an owner each, every item tied to the moment in the transcript where it was taken on. It goes by email to each signed-in participant, as a message into the channel chat and as a link in the calendar event, in the reader's own language rather than the language the stand-up was held in. The channel keeps the recap of every past session, not only the latest, so the list of two weeks ago is a search away.

For a channel's recurring meeting, the open items of the previous session are read back when the next recap is written and judged against what was said: reported finished, marked done; anything else marked not done with the reason in the words of the meeting, or "not discussed" — the check of yesterday's list, done by the recap rather than by the facilitator's memory — and at the start of the next session Mia names the open items and their owners. This part runs for selected accounts while it is being refined.

The async variant lives in the same channel. A voice note is the microphone button in the channel composer — from the web or the phone app, up to ten minutes, transcribed within seconds — and each teammate reads it in their own language, with a play button for the original; it is searched, quoted and forwarded like any text message. A channel also has its own email-in address, created by the host, so an update from someone who is in a vehicle, on a ward or in a system that only sends email lands in the channel under the sender's name. And a copy of every recap can go by email to up to ten addresses — a CRM inbox, a client's project address — set once per channel in its settings, on every plan.

A stand-up is members-only. A channel needs membership: a colleague outside the team's workspace is added by email invitation onto a free account and becomes a member who reads the channel in their language. Someone who needs to be in one session only — a client for one morning, a contractor for one hand-over — joins an ad-hoc meeting by link, from a phone, without an account, hears the meeting in their language and gets nothing afterwards; the chat of that call is wiped when it ends.

The host provides the space and, on a paid plan, pays only for the members active in the previous 28 days — joined a meeting, wrote in a chat, asked Mia. A member on leave for a month keeps access and costs nothing that month; the stand-up they come back to is in the channel, with its lists.

• Open a complete recap — summary, action items with the moment each was taken on, transcript.
• Try the live demo — no signup; speak, and hear the room translated per listener.

One habit survives any tool: the stand-up ends when the list is read aloud, and the list is posted before anyone goes back to work.

FAQ

What is a stand-up meeting?

A short daily meeting of one team, held at the same time every working day and capped at fifteen minutes, in which each person says what they finished since yesterday, what they will do until tomorrow, and what is blocking them. Its purpose is to surface blockers early so the people who can clear them know the same morning; it is not for solving them and not a status report to a manager. It leaves behind a list of blockers with a name next to each.

What are the three questions in a stand-up meeting?

The classic three: What did I do yesterday? What will I do today? What is blocking me? A version that reports less and informs more replaces activity with outcomes — "since yesterday I finished X, until tomorrow I will finish Y, I am blocked on Z by W" — or walks the board by work item instead of going round the people, so that the stuck item is named by the work and not by whoever is holding it.

How long should a stand-up meeting be?

Fifteen minutes is the ceiling; most run eight to twelve. The arithmetic is one minute per person plus two or three for yesterday's list and for naming who pairs on each blocker. A team that regularly needs the full fifteen is either too large for one stand-up or is solving problems in it; the fix is to split the team or to move the conversation after the meeting, not to lengthen it.

Why is it called a stand-up meeting?

Because the team stands for it. The habit came from software teams in the 1990s who found that standing kept the meeting short — nobody settles into a chair and opens a laptop — and the name stuck even for teams that hold it sitting or on a call. The property it names is the length, not the posture: a stand-up held on video is still a stand-up if it is fifteen minutes and leaves a blocker list.

What is the difference between a stand-up and a daily scrum?

The daily scrum is the stand-up as defined by Scrum: a 15-minute event for the Developers of one Scrum Team, every day of the Sprint, to inspect progress toward the Sprint Goal and plan the next day. The 2020 edition of the Scrum Guide prescribes no format — no three questions — and leaves the structure to the Developers. "Stand-up" is the general form: any team, any method, same length, same purpose. Every stand-up guide applies to a daily scrum; the daily scrum adds the Sprint Goal as the thing every update refers to.

How do you run a stand-up meeting?

Same time every day, start with whoever is there, a rotating facilitator at the side. Check yesterday's blockers in one word each — cleared, open, dropped. Then the round or the board walk, one minute per person, with the facilitator asking "and the blocker?" of anyone who finished without one and saying "offline" to any two people who start solving. Park anything that needs a slot but is not a blocker. End by reading the list: blocker, who has it, who helps, when they talk — and post it where the team reads before anyone goes back to work.

What is an asynchronous stand-up?

The same three parts posted as one message per person, text or voice, by a set time in one agreed channel, instead of said aloud at the same hour. The rules that keep it a stand-up: the same order every day, a reply thread per blocker so help lands under the problem, a facilitator who closes it at the set time with the day's list and the check of yesterday's, and a short live call on a fixed cadence for the blockers a thread could not clear. Teams across time zones, part-time members and field staff use it; the risk is that it quietly becomes a daily report nobody reads, which the thread rule and the live slot are there to prevent.

Should the manager attend the stand-up?

As a member of the team, yes — with a one-minute update like everyone else and the same rule not to solve things in it. As an audience, no: a stand-up where each person addresses the manager is a status meeting at eight people's cost. If the manager's presence turns the round into reporting, the usual fixes are walking the board instead of the people and rotating the facilitator among the team, so that the manager is one voice in the round and not the reason for it.

Sources: Scrum Guide — 2020 edition; Microsoft — Take meeting notes in Microsoft Teams; Microsoft — Recap in Microsoft Teams; Zoom — Using Meeting Summary with AI Companion; Zoom — Generating meeting agenda with AI Companion; Google — Calendar & Meet settings for "Take notes for me"; Google Meet — "Take notes for me" in Google Meet; Slack — Use huddles in Slack; Slack — Meeting agenda template. Vendors change plans, features and language lists over time; check their pages for the current state. Each table cell names the month its fact was checked — the earliest checked August 2026, the latest checked October 2026.