Calendar recovery
Key takeaways
- Inventory displaced work before opening new time.
- Protect preparation and decision blocks separately.
- Tell affected stakeholders what changed and why.
Operating data
Playbook
A recovery day is not an empty calendar. It is a deliberately designed bridge between an unusually demanding period and the executive's normal operating rhythm. Before moving meetings, the assistant inventories unfinished decisions, promised replies, reading, expenses, and preparation that accumulated during travel or a launch.
Classify each item as executive-only, delegable, time-sensitive, or safe to defer. Then reserve separate blocks for decisions, deep preparation, short approvals, and personal recovery. The calendar control service can help formalize these rules so a recovery day does not become an improvised cancellation exercise.
The assistant may gather context, propose moves, and draft stakeholder updates. The executive still chooses which relationships or deadlines justify an exception. When a new urgent request arrives, show exactly which recovery block it would displace and what consequence follows rather than compressing the whole day silently.
Keep a small re-entry brief with open commitments, changed assumptions, owners, and the next decision. Review it at the start and end of the day. Microsoft's guidance on focus plans offers useful product mechanics, while the executive's commitments determine the actual priority order.
Afterward, compare planned recovery work with what was completed and note which meetings or requests repeatedly consume the buffer. That evidence improves future travel schedules and launch calendars. Teams that need a durable ownership model can request a tailored support plan.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.
