Daily stand-up templates (copy-paste, Slack and Teams)

A daily stand-up template is a short, fixed set of prompts everyone answers the same way — so the meeting has a shape and nobody has to improvise what to say. The templates below are copy-paste ready for a live stand-up, a Slack or Teams channel, or an async thread. Pick one, use it unchanged for a fortnight, then adapt.

One rule before you copy anything: keep it to three prompts, and put blockers first. A longer template feels thorough and quietly trains people to write status reports. The shorter the template, the more likely each line says something the team can act on.

The classic three-question template

The default. Best for a new team that needs structure before it needs nuance.

Yesterday: what I moved forward
Today: what I'm focused on
Blockers: anything slowing me down (and what I need)

It works, with one caveat covered at length in the three stand-up questions: answered literally it produces a task diary. The “and what I need” on the blockers line is the small edit that keeps it honest.

The blockers-first template

The same three prompts, reordered so the useful part comes while the room is still awake.

🚧 Blocked on: what's stuck + who can help
🎯 Today: my one main focus
✅ Since yesterday: anything that changes your plan

Reordering looks trivial and isn’t. Leading with blockers signals what the meeting is for, and it gets the most actionable item said first instead of last.

The walk-the-board script (facilitator)

For teams past their first few sprints, run the board instead of the people. This is the facilitator’s script, not a per-person template:

1. "Sprint goal: <one sentence>. On track?"
2. Move right → left across in-progress items:
   - "What's this waiting on?"
   - "What does it need to move?"
   - "Anyone able to help push it over the line?"
3. Blockers → assign an owner to each.
4. Parking lot → confirm who stays for what.

Why this beats the per-person format — and how to facilitate it — is in the daily stand-up agenda.

Async templates for Slack and Teams

For distributed or timezone-split teams, the stand-up moves into a channel. Same brevity, one post per person, posted by a set deadline:

*Stand-up — [date]*
🎯 Focus today:
🚧 Blockers / need help with:
🙌 Anything the team should know:

Keep the main channel to one post each and push every follow-up into a thread, or the channel becomes unreadable by 11am. For the full tradeoffs — timezones, when async wins, how to stop it becoming a wall of ignored updates — see async and remote stand-ups.

What “good” looks like — with examples

A template only helps if people fill it in with signal. The difference:

• Strong: “Blocked — I need the staging DB credentials from Sam before I can test the import.” (A blocker, an owner, an action.)
• Strong: “Checkout is code-complete; starting on the failed-payment states today.” (Progress framed against the work, plus a heads-up.)
• Weak: “Worked on some tickets yesterday, more of the same today.” (Says nothing anyone can respond to.)

The test for any line is simple: would this change what a teammate does today? If not, it belongs in the ticket, not the stand-up.

Make it a habit, then vary it

Use one template unchanged long enough for it to become automatic — a fortnight is about right. Then, if the daily rhythm starts to flatten, borrow a format from the stand-up ideas catalogue rather than letting the template quietly bloat back to a status report. And whichever template you land on, it only works inside a facilitated meeting: see how to run an effective stand-up. The daily stand-up guide hub links the rest — from the agenda to the anti-patterns.

Frequently asked questions

What should a daily stand-up template include?

Three prompts at most: what’s changed since yesterday, what you’re focused on today, and what’s blocking you — with blockers first if you want the meeting to earn its time. A good template is short enough that filling it in takes a minute and pointed enough that it can’t be answered with a task diary. Anything longer trains people to write status reports.

What is a good Slack stand-up format?

One short post per person, blockers at the top, at a set time each morning. Keep it to three lines — focus, blockers, anything the team needs from you — and thread the follow-ups so the channel stays scannable. Most teams either post manually to a dedicated channel or use a stand-up bot or the TeamRetro Slack integration to prompt everyone and collect the replies in one place.

What should you say in a stand-up — with examples?

Lead with anything that changes a teammate’s day. Good: “Blocked — I need the staging DB credentials from Sam before I can test the import.” Good: “Checkout is code-complete; starting on the failed-payment states today.” Weak: “Worked on some tickets, more of the same today.” The test is whether your update gives the team something to act on or respond to.

How do you run an async stand-up in Slack or Teams?

Pick a channel, set a daily deadline (say 10am local), and have everyone post the same short template — focus, blockers, needs. A bot can prompt people and roll the replies into one digest so nobody has to scroll. Reserve threads for the back-and-forth, and escalate any blocker that isn’t moving to a quick live call. See the async and remote stand-ups chapter for the tradeoffs.