Skip to content
On this page

Measuring rework in executive meeting requests

A bounded protocol for measuring how often an executive meeting request changes materially after it has been accepted for scheduling, and where that rework originates.

Remote Executive Support Editorial Desk · · 9 min read · Sources: 5 · Verified 2026-11-04

Measuring rework in executive meeting requests

Key statistics

  • The protocol defines rework as a material change to a meeting request after it has been accepted for scheduling.
  • The cited sources describe meeting practice, work patterns, and control guidance; none reports a private-sector executive meeting rework rate.
  • The proposed review samples a fixed window and separates changes initiated by the executive, the requester, and the calendar owner.

Key takeaways

  • Rework is easier to measure when the request record shows what changed, who asked, and why the first version failed.
  • A meeting request that arrives without purpose, duration, or decision context is not automatically a failure; it is a predictable source of rework.
  • Count rework from the first recorded request, not from the moment someone notices the problem.
  • A small local sample can reveal where requests break down, but it cannot establish a universal rework benchmark.

Published November 4, 2026

A meeting request looks like a small administrative event. Someone asks for time, the assistant checks the calendar, and a slot is reserved. But many requests are not ready to schedule when they arrive. The purpose is vague, the duration is a guess, the decision to be made is unstated, and the attendee list is incomplete. The assistant schedules what was asked for, then rebuilds it when the real requirement appears. That rebuild is rework, and in a busy executive office it is often invisible because each individual adjustment looks minor.

This article proposes a bounded local protocol for measuring rework in executive meeting requests. It does not offer a universal rate or claim that the cited sources studied private executive offices. The sources describe meeting practice, work patterns, and internal-control guidance in general terms. They help explain why request quality matters; they do not tell an office what its own rework level should be. That threshold has to be written locally and reviewed against local evidence.

The question and the unit of analysis

The question is narrow: when an executive meeting request is accepted for scheduling, how often does it change materially before the meeting occurs, and where does the change originate? The unit of analysis is one request, from the first recorded ask to the meeting start or cancellation. A recurring series can be treated as one request per occurrence only if the occurrences are scheduled separately. Otherwise, use the series as the unit and note that a single change may affect several dates.

A material change is a change to the purpose, the decision or outcome the meeting must produce, the required attendees, the duration, the acceptable date or time window, the location or format, the preparation materials, or the authority to accept on the executive's behalf. A moved slot alone may be operationally minor if everything else is stable. A new decision objective is material even if the time does not change. The definition should be written before the sample begins so that the reviewer cannot redefine rework after seeing the results.

The distinction between a request and a meeting matters. A request can be declined, deferred, merged with another request, or converted into an asynchronous note. Those outcomes are not rework unless the change happens after acceptance. Counting declined requests as failures would confuse demand management with scheduling quality. The protocol is about the cost of rebuilding an accepted plan, not about whether the executive should have accepted it.

Define rework before counting it

Rework is a material change to a request after it has been accepted for scheduling. It is not every update. A requester adding a dial-in number is not rework. A requester changing the decision the meeting must produce is. A requester adding a required attendee who must approve the outcome is. A requester asking for a different room because the original was unavailable may be a facilities issue rather than a request-quality issue.

The definition should also separate changes that could have been prevented by a better first request from changes caused by new information. Both are real, but they point to different fixes. A preventable change suggests an intake field, a template, or a confirmation step. A change caused by new information suggests a review cadence or a decision to keep the meeting flexible. Mixing the two makes the office look worse than it is and hides the part it can actually fix.

A third distinction is the source of the change. An executive-initiated change is often legitimate: the executive may learn something that alters the meeting's purpose. A requester-initiated change may reflect a client who moved a deadline. A calendar-owner-initiated change may reflect a conflict the assistant discovered. An external change may come from a customer, regulator, or partner. Code the source rather than treating every change as an internal failure. The useful question is not who to blame but which source produces the most preventable work.

Code the request at intake

At intake, capture the fields that the office actually needs to schedule and prepare: requester, executive, purpose, decision or outcome, required attendees, optional attendees, proposed duration, deadline or preferred window, preparation needed, authority to accept, and a reference to the source message. A short intake checklist is enough. The assistant should not block a request for missing fields. Record what is missing and proceed if the request is authorized. The missing field is the data.

The intake record should be small and stable. A long form that nobody fills in produces missing data and resentment. A short form with a few required fields and a free-text note is easier to maintain. The assistant can add context in the note without turning the request into a project plan. The goal is to make the first version reviewable, not to make every requester write a brief.

When a change occurs, record what changed, when it was recorded, who initiated it, why it was needed, and whether the first request contained the information. Use a small vocabulary for the change type so that the sample can be counted. Free-text notes are useful for context, but they are hard to compare across cases. A short list of change types plus one explanatory line gives the reviewer both structure and meaning.

