How to manage an executive's calendar and inbox

Pull up your principal's calendar for the last four weeks and ask one question: if a stranger read only this, what would they think the company's priorities are? For most leaders the answer is uncomfortable: recruiting, a customer escalation, three vendor calls and a lot of internal meetings nobody remembers asking for, with last quarter's priorities somewhere in the gaps.

A leader's time is the scarcest resource in the company, and the calendar is the only honest record of how it was spent. This is step 4 of our Toolkit path.

Should a Chief of Staff manage the CEO's calendar?

Usually the Chief of Staff owns the rules for the CEO's calendar and an executive assistant does the scheduling. You decide, with your principal, what their time goes to, who can book them and which time is protected. An executive assistant, if there is one, runs the calendar inside those rules: booking, moving, travel and logistics.

The split follows the two roles: the executive assistant owns the leader's time and logistics, and the Chief of Staff owns priorities and follow-through. Our guide to the Chief of Staff vs executive assistant sets out the full division. Employers still ask for it: 20% of the postings in the Chief of Staff Network's 2026 Pathways Report mention gatekeeping executive time. Most of those mean deciding who gets the leader's time; some mean doing the scheduling too, which usually signals a hybrid role.

In a hybrid role, or when there's no assistant, you do all three columns. Write the rules down anyway, because rules on paper are how you hand the scheduling to someone else later. If your principal has an assistant, book thirty minutes with them to agree the table and a weekly slot to look at the next two weeks together.

Owning the rules makes you the person who says no, and a department head who can't get thirty minutes with the CEO will blame you. I'd make the rules visible to the leadership team, so the no comes from the rules and everyone can see they apply to everyone.

How do you set a time budget and booking rules?

Agree with your principal what share of their time each priority and each kind of work should get this quarter, then write a short set of booking rules that make the budget happen: who can book them, for how long, on which days, and what needs a reason. Review the budget each quarter and audit the calendar against it.

Without a budget, the calendar fills in the order requests arrive. A request is concrete, has a person attached and wants an answer today, while a priority never asks for a meeting. A budget gives every request something to be weighed against: yes to this meeting means less of priority two.

# [Principal]'s time: budget and booking rules · [quarter]

## Budget (share of working time)
| Category | Target % | Notes |
| --- | --- | --- |
| Priority 1: [name] | | |
| Priority 2: [name] | | |
| Priority 3: [name] | | |
| Running the company | | Leadership meeting, 1:1s |
| People | | Hiring, development |
| External | | Customers, investors, board |
| Focus time | | Protected, named for the work |
| Buffer | | Unplanned, but planned for |

## Booking rules
- Who can book directly: [e.g. direct reports, for 1:1s and urgent items]
- Who requests through [EA / CoS / form]: everyone else
- Default lengths: [25 / 50 min]; 15 min for a quick decision
- Every meeting needs: a purpose line and what [principal] must decide or do
- Meeting days: [e.g. internal meetings Mon to Wed, external Thu]
- No meetings: [e.g. before 9:30, Friday afternoon]
- Recurring meetings: reviewed every quarter; no review, no renewal

## When rules conflict
- Priority work beats internal meetings
- [Principal]'s commitments to their family and health are not negotiable
- The Chief of Staff decides within these rules and tells [principal] after

# CEO's time: budget and booking rules · Q3

## Budget (share of working time)
| Category | Target % | Notes |
| --- | --- | --- |
| Priority 1: Pricing project | 15 | Two named morning blocks a week |
| Priority 2: Customers | 15 | Two calls a week, on Thursdays |
| Running the company | 25 | Leadership meeting and 1:1s; three recurring meetings move to written updates |
| People | 10 | Hiring, mostly final interviews |
| External | 10 | Investors and board |
| Focus time | 10 | Named for the work it protects |
| Buffer | 15 | Unplanned, but planned for |

## Booking rules
- Book directly: direct reports, for 1:1s and urgent decisions
- Everyone else: request through the executive assistant
- Default lengths: 25 and 50 min; 15 min for a quick decision
- Every meeting needs a purpose line and what the CEO must decide or do
- Customer calls: Thursdays, booked by sales through the assistant
- 1:1s with direct reports: 25 min weekly, plus one 50-minute session a month
- No meetings: before 9:30, or on Friday afternoons

