A block of focus time survives for one of two reasons. Either nobody can see it well enough to book over it, or the person who books over it expects to get a reply. If other people have booking rights on your calendar and you have no standing to refuse them, you are working entirely on the second reason — which means focus time is not really a calendar problem for you. It is a correspondence problem, and the calendar settings are only the part that reduces how much correspondence you have to do.
Almost everything written about focus time assumes the opposite. It assumes you can set a weekly target, let software find the hours, and have the automation hold the line on your behalf. That advice is not wrong; it is written for someone whose calendar is theirs. If yours is shared with a manager, an assistant, a scheduling link, or a team that treats visible white space as an offer, the automation gets overridden by the same people who were overriding you, and now you are also paying for a subscription.
This is the version for someone with no authority. It is four messages, three settings, and one rule about when to stop defending.
Three things decide whether a block holds
Not willpower, and not how important the work is. Three mechanical properties, in this order:
Whether the block shows as busy. A calendar event marked free is an invitation. Most people booking a meeting are scanning for white space in a grid, and a free-marked block is white space with writing on it. They are not overruling you; they genuinely cannot see that there is anything there.
What the block is called. “Focus” and “Deep work” and “Head down” all name a state, and a state is negotiable — anyone can privately decide your state is less urgent than their meeting, because they have no way to know what the state is for. A block named after a deliverable is not a state. It is work with an owner and a date attached.
Whether overwriting it has a visible cost. If a meeting lands on your block and nothing happens — no reply, no reschedule, nothing moves — then the block cost nothing to take, and the next one is easier to take. This is the part no setting fixes. It is the part the four messages below are for.
Everything else people argue about — length, time of day, colour, whether you batch or scatter — matters much less than these three, and matters not at all until these three are in place. If you are going to spend one hour on this, spend it on the three.
Set the block up before you defend it
The settings come first because they reduce the number of times you have to send anything.
Mark it busy, not free
Both Google Calendar and Outlook let an event hold time as busy, and both can create a block that declines incoming invitations automatically. It is a checkbox, not a feature you buy. The exact settings on both platforms are worth ten minutes once, and they remove most of the traffic before it reaches you.
Two things to know before you turn auto-decline on. It will decline invitations from people you did not want to decline, including your manager, and it will do it in a voice that is not yours. On most setups you can add a line to the automatic response — use it, and keep it short: “Auto-declined; this block is held for the Q4 reconciliation. Send me a time either side and I will take it.” That turns a refusal into a reschedule, which is what you actually want.
Name the block after the deliverable
Not “Focus time”. Not “Deep work, do not book”. The name of the thing you owe someone:
- “Pricing model — v2 for Thursday review”
- “Incident write-up (due Fri)”
- “Migration runbook — section 3”
This is the single highest-leverage change on the list, and it costs nothing. The reason it works is not psychological. It is that a person deciding whether to book over your block is making a comparison, and they can only make it against what they can read. Against “Focus” their meeting always wins. Against “Pricing model — v2 for Thursday review” they have to decide that their meeting beats a named commitment with a date, and most people will not do that silently. They will ask. That is the whole mechanism.
It also means that when someone does book over it, the conversation is already about priorities rather than about your preferences. You never have to make the case that focus time matters in the abstract. The block made the case.
Put it where it is least convenient to take
Meetings colonise the middle of the day. If your block sits at 11:00 on a Tuesday, it is in the most contested hour of the week and you will defend it constantly. The same two hours at 08:30, or at 16:30, or on the day your team already has fewest meetings, will need defending a fraction as often.
This is a concession, and worth naming as one. The best hours of your day are the ones everyone else also wants, and if you have no authority you will not win those hours by being right. Taking the second-best hour and keeping it is better than losing the best one weekly. If the problem is fragmentation rather than load, the placement question is most of the fix on its own.
The four messages, in escalation order
These are the words. Send the lowest-numbered one that fits, and do not skip to a higher number because you are annoyed.
One: the pre-emptive note, sent once
Not a reply to anything. Sent in advance to the two or three people who book your time most often — your manager, the person who runs the team’s planning, whoever owns the standing invite.
“I’ve blocked 08:30–10:30 Tuesday and Thursday for the pricing model, which I owe Priya for the Thursday review. If something needs that slot, book either side and I’ll move things. Flagging so it doesn’t look like I’m just unavailable.”
Two things are doing the work. It names the deliverable and the person waiting for it, so the block is accountable to someone other than you. And it pre-authorises the override, which means you are not asking permission and they are not expected to grant it. Most of the time you will never need messages two to four.
Two: the 9:04 reply
Something has landed on the block. Reply the same morning — not at lunchtime, not the evening before the meeting. The window in which a reschedule is easy is about an hour wide.
“This lands on the pricing-model block — can we do 10:45 or anything Wednesday? If it has to be this morning I’ll take it, just means the v2 slips to Monday.”
The structure matters more than the wording. Offer two alternatives, state the consequence, and concede in advance. You have not refused anything, so there is nothing for them to overrule. You have made the trade visible and handed the decision back. If the answer is “it has to be this morning”, you have a sentence on record about Monday that you did not have before, which is what makes the next conversation easier.
Do not write “I have focus time then.” It reads as a preference and invites a negotiation about whether your preference outranks their meeting.
Three: the pattern message
Use this when the same block has been taken three or four times. Not about one meeting — about the pattern, and sent to your manager rather than to whoever booked it.
“The Tuesday/Thursday morning block has been booked over four of the last six times. I’m not going to get the pricing model done in the gaps, so I’d rather move it than keep losing it. Two options: I move it to 08:00, which is outside most people’s day, or we agree Thursday mornings are off-limits for me and I take the Tuesday hit. Which is easier for you?”
Count first. Four of six is a fact and arguable with; “it keeps happening” is a complaint and is not. Then bring two options, both of which you can live with, and let them pick. A manager asked to choose between two workable things will usually choose one. A manager asked to protect your time in principle will usually agree warmly and change nothing.
Four: the one that names what is not getting done
The last one, and the only one that puts a cost on someone else’s desk. For when three has not worked and something is genuinely going to be late.
“Flagging early: the pricing model is going to miss Thursday. I’ve had about three of the eight hours I planned for it since the 14th. I can either have a rough version for Thursday and a real one the following week, or hold Thursday and move two of this week’s meetings. Tell me which and I’ll sort it out.”
This is not a threat and should not read as one. It reports a consequence, early, with options attached — which is the only form of escalation that reliably works when you have no leverage. Send it before the deadline, never after. After the deadline it is an excuse, and it will be read as one.
When to give the block up instead of defending it
Sometimes the honest answer is: take the meeting. Defending every block is how you become the person who is difficult about calendars, which costs more than the hours do. Work through these in order and stop at the first yes.
- Does it stop someone else from working today? Give the block up, and say that is why. Being visibly useful when it is cheap is what buys you the harder refusals later.
- Did it come directly from someone above your manager? Give it up, and reschedule the block in the same reply so the time does not simply evaporate. This is not cowardice — the cost of refusing is real and you are the one who pays it.
- Is it the first occurrence of something recurring? Hold the block, and fix the recurrence rather than the instance. A standing invite that eats this block will eat it every week, and declining it once is work you will do fifty-two times. Getting out of a standing meeting is the right tool here, not a reschedule.
- None of the above? Hold it, with message two. Most things are here.
The rule underneath the four: give up individual blocks cheaply and recurring claims almost never. Instances cost you an hour. Recurrences cost you the hour every week and establish that the block is available, which is the expensive part.
What defending focus time costs you
There is a cost, and the advice is not trustworthy without it.
You will be slightly less available than your peers, and on a team where availability is read as commitment, that is a real tax. You will spend a few minutes a week on correspondence about your calendar, which is itself overhead. And you will occasionally be wrong — you will hold a block for work that turns out not to matter, having declined something that did.
There is no public number for how much this costs or what the hours are worth, and anyone offering you one is selling something. What you can measure is narrower and more useful: whether the thing the block was named after actually shipped. That is the only defence that compounds. Someone who holds focus time and delivers is read as focused. Someone who holds focus time and misses the same deadlines is read as precious about their calendar, and every subsequent block is harder to keep. The deliverable in the block’s name is not just a labelling trick — it is the receipt.
The one conversation to have with your manager
Have it once, in a one-to-one, and frame it as output rather than preference. The full version of this ask is worth its own preparation, but the short form is three sentences:
“The pricing model needs about eight uninterrupted hours and I’m getting it in forty-minute pieces, so it’s taking roughly twice as long. I’d like to hold Tuesday and Thursday mornings for it until the review. If that’s a problem for the team I’d rather know now and plan around it.”
No philosophy about deep work. No statistics. One deliverable, one number you can actually stand behind, one specific ask, and an explicit invitation to say no — which is what makes it a plan rather than a demand.
If the answer is no, you have learned something useful and should stop spending effort on blocks: the time is not yours to protect, and the real problem is what is on the calendar in the first place rather than how it is labelled.
If you have no focus time at all this week
Do not build a system. Do one thing:
Pick the single most consequential thing you owe someone. Find the largest gap already on your calendar in the next three days — it will probably be fifty minutes, and it will not be in the morning. Rename it after that deliverable, mark it busy, and send message one to the two people most likely to book it.
That is the whole intervention. It takes four minutes and it is most of the available benefit. The elaborate version — themed days, colour systems, a weekly ritual of rebuilding the grid — is mostly ideology, and it assumes a calendar you control. One named block, held, beats a system you abandon in week three.
When you are the one booking over someone else’s block
Worth two minutes, because it is the part that makes the rest of this work on a team rather than for one person.
If you have to take someone’s named block, say that you noticed. “I know this lands on your migration runbook — can’t avoid it this week, and I’ll keep Thursday clear.” It costs one clause. What it buys is that the next time your block is the one in the way, the same person extends you the same courtesy, and blocks on that team start carrying a visible cost to overwrite. That is the third of the three properties at the top of this post, and it is the only one you cannot set unilaterally.
The inverse is also true, and less comfortable: if you book over other people’s focus time without comment and expect yours to be respected, it will not be, and nobody will tell you why.
Holding the block, piece by piece
Why blocks get booked over and the setting that stops it, time blocking stripped down for a calendar you do not control, what a thirty-minute interruption actually costs, the auto-decline settings on both platforms step by step, and the version of this ask you put to your manager.