What a standup template is for
A standup meeting template does two jobs. During the meeting it keeps fifteen minutes from turning into forty. After the meeting it leaves a record short enough that someone will read it. Most standup templates only do the first job, which is why the same blocker can be mentioned for a week without anyone noticing it is the same blocker.
- Focus for the week. One sentence, usually the sprint goal. It is the test for every update: does this move the focus forward?
- Blockers first, with an age. The single most useful field. It turns "still waiting on credentials" into "day four", which is a different conversation.
- One line per person for done and next. Outcomes, not activity.
- Parking lot with names. Anything that needs more than thirty seconds goes here, with the people who need to stay.
- Actions with an owner and a date. Usually one or two. Many days there are none.
The top standup guides agree on four formats. Pick one and put it in the header so nobody has to guess.
- Round robin. Each person answers in turn. Simple, and fine for small teams. The weakness is that people rehearse instead of listening.
- Walk the board. Go through the task board from the items closest to done. Better when work moves between people, because it shows where things are stuck rather than who is busy.
- Blockers first. Read every blocker, assign it, then do quick updates. Good for teams under deadline pressure.
- Async. Written updates by a set time in each time zone. Good for distributed teams, but it needs a named reader or blockers sit unread.
Track blockers across days
This is the part most standup guides leave out. They say to raise blockers and take them offline, but not how to tell whether a blocker is new or has been read aloud every morning since Monday.
Carry the blocker line forward each day and increase the count. On day one, the owner chases it. On day three, the team decides: escalate to someone with more authority, work around it, or change the plan and say so. The fourth example above shows that decision written down with a fallback date. Without the count, teams wait politely for a week and then discover they have lost the sprint.
When a blocker clears, tick it rather than deleting it. At the retrospective, the list of cleared blockers and how long each took is better evidence than anyone's memory. The sprint retrospective template has a sprint facts section where those numbers belong.
Common mistakes
- Reporting to the manager. If everyone faces one person, it is a status meeting. The team should be talking to itself.
- Solving problems in the meeting. Two people debugging while six watch. Park it, name the two, end the standup.
- Activity instead of outcomes. "Worked on X" for three days running means X is stuck, and the update hides it.
- No record at all. Without notes, nobody can say when a blocker started or whether it was escalated.
- A transcript instead of a record. The opposite failure. Nobody reads paragraphs of yesterday's updates.
When to use a different template
A standup coordinates one day. Planning what goes into the next two weeks belongs in the sprint planning template, and looking back on how the sprint went belongs in the retrospective. If your daily meeting has turned into a longer discussion with decisions, use the meeting notes template for that day instead. And if you work alone and want the same habit, a work log gives you done, next and blocked without the meeting.
A standup log that knows which blockers are still open
Save this standup template in Scribelet, write blockers as tasks with dates so they carry to tomorrow's note, and ask your notes which problems keep coming back. Encrypted, free to start.
Free plan, no credit card. See pricing