Research question and scope
This protocol measures how often a temporary executive calendar hold expires without becoming a booking. The unit is one hold event on one executive calendar. An expired hold means the expiry time passed and the event was neither confirmed nor renewed. The measure describes the scheduling control, not the importance of the meeting.
Set the scope to one executive, one calendar system, and a fixed period. Record the meeting types, the expiry rule, and the assistant coverage hours. If the rule changes during the period, split the sample at the effective date. A different expiry creates a different expectation.
Keep the measure separate from a calendar utilization score. A released hold can be the correct outcome when a meeting is no longer needed. The purpose is to find holds that expired without a decision. Report the reason where the record allows it.
Population and unit of analysis
Define the population as every event labelled as a temporary hold during the period. Include holds created by the executive, the assistant, and external requesters. The unit is the hold event, not the requester. One requester may create several holds for different dates.
Include holds that were converted to a booking, released before expiry, renewed with a new deadline, and expired. Report each outcome separately. Exclude confirmed meetings that were never marked as holds. The boundary should be visible in the report.
Exclude personal reminders and focus blocks that were not requested by another party. The measure is about a reservation made for a decision. State the exclusion count with the result. A focus block is not a hold for another person.
Definitions that make the measure reproducible
Define a hold as an event with an explicit temporary label and an owner who can confirm it. Define the expiry as the time recorded in the event or the rule. Define a conversion as a confirmed meeting with the required detail present. Publish one example of each outcome.
Define a release as removal before expiry with a recorded reason. Define an expiry without booking as the end of the hold period with no confirmation. A hold that is renewed is counted once per renewal period. The rule should prevent the same slot from being counted twice.
Decide how to treat a hold that was replaced by a new hold for the same meeting at a different time. Link the two events and classify the outcome once. Record the link method. A move is not automatically a loss.
Sampling and data collection
Draw the sample from the calendar export for the full period rather than from the assistant's task list. Record the export date, the filters, and the row count. Include holds on shared calendars that the executive can see. A sample built from released holds alone cannot produce a rate.
Capture the hold identifier, the requester, the meeting type, the created time, the expiry, the outcome, the confirmed time, and the owner. Add the event notes that explain the decision. Store the export with the report. The timestamps and the outcome are the core evidence.
Check a small overlap sample with a second reviewer. If the reviewers disagree about whether a hold expired or was renewed, the renewal rule is too vague. Rewrite the rule and retest before the full sample. Agreement matters more than sample size.
Record the time spent reconciling calendar events with request threads. A report that requires reading every email will not be repeated. Note the fields the calendar does not capture. The collection cost belongs beside the result.
Measuring expired holds
Report the share of holds converted, released with a reason, renewed, and expired without a decision. Show the counts behind each share. The four groups describe different outcomes and should not be collapsed into one rate. A release can be a healthy outcome, while an expiry without a decision is a gap.
Break the result down by meeting type, requester group, and day of week. A type with many expiries may need a longer hold. A requester group with many expiries may need a clearer confirmation step. Compare only groups with similar volume and decision complexity.
Report the executive hours blocked by holds that expired without a decision. Multiply the event duration by the number of expired holds and show the total. Include the share of the executive's working hours that the block represents. The time measure shows the cost that a count alone hides.
Limitations and next action
The measure cannot show whether an expired hold was useful as protection or whether the executive was relieved to lose it. It also cannot show a decision made in a hallway and never recorded. Treat the result as a measure of the calendar record. Note the meeting types that were not included.
Give the result to the executive and the scheduling owner with one change to test. The change might be a shorter expiry, a required confirmation field, or a twice-daily hold check. Record the effective date and repeat the measure with the same definitions. A controlled change is easier to judge.
Review the boundary cases before shortening every hold. A few meeting types with long dependencies may explain a large share of the expiries. Fix the dependency or the confirmation path first if that is the pattern. The goal is a calendar that reflects real commitments, not a lower hold count by definition.
