Why focus blocks collapse under pressure
A focus block often exists only as a calendar event with no owner. When a meeting request arrives, the block looks empty because it does not have an attendee or an agenda. The assistant or the principal moves it, and the pattern repeats until the block disappears. Protecting the time requires treating it as a commitment with rules, not as leftover space.
The second reason blocks fail is that the request often comes from someone senior or from a client. A blanket refusal feels risky, so the principal accepts and promises to focus later. Later rarely arrives because the calendar fills in the same way. A workable policy names the exceptions in advance so the principal does not have to negotiate each time.
Define the protected block in calendar terms
Name the block clearly, set a recurring time, and mark it as busy so scheduling tools respect it. Add a short description that says what the time is for, such as board preparation or strategy review. A block called focus time is easier to move than a block called final board paper review. Specificity creates a reason to defend it.
Choose a length that matches the work rather than an arbitrary hour. Deep writing may need ninety minutes, while a review may need forty-five. Place the block where the principal's energy is highest and where the least external coordination is required. A block that fights the natural rhythm of the week will be abandoned first.
Give the assistant a deferral script
The assistant needs language that protects the block without sounding rigid. A useful response names the current commitment, offers two alternative times, and asks whether the request is truly urgent. This gives the requester a path forward and makes the cost of interrupting visible. The assistant should not have to improvise the wording under pressure.
Write two versions, one for internal colleagues and one for external contacts. The internal version can be direct, while the external version should protect the relationship and the principal's responsiveness. Both should avoid claiming the principal is unavailable if the real reason is focus work. Honesty about the commitment makes the boundary easier to maintain.
Rank the exceptions before they arrive
Not every interruption is equal. Define a short list of events that can break a focus block, such as a client escalation, a board chair request, or a legal deadline. Everything else waits for the next available window. The list should be specific enough that the assistant can apply it without asking the principal each time.
Review the exception list quarterly because the business changes. A category that was urgent last year may no longer deserve immediate attention. Keep the list short, ideally three to five items, and write it down where the assistant can find it. A long list of exceptions is the same as no protection at all.
Handle cross-time-zone requests
A request from another time zone can make a protected block look inflexible because the requester has fewer overlapping hours. The assistant should identify the overlap windows in advance and offer one of them rather than opening the whole calendar. If the request genuinely cannot fit, escalate with the trade-off stated clearly. The written trade-off also protects the assistant if the requester later disputes the delay.
For recurring global meetings, rotate the inconvenient time rather than always protecting the same region. The principal should know which recurring commitments are immovable and which can rotate. A fair rotation reduces resentment and makes the focus block easier to defend in every region. The assistant can keep the rotation schedule beside the calendar policy.
Measure interruptions rather than blame
Track how often a focus block is moved, shortened, or cancelled, and record the reason. The pattern will show whether the problem is a few urgent exceptions or a culture that treats all time as available. Do not use the count to criticize the principal or the assistant. Use it to decide whether the policy needs a clearer exception or a different time.
Also track what the protected time produced. A block that consistently generates a finished document, a decision, or a reviewed plan is earning its place. A block that is never used for its stated purpose may need a different design. The measure should connect the time to an output, not just count the hours.
Revisit the block design quarterly
Every quarter, compare the block schedule with the principal's actual priorities and travel pattern. A block that worked in a quiet quarter may fail during board season or a product launch. Adjust the number and placement of blocks rather than abandoning the idea. The goal is a realistic rhythm, not a perfect calendar.
Share the design with the people who schedule the principal most often so they understand the trade-off. For related guidance, see our article on running a weekly calendar debt review and our executive support services. The Harvard Business Review study of CEO time illustrates how deliberately executives must allocate their hours. The evidence is useful context, not a rule that fits every office.
Key takeaways
- Give each focus block a specific name, a recurring time, and a busy status in the calendar.
- Equip the assistant with short deferral scripts for internal and external requesters.
- Define three to five exceptions that can break a block, and review the list quarterly.
- Handle cross-time-zone requests through known overlap windows and a fair rotation.
- Measure moved or cancelled blocks and connect protected time to a real output.