Daily Standup Template
A daily standup is a fifteen-minute meeting at the start of the day where each person answers three questions: what did I finish yesterday, what am I doing today, and what is blocking me. The notes template below keeps those three questions, adds blocker-age tracking, and includes a filled-in example.
The most common failure of a standup has nothing to do with the notes template. It happens when the meeting turns into a progress report to a manager. At that point everyone speaks to one person instead of to the team, and fifteen minutes becomes forty.
This page covers the template structure, how to keep the meeting from expanding, an example from a five-person engineering team, common mistakes, and a short FAQ.
A .docx file that opens in Word, Google Docs and LibreOffice.
When to use this template
This template fits teams working on a daily cadence: product engineering, operations, or a project team in a final push. The ideal size is three to nine people. Above nine, fifteen minutes is not enough and the group should be split.
If your team meets weekly rather than daily, the weekly team meeting template is a better fit because it adds progress-by-workstream and decision sections.
A standup is not where problems get solved. When a blocker needs a real discussion, record it and hold a short follow-up straight afterwards with only the people involved. This template has a field for exactly that.
Daily standup notes structure
The seven fields below are enough for a standup. They are deliberately short, because a longer template produces a longer meeting.
| Field | How to fill it in |
|---|---|
| Date and team | The calendar date and the team name. Use the date rather than a session number, because standups get skipped on holidays and the numbering drifts. |
| Who is missing | Recording absentees is enough, there is no need to list who attended. For a small team meeting daily, the absent list is much shorter than the present list. |
| Yesterday | One line each, recording a finished result rather than an activity. Met with design is an activity, locked the checkout screen layout is a result. |
| Today | One or two items per person. If someone lists five items for a single day, that is a sign priorities have not been chosen, not that a lot will get done. |
| Blockers | What is blocked, who is blocked, and who needs to unblock it. This is the most important field in the template, because it is the only reason a daily meeting justifies itself. |
| Blocker age in days | How many consecutive days this blocker has appeared. This number is the cheapest early-warning signal a team can generate for itself. |
| Take it offline | Topics that need a deeper discussion, with the names of who will stay behind. Writing something here is a polite way to end a spiralling debate without cutting anyone off. |
Filled-in example
An example from a five-person engineering team in the week before a release. The details are illustrative.
| Field | Example content |
|---|---|
| Date | Tuesday 21 July 2026, Product team |
| Missing | Mai (on leave) |
| Linh · Yesterday | Finished pagination for the search screen, merged to main |
| Linh · Today | Writing tests for pagination, starting the date filter |
| Hung · Yesterday | No progress on bulk import, still waiting on sample data |
| Hung · Today | Switching to file upload error handling while waiting |
| Blockers | Test environment has no sample data. Hung is blocked. Quan will unblock, committed for today. |
| Blocker age | 3 days. If it reaches day four, escalate to the manager. |
| Take it offline | Naming convention for filter parameters. Linh and Nam stay 10 minutes. |
Keeping the standup to fifteen minutes
The main reason standups expand is that someone starts solving a problem on the spot. A technical question comes up, two people begin working through it, and the other three stand listening to a conversation that does not involve them.
The most effective countermeasure is one person keeping time, not necessarily the manager, with the authority to interrupt using a fixed phrase such as let us take that offline. When the phrase is used consistently and without any edge to it, the team adapts within a week.
Another approach is standing rather than sitting, which is where the name comes from. Mild physical discomfort is a self-limiting timer, and it works better than any reminder.
Speaking to the team, not to the manager
The clearest sign a standup has broken is that people look toward the manager while they speak. At that point the meeting is no longer peer synchronisation but a status report, and blockers get understated because nobody wants to report being stuck.
The fix shows up in what gets recorded. If the notes only capture what each person did, they are a report. If they capture who is blocking whom and who is unblocking whom, they are a dependency map of the team, and that is the version worth having.
When a manager does attend, a good practice is for them to speak last rather than first. Whoever speaks first sets the frame for the whole meeting.
Counting how long a blocker has lasted
This is a small detail that changes the value of standup notes entirely. A blocker appearing for one day is normal. The same blocker on day three means the current approach to removing it is not working.
Agree a fixed threshold in advance, say three days, and when a blocker reaches it, escalate automatically to whoever can allocate resources. Agreeing the threshold up front turns escalation into a process rather than a personal act, so nobody hesitates to trigger it.
The number is also good quarterly data. If most blockers routinely exceed the threshold, the problem is in how the team is structured rather than in any individual incident.
Standups for distributed teams across time zones
When a team spans time zones, a synchronous standup gets expensive because someone always meets outside their working hours. The alternative is an asynchronous standup: everyone writes their three answers in one shared place before an agreed cut-off time.
The template on this page works unchanged for that format, except each person fills in their own rows. The blocker field needs more detail than usual, because there is no chance to ask a follow-up question immediately.
The field to keep is take it offline. In an asynchronous standup it becomes the list of short calls to schedule that day, and dropping it means complex blockers drift for days without anyone discussing them.
Five common daily standup mistakes
Technical questions that need real discussion belong in a follow-up with the relevant people. Holding this line is the only way the meeting stays short.
Worked on payments says nothing. Finished the refund flow, notification to the customer still open says something.
If nobody is ever blocked, the more likely explanation is reluctance to speak up rather than everything running smoothly. In that case the facilitator should ask each person directly.
One person talking for three minutes costs a nine-person team twenty-seven minutes. Everyone should fit in a minute, and that only works when people prepare before walking in.
Without notes there is no way to know how long a blocker has been open. A very short record is enough, what matters is that it exists and lives in one place.
FAQ
How long should a daily standup be?
Fifteen minutes is standard for a team under ten people. If it regularly runs over, the cause is almost always that the meeting is being used to solve problems rather than to synchronise.
Do standups need written notes?
Yes, but very short ones. The main value is not recording who did what, it is tracking how many days a blocker has been open, which nobody remembers accurately without a written record.
Should managers attend the standup?
They can, but they should speak last and avoid questions that read as challenging progress. When a manager leads, the meeting becomes a status report and blockers get understated.
How do distributed teams run a standup?
Asynchronously: everyone writes their three answers in one shared place before an agreed cut-off. This template works unchanged, the blocker field just needs more detail because immediate follow-up questions are not possible.
How is a standup different from a weekly team meeting?
A standup synchronises within the day and focuses on blockers. A weekly meeting reviews progress by workstream and is where decisions get made. They serve different purposes and do not substitute for each other.
Record the standup and let Meco summarise it
For standups held in a room, Meco records the meeting and separates out blockers and action items with named owners, so nobody has to listen and type at the same time.
Meco captures both in-person meetings and phone calls, the situations where conferencing platform bots cannot join. The free tier includes 5 hours for life.
Try it free