Daily Standup Template (Free, Fillable + Example)

Every morning the team gathers, someone reads out what they did yesterday, and 25 minutes later people are still standing in a circle solving a problem that only two of them understand. That is not a standup — that is a meeting with extra steps. The daily standup has one job: synchronize the team quickly so work keeps moving. When it works, it takes 15 minutes. When it fails, it turns into a status report to the manager, a debugging session, or a silent ritual where everyone says “all good” and walks away. A daily standup template keeps the meeting on track by giving every person the same three questions and capturing the one thing that actually matters — blockers.

This article gives you a copy-paste daily standup template, a filled-in example, guidance for remote and async teams, where to find free templates, and the mistakes that quietly destroy the ceremony.

Quick Answer: What Should a Daily Standup Template Include?

A daily standup template should include the three classic questions — (1) What did I do yesterday? (2) What will I do today? (3) What is blocking me? — plus a small space for each person’s name, their task for the day, any help they need, and a visible blocker list. The template’s real job is to surface blockers and hand them to someone who resolves them after the meeting, because the standup itself is timeboxed at 15 minutes and is not the place to solve problems. Add a “sprint goal” line at the top so everyone anchors their daily answers to what the team is trying to finish.

What Is a Daily Standup (and Why Does It Go Wrong)?

The daily standup — called the Daily Scrum in the Scrum framework — is a 15-minute event held at the same time and place each working day. The Scrum Guide defines its purpose as inspecting progress toward the Sprint Goal and adapting the Sprint Backlog as needed. It is not a status report to a manager; it is the developers’ own planning session for the next 24 hours.

The meeting has one output that matters: a shared picture of where the team is and a short list of blockers. Everything else — deep discussion, problem solving, estimation debates — happens after the standup, with the people it concerns. That is why the template matters: it keeps the conversation inside the 15-minute box and marks the overflow for follow-up.

The Free Daily Standup Template (Copy-Paste Ready)

Copy the structure below into a shared document, a board, a chat message template, or your project tool. Fill it in as a group in 15 minutes or asynchronously.

1. Standup Basics

• Date: ____ | Team: ____
• Sprint goal (one line): ____
• Today’s focus / deadline that matters: ____
• Format: live (same time) / async | Facilitator or timer: ____

2. The Three Questions (one line each, per person)

3. Blocker & Help Queue (leave the meeting)

4. After the Meeting (5 minutes, not 15)

• Parking-lot topics (discussed later): ____
• Blockers moved to the task tracker: ____
• Any dates or dependencies updated: ____

Keep the per-person update to 60 seconds. If someone is mid-problem, put the topic in the blocker queue and let the people who can help solve it after the standup.

Filled-In Example: A Standup With Real Numbers

Here is a filled example for an 8-person product team on day 4 of a 2-week sprint.

• Sprint goal: Launch the new onboarding flow to 100% of new users.
• Date: Wednesday, Sprint 6, Day 4.
• Updates (condensed):
• Ana (dev): Yesterday shipped the signup API; today wiring the email confirmation step; no blockers.
• Boris (dev): Yesterday fixed the login redirect bug (JIRA-214); today starting the password reset flow; needs access to the staging database — blocked since yesterday.
• Clara (dev): Yesterday finished front-end of step 1; today QA pairing on the signup form; waiting on Ana’s API docs.
• Dan (QA): Yesterday ran 18 regression cases, 2 failed; today retesting the fixed login; blocked by an environment that keeps resetting.
• Emma (design): Yesterday delivered step 3 mockups; today reviewing the confirmation screen with PM; no blockers.
• Blocker queue (left the meeting): (1) Staging DB access for Boris → escalated to DevOps, resolved within 2 hours; (2) flaky test environment for Dan → owner assigned, environment reset by lunch.
• Parking lot: whether to use a third email provider — discussed later with the PM, not in the standup.

Total meeting time: 14 minutes. Two blockers left the room with owners, and one was resolved the same morning. That is the standup doing its only real job.

How Long Should a Daily Standup Be?

A daily standup should be 15 minutes — no more. The Scrum Guide fixes the Daily Scrum at 15 minutes. For a team of 8–10, that means roughly 60–90 seconds per person. If the meeting regularly runs longer, the cause is usually one of three things: people giving status reports instead of daily plans, problems being solved inside the meeting, or too many people attending who don’t need to be there. The fix is not to lengthen the meeting; it is to move discussion to the parking lot and keep the standup to its template.

How Do You Run a Standup for Remote or Async Teams?

Remote teams have two options: a live video standup at an overlapping time, or an asynchronous standup in a shared channel.

• Live remote standup: same three questions, same 15 minutes, but held on video with cameras on and a shared board visible. The template works unchanged. The extra rule: after each person speaks, the host asks “who needs help with that?” so blockers are caught in the room.
• Async standup: each person answers the three questions in a shared channel or tool before a cutoff time (for example, 10:00 local). The team lead or rotation owner compiles the blocker queue once a day. Async removes the time-zone problem but loses the conversational “I heard you say X, let me help” moment — so blockers need a stricter owner assignment.

For a team spread across four time zones, async is usually the honest choice; forcing everyone to 7am or 11pm for a live meeting costs more focus than the standup saves.

Where Can You Find Free Daily Standup Templates?

Real, reputable sources include:

