The daily standup has a reputation problem. In theory it is a focused fifteen-minute alignment — the whole team surfaces what they did yesterday, what they are doing today, and what is blocking them. In practice it is a twenty-five minute meeting where seven people take turns talking at each other while everyone else mentally drafts their grocery list.
The format is not wrong. The execution usually is. And almost always, the problem is the same: there is no structure before the meeting, no record during it, and no accountability after it. People show up, speak, and disperse, and by Tuesday nobody can remember what anyone said on Monday.
The Daily Standup for Project Teams template exists to fix the execution without changing the format. This is a walkthrough of how it works and how to run your first standup with it.
The Daily Standup template is free. Create your Notion account here and grab it from createdigitaltools.com.
The Standup That Wastes Everyone’s Time
The dysfunctional standup follows a predictable pattern. The meeting starts late because someone forgot it was happening. Each person gives a vague update — “still working on the API thing,” “did some stuff on the frontend” — with no connection to specific tasks or deadlines. Blockers are mentioned but not written down anywhere, so they are forgotten the moment the meeting ends. The team lead makes a mental note to follow up with two people and then gets pulled into something else. By the next standup, nothing that was discussed is visible anywhere, and the same blockers come up again.
The root cause is not the people — it is the absence of a system. When standup updates are spoken aloud and not recorded, they evaporate. When blockers are mentioned but not tracked, they persist. When yesterday’s commitments are not visible in today’s standup, there is no accountability. The standup becomes a ritual of reporting rather than a tool for coordination.
What a Good Standup Actually Achieves
A well-run standup achieves three things. It surfaces blockers early, before they become delays. It creates a shared picture of what the team is working on today so people know who to go to for what. And it creates a lightweight accountability loop — yesterday you said you would do X, today you report whether you did it.
None of these require a long meeting. They require a record. The standup that runs in ten minutes and leaves a written log of updates and blockers is worth ten times the standup that runs for thirty minutes and leaves nothing behind.
Why Notion Is the Right Tool for Standups
Standup tools exist. Some teams use Slack bots. Some use dedicated apps. Most of them create friction — they require a separate login, they live outside the workspace where actual work is tracked, and they produce records that nobody goes back to look at.
Notion works for standups because the standup record lives in the same place as the tasks, the projects, and the documentation. An update in the standup can link directly to the task it refers to. A blocker can be tagged with the person who needs to resolve it and connected to the project it is blocking. The record is not isolated — it is part of the workspace.
Inside the Daily Standup Template
The template has four components: a Team Member database, a Daily Entry database, a Blockers board, and a home dashboard that pulls all three together. Each component is simple on its own. Together they create a standup system that runs itself.
The Team Member Database
This is a simple database with one row per team member — name, role, and a link to their individual standup view. It exists primarily as a relation anchor: the Daily Entry and Blockers databases both link back to it, so you can filter any view by team member and see only their updates or their blockers.
Setup takes two minutes. Add one row per team member. The rest of the template references this database automatically.
The Daily Entry Database: The Heart of the System
Each row in the Daily Entry database is one person’s standup update for one day. The properties are: Date (automatically set to today), Team Member (a relation to the Team Member database), Yesterday (a text field for what was completed), Today (a text field for what is planned), and Status (a select: On Track, At Risk, Blocked).
The most important view is the Today view — filtered to Date equals today, showing all team members’ updates for the current day in a clean table. This is the view that displays on the main dashboard and that the team refers to during the standup meeting itself.
A second view called This Week shows all entries for the current week grouped by date. After three days of standups, this view becomes genuinely valuable — you can see at a glance how each team member’s focus has shifted across the week, which tasks keep appearing in the Today column without moving to Yesterday, and where the team’s collective attention is concentrated.
A third view called By Team Member groups entries by the Team Member relation property. Open any team member’s row and you see their complete standup history — every daily entry they have submitted, in chronological order. This is the accountability record that makes the standup more than a daily ritual.
The Blockers Board: Where Progress Gets Stuck
Blockers have their own database, separate from the daily entries, because they need to be tracked until they are resolved — not just mentioned once and forgotten.
Each blocker record has: a description, the team member blocked, the team member or external party who needs to resolve it, the project it is blocking (a relation to your projects database if you have one), a Status (Open, In Progress, Resolved), and a Date Raised. The board view groups blockers by Status — Open in the first column, In Progress in the second, Resolved in the third.
The critical difference from mentioning blockers verbally: they stay visible until someone changes their status to Resolved. An Open blocker raised on Monday is still in the Open column on Friday if nobody has dealt with it. That visibility creates pressure to resolve things rather than defer them.
The Dashboard: One Page for the Whole Team
The home page shows four linked views: Today’s Standup (entries from today), Open Blockers (blockers with Status = Open), This Week’s Entries (all entries from the current week), and the Team Member list. The entire state of the team’s current day and outstanding blockers is visible on one page without opening any individual database.
During the standup meeting itself, this page is the only thing you need open. Team members add their daily entry before the meeting starts. The team lead opens the dashboard and the meeting runs through what is already there — confirming updates, surfacing blockers, moving on. The meeting becomes a review of what has already been written rather than a dictation exercise.
How to Run Your First Standup With the Template
Before the first standup, add all team members to the Team Member database. Send the dashboard link to the whole team and ask everyone to add their daily entry by five minutes before the standup starts.
In the meeting, open the dashboard. Read through the Today view together. For any Status marked At Risk or Blocked, discuss briefly — what is needed to unblock it, who owns the resolution, and by when. Create a Blocker record for anything that cannot be resolved in the next twenty-four hours. Close the meeting. The whole thing should take ten to fifteen minutes.
After the meeting, the record is already there. No meeting notes to write up. No follow-up actions to chase. The blocker board is live. The daily entry history is accumulating. The system has already done most of the administrative work.
Async Standups: Making the Template Work Without a Meeting
For remote or distributed teams across time zones, synchronous standups are often impractical. The template works equally well asynchronously. Set a daily reminder for team members to add their standup entry by a specific time — 10am in their local timezone, for example. The team lead checks the dashboard once entries are in and flags blockers that need attention.
The async version actually produces better records than the synchronous one, because people write more carefully when they know the update will be read rather than spoken over. The Yesterday and Today fields become more specific. The Status selection becomes more honest. The blocker descriptions become more actionable.
What Changes After Two Weeks
After two weeks of consistent standup entries, the template becomes a project record. You can look back at any day and see exactly what the team was working on. You can see which blockers took longest to resolve. You can see which team members consistently flag themselves as blocked — a signal that they may need more support or clearer task definitions.
The standup stops being a daily obligation and starts being a source of information. That shift happens not because the team changed its behaviour, but because the system started capturing what was already happening and making it visible over time.
For teams that need more than standup tracking — a full project management system with task tracking, risk management, budget, and stakeholder management alongside the standup record — the Project Management with AI template is built to cover the complete project lifecycle. The standup template integrates directly with it when both are in the same workspace.
Disclosure: This post contains affiliate links. If you sign up for Notion through the links in this post, we may earn a small commission at no extra cost to you. All opinions are our own.
0 Comments