ExecutiveSupportStaff Editorial Team | Published
The default state of an executive calendar is reactive. Meeting requests arrive, the executive or their assistant accepts them, and the calendar fills from the outside in. By the end of a reactive week, the executive has attended dozens of meetings and made forward progress on very little of the work that actually matters.
Research published by Harvard Business Review on meeting overload found that senior executives routinely attend meetings they describe as unnecessary, and that the inability to decline requests is a primary driver of calendar inefficiency. The EA's job is to apply a consistent filter before anything reaches the executive for approval.
The goal is not to minimize meetings. Some meetings are the highest-value use of the executive's time. The goal is to ensure that the meetings on the calendar are there by deliberate choice, not by default acceptance.
A workable prioritization system uses four tiers. Tier one is must-attend: board meetings, investor conversations, key client reviews, and any session where the executive's specific judgment or authority is required. These get accepted without question and receive full preparation support.
Tier two is high value: internal leadership team sessions, external relationship-building conversations, and meetings where the executive's presence is important but not irreplaceable. These get accepted by default but can be rescheduled or shortened when a higher-priority conflict arises.
Tier three is delegable: status updates, informational briefings, and process reviews where the executive's physical presence adds little that a briefed delegate could not provide. The EA should actively offer an alternative before accepting these. Tier four is decline: meetings where the executive is a courtesy invitee, meetings with no clear decision point, and vendor pitches that can be handled by the operations team.
Four questions sharpen the triage decision on any request. The first is: what decision or outcome does this meeting produce? If the answer is unclear from the meeting request, the EA should ask before accepting. Meetings without a defined outcome rarely require the executive's presence.
The second question is: can the executive's contribution be provided another way? A 10-minute briefing before the meeting, a written comment on a document, or a delegate with clear instructions covers most situations that do not genuinely require the executive in the room. The third question is: what happens if the executive does not attend? If the honest answer is "the meeting still proceeds and a decision still gets made," that is a strong signal the meeting is tier three or four.
The fourth question is: is the meeting objective clear enough to prepare for? A vague meeting title and no agenda are not just inconveniences; they are signals that the meeting is not ready for the executive's calendar yet. Sending it back for a clearer objective is a legitimate response.
Status updates that could be written communications are the most common waste. A weekly project update that covers information the executive could read in three minutes does not warrant 30 minutes on the calendar. The EA should identify recurring meetings that fit this pattern and propose a written format as a replacement.
Recurring meetings that have outlived their purpose are the second pattern. A weekly cross-functional sync that made sense during a product launch may have no remaining agenda six months later. The EA should review recurring meetings quarterly and flag any that consistently run short or where the executive reports no clear outcome.
Meetings where the executive is a courtesy attendee are the third pattern. These are meetings where the executive was invited because their name adds perceived weight, not because their participation changes the outcome. These are the easiest tier four declinations because a clear message explaining the executive's schedule constraints rarely damages the relationship.
The key to declining without damage is offering a concrete alternative immediately. A flat no creates friction. A no with an alternative (a 15-minute pre-call with the organizer, a briefed team member attending in the executive's place, or a written response to the meeting objective) respects the organizer's underlying need while protecting the executive's time.
The EA's communication should be direct and warm, not apologetic. "The executive's availability is committed for that period" is accurate and does not create an opening for negotiation. "The executive would like to be there but unfortunately cannot" invites a request to find another time.
For the systems that make this consistent, see our guide to managing an executive's calendar. For the complementary system of protecting focus time, see the guide to time blocking for executives.
| Meeting tier | Examples | EA action |
|---|---|---|
| Tier 1: Must-attend | Board meetings, investor discussions, key client reviews, strategic decisions | Accept and prepare context brief |
| Tier 2: High value | Leadership team sessions, new external relationships being built | Accept; flag if scheduling requires trade-off |
| Tier 3: Delegable | Status updates, informational briefings, process reviews | Offer delegate or async alternative |
| Tier 4: Decline | Courtesy attendee roles, meetings with no decision point, vendor pitches | Decline with alternative |
How many hours of meetings per week is reasonable for a senior executive?
The most effective senior leaders tend to keep scheduled meetings to 40 to 60 percent of their working week, with the rest protected for deep work, decisions, and unstructured time. The specific number matters less than whether the meetings the executive does attend are the right ones. An executive who spends 70 percent in meetings is not necessarily less productive than one who spends 40 percent, if the first executive's meetings are consistently high-value.
Who should make the call to decline a meeting: the EA or the executive?
The EA should handle routine declinations using a written set of criteria the executive has approved. Borderline cases, new relationship types, and any request from a senior external party should go to the executive for a direct decision. If the EA escalates every borderline case, the executive is still doing the triage work themselves, which defeats the purpose of having an EA manage the calendar.
How do you handle a stakeholder who insists the executive must attend a meeting?
The standard response is to acknowledge the request, explain that the executive's availability is constrained for that window, and offer a concrete alternative: a briefed delegate, a 15-minute pre-call, or an async written input. Most stakeholders accept a clear alternative more readily than a flat decline. The rare cases where the stakeholder continues to push should escalate to the executive for a direct decision.