What the time record can show

Abstract

Executives often describe their week as fully booked, yet the useful question is which parts of that week are transferable. Public time-use and occupational sources describe categories of work and average patterns, not the share that a particular executive can hand off. This review sets a bounded method for estimating reclaimable coordination work from a local record. It treats delegation as a transfer of preparation and routing, not a transfer of accountability. The result should be read as a local planning estimate with explicit limits. [1][2][3]

Methodology

The review uses occupational descriptions and public time-use data as context, not as a direct measure of any executive. It separates coordination work from decision work and identifies the evidence needed for each category. A local estimate should use a defined observation window and a consistent unit, such as one calendar event or one inbox thread. The method does not convert national averages into a percentage for a specific leader. [1][2][4]

The question and its boundary

The useful question is not how many hours an executive works. It is which hours contain work that another trained person could prepare, route, or complete within a written boundary. Calendar events, inbox triage, travel logistics, and meeting preparation are candidate categories because they contain repeatable coordination. Board decisions, personnel judgments, and relationship commitments are not transferable in the same way. The boundary must be set before the estimate begins. [1][2]

A broad claim that executives can reclaim a fixed share of their week is not supported by the public sources. Occupational data describes the work of executive assistants, while time-use data describes how groups spend time. Neither source observes a specific leader's calendar or decision rights. The review therefore produces a method for a local sample rather than a universal ratio. [1][2][3]

What time-use evidence can support

The Bureau of Labor Statistics describes executive secretaries and executive administrative assistants as workers who handle high-level support, including document review, research, and report preparation. That description supports the claim that preparation work exists in the role, but it does not show how much of an executive's week is preparation. The Occupational Information Network adds task and requirement context for the same occupation. These sources are useful for defining categories, not for assigning a percentage. [1][2]

Time-use surveys show that work time is distributed across many activities, and they caution against treating one average as a personal schedule. A leader with a heavy board cycle may have a very different week from a leader in a product launch. The review should therefore compare the local record with the executive's own prior weeks. The comparison is more defensible than a benchmark borrowed from a different context. [3][4]

Why delegation is not a straight swap

A delegated hour is not automatically an hour returned to strategic work. The executive may spend time briefing the assistant, reviewing the output, or correcting a decision that crossed the boundary. Those transition costs belong in the estimate. A task that takes the executive twenty minutes and the assistant forty minutes may still be worth delegating if it protects a longer block of attention. The value depends on what the executive does with the recovered time. [2][3]

Accountability also stays with the executive. The assistant can prepare a recommendation, but the executive remains responsible for the decision and its consequences. A local method should distinguish time moved from accountability moved. If the two are conflated, the estimate will overstate the benefit and understate the review burden. The boundary should name which decisions remain with the executive. [1][2]

A local measurement design

Choose a representative two-week window and classify each calendar event and inbox thread into a small set of categories. Use categories such as decision, preparation, routing, relationship, and administration. Record the time spent and whether the executive was the only person who could perform the work. A second reviewer should code a sample so the categories do not drift. The design should be simple enough to repeat after a change. [3][4]

For each category, estimate the share that could move to a trained assistant within a written boundary. Mark the estimate as low, medium, or high confidence instead of presenting a false precision. Then subtract the expected briefing and review time. The result is a range of reclaimable coordination time, not a promise. Report the range with the assumptions that produced it. [2][3]

Risks that inflate the estimate

The most common error is counting every meeting as delegable because an assistant can attend. Attendance is not the same as authority, and a meeting without the executive may lose the relationship or the decision. Another error is ignoring the time needed to prepare the assistant for a sensitive context. A third is assuming that recovered time will automatically become strategic work. [1][4]

Calendar data can also mislead when events are labeled generically. A one-hour block called leadership may contain a decision, a coaching conversation, or a routine update. Without a short interview or diary, the label cannot support a precise estimate. The method should use at least two evidence sources and should report what could not be classified. [3][4]

What to report to leadership

Report the observed hours by category, the share estimated as transferable, the expected transition cost, and the confidence level. Separate the time moved from the decisions retained. Add the conditions that would change the estimate, such as a new board cycle, a client crisis, or a change in assistant coverage. A short table is more useful than a single headline number. [2][3]

The report should also recommend one test. A team might move travel coordination for one month and measure the executive's review time, the number of corrections, and the change in response speed. The test produces better evidence than another estimate. If the test does not reduce executive involvement, the boundary or the support model needs revision. [4][5]

A worked example from a leadership week

Imagine a chief executive with a board meeting, two client reviews, and a product decision in the same week. The calendar shows twelve hours of meetings, four hours of preparation, and a long tail of email and travel coordination. The decision meetings belong with the executive, but the preparation and routing can move to a trained assistant within a written boundary. The first pass should mark which blocks actually require the executive's voice.

The local review should tag each block before estimating. A client review that requires the executive's relationship is not the same as a status update with the same title. Once the blocks are tagged, the team can estimate the transferable share and the review time. The result is a range for one week, not a permanent ratio for the role.

What would change the estimate

A new board cycle, a client crisis, or a change in assistant coverage can move the estimate in either direction. A more experienced assistant may need less briefing, while a more regulated process may need more review. The method should record those conditions next to the result so the next review can compare like with like. Without those notes, a later reader may treat a one-week range as a permanent rule.

The estimate should also change when the executive's role changes. A leader who moves from functional ownership to enterprise-wide scope may gain more coordination work and more decision work at the same time. Repeating the local sample after a role change is more useful than applying an old percentage to a new job. The review can then show whether the support model still matches the work.

Limits and responsible use

This review does not establish that a particular executive can reclaim a specific number of hours. The sources describe occupations and time patterns, not the decision rights of one leader. Local culture, confidentiality, union or employment rules, and the assistant's experience all affect what can move. The estimate should not be used as a performance target or a staffing formula. [1][2][5]

A responsible use is to treat the result as a planning hypothesis. Test one category, measure the transition cost, and keep the executive's accountability visible. Revisit the estimate when the role, the team, or the operating model changes. For related reading, see our guide to <a href="/blog/train-a-new-executive-assistant-on-decision-rights-before-tool-access">training decision rights</a> and our <a href="/services">executive support services</a>. [3][4]

Key findings

  • Public occupational sources support the existence of preparation and coordination work but do not measure one executive's transferable share. [1][2]
  • A defensible estimate uses a local two-week sample, a small category set, and a second reviewer for coding. [3][4]
  • Transition cost includes briefing, review, and correction time and must be subtracted from the apparent gain. [2][3]
  • Authority to prepare is not authority to decide, and accountability remains with the executive. [1][2]
  • The result should be reported as a range with confidence and conditions, not as a fixed percentage. [3][4]

Sources

  1. Executive Secretaries and Executive Administrative Assistants, U.S. Bureau of Labor Statistics
  2. Executive Secretaries and Executive Administrative Assistants, O*NET OnLine
  3. American Time Use Survey, U.S. Bureau of Labor Statistics
  4. How CEOs Manage Time, Harvard Business Review
  5. Hours of Work, U.S. Department of Labor
  6. Working Time and Work Life Balance Around the World, International Labour Organization

Return to the Research Content library