Calendar Management for Executive Assistants: Own vs. Automate

Almost everything written about calendar management for executive assistants treats it as a skill problem. Color-code the blocks. Add the dial-in. Build in a buffer. Good advice, all of it, and none of it touches the question that actually decides how an executive’s week goes: which parts of this work should reach a person at all.

I’m Nir, co-founder of Catch. We build an assistant that takes admin work off executives’ plates, and the calendar is the heaviest piece of it. In almost every company we work with I see the same thing. The assistant is spending real hours on time-zone arithmetic and chasing people who haven’t replied, and barely any time on the calls only they can make. The arithmetic arrives constantly, so it wins.

Read this one together, executive and assistant in the same room, because the decision belongs to both of you. What follows splits the calendar into three buckets: judgment that needs real context on the business, mechanical work nobody should still be doing by hand, and a grey middle that shifts depending on how much context the assistant has. Where you draw those lines will matter more than any single tip.

Calendar management for executive assistants, split three ways

Executive assistant calendar management gets described as one job. It’s three, and they have very little in common.

1. Judgment. Who gets the hour. What gets declined. Whose meeting moves when two things collide. Decisions about priority and relationships, which need someone carrying the executive’s full context.
2. Mechanics. Time-zone conversion, conflict detection, confirmations, chasing non-responders, rebuilding a day after one change lands. Repetitive, high-volume, genuinely low-judgment.
3. The grey middle. Anything whose answer is “it depends how well the assistant knows this executive.” A standing one-to-one. A buffer before a board call. An inbound request from someone in the executive’s network.

Most calendars get managed as though all three were the same category of work, and that’s why the hours land where they land. Mechanics never stop arriving, so they soak up the time, and the judgment gets made in a hurry somewhere in between.

Bucket one: the judgment that needs the executive’s context

This is the part of the job that justifies the role. It also gets the least deliberate attention.

Who gets the hour

Two requests, one slot, both defensible. A customer who’s been quiet for a quarter, or a candidate for a role the executive has been trying to fill since spring. No scheduling feature answers this. It turns on what the business needs this month, which the assistant and the executive know and nobody else does.

The habit worth building: stop treating each of these as a fresh decision. Most are instances of a pattern the executive has already settled, usually without ever saying so out loud.

What gets declined

Saying no is the highest-leverage thing an assistant does with a calendar, and the hardest to delegate, because the cost of a wrong decline is lopsided. A badly declined meeting can cost a relationship. A badly accepted one costs an hour.

Which is why declines need a standing position rather than a case-by-case call under time pressure. More on building that position shortly.

Whose meeting moves when two things collide

A double-booking is mechanical to detect and political to resolve. Deciding which of the two parties gets the apology and the reschedule request is a judgment about seniority, relationship, and how many times this has already happened to them. Assistants who’ve been with an executive for years make the call in seconds, and it isn’t because they’re faster at calendars. They’re carrying context.

How to build the preference rules your executive never wrote down

Here’s the part of calendar management that pays for itself, and almost nobody does it formally. Every executive holds a set of standing scheduling positions. Almost none of them have been written down, so they live in the assistant’s head, get lost the week the assistant is away, and have to be rebuilt from scratch when the role changes hands.

Writing them down is a few hours of work, once.

Start from the calendar that already happened

Don’t start with a questionnaire. Start with the last eight weeks of the real calendar and walk it with the executive, hunting for the decisions nobody announced.

Ask about the exceptions, not the routine. Why did that Thursday meeting move twice. Why does that one person always get a full hour when everybody else gets thirty minutes. Why did that intro call get pushed three times before it finally happened, and should it have happened at all. The answers are the real preferences, and the executive is usually a little surprised to hear them said out loud.

Write them as decisions, not as preferences

“Prefers mornings” is useless. It says nothing about what to do when the only slot a key customer offers is 4pm on a Friday.

Write each one as a decision with a condition and a default:

• Investor and board requests: accept within the week, move anything internal that collides.
• Inbound sales calls: decline politely by default, forward to the relevant team lead.
• New customer intro calls: thirty minutes, Tuesday to Thursday, never the first slot of the day.
• Internal one-to-ones: moveable, but never cancelled twice in a row with the same person.
• Travel days: no calls in the ninety minutes either side of a flight.
• Deep work: two protected blocks a week, and the executive picks which, not the calendar.

Six to fifteen of these will cover the overwhelming majority of what arrives.

Name the things that are never a rule

Just as useful: write down the categories where the executive wants to be asked. It’s usually a short list. Anything touching a direct report’s performance, anything involving a named list of people, anything that moves a customer meeting. Being explicit about where the assistant should stop is what makes the rest of the autonomy comfortable.

Keep it alive

A preference sheet written once and never revisited goes wrong inside a quarter, because priorities move. The maintenance habit that actually sticks is small and regular: fifteen minutes on a Monday, walking the week ahead and the week just finished. What got moved that shouldn’t have. What got accepted that should have been declined. One or two lines change, and the sheet stays true.

This is also the document that makes the next two buckets safe to hand off, and the fastest way to bring a new assistant up to the context the last one had.

Bucket two: the mechanical work nobody should do by hand

This is where repeated calendar work consumes the most time.

Time-zone arithmetic

Three participants, three cities, one of which has just changed its clocks and one of which never does. Doing that by hand is slow, and it’s the most common reason a meeting lands at the wrong hour. The math has a right answer, so it shouldn’t be a person’s job.

