Calendar command

A double-booking costs more than a typo

Email mistakes get forgiven. Calendar mistakes get remembered, because they happen in front of other people. Put your founder in two places at once, or book a 6am call they never saw, and every apology comes out of your credibility account. Calendar command is the second pillar of the EA job, and it has exactly one rule at its core: the founder should never be surprised by their own schedule.

Timezone-safe scheduling

You live in UTC+8. Your client lives in one of four US zones that shift twice a year for daylight saving — which the Philippines doesn't observe. 9am Eastern is 9pm Manila in summer, 10pm in winter. This is where most new VAs burn themselves.

Buffer logic and meeting hygiene

A calendar packed edge-to-edge looks efficient and performs terribly. Seniors build in air: 15 minutes between calls, no meetings inside the founder's deep-work blocks, travel time as its own calendar event, and a hard rule against back-to-back external calls where one running long torpedoes the next.

Meeting hygiene means every invite you send is complete: a specific title ("Acme Q3 renewal — pricing decision," not "Sync"), the video link or address, an agenda line, and only the people who actually need to be there. If someone else's invite arrives incomplete, you fix it before it hits the founder's calendar.

Scheduling links: when to automate, when to white-glove

The judgment call: routine and inbound requests get a link. VIPs — investors, big clients, press — get white-glove manual scheduling where you propose two or three specific slots and hold them. Sending a Calendly link to an investor reads as "you schedule around us." Read the power dynamic before you paste the link.

A conflict, handled like a pro

Note the anatomy: Dana identified which event was immovable, fixed the conflict before being asked twice, confirmed with the third party directly, and reported the new state in one message. That's calendar command.

Travel booking basics

Travel is calendar work with money attached. Build a one-page preferences doc on day one: aisle or window, preferred airlines and hotel chains, loyalty numbers, TSA PreCheck/Known Traveler number, home airport, red-eye tolerance. Then follow the sequence: propose two flight options with prices, get a yes, book, and immediately build the itinerary event — flights with confirmation codes, hotel with address and check-in time, ground transport — all in the calendar with local times at each destination.

Do this now

Build a mock founder's week. Create a fresh Google Calendar and schedule: three external calls across two US timezones (with your PH secondary clock enabled), one deep-work block protected daily, 15-minute buffers, and one flight with a full itinerary event. Then break it on purpose — add a conflicting invite — and write the Slack message resolving it, using Dana's message above as your quality bar. Screenshot the week view and save it with your message draft. This becomes portfolio evidence that you've run a calendar, not just read about one. About 25 minutes.