How to Run Daily Standups in Notion (Meeting Notes Template)

Daily standups are meant to keep your team in sync—but if your notes live in different Slack threads, Google Docs or nowhere at all, you lose the patterns. You can’t spot recurring blockers, track who’s stuck, or find what was decided last week.

Notion gives you a single workspace where standup notes connect to your tasks, sprints and project boards. You’ll search past updates, filter by team member, and turn blockers into trackable to-dos without switching tools.

This guide shows you how to set up a notion standup template that works whether you’re running Scrum, Kanban or just weekly check-ins. You’ll get a reusable structure, database views, and tips to keep notes useful—not ceremonial.

Why Use Notion for Daily Standup Notes

Most teams either skip note-taking in standups or jot updates in a chat channel that gets buried by lunch. Notion solves both problems by storing every standup in a searchable database that links to your project work.

You get one source of truth. When standup notes live in the same workspace as your Kanban board or sprint plan, you can link blockers directly to tasks, see who worked on what, and review patterns across weeks.

You can filter and report. Notion’s database views let you filter notes by date, team member or project. Need to remember why a feature got delayed? Search for “API blocker” across all standups. Preparing a retro? Pull up the last sprint’s blockers in one view.

If you’re already managing projects in Notion, adding standup notes means fewer tools and less copy-pasting between meetings and tasks.

What to Include in Your Notion Standup Template

A good standup template captures the essentials without turning into a project-management deep dive. You want enough structure to spot problems, not so much that filling it out takes longer than the meeting.

Core properties for your standup database:

• Date (Date property) – When the standup happened
• Sprint or Week (Relation to sprint database, or a Select property) – Groups notes by iteration
• Attendees (Multi-select or Person property) – Who joined
• Project or Team (Select or Relation) – Useful if you track multiple teams
• Facilitator (Person property) – Optional, helps if you rotate who runs it

Inside each standup note page:

• Yesterday / Since Last Standup – Bullet list of what each person completed
• Today / Next Steps – What everyone plans to work on
• Blockers – Anything stopping progress (link these to tasks or a bug tracker if relevant)
• Action Items – Quick to-dos that came up (use a checklist or linked database)
• Notes / Decisions – Optional space for context or quick decisions

Keep sections short. Standups are meant to surface issues, not solve them. If a blocker needs a longer discussion, note it and schedule a separate call.

How to Build a Notion Standup Database (Step-by-Step)

You’ll create a database that stores every standup as a separate page, then build a template so each new meeting starts with the same structure.

Step 1: Create a New Database

Open the Notion page where you want your standup log. This could be inside your team workspace, a project hub, or alongside your sprint board. Type /database and choose Table – Inline (or full-page if you prefer).

Name the database “Daily Standups” or “Team Sync Notes”. The first column will be the standup title—use a naming convention like “Standup – 2025-01-15” or “Week 3 Standup”.

Step 2: Add Properties

Click the + icon in the table header to add new properties. Set up:

• Date (Date type) – The meeting date
• Sprint (Relation to your sprint database, or Select if you don’t track sprints) – Links the standup to the current iteration
• Attendees (Multi-select or Person) – Tag who was present
• Blockers Count (Number, optional) – Helps you spot heavy blocker days at a glance

If you’re running Scrum in Notion, relate standups to your sprint database so you can view all notes for a given sprint in one filtered list.

Step 3: Build the Standup Template

Click the dropdown arrow next to the blue New button in your database, then select + New template. This creates a reusable page layout that appears every time you log a standup.

Add headings and structure inside the template:

## Yesterday / Since Last Standup
- **[Team Member 1]:**
- **[Team Member 2]:**

## Today / Next Steps
- **[Team Member 1]:**
- **[Team Member 2]:**

## Blockers
- **[Team Member or Issue]:**

## Action Items
- [ ] 
- [ ] 

## Notes & Decisions

Customize team member names or remove them if you prefer freeform lists. Some teams add a heading per person; others just bullet updates as people speak.

Save the template. Now every time you click New in the database, you get a fresh standup page with this structure pre-filled.

Step 4: Link Blockers and Action Items to Your Task Database

If you manage tasks in a Notion database (like a backlog or Kanban board), add a Relation property to your standup notes called “Related Tasks”. When a blocker comes up, link the relevant task directly.

This means you can open a task and see every standup where it was mentioned. You can also filter your task board to show only items with blockers flagged in recent standups.

For action items, either use inline checkboxes or create a separate “Action Items” database and relate it to standups. That way action items don’t get lost in meeting notes—they appear in your main to-do views.

Database Views to Make Standup Notes Useful

A flat list of standup notes isn’t helpful after a few weeks. Set up views that let you filter, group and search the information you actually need.

View 1: This Week (Table or List)

Filter: Date is within this week. This gives you a quick view of the current week’s standups. Useful for checking what blockers are still open or what was decided earlier in the week.

View 2: By Sprint (Grouped Table)

