Weekly Standup Summary Meeting Notes Template
Turn weekly standup updates into structured mind maps with blockers, risks, decisions, and action items.
When to Use This Template
For Scrum/Agile weekly standups, cross-functional weekly syncs, and turning verbal updates into trackable action items.
What You Input
Meeting basics plus each member/module update, blockers, risks, decisions, and action items.
What You Get
A clear mind map and reusable notes structure organized by Overview → Team Updates → Blockers/Risks → Decisions → Action Items.
Template ContentCopy and customize
【Meeting Info】
Meeting: Weekly Standup
Date: YYYY-MM-DD
Time: HH:MM–HH:MM
Sprint/Version: Sprint XX / vX.Y
Facilitator:
Note Taker:
Attendees: A, B, C, ...
【Weekly Goal Review】
Goal 1:
- Status: Completed / Partially Complete / Not Started
- Notes:
Goal 2:
- Status:
- Notes:
【Team Updates (by Person/Module)】
Member/Module: A (e.g., Backend/Payments)
- This Week Completed:
- 1)
- 2)
- Next Week Plan:
- 1)
- 2)
- Blockers/Support Needed:
- Blocker:
- Support needed from:
- Risk Alert (optional):
- Risk:
- Impact:
- Mitigation:
Member/Module: B (e.g., Frontend/Workbench)
- This Week Completed:
- Next Week Plan:
- Blockers/Support Needed:
- Risk Alert (optional):
Member/Module: C (e.g., QA/Quality)
- This Week Completed:
- Next Week Plan:
- Blockers/Support Needed:
- Risk Alert (optional):
【Cross-team Dependencies & Risks】
Dependency 1:
- Depends on:
- Deliverable Needed:
- Expected Date:
- Status: Green / Yellow / Red
Risk 1:
- Description:
- Impact Scope:
- Trigger Condition:
- Mitigation:
- Owner:
【Key Decisions】
Decision 1:
- Content:
- Impact:
- Decision Maker:
- Effective Date:
Decision 2:
【Action Items】
- [ ] Action Item 1 (Owner: Due: YYYY-MM-DD)
- Acceptance Criteria:
- [ ] Action Item 2 (Owner: Due: YYYY-MM-DD)
- Acceptance Criteria:
- [ ] Action Item 3 (Owner: Due: YYYY-MM-DD)
【Next Meeting】
Date: YYYY-MM-DD HH:MM
Prep Needed:
- 1)
- 2)How to Use This Template
- 1Fill meeting info and weekly goal review
- 2Add updates by person/module with blockers, risks, and dependencies
- 3Record decisions and action items with owners, due dates, and acceptance criteria
- 4Generate and share with the team
Frequently Asked Questions
How should I format action items?
Include an owner, due date, and acceptance criteria for each action item.
How do I label blockers and risks?
Use Green/Yellow/Red for status and add impact plus mitigation notes.
Should updates be grouped by person or module?
Both work, but grouping by person/module keeps the mind map clearer than a single narrative.