Measuring executive calendar load without counting meetings

Why meeting count fails

Two executives can attend the same number of meetings with very different loads. One has ninety-minute blocks with preparation time; the other has eight twenty-minute calls separated by five-minute gaps. Counting meetings describes neither experience.

The useful unit is the working block: a meeting plus the preparation and follow-up it requires, or a protected period of focused work. Load is the shape of those blocks across the week, not the number of calendar invites.

Define fragmentation and preparation demand

Fragmentation measures how often the day breaks into blocks too short for focused work, including gaps that are too brief to use. Preparation demand measures the time required before a meeting to make the executive useful in it.

Both are estimates unless the assistant records them. A simple field on the calendar entry, such as prep minutes and follow-up minutes, produces usable data after a few weeks.

Capture recovery and travel

Travel, turnaround, and recovery time belong in the load model. A day with two site visits is not equivalent to a day with two video calls, even when the meeting count matches.

Record the travel window and the first meeting after arrival. If the schedule assumes the executive can present immediately after a flight, the calendar is making an unstated risk decision. ^[1]

Report a weekly shape, not a score

A weekly view should show protected blocks, preparation hours, fragmented gaps, travel, and the longest uninterrupted period. Those five facts are enough to start a conversation about what to move.

Avoid a composite score. A single number invites optimization of the number rather than the schedule, and it hides the trade-offs the principal actually needs to make.

Limitations

The method depends on accurate calendar data and honest time estimates. It cannot measure the cognitive cost of context switching, and it does not determine whether a meeting was valuable.

Use it to describe the week and to test changes, not to compare executives or to justify a predetermined staffing decision.

Sources

ILOSTAT Labour Statistics, International Labour Organization.
Secretaries and Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Outlook Handbook.
Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
Executive Secretaries and Executive Administrative Assistants, O*NET OnLine.
Business Formation Statistics, U.S. Census Bureau.
Nonfarm Business Sector: Labor Productivity, Federal Reserve Economic Data.
Productivity Statistics, OECD Data Explorer.
World Development Indicators, World Bank DataBank.
2024 Work Trend Index Annual Report, Microsoft and LinkedIn.
The economic potential of generative AI, McKinsey Global Institute.
Creating helpful, reliable, people first content, Google Search Central.
Search Engine Optimization Starter Guide, Google Search Central.
Dear Manager, You Are Holding Too Many Meetings, Harvard Business Review.

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.

Turn the finding into a support scope.

Bring the workflow that feels hardest to see. We will help define the role, the evidence it should maintain, and the decisions that stay with leadership.

Talk through the role