Executive calendar decision rules an assistant can apply consistently

Calendar control

Key takeaways

• Capture purpose, outcome, attendees, preparation owner, deadline, and cost of delay.
• Apply this control: compare the request with protected work, buffers, travel, and decision authority.
• Escalate if the requester cannot name an outcome or an exception would displace higher-consequence work.

Operating data

Playbook

Calendar control begins by distinguishing access from entitlement to a particular time slot. For every invitation, record the requested outcome, decision owner, essential attendees, preparation owner, deadline, and cost of waiting. Then compare those facts with protected concentration blocks, travel transitions, and existing commitments. A prestigious sender does not by itself make a meeting consequential.

Use explicit dispositions: accept, delegate, shorten, move to asynchronous review, or decline. An investor update may merit direct attendance, while a project status recital can often go to a delegate with a written decision request. Preserve buffers after negotiation-heavy sessions. The Google Calendar sharing guidance explains permission options; it does not determine who should control executive availability.

Escalate when the requester cannot name an outcome, when attendee authority is unclear, or when an exception would displace work with greater consequences. Show the executive the collision rather than silently compressing the day: identify the protected block, the new request, and the tradeoff. Never invent urgency because a proposed time is close or because several people have already accepted.

Review delegated attendance, recovered focus blocks, repeated exceptions, and meetings that produced no decision. Those observations should refine the rules by meeting type, not create a blanket rejection policy. Teams implementing this discipline can use calendar control support and the meeting preparation guide to connect admission decisions with useful pre-work and follow-through.