The record should also distinguish the time the change became known from the time it was entered. A requester may mention a change in a call on Monday and confirm it in writing on Wednesday. The gap between those moments is itself a useful signal. If changes routinely sit in someone's memory before they reach the record, the office has a documentation delay, not just a request-quality problem.

Sample a fixed window and read the record honestly

Choose one observation window, such as a quarter or four consecutive weeks. Include every request above a defined threshold. The threshold might be all requests handled by the office, all requests with at least one external attendee, or all requests that required preparation materials. State the rule and keep it fixed for the sample. A narrow sample can be useful, but it should not be presented as the whole office.

Reconstruct each case from the record, not from recollection. A reviewer should be able to see why the first request was accepted, what changed, and why the change was material. If two reviewers disagree, keep both codes and the reason for the disagreement. That disagreement is evidence about how clear the definition is. Do not force a clean category when the record genuinely does not support one.

A worked example makes the method concrete. Suppose an assistant accepts a thirty-minute vendor review for a Thursday afternoon. The request names two attendees and says the purpose is to "review the vendor." Two days later, the requester explains that the meeting is actually meant to choose between two vendors, needs sixty minutes, and must include procurement. That is a material change to purpose, duration, and required attendees. The rework is counted from the first acceptance to the recorded change. The fact that the assistant could have asked a better question at intake is relevant to the fix, but it does not change the measurement. The example is illustrative, not a benchmark.

Some cases will be ambiguous. A meeting that is cancelled because the executive's travel changed is not necessarily rework, but the preparation may have been wasted. A request that is merged with another may reduce total work even though it changes the plan. A recurring meeting that is shortened for one occurrence may be a minor adjustment. Report these as categories and explain how they were handled rather than hiding them in an average.

Interpret the result and choose one change

A shorter time to rework is not automatically better. A same-hour change may mean the office has a clear intake process, or it may mean nobody checked the purpose before scheduling. A longer gap may reflect a complex client negotiation, or it may reflect a request sitting in the wrong queue. Pair the timing measure with a quality check: did the first request name a decision or outcome, a duration, and the required attendees? Did the change record name the source and the authority? Did the meeting still achieve its purpose?

Report counts before percentages. If the sample is small, a percentage implies precision that the data does not support. Useful outputs include the number of accepted requests, the number with at least one material change, the median number of changes per affected request, the share of requests missing a decision or outcome at intake, and the share of changes coded as preventable. Also report the cases that could not be coded, because an unresolved case is not a zero.

The cited sources support the general direction without supplying a target. Microsoft's WorkLab reporting and Asana's Anatomy of Work describe meeting load and work patterns in broad terms. Harvard Business Review's classic guidance on running a meeting emphasizes purpose and preparation, which is relevant to request quality but is not a study of executive-office rework. NIST SP 800-53 and COSO's internal-control guidance describe accountability, documentation, and review disciplines that can inform the record design. None of them reports a private-sector executive meeting rework rate. The local result should be reported as a local result.

End the review with one process change, one owner, and one check date. The change might be a required decision field for external meetings, a standard duration for vendor reviews, a pre-read requirement, or a requester confirmation step before a slot is released. Choose the change that addresses the most common preventable pattern, not the one that is easiest to announce. The executive or chief of staff owns the policy decision. The assistant can maintain the intake record, prepare the sample, and route the exceptions. When the request exceeds the written authority or the records conflict, the assistant should stop and ask rather than guessing.

The value of measuring rework is not a cleaner dashboard. It is a better first request. When the office can see where meetings are rebuilt, it can fix the intake instead of absorbing the cost silently. A small sample, a stable definition, and one adopted change are enough to start.

Sources

See the open-loop audit for a companion protocol on measuring delegated follow-ups that remain open past their due date.

Frequently Asked Questions

What does Measuring rework in executive meeting requests examine?

A bounded protocol for measuring how often an executive meeting request changes materially after it has been accepted for scheduling, and where that rework originates.

What key statistics does Measuring rework in executive meeting requests report?

The protocol defines rework as a material change to a meeting request after it has been accepted for scheduling. The cited sources describe meeting practice, work patterns, and control guidance; none reports a private-sector executive meeting rework rate. The proposed review samples a fixed window and separates changes initiated by the executive, the requester, and the calendar owner.

What are the key takeaways from Measuring rework in executive meeting requests?

Rework is easier to measure when the request record shows what changed, who asked, and why the first version failed. A meeting request that arrives without purpose, duration, or decision context is not automatically a failure; it is a predictable source of rework. Count rework from the first recorded request, not from the moment someone notices the problem. A small local sample can reveal where requests break down, but it cannot establish a universal rework benchmark.

Book a Free Consultation Call