Published October 22, 2026
Focus time is easy to create and easy to lose. An assistant blocks two hours on Tuesday, a colleague sees an empty slot, and the block disappears. The owner notices only when the week ends without the deep work they planned.
The usual fix is a private calendar event labeled "busy." That hides the slot but also hides the reason. When a genuine commitment needs the time, nobody knows what was displaced or who approved the change. A better workflow protects the block without making the calendar opaque.
Table of contents
- Decide what a focus block is for
- Make the block visible in the right way
- Set the move and decline rules
- Record every displacement
- Review whether the protection works
- Sources
- Frequently Asked Questions
Decide what a focus block is for
A block needs a purpose category, not a secret. Examples: writing, financial review, interview preparation, planning, or recovery after a travel day. The category can be visible to the assistant and the owner without exposing confidential content.
Record the block's flexibility:
- Fixed: only the owner can move it.
- Flexible: the assistant may move it within the same week if a higher-priority commitment appears.
- Protected external: the block supports a client or board deadline and cannot move without that stakeholder's agreement.
The category and flexibility belong in the event description or a parallel scheduling record. Without them, every conflict becomes a judgment call made under time pressure.
Make the block visible in the right way
A block titled "Focus" with no owner or rule invites negotiation. A better title names the work category and the rule: "Focus — board memo (fixed; ask before moving)." Keep sensitive details out of the public title.
If the calendar is shared with a team, use the platform's privacy setting to show busy without details, but keep a private record that the assistant can consult. Visibility to the owner and the assistant is the requirement; visibility to everyone else is optional.
Do not use false meetings to protect time. A fake attendee or a fictitious client meeting creates a record that misrepresents the calendar and can surface in an audit or a handoff.
Set the move and decline rules
The assistant needs a short decision table.
| Situation | Assistant action |
|---|---|
| Internal meeting requests the block | Offer two alternative times; do not move without owner approval |
| Client requests the block | Notify owner with the request and the consequence; wait for a decision |
| Recurring team meeting lands on the block | Move the block if flexible; record the new time |
| Same-day urgent request from the owner | Move the block; record the reason and restore time |
| Meeting accepted by someone else on the owner's behalf | Flag the conflict; do not assume approval |
The rule should say who can approve a move. "The owner" is not enough when the owner is traveling. Name a delegate and the conditions under which the delegate may act.
Record every displacement
A displaced focus block is a small loss that becomes a pattern. Keep a simple log:
- original block time
- new time or cancellation
- who requested the change
- who approved it
- reason category
- whether equivalent time was restored in the same week
Review the log monthly. If a recurring meeting consistently displaces the same block, the problem is the meeting design, not the assistant's scheduling.
Review whether the protection works
Measure three things:
- Hold rate: the share of focus blocks that remained at their original time.
- Restore rate: the share of moved blocks that were replaced within the same week.
- Interruption source: the meeting series or person responsible for most moves.
Do not measure the owner's output from the block. That turns a scheduling control into surveillance and invites gaming. The question is whether the calendar is protecting the time the owner asked to protect.
The O*NET executive administrative assistant profile includes calendar coordination as a core task. Coordination is not the same as unlimited availability. A written rule makes the difference visible.
Sources
- O*NET OnLine: Executive Administrative Assistants
- Bureau of Labor Statistics: Occupational Outlook Handbook
- U.S. Department of Labor: Hiring
- NIST Privacy Framework
Frequently Asked Questions
Should focus blocks appear as busy to the whole company?
Use the calendar's privacy setting to show busy without details. The assistant and owner need the purpose and rule; the wider company does not.
Can an assistant decline a meeting on the owner's behalf?
Only under a written rule that names the meeting types and the approval path. Declining a client or executive meeting usually requires the owner's decision.
What if the owner keeps overriding the blocks?
Record the overrides and review the pattern. The block may be at the wrong time, too long, or protecting work the owner does not actually prioritize. Adjust the design rather than blaming the calendar.
Review cadence
Review focus-block overrides every Friday and count who asked, what they offered in return, and whether the work was truly urgent. A block that is always surrendered is not protection; it is a placeholder. Adjust the block length or the exception rule before the next month, and tell the executive which commitments displaced the time.