Astrolinks

Daily standup template: 5 formats you can copy today

Free daily standup templates to copy: classic three questions, async Slack, engineering, non-technical and blockers-first, plus a 15-minute run plan.

A video call with the whole team on a laptop screen
Photo: brian_cragun on Pixabay

Short answer

A daily standup template is a short, fixed set of prompts each person answers every day, usually: what I did yesterday, what I'll do today, and what's blocking me. Copy one of the five templates below, paste it into Slack, a doc or your meeting notes, and keep each answer to two or three lines.

Astrolinks gives each person a daily report written from their own private log. No screenshots. Get it free →

A daily standup is meant to be the shortest meeting of the day. In practice, a lot of them drift into 40-minute status readouts where half the room waits for their turn. A good daily standup template fixes most of that by keeping everyone's answers short, the same shape, and focused on what actually needs a teammate.

Below are five standup templates you can copy as they are: the classic three questions, an async standup template for Slack, an engineering version, one for non-technical teams, and a blockers-first format. After that, you'll find how to run a live standup in 15 minutes and how to choose between live and async.

What is a daily standup template?

A daily standup template is a fixed set of prompts each person answers every day. Everyone uses the same headings, so updates are quick to give and quick to scan. The classic version has three prompts: yesterday, today and blockers.

The template is the easy part. What makes it work is the rule behind it: each answer is two or three lines, and anything that needs discussion moves to after the standup.

Template 1: The classic three questions

This is the standup template most teams start with. It works for any team that shares a goal and roughly the same hours.

Yesterday: what I finished or moved forward

Today: what I'm working on next

Blockers: anything stopping me, and who could help

Example:

Yesterday: Finished the onboarding email sequence draft. Reviewed Priya's landing page copy.

Today: Set up the sequence in the email tool and test it on two accounts.

Blockers: Need the final logo file from design. Ana, can you send it by noon?

Notice the blocker names a person and a time. "Waiting on design" is a complaint. "Ana, can you send it by noon?" is a request someone can act on.

Template 2: Async standup template for Slack

When your team spans time zones, an async standup template replaces the call with a written post. Each person posts at the start of their day in a shared channel, and teammates read when they come online.

:sunrise: Standup for [date]
Done since last update:
- 
Focus today:
- 
Blocked / need help:
- 
Heads-up (optional):
- 

Tips that keep async standups useful:

  • Same channel, same time window. For example, "post within your first hour."
  • Use a thread for replies. It keeps the channel readable.
  • Tag the person who can clear a blocker, so it doesn't get lost.
  • React when you've read it. A quick checkmark tells the writer someone saw it.

Some teams prefer to post at the end of the day instead, so the update reflects what really happened rather than what was planned. We compare the two in daily standup vs. EOD report, and our guide to async check-ins for remote teams covers time zones and rollout.

Template 3: Engineering standup template

Developers usually need a bit more structure: links to tickets, what's in review, and what's waiting on someone else. This version follows the board, not the person.

Shipped / merged: ticket links

In progress: ticket and expected finish

In review, needs eyes: pull request links

Blocked: what, by whom, since when

Sprint goal check: on track, at risk, or off track

Example:

Shipped / merged: APP-412 password reset fix.

In progress: APP-419 rate limiting on the login endpoint, done tomorrow.

In review, needs eyes: PR #881 (small, 40 lines).

Blocked: APP-423 needs the staging database refreshed. Waiting on ops since Tuesday.

Sprint goal check: At risk if APP-423 isn't unblocked by Thursday.

The "Sprint goal check" line matters. The current Scrum Guide describes the Daily Scrum as a 15-minute event for developers to inspect progress toward the Sprint Goal and adapt the plan. It doesn't require the three questions at all: teams can pick whatever structure they like, as long as the focus stays on the goal. This template keeps that focus in every update.

Template 4: Standup template for non-technical teams

Marketing, support, operations and admin teams don't work in sprints, so "sprint goal" means nothing to them. This daily scrum template swaps tickets for priorities and deadlines.

Top priority today: one thing that must get done

Also on my list: two or three smaller tasks

Deadlines this week: anything due, with the day

Need from someone: a decision, a file, an approval

Example:

Top priority today: Send the November newsletter to the full list.

Also on my list: Reply to 12 support tickets. Update the pricing FAQ.

Deadlines this week: Webinar slides to Marco by Thursday.

Need from someone: Sign-off on the newsletter subject line from Jen by 11 AM.

Leading with one top priority stops the update from turning into a long to-do list nobody reads.