Group by: Sprint. If you relate standups to sprints, this view shows all standup notes organized by iteration. Perfect for sprint retros or reviews—you can see patterns across the entire sprint.

View 3: Blocker Search (Table)

No filter, but enable search and sort by date descending. When you need to find a specific blocker or decision, search keywords like “API”, “design review” or a team member’s name. The full text of each standup is searchable.

View 4: Calendar View

Switch to Calendar layout, using the Date property. This shows standups on a calendar grid. Helpful if you run standups only on certain days or want to see gaps where standups were skipped.

You can create as many views as you need. If you work with multiple teams or projects, add filters for “Team = Engineering” or “Project = Website Redesign” to isolate notes.

Tips for Running Effective Daily Standups in Notion

A template alone won’t fix a standup that’s too long, unfocused or ignored. Here’s how to use Notion’s features to keep meetings tight and notes actionable.

Pre-Fill Updates Before the Meeting

Create tomorrow’s standup note at the end of today’s meeting. Share the link in Slack or your team chat, and ask people to drop their updates before the call. This turns the live standup into a quick scan for blockers and questions, not a read-aloud session.

If your team is remote or async, you can skip the live call entirely and treat the Notion page as an async standup. Everyone fills in their section by a set time (e.g. 10 AM), and the team reads through blockers and comments as needed.

Use @Mentions for Blockers and Action Items

Tag people directly in the notes using @[name]. If someone needs to unblock a teammate, mention them in the Blockers section. They’ll get a notification in Notion and can reply or mark it resolved.

This makes accountability visible and keeps blockers from being forgotten.

Link to Your Project Board or Sprint Tracker

Add a Relation property to link standup notes to your main project database. If you’re managing work in a Kanban board or sprint planner, you can see standup updates right alongside tasks.

For teams using agile workflows, consider a ready-made setup like Scrum Board PRO—a complete Notion system with a sprint board, backlog, bug tracker and built-in meeting notes. It connects standups, sprint planning and retros in one workspace, so you don’t have to build every database from scratch.

Keep It Short and Time-Boxed

Set a timer for 15 minutes and stick to it. If a discussion goes long, note it as an action item (“Schedule API sync with [name]”) and move on. The standup note should capture what needs follow-up, not solve every problem on the spot.

Notion’s toggle blocks are handy for longer context. If someone needs to add detail, they can put it inside a toggle so the main note stays scannable.

Review Past Standups During Retros

Before your sprint retro, filter standup notes by the sprint and skim for recurring blockers or themes. Did the same issue come up three times? Did one person always have blockers? Use the data to guide the retro conversation.

This is where running Scrum in Notion pays off—you have everything connected, so you don’t need to remember what happened or dig through chat history.

Example Notion Standup Template Structure

Here’s a filled-in example to show what a typical standup note looks like in practice.

Property	Value
Title	Standup – 2025-01-20
Date	20 Jan 2025
Sprint	Sprint 5
Attendees	Anna, Ben, Clara

Page Content:

## Yesterday
- **Anna:** Finished user login API, deployed to staging
- **Ben:** Reviewed Clara's PR, updated wireframes for dashboard
- **Clara:** Fixed two bugs in the checkout flow

## Today
- **Anna:** Start work on password reset flow
- **Ben:** Design review call at 2 PM, then start homepage mockups
- **Clara:** Test checkout on staging, pick up next bug from tracker

## Blockers
- **Anna:** Need staging credentials for password reset testing (waiting on DevOps)
- **Ben:** Dashboard wireframes blocked until Anna's API is live in production

## Action Items
- [ ] Anna: Ping DevOps for staging access (Slack by 11 AM)
- [ ] Ben: Schedule design review invite

## Notes
- Agreed to push homepage redesign to Sprint 6 if API work runs long

Short, factual, and easy to skim. Anyone reading this a week later knows exactly what was in progress and what got stuck.

How to Automate Standup Note Creation in Notion

Creating a new standup page every day is low-effort, but you can automate it if you want zero friction.

Option 1: Notion Buttons

Add a button to your standup database page that creates a new entry with today’s date. Click the /button block, choose “Add pages to…”, select your standup database, and set the Date property to now(). One click, fresh standup note.

Option 2: Zapier or Make (Integromat)

Set up a daily automation that creates a new standup page at 9 AM every weekday. Use a Zap or Make scenario that triggers on a schedule, then adds a page to your Notion database with the current date and your template applied.

This works well for remote teams doing async standups—everyone wakes up to a fresh page ready to fill in.

Option 3: Recurring Tasks in Notion

Create a recurring task in a separate to-do database called “Create today’s standup note”. When you check it off, it reminds you to click New in your standup database. Low-tech, but reliable if you don’t want to set up automation.

None of these are essential—manual creation takes five seconds—but automation helps if you’re trying to build a daily habit across a team.

Connecting Standups to the Rest of Your Notion Workspace

Standup notes are most valuable when they’re wired into your broader project setup. Here’s how to link them to the databases you already use.

