Reasonable Accommodation Request Routing in Executive Operations for 2026

Research question

What evidence shows that an executive-support operation can recognize and route a workplace accommodation request promptly while protecting the requester's information and keeping decisions with the authorized owner?

Executive assistants manage calendars, meeting formats, travel, rooms, communications, and access to senior leaders. Those workflows make them likely recipients of plain-language requests for a change connected to a medical condition, disability, religion, pregnancy, or another protected need. A request may sound operational: a different meeting time, a quiet room, captioning, a modified travel plan, written instructions, or leave.

Treating it as an ordinary preference can cause delay or unnecessary disclosure.

This analysis relies on public guidance from the U.S. Equal Employment Opportunity Commission. It converts the guidance into a routing and implementation framework for executive operations; it does not decide whether an individual is entitled to a particular accommodation.

Federal, state, local, and international rules differ. HR, counsel, or another authorized accommodations owner should set the applicable process.

What the EEOC guidance establishes

The EEOC's small-employer accommodation guide explains that a person can request a workplace change in plain English and does not need to use the phrase “reasonable accommodation.” A request generally does not need to be in writing. The guide describes a prompt, informal interactive process for clarifying the need and identifying an effective accommodation.

It also emphasizes confidentiality of medical information.

The EEOC's reasonable accommodation policy tips recommend identifying responsible contacts, requiring prompt responses, updating requesters about status, considering temporary measures during delay, protecting medical information in a separate confidential file, and explaining decisions. The guidance also notes that federal, state, and local law may create different or additional duties.

For an executive assistant, the practical lesson is role clarity. The assistant can recognize a possible request, acknowledge it without demanding proof, route it promptly, and implement approved operational changes. The assistant should not test legal eligibility, seek a diagnosis, promise an outcome, or disclose the reason to colleagues.

Define the recognition threshold

A useful trigger is a request for a change at work that is linked to a condition, belief, pregnancy-related limitation, or other need covered by policy. The wording can be informal. “Long video meetings aggravate my condition; can I join by audio?”

may be enough to activate the route even though it lacks legal terminology.

Train assistants to respond with a neutral acknowledgment: confirm the requested operational change, explain that the organization has a process, and connect the requester with the named owner. If an immediate calendar or access change is within ordinary authority and does not disclose sensitive information, the assistant may be able to make it while review proceeds. The policy owner should define that boundary.

Do not ask for medical records, diagnosis details, medication information, or an explanation to satisfy personal curiosity. Where documentation is permitted and needed, the authorized owner should request and store it. The executive assistant's case note can be minimal: request received, routing time, owner, operational deadline, and implementation status.

Recognition training must avoid assumptions. An assistant should not infer a disability from appearance, performance, or behavior. Nor should every scheduling preference become a medical inquiry.

The trigger is information supplied by the person or a policy-defined circumstance, followed by respectful routing rather than investigation.

Build a confidential routing architecture

Publish more than one intake path. A requester may not want to disclose a need through the executive they support or the assistant who controls access to that executive. Provide a direct HR or accommodations channel, an alternate owner, and an accessible method for applicants or workers who cannot use the default form.

Route metadata separately from substance. The executive-support team may need to know that a meeting must include captions or that travel needs a longer connection. It usually does not need the underlying medical or religious explanation.

The accommodations owner can issue a functional instruction that contains only what implementers need.

Use restricted systems for sensitive material. Do not place a diagnosis in the executive's calendar, a broad meeting note, a shared travel profile, or an ordinary ticket queue. Calendar labels can describe the approved setup without its cause.

Access logs should show who viewed the case, while operational records should use a case identifier where practical.

Define what happens when the request concerns the executive assistant. An agency-employed assistant placed with a client may need an agency route, a client route, or both. Contracts and onboarding should state which organization receives the request, who participates in the interactive process, who funds or implements changes, and how confidential information crosses the boundary.

Convert decisions into operational instructions

An approved accommodation can affect several executive workflows. Meeting changes may involve room selection, captions, interpreters, breaks, camera expectations, written materials, or remote participation. Travel changes may affect departure time, seat or ground-transport requirements, lodging, or the pace of an itinerary.

