Auditing after-hours executive support requests against a response policy

Key takeaways

• Compare every after-hours request with the written response window rather than with an informal expectation.
• Separate true emergencies from answers given only to avoid disturbing the executive.
• Report interrupted nights, delayed tasks, and the channels that carry the requests.
• Test one policy change for two weeks and compare the same exception count.

Question and scope

This study asks whether after-hours executive support requests match the office's stated response policy and what it costs to answer the ones that do not. The unit is one request received outside the agreed business hours. The review records the time, the channel, the requester, the stated urgency, and the action taken. It does not evaluate the requester's motives or the assistant's performance.

Set the scope to one executive office and a fixed four-week window. Record the published response policy, the on-call arrangement, and the channels that are monitored after hours. If the policy changes during the window, separate the periods. A clear scope prevents the review from mixing a temporary crisis with the normal pattern.

Record the executive's normal working pattern, including travel and time-zone changes, because the same clock hour can be reasonable in one week and disruptive in another. A request at nine in the evening may be ordinary for a leader finishing a board cycle and unacceptable during a family holiday. The policy should be read in context, not as a single fixed hour. Note the week and the reason so the audit can separate a seasonal peak from a standing expectation.

What the sources establish

The Department of Labor's telework guidance describes how work outside the traditional office can blur the boundary between on and off duty. NIST access-control guidance is relevant because after-hours requests often involve confidential material opened on a personal device. The Small Business Administration's management guidance discusses written policies and clear responsibilities. Harvard Business Review's meeting and work research provides context on fragmentation, not a benchmark for response times. These sources support the need for a policy but cannot define the right window for a specific executive.

The useful local question is whether the policy and the practice agree. An office may publish a next-morning response window while the assistant answers within minutes because the executive expects it. That gap is the finding, not a reason to blame the assistant. The review should describe the gap and the consequence before recommending a change.

Ask whether the office has a written policy at all. If the rule exists only as an expectation, the audit will reveal a gap between what people believe and what they do. That finding is useful even before any change. A written policy can be tested and revised, while an unwritten one can only be debated after a difficult night. The review should quote the policy it used so the reader knows what standard was applied.

Definitions and measures

Define business hours in the executive's primary time zone and record any secondary time zones in use. Define an after-hours request as a message that arrives outside those hours and asks for an action, a decision, or a document. Define an emergency as an event that cannot wait until the next business day without a material loss. Write examples for each category so two reviewers classify the same request the same way.

Measure the number of requests, the number answered, the median response time, and the number that were true emergencies. Record the channel and whether the request was routed to the on-call person. Count the requests that were answered but could have waited. A simple count of policy exceptions is more useful than a score that combines urgency, tone, and response time into one number.

Record the device and the location used to answer each request. A response sent from a personal phone at a dinner table carries a different cost from one sent from a laptop in a hotel room. That detail is sensitive, so report it in aggregate rather than naming individuals. It helps the office see whether the on-call arrangement is realistic.

Sampling and collection

Collect every after-hours request in the window rather than a sample, because the volume is usually small enough to review. Export the messages with timestamps and remove personal details that are not needed. Record the on-call schedule and any planned travel. If a channel is not monitored, note that too, because an unanswered request may reflect the channel rather than the policy.

Ask the assistant and the executive to classify a subset independently, then compare the results. Where they disagree, discuss the example and refine the definition. That step is more valuable than adding another metric. It shows whether the policy is understood the same way by the people who send and receive the requests.

Include requests that arrived through a channel the office does not formally monitor, such as a direct text or a personal message. Those requests are often the ones that create the strongest expectation of an immediate answer. Note the channel and whether it was answered. A policy that covers only email will miss the real pattern.

Analysis and reporting

Report the requests by hour, channel, requester group, and urgency. Show the share that was answered inside the policy window and the share that was answered outside it. Separate a request that was correctly escalated from one that was handled quietly to avoid disturbing the executive. The pattern often reveals an informal expectation that the written policy does not capture.

Estimate the cost of the exceptions using the time spent and the next-day fatigue reported by the assistant. Do not invent a dollar figure if the office does not track hours. A count of interrupted nights and the tasks that were delayed is enough to start a conversation. Rank the fixes by the consequence, such as a safety issue or a repeated late approval.

Look for clusters of requests around a recurring event, such as a board meeting or a quarter close. A cluster may justify a temporary on-call arrangement rather than a permanent expectation. Report the cluster separately from the routine requests. That distinction lets the office protect the night without ignoring a predictable peak.

Compare the after-hours pattern with the office's stated on-call schedule. A request that arrives on a night with no named on-call person is a different finding from one that arrives during a scheduled rotation. Report the schedule beside the request count. That comparison shows whether the policy is resourced or only written. The answer may be a temporary rotation rather than a permanent change.

Limits and sources of error

The study cannot show whether an after-hours answer improved an outcome, because the same decision might have waited until morning without harm. The classification of an emergency is also a judgment, and a requester may label a routine matter as urgent. Report those limits and keep the raw examples so a later reviewer can test the categories. A small sample should not be presented as a general rule.

Messages may be incomplete, and a phone call may leave no record at all. The assistant may also underreport the time spent because the work happened in short bursts. Use the available record and mark the gaps. A truthful account of missing data is more useful than a complete-looking table built on estimates.

Do not treat a single missed request as proof that the policy failed. The review is about the pattern across the window, not one message that arrived at an awkward moment. Report the exceptions and the context. A fair reading of the evidence is more likely to produce a policy people will follow.

Review and next action

Choose one change, such as a clearer definition of an emergency, a single after-hours channel, or a next-morning summary for anything that can wait. Test it for two weeks. Tell requesters what changed and give them an example. The [inbox approval queue](/blog/turning-executive-inbox-approvals-into-a-tracked-queue/) can hold nonurgent requests until the next business day.

Repeat the audit with the same definitions and compare the number of exceptions. Close the review when the office can show which requests still require a night response and which were successfully deferred. Keep the policy and the evidence together. The goal is a response model that protects the executive's rest without leaving a real emergency unanswered.

Write the revised policy in the same place as the on-call schedule and the escalation contacts. A policy that lives in a slide deck will not be found at midnight. Give the assistant a short example for each category and a way to ask for a judgment call. That support is more useful than a stricter rule with no backup.

Check the revised policy against the next month of requests, not only against the examples that prompted the change. A policy that fixes one noisy requester but ignores the recurring board cycle will not last. Report the exceptions that remain and the reason for each. That follow-up keeps the policy honest and gives the assistant a way to raise a new pattern.

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. DOL, Telework.
15. NIST SP 800-53 Security and Privacy Controls.
16. SBA, Manage your business.
17. Harvard Business Review, meetings.

Related research

• Measuring the review cost of executive inbox approval queues
• Turning Executive Inbox Approvals into a Tracked Queue
• Designing an Executive Office Coverage Plan for Planned Absences

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.