Get AI summaries of any video or article — Sign up free
Notion Daily "Action Zone" Dashboard Design (Life OS) thumbnail

Notion Daily "Action Zone" Dashboard Design (Life OS)

August Bradley·
6 min read

Based on August Bradley's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

The “today” action list is filtered to show only tasks that are actionable now: due on or before today, not done, not waiting, and owned by the user.

Briefing

A daily “Action Zone” dashboard in Notion is built to keep execution laser-focused: it surfaces only what’s doable today, prioritizes by a “do date” system, and uses simple checkboxes to track completion, waiting, and dependent task chains. The payoff is behavioral—less time deciding what to do next and fewer tasks slipping through cracks—because the dashboard continuously rolls forward the right items as the day advances.

At the top level, the dashboard uses collapsible toggles to present different time horizons—today, tomorrow, upcoming week—plus a “weighting” section for tasks in someone else’s court and a “dependent” section for tasks that unlock only after earlier steps finish. A “not to-do” list in red acts as a behavioral guardrail, calling out common distraction patterns (tangents, rabbit holes, erratic starts, perfectionism in early drafts, and unhealthy late-day habits). The intent is to prevent the screen from becoming a cluttered to-do list and instead keep attention on the next actionable moves.

The core of the system sits in the “today” toggle. An embedded, filtered view of the action items (tasks) database shows anything with a due date on or before today—specifically tasks that are not marked done and not marked waiting, and where the owner is the user. Sorting starts with “do date” rather than “due date,” reflecting a central rule: every action item has a do date (or is dependent on another task that has one). This makes the list operational—what must be handled now—while the “due date” functions as an awareness flag.

Tasks are further organized by priority and time. The dashboard supports “immediate/quick” items that take minutes, plus “time items” that include an actual scheduled time. Priority is used to batch a small number of major items per day (typically two or three first-priority tasks, unless short tasks justify adding a fourth or fifth). Items without a specific time can be marked as errands, while handoffs to others become “waiting,” removing them from the main actionable view and surfacing them in a dedicated waiting list.

Execution is paired with daily tracking. A second embedded slice of the daily tracking database—filtered to today—captures morning routine completion (including bullet planner, mindset work, and visualization), then tracks what happens through the day. At day’s end, the system schedules tomorrow’s remaining items and records two scorecard percentages: time spent on scheduled work (“on schedule”) and output completed versus intended (“on target”). Low scores trigger self-calibration; repeated low performance prompts review of what’s going wrong.

The dashboard also manages dependencies and pipeline work. Dependent tasks are displayed as “next in line,” with a plus mark indicating the chain progression; completing one step assigns the do date to the next. For work in motion, the dashboard links tasks to production pipeline workspaces and client workspaces, so opening a task can jump directly into the relevant project context.

Finally, the interface balances micro-focus with situational awareness. A due-date calendar view (based on scheduled dates, not do dates) helps redistribute work across days before any single day becomes unmanageable. Less frequent but important sections—active clients, active projects, and goal outcomes with progress bars—provide quick access without pulling attention away from the day’s ordered action list. The system’s guiding principle is simple: plan the night before, execute minute-to-minute on today’s viable items, then review and roll forward regularly so weeks and months fall into place.

Cornell Notes

The “Action Zone” dashboard is designed to make daily execution in Notion feel inevitable: it shows only actionable tasks for today, sorted by a “do date” system and then by priority. Tasks that are done, waiting on others, or not owned by the user are filtered out to prevent clutter. A daily tracking slice records morning routine completion and produces end-of-day scorecards for both time-on-plan and output-on-plan, which helps calibrate whether the day’s commitments were realistic. Dependencies are handled through “next in line” chains that assign do dates as earlier tasks complete. A due-date calendar view then supports redistribution so no single day grows out of control.

How does the dashboard decide what belongs in “today” versus what should be pushed out?

“Today” is driven by a filtered view of the action items/tasks database. The filter includes tasks with a due date on or before today, but excludes anything marked done (checked in the done property) and anything marked waiting (waiting checkbox). It also requires ownership: the owner field must contain the user, so the list stays personal rather than team-wide. The result is a short, viable set of tasks that are actionable now, not a backlog that accumulates indefinitely.

