A standup is short, so its notes should be shorter. They are not a record of everything each person did yesterday. They are a quick view of who is blocked, what changed in the plan, and which follow-ups somebody agreed to pick up after the call.
The short version
- One block per person: progress, plans, blockers. One line each.
- Each blocker gets an owner: the person who will try to clear it, not only the person who is stuck.
- Routine plans for the day are not action items. “I'll keep working on the importer” is a plan.
- Anything discussed at length moves to a follow-up with the people involved. Note the follow-up, not the discussion.
- Keep yesterday's notes nearby. A blocker that hasn't changed is the most important line in today's.
Three questions are a habit, not a rule
Many teams run their standup around yesterday, today and blockers. The Scrum Guide describes the Daily Scrum as a 15-minute event for the developers to inspect progress toward the Sprint Goal, and it leaves the structure to the team. It also says the Daily Scrum is not the only time developers can adjust their plan. The full description is in the Scrum Guide.
That matters for notes. If your team starts with the sprint goal, put the goal at the top. If you walk the board instead of going person by person, organise the notes by work item. The template below follows the common person-by-person format; change the order to match how your meeting actually runs.
A standup template
Standup · [Team] · [Date]
Sprint goal: [one sentence]
[Name]
- Progress: [done since the last standup]
- Plans: [next]
- Blockers: [none, or what and who will help]
[Name]
- Progress:
- Plans:
- Blockers:
Follow-ups after the standup
- [ ] [Name] will [action] with [Name] by [time]
Still blocked from yesterday
- [Blocker] · since [date]
An example
Here is one person's block and the follow-up it produced:
Priya
- Progress: export API merged; tests pass on staging.
- Plans: start on the CSV column mapping.
- Blockers: no access to the production logs.
Follow-ups after the standup
- [ ] Ben will request log access for Priya from IT today.
Notice what is missing. There is no action for Priya to start on the column mapping. That is her plan for the day, and it will show up in tomorrow's progress. The action belongs to Ben, who offered to help, and it has a time because he said “today”.
Common mistakes
- Turning plans into tasks. A list of everyone's plans as action items hides the one real follow-up.
- Blockers without an owner. “Waiting on design” needs a name: who will ask, and when.
- Long discussions in the notes. If a topic took five minutes, the notes need one line and a follow-up.
- Notes nobody reads. Post them where the team already looks, or keep only the follow-ups.
How Poffle writes standup notes
When a recorded meeting's title contains “standup”, “stand-up”, “daily” or “scrum”, Poffle uses its standup template. It asks the on-device model to note each person's progress, plans and blockers under Progress, Plans and Blockers, using their speaker label, and it tells the model that routine plans for the day are not action items. What remains under Action items are commitments and accepted requests, like Ben's.
Per-person notes depend on knowing who spoke. Poffle labels your microphone You and separates the other voices on the call audio as Speaker 1, Speaker 2 and so on. To put names on them, open Transcript, click a speaker label, and choose an attendee from the calendar event or Enter a name…. Action owners follow the renamed speaker. In a standup around one table, recorded by one microphone, every voice is on your microphone track and is labelled You, so the notes can only tell people apart when names are said aloud.
A remote standup suits Poffle's call handling. When the call app starts using the microphone, Poffle offers Record this call?. Nothing records until you click Record. With Stop when the call ends turned on, the recording stops shortly after the call app releases the microphone, after a 15-second countdown with Keep recording if you want to carry on. Poffle does not announce the recording, so agree with the team that the standup is recorded, and say so when someone new joins.
Tomorrow's standup
A daily standup is a recurring event, so the next occurrence in Agenda shows a Last time brief with points from the previous standup and the actions that are Still open. Choose Open notes there to see yesterday's blockers in full. If a title doesn't contain one of the keywords, open the meeting's options menu and choose Rewrite notes as > Standup.
The templates guide explains detection and the other styles, and the transcript guide covers naming speakers. Recordings, transcripts and notes stay on your Mac, and the notes need Apple Intelligence on a supported Mac and language.
Sources
Official documentation and references used in this guide.