Google Calendar: how to block out days nobody can book

A Friday was marked off two weeks ago. It is grey on the grid, it has a title, and a client meeting has just landed on top of it. Nothing malfunctioned. The block that was created stops one audience and not the one that mattered.

Google Calendar has at least five separate mechanisms that all look like blocking out a day, and they defend against different things. One stops colleagues inside the same organisation from picking that slot in Find a Time. One stops a booking page from offering it. One declines invitations automatically. One does nothing except change the colour of the grid. Deciding which day needs which mechanism takes about ten minutes, and it is the only way to stop the same collision happening next month.

Five things that all get called blocking

A plain event set to Busy. The default for a new event. Other people with access to the calendar see a solid block. In Find a Time and in the availability column, that hour is taken. This is the workhorse and it is enough for most days.

An event set to Free. Same event, one setting changed, and the effect is reversed. It paints the grid without defending the time. Placeholders, reminders and anything created as a duplicate of a real event often end up here by accident, which is the single most common reason a marked day still takes a booking.

Out of office. A dedicated event type spanning a day or a range. Google states the effect directly: "When you indicate that you're out of office, your calendar will automatically decline all meetings during that time." The decline message can be edited.

Focus time. A shorter block with a headphones marker that can decline meetings and mute Chat notifications. It is limited to specific account types, covered further down.

An appointment schedule exception. Nothing to do with the grid. This is a setting inside a booking page that removes a date from the times strangers are offered. A day can be wide open on the grid and closed on the booking page, or the reverse, because they are configured in two different places.

Working hours belong in a sixth category, since they are a soft signal rather than a block. Google gates them and the related availability features: "You can use working hours and availability if your account is through your work or school organization." On a personal account they are not an option at all.

Why a day already marked busy still took a booking

Three specific settings account for most of these, and all three are quiet.

The first is the Free setting described above. Open the event, check the busy or free control, and change it. A day of Free events looks identical to a day of Busy events at a glance.

The second matters to anyone running a booking page. Google is explicit about which events count: "Unaccepted or tentative Google Calendar events do not block appointment availability." An invitation sitting in the calendar unanswered, or answered with Maybe, will not stop a stranger booking over it. Neither will an event that was declined but left visible. Every block that has to defend a day needs a Yes, or it needs to be an event created rather than received.

The third is which calendars the booking page is allowed to look at. If a block sits on a secondary calendar, a work project calendar or a shared family calendar, the booking page ignores it unless that calendar is selected for conflict checking, and that checking is a paid feature: "To check availability from secondary calendars, you need to have an eligible Google Workspace or Google One plan." With conflict checking off entirely, Google describes the result plainly. All time blocks appear as open on the booking page, and that applies even to events accepted.

One more detail is worth knowing, because it turns a half day of blocking into a whole one. When conflict checking is on, no appointment times show up on days where there is an all-day event set to Busy. A single all-day Busy event closes the whole day on the booking page, which is far quicker than editing availability hour by hour.

Out of office and focus time: what each one declines

These two are the only mechanisms that act on invitations rather than just displaying a state, and that is the reason to prefer them for real absences.

Out of office declines every meeting in the window. It is created from the top of the grid by clicking the first date away, choosing Out of office, then setting the range. Repeats are supported, which covers a standing day away each week. The decline message is editable, so the block can explain itself without anyone having to ask.

Focus time does the same job at a smaller scale, with two settings that matter. Under Automatically decline meetings, the choice is between Only new meeting invitations and New and existing meetings. By default focus time declines both new and existing meetings, which will clear invitations already accepted. Anyone placing focus time over a half-finished week should set it to new invitations only before saving.

Focus time is restricted by account type. Google lists the eligible ones as Google Workspace for Business Standard and Plus, Enterprise Standard and Plus, Education, and Nonprofits, and states that a work or school account is required. It also has to be created from Day or Week view with a specific start and end time, so it cannot be dragged across the all-day row.

The Chat side has its own conditions. Muting Chat notifications is possible only when the organisation has Chat turned on and the focus time block is less than 24 hours. A full day of focus time will not silence Chat, which surprises people who set it up for exactly that.

