One-on-one meeting notes: what to record, with a template
How to take one-on-one meeting notes that help: what to record, how to track actions across meetings, and a template you can copy for your next 1:1.
Read the articleBlog · How-to
Daily stand-up notes: a short format that still catches blockers
In short: A daily stand-up should last 15 minutes or less. Each person gives a short update and names any blocker. Write every blocker in your notes with one owner, one next step and a follow-up time, then solve it after the meeting rather than during it. The Scrum Guide does not require the three classic questions, but many teams keep them because they are quick.
What is a daily stand-up?
A daily stand-up is a short team meeting held at the same time every working day. Each person says what they finished, what they will do next, and what is stopping them. In Scrum it is called the Daily Scrum. The Scrum Guide (2020) describes its purpose as inspecting progress toward the Sprint Goal and producing an actionable plan for the next day of work.
A stand-up is not a status report for a manager. Its job is to help the team plan its day and to raise problems early. Notes from the meeting are only useful if they lead to someone acting on a blocker.
How long should a daily stand-up last?
Fifteen minutes or less. The Scrum Guide sets a 15-minute timebox for the Daily Scrum. Asana's stand-up guide gives a range by team size: five people or fewer should take 5 to 10 minutes, six to ten people 10 to 15 minutes, and more than ten people should consider splitting into smaller groups.
What should each person say?
Asana suggests three questions: what did you accomplish yesterday, what will you work on today, and is anything blocking you? The Scrum Guide does not require these questions. It lets the team choose its own structure, as long as the meeting stays focused on progress toward the Sprint Goal. Many teams keep the three questions because they are quick and cover the same ground.
Ask people to keep each answer to one or two sentences. Detail belongs in the work tool, not in the meeting.
How do you write down blockers?
Blockers are the part of the notes most worth keeping, because they are the part most likely to be forgotten. Write each one on its own line, with four fields:
| Field | What to write |
|---|---|
| Blocker | One sentence on what is stopping the work |
| Owner | The one person who will take the next step |
| Next step | A concrete action, such as “ask the vendor for the test account” |
| Follow up by | A date and time, usually the same day |
Restate the blocker before you move on, so the person who raised it knows it was understood. A blocker with no owner is a complaint. A blocker with an owner and a date is an action item.
What does a good stand-up note look like?
Here is a made-up example from a five-person product team, written straight after the meeting. Each line is short enough to scan in ten seconds.
- Yesterday: Layla finished the onboarding screens. Omar fixed the sync bug on Android.
- Today: Omar starts the export feature. Sara reviews the pricing copy with Ahmed.
- Blocker: The payment test account is not active. Owner: Sara. Next step: ask the vendor for activation. Follow up by 15:00 today.
- Blocker: The design for the summary page is not agreed. Owner: Layla. Next step: a 20-minute call with Ahmed after the stand-up. Follow up by Thursday.
Notice what is missing: no long descriptions of code, no discussion of the design, and no status for work nobody mentioned. Those belong in the work tool or the follow-up call.
What do you do when a blocker needs a longer discussion?
Do not solve it in the stand-up. Asana's guidance is to note the issue, move on, and save the deeper conversation for after the meeting, when only the people involved meet. The Scrum Guide says the Scrum Master causes the removal of impediments to the team's progress, so one named person should own the follow-up.
When a discussion goes off topic, ask the speakers to park it for a later conversation. That keeps the meeting inside its timebox without ignoring the problem.
How do you keep stand-up notes useful over time?
- Keep one running log, not a new page each day. Put the date at the start of each entry.
- Review open blockers at the start of each stand-up, and remove the ones that are cleared.
- Carry unfinished actions forward to the next day's list instead of dropping them.
The log also shows patterns. A blocker that appears on several days in a row usually points to a process problem, not a bad day. For turning decisions into owned tasks, read action items from meetings. For a ready-made layout, use the daily stand-up template, and see the definition of a stand-up.
Should you record the stand-up?
Most teams do not need a recording of a fifteen-minute update; the notes are usually enough. If you do record, tell everyone before you start and ask for their agreement. The law on recording conversations differs from country to country, so check the official rules for the place where your team works. This is not legal advice.
Where Echo fits
Echo records on an iPhone or Android phone, or on a Mac from the menu bar, without adding a bot to the call. It writes a transcript, a summary and a to-do list you can check and export. Free accounts get 30 minutes of recording a month, and pricing lists Echo Pro for unlimited minutes.
Frequently asked questions
How long should a daily stand-up be?
Fifteen minutes or less. The Scrum Guide sets a 15-minute timebox for the Daily Scrum. Smaller teams can finish sooner: Asana suggests 5 to 10 minutes for a team of five or fewer.
Do we have to ask the three questions?
No. The 2020 Scrum Guide does not prescribe questions. Many teams keep the three classic ones (what I did, what I will do, what blocks me) because they are quick. Use whatever format keeps the meeting focused on the day's work.
Should blockers be solved during the stand-up?
Usually not. Write the blocker down, name one owner and a follow-up time, and move on. Solve it straight after the meeting with only the people involved, so the whole team does not wait.
Should the stand-up be recorded?
Most teams do not need one, because the notes are enough. If you record, tell everyone first and ask for agreement. The rules on recording conversations differ by country, so check the official source for your location.
Sources
Checked on 30 October 2026.
- The Scrum Guide (2020), Daily Scrum, Ken Schwaber and Jeff Sutherland
- Stand Up Meeting: Format, 6 Steps, and Remote Tips, Asana
Try Echo on your next meeting. Free for 30 minutes a month.
Try Echo free