Cal Newport’s Time-block planner in Logseq

Logseq is used as a daily “clean slate” planner by structuring every entry around a three-part journal note: daily metrics, an “engineer’s book” for notes vs. tasks, and a time-block grid split into morning deep work and afternoon collaboration. The core idea is that each day opens on a fresh page with the date, forcing priorities to be re-anchored daily—then carried forward only when needed via templates and a weekly staging system.

The daily metrics section is adapted from Cal Newport’s time-blocking approach and turns goals into measurable, time-based habits. Three tracked targets anchor the day: one hour of writing improvement, 30 minutes of learning Go (a programming language), and reading 25 pages to build a consistent identity as a reader. The reading target is framed as a practical “velocity” method—25 pages a day can translate into finishing a book in roughly a week or a little over, depending on length. Checkboxes (via slash commands like “/to do”) make the habits actionable at a glance, while the author notes that reading is harder to time precisely during scattered moments, so page counts fit better than time tracking.

Beyond daily habits, the journal includes an “engineer’s book” section inspired by the Pragmatic Programmer’s idea of engineers keeping notebooks. It separates two streams: notes (things to remember) and tasks (things to act on). This keeps to-dos from mixing with ideas that may later become action items—such as updating agile sprint artifacts (e.g., task boards) or capturing meeting-derived action items.

Time blocking is implemented as a grid with morning and afternoon halves, with lunch as the divider. The morning is reserved for deep work—typically the first four hours—avoiding Teams, email, and other distractions. Afternoon time is left open for collaboration, meetings, and lighter work, with deep-work sessions broken into roughly one-hour to one-and-a-half-hour intervals to create mental “switch points.” The grid starts at 8 a.m., includes scheduled blocks for deep work and recovery-friendly shallow tasks, and uses the Outlook calendar to populate meeting times. A shutdown block near 4 or 4:30 is used to stage work for the next day.

To avoid rebuilding this structure daily, templates are created inside Logseq. A “time blocker” template is attached to the journal entry so new daily pages automatically populate the same sections. Even the hour lines can be templated so the author can start with times when helpful, or omit them when the day’s schedule is uncertain.

Weekly planning adds a higher abstraction: a “week ahead” page with deadlines and day headings (Monday through Thursday/Friday as needed). Tasks can be scheduled for specific dates using a date picker, and those items automatically appear at the bottom of the corresponding daily journal entry. When planning a day, the author moves staged items into the time-block grid, eliminating duplication.

Finally, tags are used as dynamic “collections,” echoing Bullet Journal concepts. A “read later” tag creates a dedicated page that aggregates all tagged notes and supports filtering by additional tags like “writing.” Meeting notes are handled similarly: recurring meeting pages link to future dates via date picker entries, so a checkbox reminder appears in the correct day’s journal when the meeting arrives.