Conflict detection

Spotting a double-booking is pattern matching across calendars, nothing more. The catch is that detecting the conflict is the easy half. Anything that flags the clash and hands it straight back leaves the assistant doing the real work: writing to both parties and negotiating the move.

Confirmations and reminders

Confirming the day before. Re-sending a dial-in somebody can’t find. Nudging the participant with a history of forgetting. Necessary, repetitive, entirely scriptable.

Chasing people who haven’t replied

An assistant can lose a surprising share of the week here. Four people were asked for availability, two answered, and now somebody has to track who owes what and nudge them at the right interval without being rude. The tracking matters, and it uses none of the assistant’s actual expertise.

Rebuilding the day after one change

One meeting moves ninety minutes and four other things stop working. The buffer before the board call is gone, the two back-to-backs on the other side of town are now impossible, and the call that was deliberately placed after the customer meeting now sits before it. Reconstructing that by hand, several times a week, is one of the most expensive habits in the job.

Booking other people’s scheduling links

Someone sends a link, the assistant opens it, reads the grid, cross-checks it against the executive’s week, clicks. A few minutes each time, dozens of times a month.

Bucket three: the grey middle

The rest of calendar management sits between the two, and where it belongs comes down to one variable: how much context the assistant has.

An assistant three weeks into the role shouldn’t be declining requests from the executive’s network, because they can’t yet tell a time-waster from a long-standing relationship that happens to look cold on paper. An assistant three years in should be declining almost all of them without asking, because by then they know.

Same logic for meeting prep, for whether a recurring meeting has stopped earning its slot, for whether an hour gets protected or released. None of these have a universal answer.

A practical test for anything in the grey middle: if the assistant can predict the executive’s answer correctly nine times out of ten, stop asking. If they can’t, keep asking, and write the answer into the preference sheet when it comes. The line moves as context builds, and it only moves one way.

The mistake runs in both directions. Executives who keep every grey-middle decision for themselves become the bottleneck in their own calendar. Assistants who take them on too early make a call the executive wouldn’t have made, and lose trust that takes months to rebuild.

Where Catch fits

Catch is an assistant that takes the second bucket outright and moves through the grey middle as it learns the executive, until the traditional assistant workload on the calendar is handled end to end. It acts rather than suggesting, and it still reminds the executive of what’s coming and flags the things that genuinely need them.

Connect Gmail or Outlook with a couple of clicks, and Catch works with Google Calendar or Outlook Calendar from there. After that:

• It spots a conflict and resolves it, which means writing to the other party and agreeing a new time rather than sending a notification and leaving the work with you.
• It schedules new meetings across several parties, confirms the time, sends the invite, and manages the participant list.
• It generates a scheduling link in seconds with real constraints attached: two specific people, mornings only, next week.
• It books inbound scheduling links on the executive’s behalf, choosing a slot against the rest of the week and the urgency of the request instead of taking the first one free.
• It modifies invites directly, adding and removing participants, shortening or lengthening meetings, accepting and declining.
• It tracks the threads waiting on someone and decides which ones genuinely need a nudge, so the chasing stops being a person’s job.
• It handles meeting prep, reminding the executive what needs doing beforehand and pulling briefs from connected tools like Notion and Asana.

There’s no rules file behind any of this. Catch builds a picture of the executive from their calendar, email, and connected tools, and sharpens it with every correction it gets: meeting lengths, who matters, which days are in the office, how much buffer this person actually needs. It acts when it has enough to act on, and comes back with a question when it genuinely doesn’t, which is roughly what a good assistant does with a new executive. Independence grows as the context does.

The calls that stay with the executive are the ones about their own priorities, which they’d want to make anyway. Everything underneath them moves. Where an executive already works with an assistant, nobody needs to be let go: the arithmetic and the chasing go away, and that time goes to the operational and in-person work a calendar never captures. Where there’s no assistant at all, Catch carries the traditional admin load itself.

A few practical details, since they tend to come up:

• You reach Catch where you already work: Slack, email, text message, iMessage, or a phone call. Voice notes work too.
• It can place real calls when a calendar problem needs one, like calling a venue to move a booking. It always says what it is, opening with “Hi, I’m the AI agent for [Name].” Emails go out signed on the executive’s behalf.
• Pricing is flat at $99 a month, calls included. No credits, no usage tiers, no per-call fees. There’s a 10-day free trial.
• On security: SOC 2 Type II, CASA Tier 2 as a Google Verified App, and data hosted in the US.

How to actually make the split

If you’re an executive and an assistant reading this together, the sequence is short.

1. Write the preference sheet. Eight weeks of calendar, the exceptions, six to fifteen decisions with conditions and defaults. Two hours, once.
2. Name the stop list. The categories where the assistant always asks first.
3. Hand over the mechanics. Time zones, conflicts, confirmations, chasing, rebuilding the day, booking other people’s links. All of it, not a sample.
4. Set the Monday review. Fifteen minutes. What moved that shouldn’t have, what was accepted that shouldn’t have been.
5. Move the grey-middle line deliberately. One category at a time, using the nine-out-of-ten test, and update the sheet when an answer changes.

Good calendar management isn’t measured by how tidy the calendar looks. It’s measured by whether the executive’s hours end up on the work only they can do, and whether everything underneath that is being handled without reaching them.

Frequently Asked Questions