What Is Block Scheduling? How It Works and Why Blocks Collapse

Tuesday, 9:00 to 11:00, blocked for the board deck. It’s been sitting there since last Thursday. Then at 9:40 your head of sales needs twenty minutes before a customer call, and twenty minutes is nothing, so you say yes. By 10:15 you’re back at the deck with forty-five minutes left and no momentum at all. The block existed. It just didn’t hold.

That gap is what this article is about. Block scheduling is easy to explain and genuinely useful, and plenty of people who try it quietly drop it inside a month. The method isn’t the problem. A block is a promise, and in most weeks nobody is around to enforce it.

I’m Nir, co-founder of Catch. We build an AI Executive Assistant that takes admin work off executives’ plates, and calendars are where most of that work ends up living. My weeks are mostly conversations with founders, CEOs and operators who have already tried every scheduling system going. So: what block scheduling actually means, how it differs from time blocking and task batching, how to build one, and what it takes to get the blocks to survive a normal week.

What is block scheduling?

Block scheduling is a planning method where you divide your day into a small number of long, uninterrupted chunks and assign each chunk to one kind of work. Rather than a to-do list you pick from whenever a gap opens up, the day has a shape: a block for deep work, a block for meetings, a block for the inbox, a block for whatever else the role demands.

The reasoning is that switching costs are real. Move between a contract review, your inbox and a hiring call, and you pay for each transition twice, once to leave the task and once to find your way back in. Longer blocks mean fewer transitions. Fewer transitions mean more of the hour actually lands on the work.

A block schedule for a typical executive week might look like this:

• 8:00 to 10:00, deep work. The one thing only you can do. Strategy, the board deck, the pricing decision.
• 10:00 to 10:30, inbox. Everything that arrived overnight, handled in one pass.
• 10:30 to 1:00, meetings. Internal and external, stacked together on purpose.
• 1:00 to 2:00, lunch and buffer. The shock absorber for anything that ran long.
• 2:00 to 4:00, meetings. The second half of the meeting load.
• 4:00 to 5:00, admin and close. Approvals, quick decisions, tomorrow’s prep.

Four or five blocks is about the realistic ceiling. The version of block scheduling that dies on day one is the one with eleven blocks and no gap anywhere between them.

Block scheduling at work versus block scheduling in school

If you searched this term and ended up reading about high schools, that’s no accident. Block scheduling is also the name for a school timetable model where students take fewer classes per day in longer periods, often 80 to 90 minutes, instead of six or seven short ones. Nursing and healthcare rotations borrow the word the same way, for longer shifts grouped into fewer days.

Same underlying idea: fewer switches, longer stretches, more depth per sitting. Everything below is about the workplace version, which happens to be the one you can change on your own.

Block scheduling vs time blocking vs task batching

The three terms get thrown around as synonyms. They aren’t, and the difference matters once you’re picking something to try.

Method	What you do	Granularity	Best for
Block scheduling	Divide the day into a few long chunks, each assigned to a category of work	1 to 3 hours per block	Giving the whole day a repeatable shape
Time blocking	Assign a specific calendar slot to a specific task	15 minutes to 2 hours per task	Making sure named pieces of work get a slot
Task batching	Group similar small tasks and do them in one pass	Varies, usually under an hour	Killing the overhead of repeated context switching

Block scheduling operates at the level of the day. It’s a container system. That 10:00 to 10:30 inbox block doesn’t care which emails arrive, only that email happens there and not in the middle of the deck.

Time blocking operates at the level of the task. You drop “review the Henderson contract” onto the calendar from 2:00 to 2:45. More precise, and more fragile, since one wrong estimate breaks that slot and everything behind it. Time blocking is probably the method you’ll see recommended most often online, and it’s also the easiest one to abandon, because an hour-by-hour plan for a whole week tends to fall apart the moment reality turns up.

Task batching is a tactic, not a schedule. You answer all your Slack messages in one sitting instead of twenty times a day. It slots neatly inside a block schedule: the batch is what you do, the block is where it lives.

Put together, they’re coherent. Block scheduling sets the shape of the day, batching fills the shallow blocks, light time blocking names what goes in the deep one. The trouble is that all three rest on the same assumption, and the assumption is usually false.

Why block scheduling fails

Pretty much every piece of advice on block scheduling assumes the blocks will still be there when you arrive. If your calendar gets written in by other people, that assumption doesn’t survive.

Watch a block collapse

Consider an illustrative example: Mark is a VP of Operations. He blocks 9:00 to 11:00 on Tuesday for a vendor consolidation analysis he’s been pushing for three weeks. Here’s how the two hours go missing.

1. 8:52. An email arrives. A supplier wants to move Thursday’s call and offers three times, one of which is Tuesday at 10:00.
2. 8:55. Mark opens it, because it’s sitting at the top of the inbox with the supplier’s name in the subject line. He is now in his inbox rather than the analysis.
3. 9:10. Still in the inbox. Two other things looked urgent.
4. 9:30. He starts the analysis.
5. 9:47. His head of sales messages: twenty minutes before a customer call, is now okay? It’s a customer. Mark says yes.
6. 10:15. Back at the desk. Forty-five minutes left, and the first fifteen go on remembering where he was.
7. 11:00. Block over. The analysis moves to next Tuesday.

Nothing in that sequence was a mistake. Each individual decision was arguably the right call. The block still died, and it died the same way the following Tuesday.

You are the only defender of your own calendar

Here’s the structural problem. A block is a claim on time, and it competes with other people’s claims on that same time. Claims get settled by whoever is paying attention. The supplier is paying attention to their own schedule. Your head of sales is paying attention to the customer call. Nobody except you is paying attention to the analysis block, and you are inside the analysis, which is precisely where you can’t also be watching the perimeter.

