Time Blocking When Clients Can Book Your Calendar

Key Takeaways

• Most time blocking advice assumes you are the only person who writes to your calendar. If clients hold a booking link, a block is just a note until your availability rules refuse to sell that hour.
• Blocks come in four kinds and only two of them can move. Client appointments and delivery work are fixed, admin and overflow absorb the week's mess. Service businesses usually have it backwards.
• Half your working day should not be bookable. A week with two and a half bookable afternoons survives contact with reality better than one that offers every slot and then cancels.
• The mechanical settings matter more than the discipline. Buffers, a minimum notice window and a daily cap on bookings do work that willpower does not.

A consultant blocks Tuesday morning for the report that is due Friday. On Monday evening a client books a 10:00 discovery call through the link in her email signature, because the booking page knows her working hours start at 09:00 and knows nothing about the report. The block was real to her and invisible to the system selling her time.

That is the part the standard guides skip. They explain how to decide what goes in each block, which is the easy half, and they assume the calendar is a private document. For anyone whose clients can book them, the harder half is making the block hold.

The problem time blocking advice skips

Search results for this method are mostly written for the same reader: a salaried knowledge worker whose calendar is filled by colleagues through meeting invites. An invite can be declined. A booking made through your own scheduling link cannot, not without a message that costs you more goodwill than the slot was worth.

So a service business runs two systems against one calendar. You write blocks into it. Your booking page writes appointments into it. If the second system does not read the first as genuinely busy, the plan quietly dissolves over about three weeks, which is roughly how long the enthusiasm lasts in a 30-comment r/productivity thread where someone describes switching from a to-do list to assigned slots and feeling the difference immediately. Nothing in that thread is wrong. It just describes a calendar nobody else can book.

The practical version of the problem shows up as tool-hunting. A 30-comment r/ProductivityApps thread looks for a planner whose blocks adjust around existing calendar events rather than sitting on top of them, and in a 7-comment r/clickup thread the workable answer is to push the blocks into the attached Google Calendar rather than keep them in the task manager. Both are the same instinct: the block has to live in the calendar that other systems check, or it does not exist.

Before you design anything, find out what the week currently looks like. Our calendar audit reads a connected Google Calendar or an export and reports your meeting share and your longest unbroken focus block. Most people guess the second number high by a factor of two.

Four kinds of block, and only two can move

The useful distinction is not task-by-task. It is who is allowed to write into the block and what happens when the week goes wrong.

Two rules fall out of the table. Deep work sits in the same category as a client appointment, which is the inversion most service businesses need: delivery work is the thing the client is paying for, so a block holding it is not a preference. And the week needs somewhere for the overrun to land, because a schedule with no slack converts every ten-minute overrun into a cascade through the afternoon.

Admin is the block people get wrong in the other direction. Invoicing, proposals, inbox and the half-written follow-ups are not deep work and do not need a protected morning. Batched into one afternoon they take less time than they do scattered across five days in fifteen-minute fragments.

A sample week, built around client appointments

This is a two-person consultancy's week, the shape that holds up when a client reschedules twice. Adapt the hours, keep the proportions.

Three decisions carry this week. Mornings are never bookable, so the hours when most people think best are never for sale. Client slots occupy two and a half afternoons rather than five, which looks like under-selling until the first week a project slips. And Friday afternoon stays closed so the week can land somewhere instead of leaking into Saturday.

If client sessions are themselves the delivery, which is true for coaches, therapists, tutors and most legal or tax consultations, invert the pattern rather than copying it. Bookable mornings, five of them, capped per day, with the afternoons holding preparation, notes and admin. The principle survives the inversion: the bookable window stays narrower than the working day, and the block that absorbs the overrun is never a client slot.

One honest limit on all of this. There is no credible figure for how many hours a week time blocking saves, and the numbers that circulate trace back to vendor blog posts rather than studies. Treat the method as a way to decide in advance where a tradeoff lands, not as a productivity multiplier. If you want the measurable version, count your unbroken focus blocks before and after, and run the comparison yourself.

Turn the blocks into booking rules

Here is where the method either becomes mechanical or stays aspirational. Five settings do most of the work, and they exist in some form in every scheduling tool worth using.

Make the booking window narrower than your working day. Working hours and bookable hours are different quantities. If you work 08:30 to 17:00 and your booking page offers 08:30 to 17:00, you have published the whole week. For the sample schedule above, the booking window is 13:00 to 17:00 on three days.

Write blocks as calendar events marked busy. A block saved as a task, a reminder or an all-day note does not read as busy to a conflict check. This is the single most common reason a protected morning gets booked anyway. If it is not an event with a start time, an end time and busy status, treat it as decoration.

Put buffers on the booking type, not on your discipline. A 45-minute call with a 15-minute buffer each side occupies 75 minutes of calendar, which is what it actually costs once you account for notes and the reset. Buffers configured on the appointment type apply whether or not you remember them at 16:50.

Set a minimum notice window. Without one, someone can book 08:00 tomorrow at 23:40 tonight, and tomorrow morning's block dies before you see it. Twenty-four hours is the usual default. For appointments that need preparation or travel, go longer.