Blocking days on a booking page is a separate job

Anyone who has published a booking link has two calendars to defend, and the second one has its own controls under the appointment schedule.

Adjusted availability is the direct answer for specific dates. Open the schedule for editing, choose Change a date's availability, pick the date, and either narrow the hours or click Unavailable all day. This is the equivalent of a blackout date in dedicated booking software, and it holds whether or not anything sits on the grid that day.

Scheduling window sets how far ahead and how close to the hour people may book. By default an appointment schedule carries a four hour minimum notice, which is why a booking page checked immediately after setup often shows nothing for today. Widening the minimum notice to a day or two blocks the entire short-notice end of the week in one setting.

Buffer time adds a gap either side of each booking, and Maximum bookings per day caps the count. Neither blocks a date outright, and together they stop the shape of day that causes most rescheduling, six calls back to back with nothing between them.

There is a trap in the interaction between these. If availability looks wrong on a booking page and nothing is obviously blocked, the cause is usually the scheduling window or the daily maximum rather than a missing block. Times outside the window simply do not appear, and once a daily cap is reached the remaining slots vanish too.

Which mechanism for which day

What needs blocking	Use	Stops colleagues booking	Stops a booking page	Account needed
A few hours of work	Event set to Busy	Yes	Only if the calendar is checked for conflicts	Any
A whole day away	All-day event set to Busy	Yes	Yes, closes the day	Any
Leave, travel, sick days	Out of office	Yes, and declines invitations	Yes	Work or school
Deep work in a working day	Focus time	Yes, and declines invitations	Yes	Business Standard and above
A public holiday on a booking link	Adjusted availability, Unavailable all day	No	Yes	Any

The table also shows the gap that catches personal account holders. Out of office and focus time are not available, so an all-day Busy event is the whole toolkit, and it has to be paired with adjusted availability on any booking page.

An audit that takes fifteen minutes

Running this once is usually cheaper than adding software, because it finds the one setting that is undoing the rest.

1. Open the busiest week from last month and click every block that was created by hand. Note which ones are set to Free. That count is the size of the problem.
2. Look at which calendar each block was saved to. Blocks scattered across a personal calendar, a work calendar and a shared project calendar cannot all be defended by the same booking page setting, and the default calendar for new events is what decides where they land.
3. Check any invitation that is being treated as a block. If the response is still blank or Maybe, it is not blocking anything on a booking page. Accept it or replace it with an event created directly.
4. Open each published booking page and compare its availability against the grid for the next two weeks. Every difference is either a scheduling window rule, a daily maximum, or a calendar that is not being checked for conflicts.
5. Decide, once, which mechanism covers a full day away. Picking one and using it every time removes the guesswork that produced the mixture in step one.

Most calendars need one change after this rather than five. The usual outcome is that the default calendar for new events was pointing somewhere unhelpful, and that every block created since has inherited the same fault. The guide covers where that default lives and how blocks behave once it is set deliberately.

Doing this from a Mac rather than a browser tab

Three of the five mechanisms are ordinary calendar events, which means a desktop calendar handles them natively. All-day Busy events, recurring blocks and the busy or free setting are all standard fields that sync straight back to Google. A desktop app is usually faster here, because blocking a week of mornings is a repeating event created once, and typing is quicker than clicking through a web form. The features list is the place to check whether a given Mac calendar exposes the busy and free control on the event editor, since some hide it.

Two of the five are Google web features. Out of office, focus time and appointment schedules are configured on calendar.google.com and cannot be created from a mobile app. A desktop calendar will display them once they exist, and they keep working whether or not that app is open, so the split in practice is that structural settings get made once in a browser and daily blocking happens wherever it is quickest. The guide to entering events covers the faster route for the daily part.

What to change first

Open the last ten blocks that were created and check the busy or free setting on each, because that one field explains most collisions. Then, if a booking link is published, set adjusted availability for every date already known to be closed, and widen the minimum notice to at least a day. For the daily blocking that follows, Caltimate is a Mac option worth a look.