Get AI summaries of any video or article — Sign up free
Time Blocking with Google Calendar + Notion PPV Daily Plan thumbnail

Time Blocking with Google Calendar + Notion PPV Daily Plan

August Bradley·
5 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

Check Google Calendar (or Outlook) the night before to identify any newly added scheduled events that must be treated as hard constraints.

Briefing

Time blocking becomes reliable when scheduled events from Google Calendar (or Outlook) are treated as fixed constraints, while the rest of the day is rebuilt from a Notion “ideal day” that includes routines, quick tasks, and deep-work blocks. The payoff is simple: commitments to personal priorities stop losing to other people’s calendars, because the highest-leverage work gets protected on the calendar with the same seriousness as meetings.

The workflow starts the night before. In Notion’s action zone (the daily focus area), priorities and quick actions are already organized into an ordered list—immediate items, then smaller quick tasks, then the first/second/third priorities. The next step is a manual check of the calendar for any scheduled events that arrived since the weekly review. Since Notion can’t yet automatically sync calendar invites, those time-specific events must be reviewed in Google Calendar and then copied into the Notion planning view so the day can be blocked correctly.

An “ideal day” template sits in Notion’s today view and is rolled forward each evening. Routine blocks—workouts, meditation, startup routines, reading, and other habit-linked time—slide into the next day unless a scheduled event interrupts them. The key move is reserving uninterrupted windows for deep work. When a meeting or other fixed event lands inside a deep-work period, the plan either shifts the deep-work block to start after the event (and optionally adds a short “prep” slot) or compresses the surrounding deep-work time so the day still contains multiple protected focus sessions.

Quick items get their own handling rule. Immediate tasks (urgent enough that they can’t wait) are placed into a dedicated quick-items window—often a recurring half-hour in the morning—before the first deep-work priority begins. If something truly urgent appears, the schedule makes room for it, even if that means trimming a deep-work block. After quick items, the day’s ordered priorities are executed inside the deep-work sessions: either each priority is completed within its assigned block (work first priority in the first deep-work window, second in the next, and so on), or—when tasks are hard to estimate—work continues through a longer stretch until the priority is finished.

The plan also builds in human limits. Breaks and transitions are part of the schedule: lunch, email checks, reading, fun time, and an evening wind-down. For deep work, the guidance is to avoid grinding for hours without movement—standing up and walking for at least five minutes every 40–60 minutes.

After execution, the system loops. The next evening, the ideal day template is rolled forward again, and any scheduled events that were accommodated on the prior day no longer interfere. Over time, the calendar becomes a tool for advancing projects rather than merely reacting to obligations. The central principle is that personal commitments—especially the tasks tied to projects that change one’s life—must be blocked on the calendar with the same specificity as meetings, using deep-work sessions as the protected container for those priorities. The manual bridge is acknowledged as temporary, with hope that future API syncing will automate the calendar-to-Notion step.

Cornell Notes

The method combines Notion’s daily “ideal day” and priority system with Google Calendar’s fixed scheduled events. Each night, priorities and quick actions are reviewed in Notion, then Google Calendar is checked for any new time-specific events that must be treated as constraints. The ideal day template is rolled forward, routines slide into open time, and deep-work blocks are adjusted around meetings—often by starting deep work after the event and adding a short prep slot. Quick items get a dedicated window (including an “immediate” rule), while lunch, email checks, breaks, fun time, and an evening wind-down keep the schedule realistic. The result is consistent execution of first/second/third priorities rather than letting other people’s calendars crowd out personal commitments.

How does the system handle the mismatch between Notion planning and calendar invites?

Scheduled events from Google Calendar (or Outlook) are treated as fixed, time-specific constraints. Because Notion can’t yet automatically sync invites, the workflow requires a manual bridge: after the weekly review, the night before the next day, the calendar is checked for any newly added scheduled events, and those events are brought into the Notion planning view so the day can be time blocked accurately. The plan then adjusts deep-work windows around these events.

