The EA's Calendar Philosophy
An effective EA does not just fill calendar slots — they act as a scheduling strategist, ensuring that the executive's time reflects the organization's priorities rather than whoever called last. This requires a clear understanding of the executive's goals, a working scheduling policy, and the authority to enforce it on the executive's behalf.
Without a documented scheduling policy, an EA defaults to filling available slots rather than protecting the structure that makes the executive most effective.
Core EA Calendar Management Principles
- Maintain a documented scheduling policy: what meeting types the exec takes, with whom, and at what frequency.
- Protect morning blocks for strategic work before external requests begin.
- Cluster external meetings (board, investors, media) on designated days.
- Build travel time and recovery into the schedule — back-to-back across time zones is not sustainable.
- Conduct a weekly calendar review with the executive to align on upcoming commitments and flag conflicts.
- Never schedule an executive at more than 70% of available hours — the unscheduled space is not wasted, it is reserve capacity.
The Scheduling Policy
The scheduling policy is the EA's operating manual. It answers: which meeting types can be scheduled without executive approval? What are the time restrictions for different meeting types? Who gets direct access, and who goes through the EA? What is the standard notice period for meetings?
A well-designed policy allows the EA to handle the vast majority of scheduling requests autonomously — and to handle them in a way that the executive would endorse.
The thirty percent buffer — keeping at least thirty percent of the executive's calendar unscheduled — is not slack. It is the space for the unexpected important meeting, the crisis that requires immediate attention, and the thinking time that produces the decisions the organization needs.
Managing Travel and Time Zone Complexity
Executive travel creates temporary calendar complexity that requires proactive management. Building travel time, airport transit, and recovery time into the schedule — not just the event itself — prevents the collapse of the day around a red-eye flight. For distributed organizations, see our related guide on managing time zones in Google Calendar for distributed teams.
How Schedule Calendar helps
EAs managing an executive's schedule often work from their own computer while monitoring the executive's calendar. Schedule Calendar's popup view on the EA's own browser shows their upcoming tasks and meetings — which is the execution layer for the scheduling support work. For an EA who needs to check the executive's calendar specifically, they would use Google Calendar's shared calendar view, while Schedule Calendar covers their own scheduling context.
Frequently asked questions
Maintain a documented scheduling policy that covers which meetings the executive takes, with whom, at what frequency, and at what times. Protect morning blocks for strategic work. Cluster external meetings on designated days. Keep at least thirty percent of the calendar unscheduled as reserve capacity. Conduct a weekly review with the executive to align on upcoming commitments and flag potential conflicts.
The policy should specify: which meeting types the EA can schedule without approval, time of day restrictions for different meeting types (no external meetings before 9 AM, for example), standard meeting durations for recurring categories, notice period requirements, who can access the direct calendar versus who goes through the EA, and how to handle same-day urgent requests.
A minimum of thirty percent unscheduled time is a widely cited benchmark for executive calendars. This buffer accommodates unexpected urgent meetings, provides thinking and preparation time, and reduces the cognitive load of a completely packed schedule. Executives who consistently run at ninety to one hundred percent scheduled capacity make lower-quality decisions and have less capacity for unexpected demands.
Block focus time as a recurring event in the executive's calendar, marked as busy. Give it a descriptive label (Strategic thinking, Preparation, Do not schedule) so requestors understand the nature of the block. Maintain the block consistently — an EA who allows focus time to be routinely overridden sends a signal that the protection is not real. Escalate conflicts to the executive only for genuinely important exceptions.
The scheduling policy should specify the threshold for last-minute requests. Requests that meet the threshold for urgency (as defined in the policy) get triaged for same-day or next-day scheduling. Requests that do not meet the threshold are offered the next available standard slot. An EA who handles this consistently — with clear communication — educates requestors about the lead time required without requiring executive involvement.
Block travel time, airport transit, hotel check-in, and recovery time around travel events — not just the event itself. A flight that lands at 6 PM should not be followed by a dinner meeting at 7 PM without a recovery buffer. Add time zone information to events during travel periods so the executive sees the correct local time rather than their home timezone. Brief the executive on the travel-week schedule a few days in advance.