On-Call and Standby Time Rules for Executive Support

Availability is the hidden part of executive support

Executive support rarely stops at the end of the scheduled day. An assistant may be expected to monitor a phone for a travel disruption, check a message before a board meeting, or remain reachable while the executive attends a dinner. Sometimes the expectation is explicit in a policy. Often it is implied by the culture: the assistant knows that a slow reply on a Sunday will be noticed. The distinction between being available and actually working is the center of the on-call analysis.

The Fair Labor Standards Act requires employers to pay covered, non-exempt employees for all hours worked, including overtime beyond forty hours in a workweek. The difficult question is whether standby time counts as hours worked when the assistant is not actively performing a task. The Department of Labor's regulations provide a framework, but the answer depends on the facts. An agency that wants a defensible policy has to look at what the assistant can actually do during the standby period, not just what the handbook says.

The federal framework starts with control

The key regulation is 29 CFR 785.17, which addresses on-call time. The test is whether the employee can use the time effectively for personal purposes. If the employee is unable to do so because of the employer's requirements, the time is hours worked. If the employee is free to use the time as they wish, subject to the need to respond to a call, the time may be off duty.

The regulation is old, but the question is familiar to anyone who has carried a phone for an executive. An assistant who must stay within fifteen minutes of a laptop and check messages every half hour is not really free. An assistant who can go to a movie as long as they answer a rare call is in a different position. The facts matter: the frequency of calls, the response window, the consequences of a missed call, and whether the assistant can trade the on-call shift with a colleague.

Frequency and response time are the practical tests

Two factors do most of the work in real cases. The first is how often the assistant is actually called. A shift with one possible call in eight hours looks different from a shift with a steady stream of requests. The second is how quickly the assistant must respond. A thirty-minute response window leaves room for ordinary life. A five-minute window with a requirement to be at a computer effectively keeps the assistant tethered to the desk.

The Department's Fact Sheet #22 discusses waiting time and the conditions that make it compensable. The agency should translate those factors into its own policy: define the response window, estimate the expected volume, and state whether the assistant may decline a shift or arrange a swap. Those details are evidence of whether the time is genuinely the assistant's own. Review the policy against actual call logs each quarter rather than relying on the original assumptions.

Not all standby is paid the same way

Federal law does not require an employer to pay a non-exempt employee for on-call time that is not hours worked. It also does not prohibit the employer from paying a standby stipend or a lower on-call rate, as long as the arrangement complies with minimum pay and overtime rules when the time does become hours worked. Some states impose stricter requirements, including pay for specified standby periods or reporting-time pay. The agency should check the law for each assistant's work location.

A common mistake is to pay a flat on-call stipend and assume it covers all work performed during the period. If the assistant answers calls and performs tasks, those hours may need to be compensated at the applicable rate, and overtime may apply. The stipend may be credited toward the pay owed if the arrangement is structured correctly, but the calculation has to be documented. An agency that cannot explain how the stipend relates to the hours worked is exposed in a pay audit.

Sleep time and extended duty

Some executive support arrangements involve overnight travel or multi-day events where the assistant is expected to remain available. The regulations address sleep time for employees on duty for twenty-four hours or more. Under 29 CFR 785.22, the employer and employee may agree to exclude bona fide meal periods and a bona fide sleep period of up to eight hours, provided the employer furnishes adequate sleeping facilities and the employee can usually enjoy an uninterrupted night's sleep. The exception is narrow, and it depends on conditions the agency can actually verify during the assignment.

Interruptions change the calculation. If the assistant is called during the sleep period and the interruption is substantial, the time may count as hours worked. If the assistant cannot get a reasonable night's sleep because of the assignment, the exclusion may not apply at all. A policy that automatically deducts eight hours for sleep without checking the actual conditions is not reliable. The agency should document the agreement, the facilities, and any interruptions.

Remote devices make the boundary harder

A phone in a pocket blurs the line between on-call and working. The assistant may see a message, answer it in two minutes, and return to dinner. The time spent answering is work, even if the assistant does not record it. Over a month, those small interruptions can add up to a significant number of hours that never reach the payroll system. The agency should give assistants a simple way to record them and should review the pattern.

The review should distinguish between genuine emergencies and routine expectations. If the executive routinely sends non-urgent requests at night and expects an immediate reply, the agency has created a de facto on-call requirement. The fix may be a policy change, a different coverage model, or a clearer expectation about response times. The weekly one-on-one agenda is a good place to surface the pattern before it becomes a payroll problem.

Exempt status does not answer every question

Many executive assistants are classified as exempt and paid a fixed amount. Exempt employees are generally not entitled to overtime, and the fixed amount is intended to cover all hours worked in the workweek. That does not mean the agency can ignore on-call arrangements. The exemption depends on the duties test and the fixed-pay basis test, and a misclassified assistant may be owed overtime for all hours worked, including standby time that qualifies.

The agency should document the exemption analysis and review it when the role changes. An assistant who spends most of the day on administrative tasks may not meet the duties test, even if the fixed amount is above the threshold. The overtime boundaries research explores how coverage models create overtime exposure. On-call is one more input into that analysis, not a separate exception.

Build a policy the team can follow

A workable on-call policy should define the shifts, the response expectations, the compensation, and the escalation path. It should state who is eligible, how shifts are assigned, and how swaps are approved. It should explain what counts as an emergency and what can wait until the next business day. It should also explain how the assistant records time spent responding and how the agency reviews it.

The policy should be short enough to read in one sitting and specific enough to apply without a supervisor's interpretation. Add examples for common situations: a flight cancellation at night, a board deck change on a weekend, and a routine request from a client in another time zone. Train supervisors on the examples, and give assistants a way to raise a concern without fearing retaliation. The decision log can record changes to the policy and the reasons behind them.

Keep records that reflect the real arrangement

The FLSA recordkeeping rules require employers to keep payroll records and hours-worked information for covered employees. The agency should retain on-call schedules, response logs, time records, and the policy that applied during the period. If the assistant uses a phone app to log calls, export the data regularly and store it with the payroll file. Do not rely on a supervisor's memory of how often the phone rang.

The records should also show that the agency reviewed the arrangement. A quarterly report on on-call volume, response times, and overtime can reveal whether the policy is working. If the volume is rising, the agency may need more coverage or a different schedule. If the response times are consistently short, the standby may be more restrictive than the policy admits. Those findings should lead to a documented adjustment.

Coordinate with state law and counsel

Federal law is the starting point, but state rules can be more demanding. Some states require pay for standby time, impose reporting-time pay, or apply a stricter test for when on-call time is compensable. The agency should identify the assistant's work location, review the state guidance, and document the conclusion. When the analysis is uncertain, ask employment counsel before the first shift, not after a complaint.

This report is an operational overview, not legal advice. On-call rules depend on facts that vary by role, schedule, and jurisdiction. The agency should combine the federal framework, the applicable state rules, and its own coverage needs into a written policy that it can explain and defend. An assistant who is genuinely free during standby should be treated that way, and an assistant who is effectively working should be paid for the time. For help designing an after-hours support model, contact our team.