Link to Sprint or Project Databases

Add a Relation property in your standup database that points to your sprint tracker or project list. Every standup then “belongs” to a sprint or project. You can roll up blocker counts, see all standups for a project, or filter by active sprint.

If you’re managing everything in one workspace, check out Digitify’s Notion templates collection for more project-management setups that connect tasks, sprints and meetings.

Embed Standup Notes in Your Sprint Dashboard

Create a linked database view on your sprint dashboard that shows only standups for the current sprint. Use the filter Sprint = [current sprint name]. Now your sprint page shows tasks, backlog, and recent standup notes all in one place.

Use Rollups to Track Blocker Trends

If you track blockers as separate database entries, use a Rollup property to count how many blockers were logged per standup. Sort standups by blocker count to spot problem days. If every standup in a sprint had 3+ blockers, that’s a signal for your retro.

Cross-Reference with Bug Trackers and Backlogs

When a blocker involves a bug, link the standup note to your bug tracker. When a new feature is mentioned, link it to your backlog. This builds a web of context—every task shows which standups discussed it, and every standup shows which tasks it touched.

For teams comparing tools, this level of integration is one reason Notion can replace Jira for small teams—you get flexibility without needing a dedicated project-management admin.

Common Mistakes to Avoid With Notion Standup Templates

Even a good template can fail if you overcomplicate it or let notes pile up unused. Here are the traps to watch for.

Making the Template Too Detailed

Don’t turn your standup template into a project report. If filling out the note takes more than two minutes per person, it’s too long. Stick to yesterday, today, blockers. Move detailed updates to task comments or project docs.

Not Reviewing Past Notes

If nobody ever reads old standups, the database becomes busywork. Build a habit of filtering notes during retros, one-on-ones or when planning the next sprint. The value is in spotting patterns, not just logging updates.

Skipping Action Items

Blockers without follow-up stay blockers. If you note a blocker but don’t assign an action item or link it to a task, it won’t get resolved. Use checkboxes, mentions or linked tasks to make sure someone owns the fix.

Using Standups as Status Reports for Managers

Standups are for the team, not for reporting up. If your notes are written to impress a boss, they’ll be vague and useless. Keep them honest and internal. If you need stakeholder updates, create a separate summary or use a project dashboard.

When to Use a Pre-Built Notion Template for Standups

If you’re setting up standups as part of a larger agile workflow—with sprints, backlogs, bugs and retros—building every database from scratch takes time. A pre-built template gives you the structure and connections already in place.

For teams running Scrum or Kanban in Notion, Scrum Board PRO includes a ready-to-use standup notes database linked to sprint boards, backlogs and meeting logs. You get MoSCoW-prioritized backlogs, burndown tracking, bug logs and a full meeting-notes system—set up in 10 minutes with no subscription fees.

If you just need standup notes and already have a project system, the manual setup in this guide is faster. But if you’re building a full project workspace, a template saves hours of database design and relation mapping.

Making Standups Actually Useful

A Notion standup template won’t fix a dysfunctional meeting, but it will make a good standup better. You’ll have a searchable record, clear ownership of blockers, and a way to see what actually happened across a sprint or project.

Start simple: one database, one template, one view filtered to this week. Add automation, rollups and linked databases only when the basic habit is working.

If your team is already using Notion for tasks or projects, standup notes belong in the same workspace. Connect them to your project-management setup, your sprint tracker, or your freelance client workspace—wherever your work lives.

The goal isn’t perfect notes. It’s a lightweight system that surfaces blockers, tracks follow-up, and gives you data to improve how your team works.

Frequently asked questions

Can I use a Notion standup template for async standups?

Yes. Create the standup note page and share the link with your team. Set a deadline (e.g. everyone fills in their section by 10 AM), then review blockers and comments asynchronously. This works well for remote or distributed teams across time zones.

How do I link standup notes to tasks in Notion?

Add a Relation property in your standup database that connects to your task or project database. When you mention a blocker or action item, link the relevant task. This lets you see which standups discussed a task and filter tasks by standup mentions.

Should I create a new standup database for each sprint?

No. Use one standup database for all meetings, then add a Relation or Select property to tag which sprint or project each standup belongs to. Filter or group by sprint to view notes for a specific iteration.

Can I automate creating a new standup note every day in Notion?

Yes. Use a Notion button block that adds a new page with today's date, or set up a Zapier or Make automation that creates a daily standup entry at a scheduled time. Manual creation only takes a few seconds, so automation is optional.

What's the best way to track blockers from standup notes in Notion?

Either use a separate Blockers database and relate it to standup notes, or add a multi-select or text property in your task database called Blocker. Link each blocker mentioned in a standup to the relevant task so you can filter your board by blocked items.

Do I need a paid Notion plan to use a standup template?

No. The free Notion plan supports databases, templates, relations and all the features you need for standup notes. Paid plans add version history, advanced permissions and more storage, but aren't required for basic standup tracking.