Why templates help
Starting a time blocking system from scratch means making dozens of small decisions each week: when do I block deep work, how long should each block be, where do I put email and admin, how do I handle the days that are mostly meetings?
A template provides a starting pattern — not a fixed rule, but a default structure to adapt. Most people modify their template significantly within a month, but having one at the start is faster than building from nothing.
Template 1: The maker schedule
Morning: 2–3 hour deep work block
This template works for roles with significant output work: engineers, writers, designers, researchers. The goal is a long morning block of uninterrupted focus, with all meetings and communication batched to the afternoon.
Midday: shallow work batch
A practical version: 8:00–10:30 deep work (Busy), 10:30–11:00 email/Slack batch, 11:00–12:00 meetings, 12:00–13:00 lunch, 13:00–17:00 available for meetings, with a 30-min wrap-up buffer at 16:30.
Afternoon: meetings only
The critical rule: the morning block is non-negotiable except for genuine emergencies. Everything else fits around it.
Template 2: The manager schedule
Morning: 1-on-1s and team syncs
Managers typically have less control over when meetings happen. This template accepts that reality and protects one reliable focus window rather than trying to minimize meetings.
Midday: a single focus block
A practical version: 9:00–12:00 available for team meetings (clustered), 12:00–13:30 protected focus block (Busy), 13:30–17:00 meetings and availability for decisions. The midday block is used for thinking that requires no interruption: planning, writing, reviewing strategy.
Afternoon: strategic decisions
The key: cluster meetings into the morning to create a predictable afternoon block that does not move.
Template 3: The remote worker
Morning: async communication catch-up
Remote work often means a mix of sync and async communication across time zones. This template front-loads async catch-up to clear communication overhead before the focus block begins.
Mid-morning: deep work block
A practical version: 8:00–9:00 async catch-up (email, Slack backlog, doc comments), 9:00–11:30 deep work block (Busy, notifications off), 11:30–12:30 lunch and light admin, 13:00–16:00 meetings and collaborative work.
Afternoon: availability window
The advantage: by 9am, the communication backlog is handled and the focus block starts with a clear head.
Template 4: The reactive day
Fixed anchor: one 60-min block
Some roles genuinely cannot control their schedule — support, sales, recruiting, operations. For these roles, the goal is not to minimize meetings but to protect one reliable anchor block each day.
Flexible: everything else reactive
A practical version: a single 60-minute block, same time each day (often before 9am or after 3pm when meeting density is lower), dedicated to the most important proactive work. Everything else responds to demand. The anchor block is the only scheduled proactive time — but it is reliable.
How Schedule Calendar helps
Whichever template you use, the ongoing need is the same: knowing how much time remains in a block, when the next meeting starts, and whether you have room to start something new. Schedule Calendar surfaces this information in the browser toolbar — a one-second glance instead of a full tab switch.
Start with the template closest to your role and schedule. Expect to modify it. The first version of any time blocking system is a hypothesis about how your week should work — the real data comes from running it for two to three weeks.
Frequently asked questions
A time blocking template is a default structure for your work week that specifies when deep work happens, when meetings are clustered, and when communication tasks are batched. It is a starting point rather than a fixed rule — most people adapt their template over the first few weeks.
Yes. Makers (engineers, writers, designers) typically need long uninterrupted morning blocks with meetings clustered in the afternoon. Managers typically have less control over when meetings happen, so the template focuses on protecting one reliable midday or early afternoon focus window rather than minimizing meeting volume.
Create recurring events for your standard block types — deep work, shallow work batch, buffer time. Set them at consistent times each week. Use colors to distinguish block types from meetings. Once the recurring pattern is in place, you can adjust individual instances without losing the overall structure.
The maker schedule, described by Paul Graham, involves long uninterrupted focus sessions. A single meeting can break the entire shape of a maker's day. The manager schedule is built around one-hour slots, with meetings clustered throughout the day. The time blocking approach for each role looks very different.
Even highly reactive roles benefit from one reliable anchor block — a fixed 60-minute window at the same time each day, protected for the most important proactive work. The goal is not to eliminate reactivity but to preserve at least one predictable window for meaningful output.
Most people need 2–3 weeks before a template becomes a stable habit. The first week reveals conflicts between the template and existing calendar patterns. The second week allows adjustments. By week three, the structure usually holds more consistently.