Part 1 had a whole failure mode on plan rigidity, the calendar as a trap. So it might surprise you that a calendar has a place here at all. The distinction is everything.
You are not using the calendar to decide what matters. The system does that; the score does that. Blocking your whole day in advance, deciding every task that you will do from 8 a.m. to 5 p.m., is the rigidity that shatters the moment your day goes sideways. That’s the thing we’re not doing.
What you are doing is reserving execution time for the handful of things that genuinely must land by a certain time. A calendar block, used this narrowly, is really just a cousin of the due date: a hard commitment that guarantees the hours exist. If something is due today and it’ll take two hours, those two hours have to come from somewhere, and blocking them is how you make sure they do. You’re not planning your day; you’re protecting time for what’s actually pinned to the clock.
When I reserve calendar time for a task, I set the task’s start date to the time of the block. Remember the start date from Part 3, it hides a task until it’s eligible. So the task drops out of my system’s view until the moment I’ve committed to work on it, and then it reappears, right when I sit down to do it. The calendar holds the appointment; the start date keeps the task quiet until the appointment arrives, so it isn’t cluttering my list in the meantime. How completely you can pull a booked task off your list, though, depends on your tool. A start date that understands the time of day can hide a task right up to the hour your block begins. A tool that only thinks in whole days, paper, or the spreadsheet, can hide a task until a future day but not until 2 p.m. today; for a same-day block, the task stays on the list and you lean on the calendar itself to hold the commitment. Either way the principle is the same: you’ve reserved the time, so the task is handled whether or not it’s still visible.
Alongside the due-today check, I take a separate pass to look a few days ahead. Not far, just far enough to catch anything landing within the next five to seven days that will need real time or preparation. A task due Thursday that needs four hours can’t be discovered Thursday morning; found on Monday, it’s easy. This is also where you sanity-check the calendar against reality: a day off, a holiday, a packed afternoon can mean a task is effectively due sooner than its date suggests, something “due Wednesday” is really due Tuesday if Wednesday is spoken for. The look-ahead is what turns “I have time to do this well” into the default instead of the scramble.
TaskBeacon can take some of this off you. Give a task an effort estimate, and it works out the latest moment you can start and still finish on time, then tells you when that moment arrives, as long as it’s open. It’s the look-ahead done for you, but the habit is the same either way: find the big things before the day they’re due.
After all this, capture processed, tasks shaped, time reserved for what’s pinned, I stop planning and start working. I look at what the system is surfacing, and I do the top thing. That’s the whole morning. Fifteen minutes, most days, and then the system carries the decisions so I don’t have to.