You blocked the time. It is still on the calendar, and there is a meeting on top of it. This happens for six reasons, they are mutually exclusive, and each one needs a different fix — which is why the general advice to “protect your blocks” has never once worked for anybody. You cannot protect a focus period until you know which way it is failing.
Work out which of these yours is before changing anything. Five of the six are settings or wording and take a minute. The sixth is a person, and takes a conversation.
Six ways a block gets taken
| What is happening | The tell | The fix |
|---|---|---|
| It shows as free | Invitations land on it with no hesitation, from people who are otherwise considerate | Mark it busy |
| It is busy but unlabelled in any useful way | People ask “can you move your focus thing?” | Rename it after the deliverable |
| It is on a calendar nobody else can see | Only people outside your team book over it | Share busy-only visibility, or move the block to the shared calendar |
| A booking link is selling the slot | Externals land on it; colleagues do not | Fix the availability window on the link |
| Nobody ever hears about it when it happens | The same slot goes repeatedly, from several different people | Reply every time, same morning |
| One person does it knowingly | It is always the same name | A direct conversation, not a setting |
The first four are mechanical and you can do all of them in under five minutes. The fifth is the one most people skip, and it is the one that actually determines whether the block has a future. The sixth is the only one that is about a person, and treating it as a settings problem will waste a month.
When a focus period is visible but not legible
The most common failure is not invisibility. It is a block that is perfectly visible and tells the reader nothing they can act on.
“Focus time”, “Deep work”, “DNB”, “Heads down”, “Writing” — all visible, all busy, all booked over constantly. The person looking at your calendar is making a decision, and the only information you have given them is that you would prefer not to be interrupted. Everyone would prefer not to be interrupted. It does not help them decide.
Compare the two things they could be reading:
- “Focus time” — a state. Reads as: Cass would rather not. Their meeting beats it.
- “Churn model — numbers for Monday’s board pack” — a commitment, with a date and an implied other person. Their meeting now has to beat the board pack, in public, and they will usually ask rather than decide.
Nothing else on this page is as cheap as renaming the block, and nothing else works as well. If you do one thing, do that.
A caveat worth knowing: if the work is confidential, a descriptive name leaks it. Use the project’s internal codename, or something true but uninformative — “Prep for Thursday review”. The property you need is that it reads as owed to someone, not that it is specific about what it is.
Auto-decline, and the two things it breaks
Both Google Calendar and Outlook can hold a block that declines incoming invitations without you touching anything, and the setup on both platforms takes about ten minutes. It removes most of the traffic. It also breaks two things, and you should know which before you turn it on.
It declines people you would not have declined. Your manager, the person coordinating something genuinely urgent, an interviewer slot. The automatic decline goes out in a neutral system voice, immediately, and some people read that as a refusal with attitude. Where the platform lets you add a line to the response, add one and make it a reschedule rather than a no: “Auto-declined — this block is held for the board-pack numbers. Anything either side of it works.”
It hides the pattern from you. Once declining is automatic you stop seeing how often your block is being targeted, which is exactly the data you need for the conversation in the next section. Check the declined invitations once a week. If the same slot is drawing four attempts a week, the block is in the wrong place and no amount of automatic declining will fix that — move it to a less contested hour instead of fighting for the contested one every week.
The two mechanical ones nobody checks
Rows three and four of the table, which take a minute each and get skipped because they are boring.
Check what your calendar looks like to someone else. Not to you. Open the scheduling view your colleagues use and look at your own Tuesday. If the block was created on a secondary or personal calendar, or on one that is shared with your team but not with the wider organisation, it is genuinely absent from their grid — they are booking into white space, correctly, by the only information they have. The fix is to put the block on whichever calendar your availability is read from, even if that means a duplicate.
Check the window on your booking link. If you hand out a scheduling link, its availability rules are a separate set of opinions from your calendar’s, and most links are configured once and never looked at again. A link offering 08:00–18:00 will sell your focus period to an external stranger who has no way of knowing it was held, and you will have agreed to it in advance. Narrow the window to the hours you are actually willing to lose.
The serial overbooker
One name, repeatedly, usually someone who coordinates scheduling for other people and is optimising for the room rather than for you.
Do not escalate and do not add a setting. Say it to them directly, once, in person or in a direct message, and keep it about the mechanics rather than about respect:
“You’ve landed on my Tuesday morning block three weeks running — I think it’s just the first gap your tool finds. Could you treat 08:30–10:30 Tuesday and Thursday as booked? Anything either side is genuinely fine and I’d rather you took 11:00 than asked me.”
Most of the time this is a tooling artifact rather than a judgement about your work, and naming it as one gives the other person an easy exit. If it happens a fourth time after that conversation, it is a priority disagreement rather than a scheduling accident, and it belongs with your manager as the pattern message rather than with you.
The block you keep moving yourself
Worth checking honestly, because it is more common than being overbooked and nobody writes about it.
Look at the last three weeks. How many times did the block disappear because somebody booked over it, and how many times did you move it, decline it, or quietly work on something else inside it? If it is mostly the second, the calendar is not the problem and no setting on this page will help. Either the work in the block is not actually the priority — in which case rename it after something that is — or the block is in an hour where you cannot think, in which case move it.
A block you reliably abandon teaches your team the block is soft, in exactly the same way that one you never defend does. The signal is the same from the outside.
What a block cannot fix
Two things, so you do not spend a month on the wrong problem.
A block cannot create time that is not there. If you are in meetings thirty hours a week, a protected two-hour slot is not a focus problem but an arithmetic one, and the work is in the recurring set rather than in your labelling. Count first.
And a block cannot hold against a team norm that says availability is the job. Where being reachable is what gets rewarded, an individual block is a standing refusal of the norm and will be read that way whatever it is called. That is a policy problem, not a personal one, and it gets solved — if at all — at the level of a written policy with someone senior visibly bound by it.
Knowing which of those two you are in is worth more than any of the fixes above. The six failures all have answers. These two do not, at your level, and recognising one early saves you the effort of defending something that was never going to hold.