## When rules conflict
- Pricing blocks beat internal meetings
- Family and health commitments are not negotiable
- The Chief of Staff decides within these rules and tells the CEO after

There's no split that works for every leader, and I'd be wary of anyone who gives you one. The budget follows the priorities and the stage of the company. Draft it with your best guess at the numbers, then ask your principal to change them, so the budget is theirs before you audit against it.

A worked example: from a wish to rules

This is a labeled illustration, and the example above shows where it ends up. The CEO of a 120-person company says she wants "more time with customers and on the pricing project". Your first draft gives hiring 15% and buffer 10%. She moves hiring down to 10% and buffer up to 15%, and now the budget is hers.

In the rules, direct-report 1:1s drop from 50 minutes to 25 each week, and the arithmetic forces one hard call: running the company was taking about 40% of her time, so three recurring internal meetings have to go or move to written updates. That conversation is where the budget becomes real.

Judgment calls on the budget

When your principal breaks their own budget, ask whether the budget was wrong or the week was unusual, and change one or the other. A budget the leader ignores every week teaches everyone the rules are optional. I'd give exceptions to direct reports who need a decision this week and to the board, and to almost nobody else. A founder raising money may spend half their time with investors for six weeks, so write a seasonal budget with an end date.

The shape shifts with the principal. A VC partner's budget splits by deals, portfolio and network. A functional leader's leans internal, with a share for the CEO's priorities, and across time zones booking rules need meeting windows as well as days.

[SCOTT: what the CEO's week at Spring was supposed to go to, and what it actually went to]

Sofia Badalamenti, Chief of Staff to Nihal Mehta at Eniac Ventures, described two rules on our podcast worth copying. They set a high bar for in-person meetings and move almost everything else to email. And each Monday they put an invite on the calendar laying out the week's priorities by focus area (deals, the portfolio, the network and, when it's on, fundraising), so the week's plan sits where both of them see it every day.

Share the booking rules with the leadership team, and many requests sort themselves out before they reach you. Then put a weekly look-ahead, the next two weeks against the budget, on the agenda of your weekly update or your 1:1.

How do you run a calendar audit?

Take the last four weeks of your principal's calendar, tag every meeting by which priority it served, and compare the totals with the time budget. The audit takes about two hours. Expect it to start the most useful conversation you'll have with your principal that quarter.

One week is too easy to explain away, and a quarter is too much to tag by hand. Use the company's current priorities as categories, then add four more: running the company, people, external and "none of the above". The size of that last category is usually the finding.

# Calendar audit: [principal] · [dates, 4 weeks]

## 1. Categories
- Priority 1: [name]
- Priority 2: [name]
- Priority 3: [name]
- Running the company: leadership meeting, 1:1s with direct reports
- People: hiring, development, culture
- External: customers, investors, board, partners
- None of the above

## 2. Totals (hours over 4 weeks)
| Category | Hours | % of meeting time | Budget % | Gap |
| --- | --- | --- | --- | --- |
| Priority 1 | | | | |
| Priority 2 | | | | |
| Priority 3 | | | | |
| Running the company | | | | |
| People | | | | |
| External | | | | |
| None of the above | | | | |
| Focus time (protected, used) | | | | |

## 3. Patterns
- Meetings with no agenda: [count]
- Recurring meetings nobody has reviewed in 6 months: [list]
- Meetings where [principal] wasn't needed: [list]
- Longest stretch without a meeting, by week: [hours]

## 4. Recommendations (max 5)
1. Stop:
2. Shorten:
3. Delegate to:
4. Protect:
5. Add:

Bring the totals to your principal before your recommendations. Leaders argue with advice about their time, but they rarely argue with their own calendar, and once they react to the numbers the recommendations become their idea.

Calendars drift for structural reasons. Recurring meetings get added when a problem appears and rarely removed when it's solved. Delegation that never finished shows up as attendance: if the head of partnerships owns a relationship, the CEO shouldn't be on every call about it. Itamar Melamed, Senior Director and Chief of Staff at Empathy, described on our podcast reading his CEO's calendar for patterns and asking about repeated items, and using it to anticipate, such as planning a recovery day after a big trip before the CEO thinks to ask.

A worked example: reading the totals