• Trello — free daily standup board templates with Yesterday / Today / Blockers lists that double as a simple tracker. Trade-off: simple and free, but no reminders or async compilation built in.
• Asana — free daily standup templates that turn each day’s updates into tasks, so blockers become assignable items immediately. Trade-off: better for the tracker half than the 15-minute ritual half.
• Atlassian Jira and Confluence — Jira’s Scrum/board setups include standup-friendly views (backlog, board, reports), and Confluence has daily standup meeting templates. Trade-off: built for teams already inside the Atlassian stack.
• Notion and Miro — flexible standup page and board templates. Trade-off: you build the cadence and reminder logic yourself.
• Async standup tools (Standuply, Geekbot, Range) — automate the three questions through Slack/Teams and compile responses. Trade-off: subscription cost and a dependency on your chat tool, but excellent for distributed teams.

The pattern: free templates give you either a great meeting surface or good blocker tracking. Whichever source you pick, the blocker queue (section 3) is the part you must connect to your real work tracker so nothing discussed in the standup disappears.

What Happens to Blockers Raised in the Standup?

Blockers are the standup’s only deliverable, and they need a process:

1. During the standup, name an owner for each blocker. “This is blocking me” becomes “Boris, you own getting me staging DB access.”
2. Move every blocker into the task tracker the same day with a due time, not just a due date.
3. Escalate anything not resolved within 24 hours. A blocker older than a day is no longer a standup issue; it is a project risk and belongs in a risk review or with the project manager.
4. Review the blocker queue at the end of the week — if the same category of blocker (staging access, missing design specs, unclear requirements) keeps recurring, it is a process problem for the retrospective, not for the daily standup.

Scenario 1: An 8-person engineering team saving 25 minutes a day

Before the template, the team’s standup ran 25–30 minutes because two people debugged live. After adopting the three-question template with a blocker queue and a 15-minute timer, the meeting returned to 14 minutes. Over a 20-day sprint that saves roughly 3–4 hours of team time, plus the developers who used to stand around watching a debugging session got their morning back.

Scenario 2: A remote team of 10 across four time zones

A live standup forced three people to join at 7:30am and two at 10pm. The team switched to an async standup: everyone answers the three questions in a shared channel by 10am their local time; the rotation owner compiles the blocker queue at 11am and assigns owners. Blockers resolved in the same day went from 40% to 75% in three weeks, and the two late-night joiners reclaimed their evenings.

Scenario 3: A 12-person operations team where the standup became a status report

A manager attended and the updates shifted to reporting upward. The fix: the manager stopped attending daily (they get a weekly written summary) and the team adopted the template with the sprint goal on top. Updates shortened from 2 minutes per person to 60 seconds, and the daily meeting dropped from 22 minutes to 14. The blockers — two recurring deployment issues — surfaced within a week and were fixed as tracked tasks instead of being absorbed silently.

Common Mistakes

Mistake 1: Treating it as a status report to a manager. When people report “done” for approval, the meeting stops being a planning event. Managers belong at the standup as participants when needed, not as the audience.

Mistake 2: Solving problems inside the standup. Two people diving into a bug while eight people watch is the classic 25-minute standup. Park the topic, keep the meeting moving, solve it after.

Mistake 3: Going around the room one by one without focus. Without the three questions, updates drift into storytelling. Keep each person to 60 seconds and one line per question.

Mistake 4: Letting blockers vanish. If the blocker queue has no owners and no follow-up, the standup becomes theater. Blockers must leave the meeting as tracked items.

Mistake 5: Inviting people who don’t need to be there. The standup is for people doing the daily work. A 25-person “update circle” is a different (worse) meeting.

Mistake 6: Scheduling it at a time that ruins someone’s day. For distributed teams, an async standup beats forcing one person to join at 7am or 11pm.

Know This Before You Choose

• The template is a discipline device, not a document. Its value is keeping every update to three short answers and forcing blockers to leave the room with owners.
• 15 minutes is the ceiling, not a target. A 10-person team hitting 18 minutes is doing something wrong — usually solving problems in the meeting.
• The sprint goal line matters more than it looks. It anchors “today I will…” answers to what the team is actually trying to ship this week.
• Async is a legitimate choice, not a compromise. For teams across time zones it produces more honest, complete updates than a dragged-together live call.
• Blockers recurring in the same category are a process signal. Handle the daily instance, but take the pattern to the retrospective.

How Can You Run This Template in Doitify?

The part of the standup that usually falls apart is the blocker follow-up — “we talked about it, then nothing happened.” To be transparent: Doitify is our product, which is why we know its capabilities from the inside. In Doitify you can keep your sprint and daily work as tasks and sub-tasks with owners and due dates, run the work on Kanban boards and sprints with a shared backlog, and turn every blocker raised in the standup into a tracked task with a reminder attached — so the 15-minute meeting’s only deliverable is captured where the work lives. Team chat keeps the conversation flowing between standups, and work/performance reports give the weekly review real numbers. If your standup is fine but its blockers keep evaporating, closing that loop is exactly what this workflow is for. Explore project management templates to build the full daily rhythm in one workspace.

Conclusion

The daily standup is a 15-minute synchronization, and a template keeps it honest: the sprint goal on top, three short questions per person, and a blocker queue that leaves the meeting with owners and due times. Copy the fillable template in this article, enforce the timebox, and move every blocker into your task tracker the same day. The team that fixes blockers instead of discussing them will find its standups getting shorter and its sprint goals getting hit more often — which is the whole point of the ceremony.