Define the audit's decision rights
A calendar audit is useful only when the assistant knows which changes can be made without asking. Write down the meeting types, the protected blocks, and the people whose requests always need the executive's view. The assistant can then resolve a conflict inside those rules instead of escalating every overlap. The rules should be reviewed with the executive rather than inferred from habit.
Separate the calendar owner from the calendar gatekeeper. The owner keeps the week coherent and surfaces trade-offs; the gatekeeper decides who deserves access. An assistant who quietly rejects meetings may be acting with good intent and still be making a judgment that belongs to the executive. The audit should make that boundary visible in the weekly note.
Record the executive's default preferences, such as no meetings before a certain hour or a travel buffer after a red-eye. These are not absolute rules, and the audit should show when they are broken. A preference that is never documented becomes a source of friction each week. A short written standard makes the exceptions easier to explain.
Write the audit rules in one page that the executive can review each quarter. Include the meeting types the assistant may move and the ones that always need a decision. Name the backup approver for the week the executive is away. A written rule is easier to follow than a recollection of last month's preferences.
Audit for conflict, not for preference
Start the audit with hard conflicts: two meetings at the same time, a travel booking that cannot be met, or a preparation window that disappears. These are objective problems that the assistant can fix or escalate with evidence. Do not begin with meetings the assistant personally finds unnecessary. That path turns the audit into a taste exercise.
Then review soft conflicts, such as back-to-back meetings with no transition or a decision meeting placed after a long external session. Mark them as risks rather than errors. The executive may choose to keep the sequence because the relationship matters. The audit should inform that choice, not remove it.
Check the week against the executive's stated priorities. If a major decision has no preparation time while a low-value recurring meeting keeps its slot, surface the trade-off. The assistant can propose a change, but the executive should decide what gives way. A weekly audit is a decision aid, not a silent reallocation of attention.
Use a simple conflict scale so the assistant does not have to describe every overlap in prose. Mark a hard conflict, a soft conflict, and a watch item. The executive can then scan the week and decide where to spend attention. The scale should stay stable so week-to-week comparisons mean something.
Protect focus blocks and recovery time
Identify the blocks the executive uses for writing, review, or thinking, and treat them as real appointments. A focus block that can be moved for any request is not protected at all. The audit should show how often those blocks were shortened or cancelled in the past week. That count is more useful than a general complaint about busyness.
Check the time between high-intensity events. A back-to-back sequence across time zones can leave no room to eat, prepare, or recover. The assistant should flag the sequence before the week begins, not after the executive is already tired. A small buffer is easier to defend when it is attached to a specific commitment.
Review the recovery time after travel and late calls. A meeting placed too soon after an international arrival may look efficient on paper and fail in practice. Record the actual arrival time and the first commitment, then show the gap. The executive can decide whether the gap is enough.
Put the protected blocks on the calendar as appointments with a purpose, not as blank space. A blank block is the first thing a request will take. Review the blocks that were lost and ask whether the trade-off was worth it. That conversation is more useful than a general instruction to protect focus time.
Publish changes with a named owner
Every change made during the audit should have an owner and a reason. The owner may be the assistant, the chief of staff, or the executive. The reason should be short and specific, such as a conflict, a travel buffer, or a preparation requirement. A change without a reason is difficult to defend when someone asks why the meeting moved.
Tell the affected people once, through the approved channel, and include the new time and the reason they need. Do not let the executive discover a change from a third party. If a change affects an external commitment, confirm that the other side received it. The audit is not complete until the calendar and the people agree.
Keep a weekly log of changes and the decisions behind them. The log helps the next audit see whether the same conflict keeps returning. It also protects the assistant when a request is challenged later. A short record is enough; the goal is traceability, not a second calendar.
Send the weekly change note to the executive and the chief of staff at the same time. Include the changes that were not made and why. A rejected request is still useful information for the next week. The note should not become a forum for relitigating every meeting.
Close the loop with the executive
End the audit with a one-page note: the conflicts found, the changes made, the decisions still open, and the risks for the coming week. Put the most important trade-off at the top. The executive should be able to read it in a few minutes and give a clear direction. A long report that repeats the calendar is not a close.
Ask for a decision only where the assistant cannot act within the written rules. That keeps the conversation focused on the real trade-offs. If the executive wants to change a rule, record the new version and the date. The next audit should apply the updated rule rather than relitigating it.
Review the audit itself after a month. Is it catching the same conflicts, or is it producing a stable week? Are the focus blocks surviving? Is the executive spending time on decisions that should be delegated? A good audit reduces the number of surprises, not the number of meetings.
Keep the audit to a fixed day and time so it does not become an emergency exercise. A thirty-minute review on Friday can set the next week before the requests arrive. Cancel it only when the executive is traveling, and replace it with a written note. The rhythm matters more than the length.
Related resources
Read also: executive office coverage plan and context switching research.
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation