The purpose is not to report activity to a manager. It is to help the team inspect progress toward its goal and adapt the plan.
Daily standup template at a glance
| Item | Recommendation |
|---|---|
| Best for | Fast team coordination around one shared goal |
| Core prompts | Completed, next, blockers, help needed |
| Live duration | Usually 15 minutes or less |
| Async use | Post by an agreed deadline and respond to blockers |
| Move elsewhere | Detailed problem solving, planning, and performance evaluation |
Copyable daily standup template
# Daily standup: [Team or project]
**Date:** YYYY-MM-DD
**Goal or sprint:** [Current outcome]
## Team updates
### [Name]
- **Completed since last update:** [Finished outcome]
- **Next:** [Most important planned outcome]
- **Blockers:** [Blocker, decision, or “None”]
- **Help needed from:** [Name or team]
## Blocker board
| Blocker | Impact | Owner | Next action | Due |
|---|---|---|---|---|
| [Blocker] | [What cannot move] | [Name] | [Action] | YYYY-MM-DD |
## Follow-up after the standup
- [ ] [Discussion or action] · **People:** [Names] · **When:** [Time]
## Parking lot
- [Topic that needs a separate conversation]
What should a daily standup include?
Each update should answer four practical questions:
- What outcome was completed since the previous update?
- What is the most important outcome before the next update?
- What is blocked or at risk?
- Who can help, and what response is needed?
“Worked on the report” describes activity. “Completed the first draft and sent it for legal review” describes a result and makes the next dependency visible.
Yesterday, today, blockers: useful but not mandatory
The familiar “yesterday, today, blockers” format is a simple memory aid. It is not the only valid format.
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 Sprint Backlog. It does not require those three exact questions.
Use the wording that produces the clearest coordination for your team. Outcome, next priority, blocker, and help needed is often more actionable than a diary of tasks.
How to run a short standup
Start from the goal
Show the sprint, project, or operational goal at the top. Updates without a shared goal can become unrelated status reports.
Discuss blockers, not every detail
A blocker entry should name its impact and the person who can move it. “Waiting for finance approval, which blocks purchase by Friday” is clearer than “finance issue.”
Park long discussions
If a topic needs analysis, add it to the follow-up section with the smallest necessary group. Do not make the whole team watch two people troubleshoot.
Close the loop
At the next standup, check whether yesterday’s blocker was resolved. A blocker board that never clears is only a list.
Async daily standup template
The same document can support an asynchronous team.
Set three rules:
- updates are posted by a known time in a named time zone;
- blockers receive an acknowledgement within a defined window;
- complex discussions move to a thread, call, or work item.
Do not require people to repeat information already visible in the project system. Link to the relevant work item and explain only what changed or needs help.
Completed standup example
### Mei
- **Completed since last update:** Approved the revised email copy with compliance.
- **Next:** Load the approved copy and send the internal test by 15:00 SGT.
- **Blockers:** The French translation has not arrived; launch can continue in English only.
- **Help needed from:** Ana to confirm whether French ships one day later.
## Blocker board
| Blocker | Impact | Owner | Next action | Due |
|---|---|---|---|---|
| French translation missing | French launch may move by one day | Ana | Decide split launch or move all markets | 2026-10-02 |
This update makes the decision and consequence visible. It avoids a long narration of yesterday’s work.
Daily standup versus weekly status report
A daily standup coordinates near-term work within a team. A weekly status report briefs stakeholders on progress, confidence, risks, decisions, and next week.
Do not make the standup note perform both jobs. Stakeholders usually need a concise weekly summary rather than every person’s daily update.
Common standup mistakes
- Reporting to the facilitator instead of coordinating with the team.
- Listing activity without a completed or planned outcome.
- Saying “no blockers” when a decision or dependency is pending.
- Solving every problem during the meeting.
- Carrying the same blocker without an owner or escalation.
- Requiring duplicate updates in the note and the task system.
- Using standup updates to assess individual performance.
Daily standup FAQ
How long should a daily standup be?
In Scrum, the Daily Scrum is a 15-minute event. Other teams can choose a shorter or asynchronous format, but the meeting should remain focused on coordination.
Is a daily standup only for software teams?
No. Marketing, operations, events, support, and other teams can use the format when work is interdependent and needs frequent coordination.
Should managers attend?
Attendance depends on the team and method. A manager should not turn the meeting into individual reporting. The people coordinating the work need space to adapt their plan.
What counts as a blocker?
A blocker is anything that prevents or materially delays the next outcome: a missing decision, access, information, approval, dependency, or resource.
Can the standup be asynchronous?
Yes. Define the posting deadline, response expectation for blockers, and place for follow-up discussion.