Cap bookings per day. Four discovery calls is a different day than one, even when the calendar shows the same number of free hours. A per-day limit is the only rule in this list that protects the quality of the work rather than the quantity of the time.

Then connect every calendar that holds blocks. If your delivery blocks sit in a work calendar and your gym, school pickup and side project sit in a personal one, a tool reading only the first will cheerfully sell the second. Merging them is a prerequisite rather than a nicety, and syncing Google Calendar with Outlook is often the unglamorous first step.

Wanting a planner that keeps the blocks and the bookings in one place is reasonable, and the hunt shows up repeatedly: a 20-comment r/productivity thread runs through dozens of abandoned planner and tracker apps looking for one that sticks. The pattern in those threads is that the apps that stick are the ones writing into the calendar other systems already read, not the ones maintaining a parallel plan.

Where meetergo fits

meetergo is a Cologne-built scheduling and client-pipeline tool: booking pages, polls, forms, built-in video, payments and e-signatures in one place, with feature coverage across consulting, sales, healthcare, talent and other verticals. For time blocking it does one specific job, which is enforcing the blocks you have already drawn.

The availability settings carry that. You define working hours per booking type, add a buffer before and after an event, set a minimum notice window and block specific time windows or booking limits so a protected morning is never offered. Buffers appear as busy on all connected calendars rather than only inside meetergo, which is the detail that keeps a second tool from booking over them. None of these appear as plan-gated rows on the pricing table, so they are per booking type settings rather than an upgrade (checked 2026-10-02).

Conflict checking is the other half. meetergo reads your connected Google, Outlook, iCloud or CalDAV calendars in real time and only offers slots that are genuinely open, so a block written as a busy event is treated exactly like a client appointment. The unified calendar view puts work and personal calendars in one surface, out of office blocks a date range and reassigns existing appointments with conflict detection rather than leaving you to cancel by hand, and manual confirmation holds a request for approval when a slot sits close to something you want to protect.

Two things make the enforced version easier to keep. Automated workflows send the reminders, which is what stops a no-show converting a client block into dead time, and recurring bookings let a client take the same slot for eight or twelve weeks so a standing session stops being renegotiated. For how reminder timing affects attendance, our guide to appointment reminders covers the specifics.

The honest limitation: the free plan connects one calendar and three booking types (checked 2026-10-02). One calendar is the binding constraint for this use case, because the point of the exercise is having every block in one conflict surface, so a split work and personal setup needs Light at €9.90 a month or above, where six connected calendars are included. meetergo also does not plan your week for you. There is no automatic rescheduling of your own blocks around new bookings, so the schedule stays a decision you make rather than one the software makes.

Set your bookable window to the hours you actually want to sell and see how the week looks after two weeks. Free plan, no credit card required.

Common mistakes

Blocking time you have already put up for sale. Drawing a block in your calendar while your booking page still offers the same hour is the mistake underneath most failed attempts. Change the availability rule first, then draw the block.

Writing blocks as tasks or all-day events. An all-day event usually does not mark you busy, and a task is invisible to a conflict check. Both look identical to you and like free time to everything else.

Planning the whole week on Monday morning. By Wednesday the plan is fiction and the fiction is demoralising. Block the shape of the week on Monday and the detail one day ahead, which is also how you notice a day that has quietly filled with reschedules.

Treating the delivery block as the flexible one. When a client asks for Tuesday morning, the delivery block is the easiest thing to move and the most expensive. Move the admin batch and offer the client Thursday.

Running blocks in one app and bookings in another. Maintaining the plan in a task manager while the calendar accepts bookings means reconciling two pictures by hand every day, and nobody does that past the second week.

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.

Use for free

Sarah NowakManaging Director · Intro call · 30 min09:0010:3014:00

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.

Use for free

FAQ

How long should a time block be?
Long enough to finish a unit of work, which for most delivery tasks is 90 minutes to three hours. Blocks under 45 minutes mostly measure the setup cost of starting. For client-facing slots, the length is whatever the appointment type genuinely takes plus the buffer.

Should I block time for email?
Yes, in the admin batch rather than as its own daily ritual. Two fixed windows a day beats a standing block, and both beat the default of reading mail inside every other block.

What do I do when a client wants a slot inside a blocked morning?
Offer the next bookable slot and say when it is, rather than explaining the system. If you say yes often enough that the exception is the rule, the bookable window is drawn in the wrong place and the schedule needs changing, not defending. Our guide to writing your availability in an email covers the phrasing.

Does this work if my week is almost entirely client appointments?
It works differently. With a therapy or coaching load the blocks are mostly client sessions, so the method becomes capping sessions per day, protecting the notes and preparation time between them, and keeping one unbooked slot as the overflow. The admin batch still needs its own window.

How many bookable hours a day is realistic?
For consulting and sales conversations, three to four client hours a day is the practical ceiling before the quality of the last one drops. Open more than that and you are selling availability rather than attention. A per-day booking cap is how you hold the line.

Do I need an app for this?
Not for the planning. A paper plan and a drag-and-drop schedule builder are enough to design the week and export it as a calendar file. You need a scheduling tool only for the enforcement half, which is where a shared booking link is involved. If the hard part is finding a slot several people can take, an appointment poll solves that before any blocking question arises.