Daily Standup Notes Template
Daily standup (daily scrum) notes — per-person Yesterday / Today / Blockers, with date, team, attendees, and a team-blockers / parking-lot section.
Live preview
DAILY STANDUP NOTES Team: Platform Squad Date: July 16, 2026 Attendees: 6 of 7 (one PTO) Each person answers three questions: what did I do yesterday, what will I do today, and what (if anything) is blocking me. Keep it to ~15 minutes; take detailed discussions to the parking lot. ================== UPDATES ================== Sam Yesterday: Shipped the auth refactor; reviewed 3 PRs Today: Start rate-limiter; pair with Dana 2pm Blockers: None Dana Yesterday: Investigated the flaky deploy Today: Finish flaky-deploy fix; pair on rate-limiter Blockers: Waiting on staging access from IT Priya Yesterday: Wrote the Q3 planning doc Today: Groom backlog; 1:1s Blockers: None Alex Yesterday: Fixed the search bug (#4821) Today: Add tests for search; start export feature Blockers: Blocked: needs the new API key from vendor ============== TEAM BLOCKERS / RISKS ============== - Staging environment is flaky — IT ticket #3391 open. - Vendor API key delay is holding up the export feature. ================= PARKING LOT ================= (topics to take offline / after standup) - Discuss async vs. sync standup format — Sam to propose. - Refactor of the legacy billing module — schedule a spike.
About this template
The daily standup (or "daily scrum") is the most common agile ceremony, and the notes it produces are most useful when they are short, consistent, and focused on **flow, not status reporting to a manager**. The classic three-question format — what did I do yesterday, what will I do today, and what is blocking me — keeps the meeting to about fifteen minutes and surfaces the one thing that actually matters: **blockers**. A standup's real job is to make impediments visible fast so someone can clear them; everything else is secondary. Capturing the notes (rather than letting the meeting evaporate) does three things: it gives absent or distributed teammates an async catch-up, it creates a record of recurring blockers worth escalating, and it feeds the parking lot — the list of topics that came up but should be discussed *after* standup with only the people involved, so the meeting does not balloon. A few practices keep standups healthy: timebox it hard (longer means it has become a status meeting); have people talk to the *board/work*, not to the manager; resist solving problems in the meeting (note the blocker, take the fix offline); and actually follow up on blockers and parking-lot items by the next standup, or the team learns the ritual is theater. This template mirrors that structure — per-person yesterday/today/blockers, a team-wide blockers list for things bigger than one person, and a parking lot — so the notes are quick to fill and immediately useful to anyone who missed the meeting.
When to use it
- Recording a daily standup / daily scrum for an agile team.
- Giving distributed or absent teammates an async catch-up.
- Tracking recurring blockers worth escalating.
- Running a lightweight async standup in a doc or chat.
What to include
- Date, team, and who attended.
- Per person: yesterday, today, and blockers.
- A team-wide blockers/risks list for issues bigger than one person.
- A parking lot for topics to take offline.
- Nothing more — keep it short.
Frequently asked
Related templates
More tools you might like
Hand-picked tools that pair well with this one — same audience, same intent.
A coaching session notes template — coach and client, session focus/goals, agenda, key takeaways/insights, agreed action items, and the next session date.
A daycare daily report for parents — meals and how much was eaten, naps, diaper/bathroom log, activities, mood, supplies needed, and notes from the caregiver.
Daily jobsite log — date, weather, crew + labor hours, work completed by trade, materials + deliveries, equipment, visitors, safety + quality issues, photos referenced. Contemporaneous evidence for schedule + claim + payment disputes.
A Start / Stop / Continue sprint retrospective worksheet with an action-items section (owner + due date) and team/date header.
A substitute teacher day plan — the regular teacher's handoff: daily schedule by period, key contacts, classroom procedures and rules, per-period lesson summaries, and emergency/important notes.
A daily beach lifeguard log — tower / shift details, beach conditions (flag, surf, water temp, UV), hourly attendance estimate, rescues and assists, medical calls, equipment status, and supervisor sign-off.
An eBay item description worksheet — a keyword-rich title, condition and item specifics (brand, model/MPN, size), an accurate description with an honest flaws/defects section, photo checklist, and shipping/returns notes.
Total Daily Energy Expenditure broken into BMR, TEF, NEAT, and exercise.