Calendar displacement decisions: what evidence should an assistant preserve?

Methodology

1. Evidence scope: this review treats calendar displacement as a decision event, not as a scheduling inconvenience. The observation unit is one proposed move, cancellation, shortening, or substitution involving an executive commitment. A usable record identifies the original purpose, participants, decision required, preparation state, deadline source, displacement request, affected dependencies, authority used, and final disposition. Microsoft documents an environment of meetings and communication pressure, while BLS describes scheduling and coordination within administrative work. Neither source measures the quality of a specific assistant's choices. Their role here is to define relevant context. Facts come from invitations, agenda records, participant messages, and approved priority rules. Analysis begins only after those artifacts are separated from assumptions about status, urgency, or seniority.
2. Method: compare the state immediately before the displacement request with the state after the decision. Code whether the original commitment had a named decision, a real external deadline, required attendees, ready materials, downstream work, and a recoverable alternative. Then code the competing request with the same fields. This paired design prevents a persuasive new invitation from being reviewed in isolation. Reviewers also record who had authority to move each event and whether consultation was possible within the available window. A move counts as documented only when the record explains the tradeoff in ordinary language. Calendar color, meeting title, or sender rank does not substitute for evidence. The method does not calculate a productivity score or presume that more protected time always produces a better result.
3. Analysis boundary: the assistant can assemble evidence, apply approved rules, identify conflicts, and execute an authorized change. The assistant should not invent executive intent, settle an unresolved business priority, or conceal a tradeoff by silently moving an event. NIST access-control guidance informs the authority boundary because calendar permission and decision authority are different things. Plain-language guidance informs the short decision note: what changed, why, whose authority applied, what consequence remains, and what follow-up is due. Records guidance supports retaining the approved outcome where the organization treats it as a business record. These sources do not require one software field set, and the review does not claim legal sufficiency for any retention practice.
4. Limitations: no cited publication runs a controlled trial of executive calendar displacement records. The proposed fields are an evidence model derived from adjacent administrative, collaboration, security, and records guidance. They may overstate documentation needs for routine internal moves and understate them for regulated, contractual, or public-sector meetings. Calendar metadata can also be incomplete: an apparently optional meeting may carry an unstated relationship cost, while a senior invitation may require no executive decision. The conclusion therefore applies to reviewability, not to the wisdom of any specific business choice. Teams should sample counterexamples, including moves that looked correct but caused harm and moves that broke a local rule but protected a more important obligation.
5. Evidence interpretation: review results should show absolute counts for each displacement class and preserve the denominator of eligible conflicts. A reviewer should read a small sample of unchanged events as a comparison group because a rule may appear effective only when the difficult cases are excluded. Repeat moves need their own history: moving the same preparation block three times is different from three unrelated conflicts. Corrections should retain the original classification and the reason it changed. A practical follow-up records the rule adjusted, the decision owner, the next review date, and the evidence that would justify keeping or reversing that adjustment. This design keeps the study close to observed calendar records and prevents a local pattern from becoming an unsupported claim about all executive teams.