Standup meeting notes: what to write down and what to skip

This guide covers what is worth recording, what to skip, a template that takes a minute to fill in, and how standup notes feed into retrospectives.

What a standup is for

A daily standup is a short meeting for a team to coordinate: to spot when someone is stuck, when two people are about to collide, and when the plan for the day or the sprint has to change. It is not a status report to a manager, even when it drifts into one.

Notes should serve the same purpose. If a line in the notes would not change what anyone does, it probably does not need to be there.

What to write down

Blockers

Anything stopping someone from making progress, and who is going to help. "Tom blocked on test data for Northwind import — Priya to share the sample file after standup." A blocker that is written down with a name beside it gets resolved; one that is only said out loud is often repeated the next morning.

Changes to the plan

When something moves: a task is dropped, a priority changes, a date slips, someone is off sick and their work is picked up by someone else. These are the things people who missed the standup need to know.

Follow-ups after the standup

Standups work best when discussions are cut short and moved to afterwards. Write down who is meeting about what — "Ana and Marc to discuss the release note wording after standup" — so the parking lot actually happens.

Decisions, if any

Most standups do not make decisions. When one does (say, to hold a release), write it as a decision, and copy it to wherever the team keeps decisions, such as a decision log.

What to skip

• Yesterday's and today's work, item by item. It is in the tracker, or should be. Writing it down twice means one version will be wrong.
• "No blockers." Only note the people who have one.
• Discussion. If the standup turned into a design argument, note that it happened and who is continuing it, not what was said.
• Absences and reasons. Note who is covering, not why someone is out.

A template

For a team that posts notes in a channel or keeps a running page:

### Standup — 25 September 2026

**Blockers**

- Tom: needs Northwind sample data for the import test → Priya shares after standup

**Changes**

- CSV export dropped from this sprint; Marc picks up the date format bug instead
- Ana out Friday; Priya covers release note review

**After standup**

- Ana + Marc: release note wording
- Tom + Priya: import test data

**Decided**

- Hold 2.4 until both open pull requests are merged

On a quiet day this may be two lines. That is fine; it means the day is going to plan.

Keeping it quick

• Write as it happens, not afterwards. If only blockers and changes go in, the note-taker can keep up without asking people to repeat themselves.
• Rotate the job. A different person each week spreads the habit of listening for blockers rather than for status.
• Read out the blockers at the end. Five seconds: "So, Tom needs test data from Priya, and Ana and Marc are staying on for the release note." It catches anything missed.
• Post the notes straight away, in the same place each day.

Recording a standup

Most teams have no reason to record a daily standup. It is short, the information is in the tracker, and a recording of fifteen minutes of status is rarely replayed.

There are exceptions: a team across time zones where some people cannot attend, or a lead who wants to write the notes afterwards rather than during. If you do record one, tell the team, and agree it as a standing arrangement rather than switching it on without saying. A recorder that runs on one person's computer is not visible to anyone else in the call.

Notey can record a standup on your Mac and transcribe it there. If you ask for a summary, it is written from the transcript, and its action items list who agreed to do what; if nobody committed to anything, it says so rather than inventing items. That makes it a quick way to check the blockers you noted, but for a standup the note-taker's one-minute list is usually enough on its own.

From standups to retrospectives

Standup notes are the raw material for a retrospective. A blocker that appears three days in a row, or a change of plan that keeps happening for the same reason, is exactly what a retrospective should look at. Scanning a fortnight of standup notes before a retro takes a few minutes and brings specific examples to the conversation instead of impressions.

Retrospective meeting notes covers how to turn those patterns into changes the team agrees to try. For other kinds of meeting, the general meeting notes template applies, and writing action items that get done covers the follow-ups that come out of standups.

A quick check

At the end of a standup, the notes should answer three questions for someone who missed it:

1. Is anyone stuck, and who is helping?
2. Has anything changed since yesterday?
3. Who is talking to whom afterwards?

If the notes answer those, they are complete, however short they are.

Frequently asked questions

Should you take notes in a daily standup?

Take a few, not many. Blockers, changes of plan and anything agreed to follow up after the standup are worth writing down. Each person's status usually is not.

Who takes notes in a standup?

Whoever runs it, or a rotating volunteer. It takes a minute if you only record blockers and changes, so it does not need a dedicated note-taker.

Where should standup notes go?

Somewhere the team already looks, such as a pinned thread in the team channel or a section of the team's board. A separate document per day tends to go unread.

Are the three standup questions still useful?

What you did yesterday, what you will do today and what is blocking you are a reasonable prompt. For notes, only the third reliably matters; the first two are only worth writing down when they differ from the plan.