The work that leaves no invoice

Abstract

After-hours coordination is real work, but it rarely appears as a separate line item in an executive office budget. Public time-use and occupational sources can describe working patterns and the risks of long or irregular hours, but they do not publish an after-hours cost for executive support. This review sets a bounded local method for observing the hours, valuing them, and reporting the result without turning the desk into a monitoring system [1][2][3].

Methodology

The review uses public time-use, wage, and occupational safety guidance as context, not as a local estimate. It defines after-hours work as coordination performed outside the desk's agreed schedule. The local method uses a four-week log with date, duration, reason, and whether the work was planned, and it values the hours with a stated proxy. Results are reported at the team level with their limits [1][2][4].

The question and what can be measured

After-hours coordination is the work that happens outside the principal's normal day: checking a late email, rebooking a flight, or preparing a briefing for an early meeting. Much of it is invisible because it leaves no separate invoice. The question is what it costs the support desk and the organization [1][2]. Public data does not publish an after-hours cost figure for executive support. It describes working time, occupational wages, and the risks of long or irregular hours. A useful review separates those public context points from the local observation of actual evening work [3][4].

Start by separating coordination from the principal's own work. A late email from the principal may be a request, while a late email from a vendor may be a routine update. The two have different costs and different fixes. The log should record the source and the reason.

How public time-use data is collected

The American Time Use Survey asks people how they spent their time on a specific day and records the activities in detail. It is designed to describe the population, not a single occupation or employer. The survey can show patterns of work at different times, but it does not measure the quality or necessity of that work [1][2]. The data is self-reported and collected after the fact, which introduces recall limits. It also captures one day rather than a full week. Those limitations matter when a team wants to estimate the after-hours load of its own desk [3][4].

The survey's strength is its detail about activities, not its precision about a single occupation. Use it to describe the context, then stop. A local log is the only way to see the desk's actual pattern. Do not scale a national average onto a small team.

What the published data can say

The survey can show that work occurs outside standard daytime hours across the economy and that some occupations report more evening or weekend work than others. It cannot show whether a particular assistant is answering messages at ten at night. That requires local records or a structured conversation with the team [1][3]. Wage data adds another piece: an hourly rate can be used to value time, but salaried support roles often do not record extra hours separately. The absence of a line item does not mean the time is free. A local review should estimate the hours and describe how they were identified [2][4].

Published wage data can value an hour, but it cannot say whether that hour was necessary. A late call with a client may be valuable, while a late status email may be avoidable. The local review should separate the two before recommending a change. Cost alone is not a verdict.

Why coordination spills into evenings

Coordination spills into evenings because the principal's day is full and the desk needs quiet time to prepare. A briefing for tomorrow is easier to write after the calls end. A travel change is easier to solve when the office is empty. Those are real operational reasons, not simply poor planning [2][3]. Time zones add another cause. A team supporting principals across regions may need early or late coverage that no single schedule can absorb. The desk should distinguish predictable coverage from unplanned spillover. The first can be designed and rotated, while the second usually signals a process problem [1][4].

Ask the desk which tasks could move earlier without losing quality. A briefing that is written at nine at night may be just as good at four in the afternoon. The answer often reveals a scheduling problem rather than a workload problem. Fix the schedule before adding headcount.

The hidden cost of availability

The cost of after-hours work includes pay, but it also includes fatigue, error rates, and turnover. A person who is always available may be less able to concentrate during the day. Over time, the desk may lose the people who know the most about the principal's preferences [1][3]. Availability also creates an expectation that is hard to reverse. If the principal learns that a message at nine at night gets an answer, the boundary disappears. The cost is then built into the relationship rather than into a budget line. That makes it easy to underestimate [2][4].

Track the recovery time after a late night as well as the late night itself. A single late call may be manageable, while three in a week change the pattern. The log should show the cluster, not only the total. Clusters are what make the cost visible.

A bounded local method

Ask the desk to log after-hours work for four weeks, using a simple form with the date, the duration, the reason, and whether it was planned. Do not ask for message content. Pair the log with a short conversation about what could have waited [1][2]. Estimate the cost using the hourly rate or a stated proxy, and report the hours separately from the pay. Include the number of interruptions and the number of nights affected. The result is a range, not a precise invoice [3][4].

Choose a four-week period that includes a normal week and a peak week. A quiet period will understate the load, while a crisis will overstate it. State which weeks were included and why. The comparison is more useful than a single average.

What to report to leadership

Report the hours, the patterns, the reasons, and the estimated cost. Add the limits of the log, including under-reporting and the short period. Recommend one change, such as a rotation, a quiet-hours protocol, or an earlier cut-off for routine requests [2][4]. Give the change a measure and a review date. Do not present the estimate as proof that the desk is understaffed. It is evidence for a conversation about coverage and planning [1][3].

Include the number of people affected, not only the hours. Ten hours spread across five people is a different problem from ten hours carried by one person. Report both the total and the concentration. The second number often drives the decision.

Limits and responsible use

The estimate cannot capture the long-term health effects of irregular hours or the value of lost recovery time. It cannot prove that a specific change will reduce turnover. It also depends on honest reporting, which requires trust [1][3]. Protect the people who provide the data by reporting at the team level and by not using the log in performance reviews. Keep the purpose visible and stop collecting when the review is complete. Responsible measurement is part of the fix, not an additional burden [2][4].

Agree in advance how the data will be stored and when it will be deleted. A log that lives indefinitely becomes a surveillance record. Keep only what the review needs and remove the detail afterward. The team should know the plan before they start reporting.

Key findings

  • Public sources describe time use and fatigue risk but do not publish an after-hours cost for executive support [1][2].
  • A four-week log with duration and reason is more useful than a single estimate based on memory [1][4].
  • Separate predictable cross-time-zone coverage from unplanned evening spillover [1][4].
  • Value the hours with a stated proxy and report the result as a range, not an invoice [2][4].
  • Report at the team level and never use the log in individual performance reviews [1][3].

Sources

  1. American Time Use Survey, U.S. Bureau of Labor Statistics
  2. Worker Fatigue, Occupational Safety and Health Administration
  3. Occupational Employment and Wage Statistics, U.S. Bureau of Labor Statistics
  4. Fair Labor Standards Act, U.S. Department of Labor

Return to the Research Content library