Auditing Last-Minute Meeting Request Handling in an Executive Office

Key takeaways

• Sample unscheduled requests, including the ones that were declined.
• Check the decision, the reason, and the displaced commitment together.
• Report the requests that were answered without a specific next step.
• Verify that the confirmation reached the requester and the CEO.

Question and scope

This audit asks whether an executive office can show how it handled an unscheduled meeting request and what the decision displaced. The unit is one request tied to one requester and one executive day. The review examines the first ask, the decision, the confirmation, and the calendar change. It does not judge whether the meeting was worth holding.

Set the scope to one executive office and a fixed period. Record the intake channels, the decision rules, and the calendar system. If the office changes its rules during the window, separate the periods. A rule change can make an old decision look inconsistent with the current standard.

Include requests that were accepted, declined, deferred, and never answered. Include at least one request from an internal colleague and one from an external investor or client. Record the requester type and the time. The sample should show the full range of handling.

Include a request that arrived through a channel outside the formal intake, such as a text or a hallway conversation. These requests are easy to miss and hard to audit. Record the channel and the time. The sample should show the whole intake.

What the sources establish

Microsoft's Work Trend Index describes the volume of meetings and messages, which establishes the pressure but not a local standard. Harvard Business Review's meetings material discusses preparation and the work that meetings displace. BLS occupational data describes the assistant role but not a benchmark for one office. The sources support a process audit, not a productivity claim.

The sources do not establish a required response time or a rule for accepting an unscheduled meeting. They also do not tell the office which requests deserve priority. The audit therefore measures whether the office followed its own rules and whether the requester received a usable answer. Record the requester type beside the decision.

The sources also support separating the decision from the communication. A good decision that is never confirmed can still fail. The audit should review both. A confirmed meeting without a preparation owner is also incomplete.

Definitions, measures, and sampling

Define an unscheduled request as a meeting ask that was not on the executive's calendar when it arrived. Define a decision as an acceptance, a decline, a deferral with a date, or a routing to another owner. Define a complete handling as one with a recorded decision, a reason the office can share, a confirmation, and a record of the displaced commitment. Record the requester type beside the decision.

Measure the time from the request to the first response, the time to the decision, and the time to confirmation. Report the requests with no response and the requests with no next step. Keep the denominator as requests, not meetings. One request can produce several messages.

Record the evidence type for each case, such as an email, a calendar note, or a call log. A verbal decision is weaker evidence than a stored one. The audit should show the evidence type beside the result. The pattern of evidence often explains the pattern of gaps.

Record whether the decision was made by the assistant, the chief of staff, or the executive. The decision owner shapes the reason and the speed. Report the owner and the rule. The audit should not treat every decision as the assistant's.

Sample requests from the inbox, the assistant's log, and the calendar changes. Include requests that arrived during a board cycle and requests that arrived on a quiet day. Include at least one request that was declined and one that was accepted with a shortened format. Record the requester type and the staff role.

Collect the request, the response, the calendar change, and the confirmation. Mask sensitive content that is not needed to classify the case. If the decision was made in a conversation, record the time and the people. A verbal decision may be real and still leave weak evidence.

Include requests that were routed to another owner, because routing is a valid handling path. Record the owner and the time. The audit should not treat every non-meeting as an unanswered request. Record the requester type beside the decision.

Include a request that was repeated after no answer. A repeat is a sign that the first handling failed. Record the first and second request times. The gap between them is part of the response measure.

Verification pathway

Check whether the request included the purpose, the participants, and the timing constraint. A request without those details is hard to decide. Record what was missing and whether the assistant asked for it. The audit should show whether the intake was complete.

Confirm that the decision was recorded with a reason the office can share and the commitment that moved. A decision without a displaced commitment may hide the cost. Record the block and the new time. The calendar should match the decision note.

Review the confirmation sent to the requester. It should include the time, the format, the participants, and the preparation. A vague confirmation invites a no-show or a second request. The audit should verify that the requester acknowledged it.

Check whether the requester received a confirmation with the participants and the preparation. A time without the other details can still produce a failed meeting. Record the confirmation and the reply. The audit should review the whole message.

Scheduling and relationship side effects

Check whether the accepted request displaced a preparation block or a recovery period. Record what moved and whether the executive approved it. A meeting that is added without protecting the preparation may cost more than it saves. The audit should show the trade-off.

Review the requests that were declined. A decline with a clear alternative preserves the relationship; a bare no may damage it. Record the alternative offered and the requester's response. The audit should not assume that a decline is a failure.

Check whether the same requester made repeated requests in the period. A pattern may point to an unclear intake path or a relationship that needs a standing cadence. Record the count and the handling. The pattern is more useful than a single case.

Analysis, reporting, and limits

Report the number of requests, the share with a first response, the share with a decision, and the share with a confirmation. Break the results down by requester type, day, and staff role. Report the requests with no next step separately. A single response rate can hide a group of requests that were never decided.

Inspect the failures for patterns. A cluster of missing purposes may point to the intake form, while a cluster of unconfirmed acceptances may point to the handoff. Choose one change, such as a required request template or a confirmation checklist. Do not rank assistants by response time when their request mix differs.

Report the time from the request to the calendar change, not only the time to the first reply. A fast reply that leaves the meeting unbooked is not a resolution. Show the median and the longest case. That measure is closer to the requester's experience.

Report the share of requests that displaced a protected block. A high share may mean the office accepts too much or protects too little. Show the block type and the approver. The pattern points to the next rule change.

The audit cannot prove that the meeting was necessary or that the decision was the best one for the company. It also cannot capture a request that was handled entirely in a hallway conversation. The report should state those limits and avoid treating the inbox as the whole office. Record the requester type beside the decision.

Set a repeat audit date and keep the definitions stable. Assign the correction to the executive office lead and give the assistant a clear decision rule. The next audit should test whether the same request type or the same step fails again. A useful result is a request path that the requester and the CEO can both trust.

Sources

1. Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
2. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
3. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
4. Business Formation Statistics, U.S. Census Bureau.
5. Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
6. Productivity Statistics, OECD Data Explorer.
7. World Development Indicators, World Bank DataBank.
8. ILOSTAT Labour Statistics, International Labour Organization.
9. 2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
10. The economic potential of generative AI, McKinsey Global Institute.
11. Creating helpful, reliable, people first content, Google Search Central.
12. Search Engine Optimization Starter Guide, Google Search Central.
13. Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.
14. Microsoft 2024 Work Trend Index Annual Report.
15. Harvard Business Review, meetings.
16. BLS, Secretaries and Administrative Assistants.

Related research

• Handling a Last-Minute Investor Meeting Request When the CEO's Day Is Already Full
• Measuring the cost of context switching in an executive calendar
• Running a Weekly Executive Calendar Audit Without Becoming a Gatekeeper

Apply the research

Use the finding to frame one question for your own team: which support work is currently invisible, and who should own the next step? A scoped consultation can turn that question into a practical role. Write the question down before the meeting. Name the person who owns the next step.