What does “rolling forward” the ideal day mean in practice?

Notion’s today view contains an “ideal day” mapped out with routines and habit-linked time blocks. On the evening before, the current day’s template is rolled forward to the next day: routine blocks like workout/stretch/shower, meditation, startup routines, and reading slide into the new day’s open time. Past tracking history isn’t the focus; the system keeps what matters for execution tomorrow and only changes blocks where scheduled events interrupt.

Where do quick actions and immediate tasks go, and what rule decides their timing?

Quick items are placed into a dedicated quick-items entry point—often a half-hour in the morning. “Immediate” tasks are urgent enough to be handled before the first deep-work priority; if they can’t wait until after the startup routine, the schedule makes room for them even if that means trimming deep work. Less urgent quick items follow the quick-items window, so the day’s most important priorities still get protected focus time.

How are deep-work sessions structured around meetings?

Deep work is scheduled as long, uninterrupted windows for the day’s top priorities (first/second/third). If a scheduled event falls inside a deep-work period, the plan either shifts deep work to start after the event and inserts a short prep block, or compresses the deep-work session to fit the remaining time. The goal is to keep multiple protected focus blocks even when interruptions occur.

What are the two ways to execute the first/second/third priorities inside deep work?

One approach assigns each priority to a specific deep-work block: finish first priority in the first block, second in the next, and third in the third. The other approach is to work through a priority until it’s done when tasks are hard to estimate, accepting less discipline about hard cutoffs. The system also recommends standing up and walking every 40–60 minutes to avoid desk fatigue.

How does the schedule prevent meetings from derailing project progress?

Meetings are planned as fixed events, but project progress is protected by reserving deep-work sessions for the priorities tied to active projects. The system explicitly treats personal commitments like meetings: block time for deep work on the calendar, adjust around other people’s events, and roll the ideal day forward nightly so execution doesn’t start from scratch each day.

Review Questions

  1. When you find a new scheduled event in Google Calendar the night before, what steps should be taken to keep deep work protected in the Notion plan?
  2. What decision rule determines whether an “immediate” quick item goes before or after the startup routine?
  3. How do the two execution strategies (priority-per-block vs. priority-until-done) change discipline and time pressure during deep-work sessions?

Key Points

  1. 1

    Check Google Calendar (or Outlook) the night before to identify any newly added scheduled events that must be treated as hard constraints.

  2. 2

    Roll forward a Notion “ideal day” template each evening so routines and habit-linked blocks automatically populate the next day.

  3. 3

    Reserve multiple uninterrupted deep-work windows for the first/second/third priorities, and adjust them around meetings by shifting start times and adding prep slots.

  4. 4

    Use a dedicated quick-items window (often a half-hour) to process quick tasks, with an “immediate” rule that can override deep-work timing if necessary.

  5. 5

    Build breaks, lunch, email checks, reading, fun time, and an evening wind-down into the schedule so the plan is executable, not aspirational.

  6. 6

    Execute priorities inside deep-work blocks either by finishing each priority within its assigned window or by continuing until completion when tasks are hard to estimate.

  7. 7

    Treat time for personal project priorities as seriously as meetings by blocking it on the calendar rather than relying on leftover time.

Highlights

Deep work isn’t left to chance: meetings from Google Calendar are copied into the Notion plan so focus windows can be reshaped around fixed events.
The “ideal day” template rolls forward nightly, letting routines slide into open time while only disrupted blocks are adjusted.
Immediate tasks get a clear rule: they move into the quick-items window and can force deep-work trimming if they can’t wait.
The system uses first/second/third priorities inside protected deep-work sessions, with either hard cutoffs per block or task-based completion when estimates are unreliable.
The core principle is behavioral: personal commitments tied to projects must be scheduled on the calendar with the same specificity as obligations to other people.

Topics

Mentioned