I can't believe how well this Notion daily planner helps me focus

TL;DR

Create a dedicated “my day” checkbox property in the tasks database; use it as the single source of truth for what appears in the Execute list.

Briefing Cornell Notes

Briefing

A daily planning system in Notion becomes dramatically more effective when it forces an “execute” list to start empty every day, then only fills it with a deliberately chosen set of tasks. The core idea is simple: plan what matters, work from a clean short list, and clear it at day’s end—so overdue clutter never accumulates and “due today” doesn’t silently turn into a permanent backlog.

The build centers on a page called “my day,” organized into three sections: **Plan**, **Execute**, and **Wrap-up**. In the morning (or the night before), the user checks a **“my day”** checkbox on tasks in the Plan area. That checkbox doesn’t move tasks into a new place; instead, it makes them appear in the **Execute** view through database filtering. Execute is designed to be the day’s tight working list—blank at the start, populated on purpose, and then cleared when the day ends.

The Execute view is the heart of the system. It’s created by copying a linked database view from a base task manager template and then changing the view’s filter criteria: it shows only tasks where **my day is checked**. To keep the list usable, sorting is removed so tasks can be drag-and-dropped into the order the day will actually be tackled. The result is a focused queue rather than a dashboard of everything that’s “due,” “overdue,” or “urgent.”

At the end of the day, a **“clear my day”** button in the Wrap-up section unchecks the **my day** property for tasks that were selected for that day. In practice, this empties Execute again so the next planning session begins from a blank slate. The button is implemented as a Notion “edit pages in action” workflow: filter tasks where **my day is checked**, then set **my day** to unchecked. A confirmation prompt (“Are you sure…”) can be added to prevent accidental clearing.

Because clearing can feel like losing context, the system adds table-style views that help recover and refine tasks later. A **“clear my day” table view** lets users quickly edit properties (like project or due date) for tasks that didn’t get done before clearing. Additional views support planning the next day: **“review calendar”** surfaces tasks with hard deadlines, while **“plan tomorrow”** lists tasks most recently edited—often the ones that just got cleared—so the user can rebuild tomorrow’s list efficiently.

Finally, the system adds prioritization through three select properties—**energy**, **location**, and **P/I** (process vs immersive). These properties are added to the underlying tasks database, pinned so they appear when viewing any task, and then used to create drag-and-drop grouped views inside my day. The grouping lets tasks be batched by mental energy, errands vs home/office, and whether they’re meant to be started (process) or require full attention (immersive). The practical payoff is sequencing: get process tasks rolling, then switch into immersive work without having blocked tasks pile up behind long focus sessions.

Cornell Notes

The “my day” dashboard in Notion is built around one rule: the Execute list must be empty at the start of each day, then filled only with tasks deliberately selected for that day. A checkbox property called “my day” drives the system—checking it on tasks in the Plan area makes them appear in Execute via database filters. A “clear my day” button unchecks that property for all selected tasks, emptying Execute again so overdue clutter doesn’t accumulate. To prevent losing context, table-style views and next-day planning views help users edit unfinished tasks and quickly rebuild tomorrow’s list. Optional prioritization tags (energy, location, and P/I) further improve ordering by batching similar work and sequencing process vs immersive tasks.

How does the system ensure the daily working list stays clean instead of turning into an overdue backlog?

Execute is filtered to show only tasks where the “my day” checkbox is checked. That means the list isn’t based on “due today” or “overdue” status; it’s based on deliberate selection. At day’s end, the “clear my day” button runs an action that edits tasks where “my day” is checked and sets “my day” to unchecked, which empties Execute again for the next planning session.

What’s the difference between the Plan views and the Execute view in this setup?

Plan is essentially the underlying task manager views (due today, overdue, inbox, everything else), where tasks are reviewed and the “my day” checkbox is checked. Execute is the focused list view that shows only tasks with “my day” checked. Execute also removes sorting so tasks can be drag-and-dropped into the order the user intends to do them.

Why does the tutorial add extra views after clearing the day?

Clearing unchecks “my day,” so tasks disappear from Execute. Users can still recover and refine them using table-style views that let them edit key properties (like project or due date) before clearing again. The system also includes “review calendar” for tasks with hard deadlines and “plan tomorrow” for tasks sorted by last edited time so recently cleared items percolate to the top.

How are prioritization tags implemented, and what do they change operationally?

Three select properties—energy, location, and P/I—are added to the tasks database. They’re pinned so they appear when opening tasks from other views. Inside my day, duplicate views are grouped by each property (group by energy, group by location, group by P/I) with filters still requiring “my day” checked. This enables drag-and-drop batching and ordering by mental energy, where the work happens, and whether tasks are process or immersive.

What does “P/I” (process vs immersive) help with in daily execution?

Process tasks are meant to get the ball rolling and then run in the background (examples include starting something like heating an oven or sending details so someone else can act). Immersive tasks require full focus for the duration. Sequencing them matters: starting process tasks first can reduce the number of blocked items waiting behind long immersive work sessions.

Review Questions

If Execute is filtered only by the “my day” checkbox, what exact action makes the list reappear the next day?
How would you modify the system if you wanted Execute to be sorted by due date instead of allowing drag-and-drop ordering?
What properties should be edited in the table-style “clear my day” view to avoid losing important context after clearing?

Key Points

1
Create a dedicated “my day” checkbox property in the tasks database; use it as the single source of truth for what appears in the Execute list.
2
Build Execute as a filtered view that shows only tasks with “my day” checked, and remove sorting so tasks can be manually ordered by drag-and-drop.
3
Add a “clear my day” button that unchecks “my day” for all tasks currently selected, ensuring Execute starts empty each day.
4
Include recovery and planning views (table-style edits, “review calendar,” and “plan tomorrow”) so clearing doesn’t erase useful context.
5
Add prioritization select properties—energy, location, and P/I—and use grouped drag-and-drop views to batch similar tasks and improve sequencing.
6
Pin “my day” and the prioritization properties so they remain visible when opening tasks from other parts of the system.
7
Lock the tasks database after structural changes to reduce accidental edits, especially when collaborating.

Highlights

The Execute list is intentionally blank every morning: checking “my day” populates it, and the “clear my day” button empties it again at day’s end.

Execute is driven by a checkbox filter, not by “due today” status—preventing overdue clutter from silently taking over.

A “clear my day” table view solves the biggest psychological issue with clearing: unfinished tasks can be updated (e.g., project/due date) before they disappear.

Drag-and-drop batching comes from grouped views using energy, location, and P/I, letting users sequence process work before immersive focus.

“Plan tomorrow” uses last edited time so tasks that were just cleared naturally rise to the top for quick rebuilding.

Topics

Notion Daily Planner
Database Views
Task Execution
Checkbox Filtering
Prioritization Tags

Mentioned

Thomas Frank