Another labeled illustration. The audit of your CEO's last four weeks shows 128 meeting hours. The top priority, which the budget gave 25%, got 9%. "None of the above" was 22%. Of 14 recurring meetings, five haven't been reviewed in six months, and partnership calls took 11 hours with the head of partnerships in every one.

Your five recommendations follow from those lines. Stop two of the unreviewed recurring meetings. Shorten the weekly product review from 60 to 30 minutes. Delegate the partnership calls, with a monthly summary. Protect two named blocks a week for the top priority. Add one customer call a week. You bring the table first, and the CEO spots the 9% before you mention it.

Judgment calls after the audit

Leave room for some "none of the above". A coffee with a new manager or an hour at a team event may serve no listed priority and still be time well spent, so I'd keep a small allowance for it. When a recurring meeting is cut, the explanation should come from your principal. Around month three the calendar drifts back toward its old shape, so put the next audit on the calendar now. Our guide to a Chief of Staff's day suggests the same exercise on your own calendar.

If your company allows it, an assistant can do the first pass of tagging from a calendar export. Remove private event titles first, and check every tag, because the assistant can't know that "coffee with Sam" was a hiring conversation.

You are helping a Chief of Staff audit an executive's calendar.

Below is a 4-week calendar export (title, date, length, attendees), with private items removed: [paste]

Our priorities this quarter: [list 3]
Other categories: running the company, people, external, none of the above.

1. Tag each meeting with one category. If you can't tell, tag it "unclear" and say why.
2. Total the hours by category and as a share of all meeting time.
3. List recurring meetings, with total hours each over the 4 weeks.
4. List meetings with more than 8 attendees.
Do not recommend changes yet. I'll review the tags first.

Read the "unclear" list first: it shows the meetings nobody can explain, including you. This week, export four weeks of your principal's calendar and tag it, and don't recommend anything until your principal has seen the totals.

How do you protect a leader's focus time?

Book it first, name it for the work it's for, and decide in advance which meetings are allowed to move it. Focus time that's booked last, labeled "hold" and moved for any request will be gone within a month.

Blank space on a calendar reads as available, and anyone with booking access will fill it in good faith. A block named "Q1 plan: draft pricing memo" is harder to take than one named "focus", because whoever moves it can see what they're displacing.

Melinda Munroe, Chief of Staff at Nexla, described on our podcast blocking time for her own project work and letting people schedule over it when a call really needs her; the blocks still show her the week at a glance. I'd copy that middle ground, because rigid blocks get resented and resented blocks get ignored. Lauren Stein, Chief of Staff at GrowthLoop, described on our tools episode a tool that rearranges movable meetings into longer focus blocks, which works best once the rules about what's movable are clear.

Name every focus block for the work it protects. Blank space reads as available.

Four rules that keep focus time alive

1. Book it before the quarter starts, at the times your principal actually thinks best.
2. Name it for the specific work: the memo, the plan, the hiring decision.
3. Set the bar for moving it, for example only the board, a key customer or an emergency, and never twice in the same week.
4. Check it in the weekly look-ahead. If a block was moved, rebook it the same week.

A leader with protected time is slower to reach on some days. Say so to the leadership team so nobody reads it as being ignored. Before the week is out, rename every focus block on your principal's calendar for the next two weeks with the work it's for.

How do you manage an executive's inbox?

Agree written triage rules with your principal: which emails you or the assistant handle, which you draft for them, which they must see, and how fast each kind gets an answer. Then sort the inbox into those groups every day. Never send in your principal's name without their approval until they've told you, in writing, which kinds of email you can send alone.

Inbox access is the most trust-heavy thing a principal gives you: compensation, board conversations, personal matters and people they're worried about. Read what you need for the job, act only within the rules, and flag anything that needs a sensitive judgment. A leader whose inbox has been sorted reads the ten that matter, and the hours saved go back to work only they can do.

# Inbox rules: [principal] · agreed [date]

## Handle and file (no need to show [principal])
- Scheduling requests: apply the booking rules
- Newsletters, notifications, vendor pitches: file or decline
- Internal FYIs with no ask: summarize in the daily digest

## Draft for [principal] to approve
- Replies to direct reports on decisions already made
- Thank-you and follow-up notes
- Introductions [principal] has agreed to