Why use “do dates” instead of “due dates” as the primary sorting mechanism?

The system treats “do date” as the operational trigger for action—what must be handled now—while “due date” is an awareness marker. The dashboard sorts first by date using do dates, and it relies on a rule that every action item has a do date or is dependent on another task that has a do date. This prevents the common failure mode where tasks only appear when they’re already late, and it keeps the day’s plan realistic and doable.

What’s the role of priority and batching in keeping the day manageable?

Priority is used to batch a small number of major items. The dashboard avoids having multiple tasks share the same priority unless they’re intentionally grouped for batching (for example, recording multiple videos in one sitting). The system aims for two or three major first-priority items per day; if a fourth or fifth is added, it’s typically because those tasks are short enough to fit. Time-specific items are labeled with an actual time, while errands can be marked without a specific time.

How does the dashboard handle tasks blocked by other people?

Tasks that depend on someone else are marked as waiting. When waiting is checked, the task disappears from the main “today” actionable list and appears in a dedicated waiting section. The waiting list is intentionally low-friction: it doesn’t require due dates or priorities because waiting items aren’t directly actionable. During weekly review, waiting items can be assigned a follow-up due date and a quick priority (e.g., “quick” for a one-sentence check-in), which moves them back into scheduled action.

How do dependent task chains work in this system?

Dependent tasks are organized as “next in line” items. A chain is set up so that when the first task in the sequence is completed, the next task receives a do date (and becomes the actionable step). The dashboard uses a plus mark to indicate dependent tasks, and completing one step triggers the due date assignment for the following step. This keeps multi-step workflows from stalling because the next action isn’t forgotten.

What does the end-of-day scorecard measure, and how is it used?

The daily tracking slice records two percentages. One measures time spent on scheduled work (“on schedule,” e.g., 70% time on plan). The other measures output completed versus intended (“on target,” e.g., 65% completion). The system uses the combination to diagnose mismatches—such as spending 70% of time on plan but completing only 40% of intended output, which suggests the day’s commitments were unrealistic. Repeated low scores trigger a review and adjustment for future days.

Review Questions

  1. If a task is not done but is currently blocked by someone else, which checkbox should be used so it doesn’t clutter the actionable “today” list—and where should it appear instead?
  2. How does the do date rule prevent tasks from piling up as a “fantasy wishlist,” and what happens when a task isn’t viable for the current day?
  3. What diagnostic value comes from comparing “on schedule” (time) versus “on target” (output) percentages at the end of the day?

Key Points

  1. 1

    The “today” action list is filtered to show only tasks that are actionable now: due on or before today, not done, not waiting, and owned by the user.

  2. 2

    Sorting is anchored on “do dates” (what to act on now), with “due dates” used as an awareness layer rather than the primary driver.

  3. 3

    A red “not to-do” list functions as a behavioral checklist to prevent predictable distraction and perfectionism traps.

  4. 4

    Waiting items are removed from the main execution list and tracked separately, then converted back into actionable follow-ups during review.

  5. 5

    Dependent task chains use “next in line” progression so completing one step assigns the do date to the next step automatically.

  6. 6

    Daily tracking turns execution into a scorecard by measuring both time-on-plan and output-on-plan, enabling calibration when commitments are unrealistic.

  7. 7

    A due-date calendar view supports redistribution across days so no single day becomes overloaded, replacing manual Kanban-style sorting for daily actions.

Highlights

The dashboard’s core filter keeps “today” clean: tasks must be due on or before today, not done, not waiting, and owned by the user.
“Do dates” drive the system—every action item has a do date or depends on another task with one—so the list reflects what must happen now.
Waiting and dependencies are treated as first-class states: waiting moves tasks out of the main list, while dependent chains assign the next do date when the prior step completes.
End-of-day performance is quantified with two percentages—time on schedule and output on target—so low scores prompt review rather than vague self-judgment.
A due-date calendar view is preferred over Kanban for daily action management because it sorts by real dates and rolls items forward automatically.

Topics