Calendar Control Boundaries: Measuring Protected Focus Without Surveillance

Table of contents

• Question and method
• Why calendar data is the right level
• Define a focus block
• The three measures
• Record displacement events
• Avoiding surveillance
• What the measure cannot show
• Reporting cadence
• Sources
• Frequently Asked Questions

Question and method

Research question: How can an executive-support team measure whether protected focus time survives contact with the calendar, without turning the measure into employee surveillance?

This paper defines a calendar-level measurement design. It does not estimate the productivity value of focus time or claim that a particular number of protected hours is optimal. The unit of analysis is the scheduled focus block and the change events that affect it.

The design is deliberately narrow. It looks at whether time the owner asked to protect remained protected, whether displaced time was restored, and which commitments caused the displacement. It does not inspect documents, keystrokes, or output.

Why calendar data is the right level

Calendar events are shared coordination records. They show the block, the change, and the participants. They do not show what the owner did during the block. That limitation is also a protection: the measure can answer a scheduling question without evaluating the person's work.

The O*NET executive administrative assistant profile includes calendar coordination as a core task. Coordination requires rules about which commitments can displace which. A measure of hold rate tests whether those rules are working.

Define a focus block

A focus block is a calendar event created to protect time for a category of work. Record:

• category: writing, analysis, planning, interview preparation, recovery, or other
• flexibility: fixed, flexible within the week, or externally protected
• owner and backup scheduler
• creation date and source of the request
• intended duration

Blocks without a category or rule are not measurable. They may still be useful, but they cannot be evaluated against a displacement rule.

The three measures

1. Hold rate: the share of focus blocks that remained at their original time. A block moved and restored later still counts as displaced for this measure.
2. Restore rate: the share of displaced blocks that were replaced with equivalent time in the same week. This captures whether the calendar recovered the loss.
3. Interruption source: the meeting series, role, or request type that caused the displacement. Aggregate this by source, not by individual requester, in reports.

A high hold rate with a low restore rate is better than the reverse, but neither is sufficient alone. A team may hold most blocks and fail to restore the ones that move. Another may move freely and restore consistently. The two patterns imply different rules.

Record displacement events

For each displacement:

The reason category should be broad enough to compare. "Meeting" is too vague; "client interview" and "internal recurring meeting" are useful.

Avoiding surveillance

The measure becomes surveillance when it is used to rank assistants on how much focus time they protect, or when it is combined with output data to evaluate the owner. Avoid both.

Use aggregate reporting by team or role. Review individual cases only to understand a specific conflict, and keep the conversation about the calendar rule rather than the person's performance. Do not publish a leaderboard of "focus hours protected."

Consent and transparency matter. The owner should know what is measured and why. The assistant should know which blocks are fixed and which are flexible. A hidden measure invites gaming: fake blocks, private events with misleading titles, or time moved outside the calendar.

What the measure cannot show

It cannot show whether the protected time was used well. It cannot show whether the owner's priorities were right. It cannot show the cost of an interruption beyond the displaced minutes. Those questions require different methods, including the owner's own reflection.

It also cannot capture work that happens outside the calendar. A leader who protects two hours but answers messages throughout has not created uninterrupted time. The calendar measure is a proxy for the scheduling condition, not the full experience.

Reporting cadence

Review monthly for a stable team. Report:

• blocks scheduled
• hold rate
• restore rate
• displacement reasons
• one rule change to test next month

Do not change the rules every week. A monthly cadence gives the team enough data to see a pattern without turning the review into a reaction to one bad Tuesday.

The NIST Privacy Framework offers a useful structure for limiting data collection and access. The Bureau of Labor Statistics and U.S. Department of Labor provide occupational context, not a focus-time standard.

Sources

1. O*NET OnLine: Executive Administrative Assistants
2. NIST Privacy Framework
3. Bureau of Labor Statistics: Occupational Outlook Handbook
4. U.S. Department of Labor: Hiring
5. U.S. Office of Personnel Management: Delegation

Frequently Asked Questions

Is a focus block that moves but is restored a success?

It is a partial success. The hold rate records the displacement, and the restore rate records the recovery. Report both so the pattern is visible.

Should we measure the owner's output during focus time?

No. That turns a calendar control into performance monitoring and is outside the purpose of the measure. Keep the unit of analysis at the scheduling event.

How do we handle confidential blocks?

Record the category and rule in a private field, and show only "busy" to the wider calendar. The measure needs the block and the change, not the content.

Review cadence

Review the boundary every quarter, not only when the executive complains. Compare the protected time with the interruptions that displaced it, and separate a genuine emergency from a preference. Adjust one rule and measure again. A boundary that is never reviewed becomes either invisible or rigid.

A good boundary review separates the interruptions the executive chose from the ones the organization imposed. The first is a preference to discuss; the second is a capacity problem to solve. Report both and avoid treating every interruption as a failure of discipline. The measure should inform a decision, not assign blame.

Record the outcome of each change and the date of the next review. If the boundary holds, document the condition that made it work; if it fails, describe the pressure that displaced it. That note is more useful than another policy paragraph. A boundary that is documented can be tested; one that is only remembered cannot. Use the note in the next planning conversation instead of starting from memory. The next review should start with the documented outcome, not a fresh debate about whether the boundary exists. Keep the same review interval each quarter so the comparison reflects the change, not a different sample. The review note should name the owner and the next test date.