## [Principal] must see (flag same day)
- Board, investors, key customers: [names or domains]
- Anything about a person's pay, performance or health
- Legal, press, regulators
- Anything you're not sure about

## Response times
- Flagged: same day
- Drafts: within 24 hours
- Everything else: within 2 working days, or decline

## Sending
- [Principal] approves every email sent in their name, except: [list agreed categories]
- After-hours sends are scheduled for [8:00] the next working morning

Nihal Mehta, co-founder of Eniac Ventures, said on the same episode that he writes plenty of email at night but schedules it to send in the morning, so his team isn't working at night just because he is. A leader's send time sets everyone else's working hours.

If your principal has an executive assistant, they usually own the triage and you own the rules and the drafts that need judgment; agree it before you both start reading the same inbox. Our AI setup guide covers connecting an assistant to email safely.

How do you manage your own time as a Chief of Staff?

Give your own week the same treatment you give your principal's: a budget, booked thinking time and a few rules. Book your thinking and writing time first, set your working hours and tell people what they are, and plan your time off with a written handover. Your judgment work is the first thing a full calendar squeezes out.

Your calendar fills from three directions: most of what your principal attends, your own projects, and everyone who wants a word with the leader and comes to you first. Emily Sander, an executive coach and longtime Chief of Staff advocate, described on our podcast about strategy and operations how a Chief of Staff moves in and out of strategy and operations, a motion she compared to a porpoise surfacing and diving. Earlier-stage companies pull you into operations, and as the role matures you lift out into strategy.

Check your own week every quarter. If operational firefighting fills more of it than you and your principal agreed, that's a conversation about your mandate, and better time management won't fix it. Our guide to a Chief of Staff's day has a weekly calendar template built around this.

Melinda Munroe, a working mom, described in the same conversation deciding when she works best, telling people, and stepping away from anything that can wait. When things come up that you can't control, her answer was to give yourself some grace and over-communicate. Put your working hours in your calendar and chat status, and say in your weekly update when you'll be offline. This week, put two blocks of thinking time on your own calendar for next week, named for the work.

You can take real time off in this role with a handover written a week before you go: what's in flight, who decides what while you're out, and what can wait. Our guide to context management covers handing over context, including what to keep out of writing.

# Out of office: [dates] · Back [date]

## While I'm out
- [Principal]'s calendar and inbox: [name] applies the usual rules
- Decisions within my remit: [name] decides; [principal] for anything bigger
- Urgent only: [how to reach me, and what counts as urgent]

## In flight (owner while I'm out)
| Item | Status | Next step | Owner | Can it wait? |
| --- | --- | --- | --- | --- |
| | | | | |

## Meetings I run
- Leadership meeting [date]: [name] runs it; agenda is ready in [link]
- [Other]: cancelled / [name] covers

## When I'm back
- First morning: 30 min with [name] to hand back

What can AI do with a calendar and inbox today?

An AI assistant connected to a calendar and inbox can brief your principal on tomorrow's meetings, tag a calendar for an audit, check next week against the time budget, pull asks and commitments out of email threads and draft replies. The decisions about whose time comes first and what gets sent stay with people.

A daily brief that used to take you twenty minutes to assemble takes two minutes to check, and the weekly look-ahead happens every week because nobody builds it by hand. The risks are an assistant that sends in your principal's name, or that reads private calendar entries and repeats them where they don't belong.

I'd start with Claude, but you can pick any tool you prefer or your company allows; Claude and ChatGPT both connect to the common calendar and email suites once your admin turns the connections on. Connect the calendar first, with read access, and keep email on read and draft for at least the first month. Our AI setup guide walks through the connections and how to agree all this with an executive assistant. The weekly look-ahead is the best first job.

You are helping a Chief of Staff plan an executive's week.

Read [principal]'s calendar for next week. Use the time budget and booking rules below.

[paste budget and rules]

1. Total next week's meeting hours by budget category and compare with the targets.
2. List meetings that break a booking rule (no purpose line, wrong day, too long, no decision needed from [principal]).
3. List focus blocks and say whether each is named for specific work.
4. Suggest up to 3 changes, each with the reason from the rules.
Do not move, cancel or accept anything. I'll decide.

Keep the last line in every calendar prompt. An assistant that can read the calendar should still leave every change to you or the person who owns the scheduling.