Work allocation may require different communication methods or schedule boundaries.

Translate the decision into an implementation record with an owner, start date, review date, and fallback. Avoid recording the protected reason. For a recurring meeting, define whether the change applies to one series, all meetings, or a specific period.

For travel, confirm which details can be shared with a travel provider and whether explicit authorization is required.

Test the instruction from the requester's perspective. A nominally available feature may not be effective. Captions that are switched on after a meeting starts, an accessible entrance that is locked, or written material delivered too late can defeat the arrangement.

The authorized owner, requester, and implementer should have a quick way to identify and correct failures.

Temporary measures deserve a controlled state. If a permanent tool, room, or schedule change takes time, record the interim measure, who approved it, when it expires, and how status updates will reach the requester. Temporary should not become indefinite through silence.

Measure process quality without scoring people

Measure the operation, not the requester. Useful measures include time from receipt to acknowledgment, time to an assigned owner, percentage of implementations completed by the required date, number of overdue status updates, recurrence of the same implementation failure, and closure of corrective actions.

Report denominators and exclusions. An average response time can hide a small number of long, consequential delays. Segment by workflow type only when the analysis preserves privacy.

Small teams should avoid dashboards that allow colleagues to identify a requester from a date, location, or rare accommodation.

Do not rank requests by perceived legitimacy, cost, or the seniority of the person involved. Urgency can reflect a near-term event, but entitlement and hardship decisions belong to the authorized process. The executive's preference or schedule importance should not silently override it.

Audit samples should show that a request reached the correct owner, sensitive information stayed restricted, the interactive process was documented by that owner, implementation instructions were clear, and follow-up occurred. Auditors usually do not need unrestricted access to medical records to test these controls.

Common failure modes in executive operations

The first failure is insisting on a form before routing an oral request. A form may support administration, but the EEOC guidance says a request need not be in writing. The second is over-collection: the assistant asks for detailed evidence and stores it in email.

The third is informal disclosure, such as explaining to an executive team why a colleague receives a different schedule.

Another failure is executive bypass. A senior leader asks the assistant to decline a change without involving the accommodations owner, or the assistant promises that a request will be approved because the operational change seems easy. Both remove the decision from the defined process.

Implementation drift is equally important. An accommodation is approved, but recurring meetings are copied from an old template, a substitute assistant is not briefed, or a travel vendor does not receive the necessary functional instruction. Versioned preferences, constrained access, and owner checks can reduce this drift without exposing the underlying reason.

Finally, a company may provide only one reporting relationship. A requester who needs a change related to the executive, their manager, or an assistant may not feel safe using that route. An independent alternative is a basic design requirement.

Evidence to request from a support provider

When evaluating an executive-assistant agency, ask for the accommodation-routing policy that applies to placed workers and client stakeholders. Look for named contacts, recognition training, confidentiality rules, accessible intake, alternate escalation, implementation ownership, and a method for resolving conflicts between client practice and agency policy.

Ask how the provider distinguishes functional instructions from sensitive records. A claim that all preferences are saved in the assistant's profile can be a warning sign if the profile also contains medical explanations. Request a de-identified example showing receipt, routing, authorized decision, implementation, and review without exposing a person's condition.

Confirm that supervisors and substitute assistants receive only the information needed to implement an approved change. Check how temporary arrangements survive handoffs and how a requester reports that the change is ineffective.

Limits and decision use

This framework is not legal advice and does not decide coverage, effectiveness, or undue hardship. Those determinations depend on the facts and applicable law. Religious, disability, pregnancy, leave, labor, privacy, and local requirements may intersect.

Qualified owners should maintain the governing policy and approve case decisions.

Good routing does not guarantee a particular outcome. It makes the process prompt, accessible, confidential, and traceable. It also keeps an executive assistant from becoming an accidental gatekeeper to rights-sensitive information.

Teams can compare this operating model with the executive operations research library and the service boundaries for remote executive assistant support. Organizations that need to design a confidential schedule, meeting, travel, and accommodation handoff can start a support-design conversation with HR and legal owners included.