Which is why executives with a good assistant can block schedule successfully and executives without one mostly can’t. The assistant is the defender. When the supplier emails, the request never reaches the executive mid-block. It gets read, weighed against what’s already on the calendar, answered with a Thursday alternative, confirmed. The block holds because somebody whose entire job was watching it decided it should.

Without that, you’re being asked to be the person doing deep work and the person triaging interruptions, in the same two hours. Those two roles cancel each other out. No technique fixes it, which is why “just protect your focus time” keeps failing for people who are genuinely trying.

What it takes to make a block survive

Three things, and all three have to be true.

1. Something has to see the request before you do. The interruption that kills a block nearly always shows up as an email, a Slack message or a text. If it lands in front of you while you’re working, the block is already damaged, even if you decline. Declining costs attention too. Requests need intercepting, not resisting.

2. Something has to answer on your behalf. Declining isn’t enough on its own. The supplier still needs a time. If no reply goes out, the request comes back tomorrow, and the second ask is harder to refuse than the first. A defended block needs someone to propose Thursday at 2:00, confirm it and send the invite, all without you.

3. The work has to be re-placed, not deleted. Sometimes a block genuinely has to move. Fine, but it needs to land somewhere else in the week rather than evaporating. The reason Mark’s analysis sat untouched for three weeks is that every collapse pushed it into a vague “next Tuesday” that was itself undefended.

Most tools built around block scheduling cover a slice of this. Very few cover all three, because the first two aren’t calendar problems at all. They’re communication problems that happen to show up on a calendar.

Tools that help, and where each one stops

A straight read on the main options, Catch first because it’s ours.

Catch

Catch is an AI Executive Assistant that handles the admin work around your calendar instead of just displaying it. It works across Slack, email, text message, iMessage and phone, which matters here because that’s where the interruptions actually arrive.

So when the supplier emails about moving Thursday, Catch reads it, weighs it against what’s already on your calendar, and handles the reply and the booking itself rather than surfacing a draft for you to approve. Scheduling is clicked through and confirmed, not handed back as a link. When something genuinely needs your decision, Catch brings it to you with the context and waits.

Autonomy is earned rather than switched on at signup. Early on Catch checks with you before acting, then handles more by itself as it learns how you work and what you care about. It confirms the details before doing things on your behalf, and the questions thin out as its picture of you sharpens.

It’s a flat $99 per person per month, with voice included and no per-call fees, and Catch can place calls on your behalf when a booking needs a phone rather than an inbox. On security: SOC 2 Type II and CASA Tier 2.

Where it stops: anything that has to happen physically in the room stays with a person, and expense and reimbursement work isn’t part of Catch today.

Reclaim

Reclaim, owned by Dropbox, is built specifically around defending calendar blocks. Automated Focus Time blocks and defends flexible time for deep work based on your weekly goals, Automated Habit Scheduling fits recurring routines around conflicts, and No-Meeting Days defend whole days for heads-down work. It also auto-schedules breaks and travel buffers around meetings, and offers scheduling links and calendar sync across work and personal calendars. Pricing runs Lite free, Starter $10, Business $15, and Enterprise $22, all per seat per month.

Where it stops: Reclaim works inside your calendar. It does not read, triage, or reply from your inbox, which means it can rearrange a block after a meeting lands but cannot intercept the email that caused it. It’s a layer between you and your own calendar rather than an assistant reaching into the outside world for you.

Motion

Motion combines calendar, tasks, project management and docs in one workspace, pitched as a replacement for Asana or Monday.com. It adds Travel Time buffers around events, such as 15, 30 or 45 minutes before or after, supports Google Meet and Zoom, includes an AI Notetaker for meeting summaries and recaps, and lets you forward an email to a dedicated address to turn it into a scheduled task. Pro AI is $29 per seat month-to-month or $19 per seat billed annually; Business AI is $49 month-to-month or $29 annually. Individual rates are higher. There is no free plan, and Motion states SOC 2 Type II.

Where it stops: it’s a planning and work management system, and that’s the lane it’s built for. If what you want is to replace Asana, go and look at Motion. If what you want is the admin, the emails, the scheduling and the follow-ups handled, that’s a different job.

Sunsama

Sunsama is built around a daily planning routine. You review yesterday’s unfinished work, pull tasks in from Slack, Gmail, Jira, Notion, Asana, Linear and others, check the total against your actual capacity, and timebox everything onto a calendar timeline to block out the day. A built-in AI assistant called Sunny can create tasks, organize backlogs and run the routine with you, and Sunsama’s AI also suggests time estimates and sorts tasks into channels based on how you’ve worked before. There is no free tier, a 14-day free trial, and the Pro plan is $22 per user per month billed monthly or $204 per user per year, which the pricing card shows as $17 a month.

Where it stops: the planning is the product. The capacity check is genuinely good at making you honest about how much actually fits in a day, and that honesty is worth something, but the blocks are the ones you place yourself during the routine.

Where to start this week

If you want block scheduling to hold, do these in order.

1. Cut to three blocks. One deep work block, one meeting block, one admin block. Nothing else. A sparse schedule survives a bad day; a dense one doesn’t.
2. Put the deep work block first in the day, before anyone else’s requests have had time to pile up.
3. Leave an hour genuinely empty. Not reserved, empty. That’s where the overruns go.
4. Decide in advance what’s allowed to break a block. Write the list down. A customer escalation, yes. A twenty-minute internal pre-call, probably not.
5. Work out who is defending the blocks. If the answer is only you, go back and read Mark’s Tuesday again, because that’s the week you’re planning for.

That last step decides whether any of the rest holds. Block scheduling is a sound method. It just quietly assumes a defender, and for most executives that role is sitting unfilled.

Frequently Asked Questions