Standup · Meeting notes · Templates
Daily standup notes: what to write, with a two-day example
By T. Krause
Daily standup notes record what each person finished, what they'll do today and what's blocking them. Here is the format, the difference between a useful line and an empty one, and two consecutive days of notes for an invented team.
Daily standup notes record three lines for each person: what they finished yesterday, what they'll do today and what's blocking them. Below those sit a parking lot for topics that need a longer talk and a list of follow-ups with names. Each person writes their own lines before the meeting, so the call goes on blockers and questions, and anyone who missed it can read where things stand.
Read each day's page against the one before it. Tuesday's "today" line should come back as Wednesday's "yesterday" line, and a blocker should either be gone or have someone working on it. The example in this guide runs over two consecutive days so you can watch that happen. If you'd rather start from a page with the headings in place, copy our free daily standup notes template.
The format
Standup, Wednesday 14 October
Name
- Yesterday:
- Today:
- Blockers:
Parking lot
- Topic, and who will talk about it after the call
Follow-ups
- [ ] Name: action
Repeat the name block for each person, and keep the names in the same order every day so people can find their place.
The three lines come from a long-standing pattern. In It's Not Just Standing Up, Jason Yip lists them as "What did I accomplish yesterday?", "What will I do today?" and "What obstacles are impeding my progress?", and calls them "the minimum number of questions that satisfy the goals of daily stand-ups".
If your team runs Scrum, you can change them. The Scrum Guide describes a 15-minute Daily Scrum whose purpose is "to inspect progress toward the Sprint Goal", and says Developers "can select whatever structure and techniques they want". It doesn't mention the three questions at all. A Scrum team might put the sprint goal at the top of the page and answer against that. A support team might write tickets closed, focus today and escalations. Change the words to fit the work, and keep the same lines for everyone so the page is quick to scan.
What to write on each line
The test for a line is whether a teammate could act on it. The lines in this table are invented.
| Line | Says little | Says something |
|---|---|---|
| Yesterday | Worked on the import | Finished the importer. It reads the sample file without errors |
| Today | Carrying on with the import | Run the importer on the real October file |
| Blockers | Waiting on the office | Need the October file from Rania. Can only test with the sample until it arrives |
Three habits make the right-hand column easier to write.
Say what changed. "Busy with the import" tells the team how you spent the day. "Reads the sample file without errors" tells them where the work stands.
Name the person on any blocker. A blocker with a name can be cleared by someone. "Waiting on the office" gives nobody a next step.
Write "none" when there are none. Don't stretch for something to report. An honest "none" takes two seconds to read.
Leave the discussion out. Standup notes aren't meeting minutes, so who said what during the call doesn't belong on the page. If the team reaches a decision that will matter later, put it in the decision log and leave the standup page short.
Who writes the notes
There are three common setups, and they suit different teams.
Everyone writes before the call. This is the one we'd start with. Each person spends two minutes on their lines before the meeting, and everyone skims the page when the call opens. People then ask about what they read, which takes less time than hearing each update aloud.
One person takes notes live. This suits a team that really won't write in advance. Rotate the job weekly, because the notetaker has to type and can't follow the conversation closely at the same time.
Written only, with no call. This suits remote teams across time zones. Everyone posts by a set hour in their own morning, and one named person reads all the blockers that day and starts a conversation about any that need one. Without that named person, a written standup turns into a page nobody reads.
The parking lot and the follow-ups
These two lists keep the call to 15 minutes, and they keep the notes useful afterwards.
The parking lot takes any topic that runs past two minutes. Yip's name for the habit is "Take It Offline", and he says other discussion "should be deferred until after the meeting". An entry needs the topic and the names of the people who will talk, for example "Do bookings move when a class moves? Priya and Sam after standup". Without names, nobody picks it up.
The follow-ups list takes actions. Use one rule for it: if someone other than the blocked person can clear a blocker, that person gets a follow-up with their name on it. The blocked person usually can't chase the answer and do their work at once. Open each call by checking yesterday's follow-ups, which takes under a minute.
A filled-in example: two days
The team, the project and the notes below are invented. Four people are building online class bookings for a group of public swimming pools: Priya on the back end, Tom on the front end, Anneke on design and Sam leading the project. Rania works in the pools' office, outside the team. The notes use the headings of the standup notes template.
Standup, Tuesday 13 October 2026
15 minutes. Anything that needs more than two minutes goes to the parking lot.
Priya
- Yesterday: finished the timetable importer. It reads the sample file without errors
- Today: run the importer on the real October timetable
- Blockers: the real file hasn't come from Rania, so testing is limited to the sample
Tom
- Yesterday: built the class list page, with filters for pool and day
- Today: add the booking button and the "class full" state
- Blockers: needs Anneke's design for the "class full" state
Anneke
- Yesterday: finished the design for the confirmation email
- Today: design the "class full" state, then sketch the waiting list
- Blockers: none
Sam
- Yesterday: sent the launch plan to the pool managers
- Today: write the test script for Friday's walkthrough with pool staff
- Blockers: none
Parking lot
- If a class moves to another day, do its bookings move with it? Priya and Sam after standup
Follow-ups
- Sam: ask Rania for the real October timetable today
- Anneke: send Tom the "class full" design by lunchtime
Standup, Wednesday 14 October 2026
15 minutes. Anything that needs more than two minutes goes to the parking lot.
Priya
- Yesterday: ran the importer on the real timetable after it arrived at 15:00. 212 of 240 classes imported. The other 28 have no instructor listed, so the importer skipped them. Agreed with Sam that bookings move with a class
- Today: add booking limits to the 212 imported classes
- Blockers: the 28 skipped classes wait until Rania says whether a class with no instructor can be booked
Tom
- Yesterday: added the booking button. Anneke's design came at 12:30, so the "class full" state is only half built
- Today: finish the "class full" state, then start the confirmation email
- Blockers: none
Anneke
- Yesterday: sent Tom the "class full" design at 12:30, then sketched the waiting list
- Today: turn the waiting list sketch into a design, if it's staying in the first release
- Blockers: none
Sam
- Yesterday: asked Rania for the timetable, which reached Priya at 15:00. Wrote the test script. Agreed with Priya that bookings move with a class
- Today: book pool staff for Friday's walkthrough
- Blockers: none
Parking lot
- Is the waiting list in the first release? Anneke and Sam after standup
Follow-ups
- Sam: ask Rania whether a class with no instructor can be booked
- Priya: add "bookings move with a class" to the decision log
What to notice
Line up Tuesday's "today" with Wednesday's "yesterday". Priya, Anneke and Sam each did what they said. Tom did half, and his line says why: the design he needed came at 12:30. Nobody has to ask him about it.
Follow Priya's blocker. On Tuesday the missing file became a follow-up for Sam. On Wednesday it has gone, because the file arrived, and running the importer turned up a different problem with 28 classes. That problem gets its own follow-up on the same page, and her line gives the cause, so nobody has to ask what happened to them.
The Tuesday parking lot item doesn't get discussed during the call. Its answer shows up on Priya's and Sam's Wednesday lines, and because the rule will matter later, it gets a follow-up to go into the decision log.
What the notes tell you about the standup
After a couple of weeks, the pages show you how the meeting itself is working.
- The same "today" line three days running. The task is too large, or the person is stuck and hasn't said so. Ask, and split the work if it needs splitting.
- Blockers are always "none" while work slips. People may not be comfortable raising problems on the page. Raise it privately, for example in a one-on-one.
- The same blocker on several pages. Nobody owns it. Give it a follow-up with a name, and take it to the next retrospective if it keeps coming back.
- An empty parking lot and a call that overruns. The long topics are being discussed in the meeting. Yip's advice here is to "Time the Meetings and publish the results". We'd do that for a few days, which should be enough to show the team the problem, and then stop.
- Lines that say the same thing as the board. If your team already tracks everything on a board, the lines may be repeating it. Yip describes the alternative as "Walk the Board", which structures the meeting around the work items instead of the people. Our sprint board template suits that, and the notes shrink to the parking lot and follow-ups.
Don't use the notes to measure individuals. Once people think their lines are being scored, they write to look busy, and you lose the blockers.
How long to keep them
Most standup pages stop being useful after a week or two, and that's fine. Their last job comes on Friday, when someone writing the weekly status update skims the week's pages for what got done and which blockers are still open. Keep older pages in one parent page so they stay out of the way and you can still search them.
Standup notes in Prompt Notebook
Prompt Notebook is ours, so read this part with that in mind. The daily standup notes template is a page titled with the day's date. It opens with a callout for the 15-minute rule, then has a heading per person with Yesterday, Today and Blockers lines, then Parking lot and Follow-ups, where follow-ups are to-dos with a checkbox. The sample inside uses an invented team, so replace those names with yours.
Use Save as template once with your own names in place, so each day starts from the same headings. In a blocker line, type @ to link the page or database row that's blocked, which keeps the context one click away. When a blocker looks familiar, name it in Ask your workspace: "has the timetable file blocked Priya before?" Ask reads up to eight pages per question, so it can't total a month of standups, and a blocker that lasted longer than that can come back with days missing. Each claim carries a numbered link to its page, so open those before you say how long something has been stuck.
Frequently asked questions
What should daily standup notes include?
For each person, what they finished yesterday, what they'll do today and what's blocking them. Add a parking lot for topics that need a longer talk, with the names of the people involved, and a list of follow-ups with an owner on each. Leave out the discussion itself.
Who should take notes at a daily standup?
Ideally everyone writes their own three lines before the call, which leaves nobody typing during the meeting. If your team won't do that, rotate one notetaker each week. Someone still needs to own the follow-ups, and on most teams that's the team lead or the person who runs the call.
Do you need notes for a daily standup at all?
Not always. A small team in one room with an up-to-date board can get by with a parking lot and follow-ups. Written lines start to pay for themselves when someone is regularly absent, when the team works across time zones or when you write a weekly report from them.
How long should a daily standup take?
Fifteen minutes is the usual limit, and it's the length the Scrum Guide sets for the Daily Scrum. If yours runs longer, check the parking lot. An empty one usually means long topics are being discussed in the meeting.
Can written updates replace a daily standup call?
Yes, particularly across time zones. Agree a time by which everyone posts, and name one person to read every blocker that day and follow up on any that need a conversation. Keep a call for days when a blocker needs several people at once.