What the coordination record can show

Abstract

Executives and support teams often describe meeting load as a single number, but the desk's work sits in preparation, rescheduling, and follow-up rather than in the meeting itself. Public time-use and occupational data can describe categories of coordination work, not the load of one leader. This review sets a bounded local method for counting the meeting-related work a support desk handles in a month. It separates the meeting hour from the coordination hours around it and reports the result as a range with explicit limits. [1][2][3]

Methodology

The review uses occupational descriptions and public time-use data as context and does not convert a national average into a local target. It defines a monthly observation window and a consistent unit, such as one meeting or one reschedule event. A small sample is coded by two reviewers, and transition time is recorded separately. The method is repeatable across months and does not require reading private message content. [1][2][4]

The question and its boundary

The useful question is how many hours the desk spends on meeting coordination, not how many hours the executive spends in meetings. Coordination includes agenda collection, room and travel setup, calendar negotiation, materials, reminders, and follow-up. It excludes the meeting itself unless the assistant attends to take notes. The boundary must be written before counting begins. [1][2]

A single monthly total hides more than it reveals. One heavy board week can dominate the average, and a quiet month can make the desk look underused. The review should report the median week, the peak week, and the number of reschedules. Those three numbers describe the rhythm better than a monthly average. [3][4]

What public time-use data can show

The American Time Use Survey describes how groups spend time across work and non-work activities. It can show that meetings and work-related communication occupy a meaningful share of the workday, but it does not measure an assistant's coordination load. The BLS occupational profile describes executive assistants as workers who handle scheduling, correspondence, and research. Those sources support the existence of the work, not a specific local volume. [1][2][3]

O*NET adds task and requirement context for the occupation, including coordination and time management. That context is useful for building a category list. It is not a benchmark for one desk or one executive. The review should use the sources to justify what to count and then rely on local records for the count itself. [2][5]

Why coordination time is not meeting time

A ninety-minute meeting can consume three hours of desk time before and after it. The preparation may include a briefing note, a travel change, and a set of slides that need review. The follow-up may include minutes, action tracking, and a reschedule for the next week. Counting only the meeting hour understates the load and misallocates support capacity. [3][4]

Coordination also happens in small fragments. A five-minute calendar negotiation or a two-line confirmation can be invisible in a time log but expensive in attention. The method should capture these fragments in a separate category rather than forcing them into the meeting total. A short daily note is often more accurate than a retrospective estimate. [1][4]

A local measurement design

Choose a four-week window and list every meeting the desk touched. For each meeting, record the preparation minutes, the live minutes if the assistant attended, and the follow-up minutes. Add a category for reschedules and a category for travel or room changes. Use a simple spreadsheet with one row per meeting and a short definition for each field. [3][4]

A second reviewer should code one week independently and compare the totals. Differences usually reveal an unclear boundary, such as whether reading a briefing counts as preparation. Resolve the definition and recode before analyzing. The comparison is more valuable than a perfectly precise single count because it shows whether the method can be repeated. [2][4]

Estimating the coordination load

Report the total hours by category, the number of meetings touched, and the average minutes per meeting. Then show the distribution, because a few large events may carry most of the load. A board meeting with a packet can be an outlier that changes staffing decisions. The report should separate routine meetings from high-stakes events. [3][5]

Add a confidence note based on the quality of the local records. If the desk tracked time daily, confidence is higher than if the estimate was reconstructed at month end. State the assumptions, such as whether travel booking time was included. A range with clear assumptions is more useful than a single number with false precision. [2][4]

Risks that distort the count

The first risk is double counting. A reschedule may appear in both the calendar category and the communication category. The second is missing invisible work, such as monitoring a thread or waiting for a reply. The third is attributing the executive's meeting time to the desk. The coding rules should address each risk explicitly. [1][3]

A fourth risk is seasonal distortion. Board cycles, annual planning, and fiscal close can create peaks that look like a permanent trend. The review should compare the same four weeks across two quarters before recommending a staffing change. A single month is a starting point, not a verdict. [4][5]

What to report to leadership

Report the hours by category, the peak week, the number of reschedules, and the share of time spent on high-stakes meetings. Add one sentence on what the desk could stop doing or automate. Leadership needs a decision, not a data dump. The report should fit on one page and link to the detailed sheet. [3][4]

Recommend one test, such as batching calendar changes into two daily windows or standardizing the briefing template. Give the test a measure and a review date. If the test reduces coordination time without hurting response quality, keep it. If it moves the work elsewhere, the report should say so. [2][5]

What the desk should stop counting

Some work is meeting-related but too small to track every month. A single calendar confirmation or a one-line room change may not justify a row in the time sheet. The review should set a minimum, such as five minutes, and note the work that falls below it. The goal is a useful estimate, not a perfect ledger. [2][3]

Standing events deserve separate treatment because they repeat without a new request. A weekly leadership call may require the same preparation each time, so the desk can sample it once and multiply. A one-off board meeting needs its own record. Mixing the two makes the recurring load look larger than it is. [1][4]

A worked example from a board month

Consider a hypothetical desk that supports two executives and tracks four weeks of work. The record shows forty routine meetings, six high-stakes events, and eighteen reschedules. Preparation and follow-up add an average of fifty minutes to each routine meeting and three hours to each high-stakes event. The monthly coordination total is then a range built from those observed minutes, not a guess. [3][4]

The example is useful because it shows where the load sits. The six high-stakes events may consume more desk time than the forty routine meetings even though they are a small share of the count. A staffing decision based only on the number of meetings would miss that concentration. The report should show both the count and the hours. [2][4]

How the result changes with scope

The same method produces different totals when the scope changes. Adding a third executive, a second time zone, or a board committee increases coordination without necessarily increasing the number of meetings. The review should record the scope next to the result so a later comparison is fair. A monthly total without the scope is hard to interpret. [1][3]

Assistant attendance also changes the count. If the assistant sits in meetings to take notes, the live minutes belong in the total. If the assistant only prepares and follows up, those minutes should be recorded separately. The report should state which model applied. Otherwise two teams can compare numbers that measure different work. [2][4]

Limits and responsible use

This review cannot prove that a desk is understaffed or overstaffed. It measures the work that was recorded, not the work that was missed. Local tools, executive preferences, and the number of time zones all affect the load. The result should be used to ask better questions, not to set a universal ratio. [1][3]

The method should also protect privacy. A meeting title can reveal a sensitive negotiation, so the report should use categories and counts rather than names. Store the detailed sheet only as long as needed and restrict access. For related reading, see our guide to <a href="/blog/create-a-coverage-card-for-the-day-an-assistant-calls-in-sick">planning coverage for an unplanned absence</a> and our <a href="/services">executive support services</a>. [2][4]

Key findings

  • The desk load is coordination around the meeting, not the meeting hour alone, and the boundary must be fixed before counting. [1][2]
  • A four-week local sample with preparation, live, follow-up, and reschedule categories produces a repeatable estimate. [3][4]
  • Report the median week, peak week, and reschedule count rather than one monthly average. [3][4]
  • Public time-use and occupational sources justify categories but cannot set a local staffing ratio. [1][2][5]
  • Use a range with confidence notes and protect meeting titles when the report is shared. [2][4]

Sources

  1. American Time Use Survey, U.S. Bureau of Labor Statistics
  2. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics
  3. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine
  4. Hours of Work, U.S. Department of Labor
  5. How CEOs Manage Time, Harvard Business Review

Return to the Research Content library