A smiling woman with a headset at her desk in an open office
Photo: mv-fotos on Pixabay

Template 5: Blockers-first standup

When a team keeps missing deadlines because problems surface late, flip the order. Put blockers first, and only then the rest.

Blocked or at risk: what, and who can help

Done: one line

Next: one line

Run it like this: go round the room or channel and collect only blockers first. Assign an owner to each. Then, if there's time left, do a quick round of done and next. Often there isn't time left, and that's fine. Blockers are the reason the standup exists.

This format also suits a team that already sends written end-of-day updates. The written update covers done and next, so the live standup can be five minutes of blockers only.

How do you run a daily standup in 15 minutes?

Fifteen minutes is enough for a team of up to about eight people. The rules:

  1. Start on time, every time. Don't wait for latecomers or recap for them.
  2. Same order every day. Alphabetical, or by board column. No "who wants to go next?"
  3. About 90 seconds each. Use the template, two or three lines per heading.
  4. Park discussions. When two people start solving a problem, say "let's take that after" and note it. Only the people needed stay.
  5. Look at the board, not the manager. People should speak to the team. If they're reporting to one person, the standup has become a status meeting.
  6. End with blockers. Read back each one and its owner before you hang up.

If your standup still runs long with these rules, the team is probably too big. Split it, or move to async.

Should your standup be live or async?

Both work. The right choice depends on how your team works.

Choose live when Choose async when
The team shares most working hours People are spread over several time zones
Work is tightly linked, like one sprint People work on mostly separate tasks
The team is new and still building trust The team is settled and writes clearly
Blockers need quick back-and-forth Blockers can wait a few hours for an answer

Many remote teams land on a mix: async updates every day, plus a short live call once or twice a week for anything that needs discussion. Our guide on how to manage remote teams covers a full weekly rhythm with updates, one-on-ones and team calls.

What makes a standup update useful?

The same day, written two ways:

Vague: Worked on the report. Some issues. Continuing today.

Useful: Finished the Q3 numbers in the client report, except churn. Blocked: the churn export from billing fails for October. Sam owns billing access. Today: churn section, then send the draft to Lee.

The useful version takes 30 more seconds and answers the questions a teammate would otherwise have to ask. A few habits get you there:

  • Name the thing. "The Q3 report", not "the report".
  • Say what done means. "Draft sent to Lee" is clearer than "worked on it".
  • Make blockers specific. What's stuck, who can help, and since when.
  • Skip the hours. A standup is about progress and problems, not time spent.

Common standup mistakes

  • Turning it into a status report for the manager. It's a team planning check, not an audit.
  • Solving problems in the meeting. Everyone else waits. Park it.
  • Updates nobody reads. In async standups, if blockers get no reply, people stop posting them.
  • Too many people. Past about eight, split the group.
  • Changing the template every week. Pick one, run it for a month, then adjust.

Astrolinks doesn't run your standup. It helps with the written side. Each person keeps a private log of their workday on their own computer, and at clock-out the app drafts an end-of-day report with Done, Blockers and Tomorrow. They read it, edit it and send it. With the Team plan, reports land in one Team inbox, where managers see an Overview of who has sent and what's blocked. No screenshots, no keystroke logging. Those reports cover yesterday's done and today's plan before the standup starts, so the live call can stick to blockers. See end-of-day reports and Astrolinks for remote teams.

Let the report write itself

Astrolinks keeps a private log of your workday on your Mac and Windows and writes each client’s end-of-day report when you clock out. You check it and send. 7 days of Pro to start, no card.

Questions

What are the 3 questions in a daily standup?

What did I do yesterday, what will I do today, and is anything blocking me? Many teams now reword them around the goal: what moved us forward, what's next, and what's in the way.

How long should a daily standup be?

15 minutes or less. The Scrum Guide sets the Daily Scrum at 15 minutes for the developers. If yours runs longer, move problem solving to a follow-up with only the people who need to be there.

What is an async standup?

An async standup is a written version of the daily standup. Each person posts their answers in a channel or tool at a set time in their own day, and teammates read them when they start work, so nobody has to join a live call.

Is a daily scrum the same as a daily standup?

Close, but not identical. The Daily Scrum is the Scrum event where developers inspect progress toward the Sprint Goal and plan the next day. Daily standup is the broader name many teams use for any short daily sync, Scrum or not.

Should managers attend the daily standup?

They can listen, but the standup belongs to the team doing the work. If people start reporting to the manager instead of talking to each other, it has turned into a status meeting. Managers get more from written updates.

Clock out with the report already written

7 days of Pro to start. No card. Your log stays on your computer.