ADA Accommodations & Flexible Work Requests
An ADA accommodation request workflow routes a disability accommodation or flexible work request through the interactive process the ADA requires: identifying the specific limitation, exploring accommodations together with the employee, and documenting the outcome. Employers sometimes must initiate this process without a formal request if they have reason to know an employee needs one. Remote work is a reasonable accommodation only when it enables performance of the job's essential functions, not simply when it would make the employee more comfortable.
Key takeaways
-
The ADA does not require an employer to guess correctly on the first try. It requires a genuine, good-faith interactive process between the employer and the employee to figure out what accommodation actually works, and an employer that never engages in that process at all is exposed regardless of what accommodation eventually would have been reasonable.
-
Sometimes the institution has to start the interactive process itself, without waiting for a formal request, if it knows an employee has a disability, knows the employee is having workplace problems because of it, and has reason to know the disability itself is preventing the employee from asking.
-
Remote work is not automatically required or automatically deniable. It depends on whether physical presence is actually an essential function of that specific role, which means the same accommodation request can have a different answer depending on the job, not the disability.
Why "we'll figure out an accommodation" is not enough
A manager receives a request for a flexible schedule or a modified workspace from an employee managing a disability, and responds informally, maybe adjusting a start time without ever documenting what was actually requested or why. This feels accommodating, and it might even work for that specific employee. It also creates no record that an interactive process happened at all, which becomes a real problem the moment that informal arrangement changes, the manager leaves, or the employee's needs shift and nobody remembers what the original accommodation was supposed to address.
The interactive process, and who actually has to start it
Under 29 CFR 1630.2, determining an appropriate reasonable accommodation may require the employer to initiate an informal, interactive process with the employee to identify the precise limitations the disability creates and the potential accommodations that could address them. EEOC enforcement guidance is explicit that an employer cannot sit back passively once it is aware a need exists; the employer has to meet the employee "half-way." In some circumstances, the institution has to start this process itself, without a formal request, if it already knows the employee has a disability, knows the employee is experiencing workplace problems connected to it, and has reason to know the disability itself is what is preventing the employee from asking. Waiting for a perfectly worded formal request in that situation is not neutral. It is a failure to engage. The Job Accommodation Network, a Department of Labor-funded resource, exists specifically to help employers identify accommodation options once that process starts.
When remote work has to be granted, and when it doesn't
EEOC guidance on telework as a reasonable accommodation ties the answer directly to essential job functions: telework is required as an accommodation when it would enable the employee to perform the essential functions of the role, not simply because working from home would ease symptoms or improve comfort. An employer is not required to eliminate an essential function to grant a remote work request, and physical presence itself can be an essential function for roles that require in-person supervision, hands-on interaction, or team-based work that does not translate remotely. The same disability can produce a different answer for two different roles at the same institution, because the analysis turns on the job's actual essential functions, not on the disability itself. EEOC's 2026 federal sector telework FAQs, while formally directed at federal agencies, rely on the same ADA standards and case law that apply to any employer working through this analysis.
What has to happen for each accommodation type
|
Request type |
What triggers review |
What the process has to establish |
|
Physical workspace modification |
Employee request or known need |
Specific limitation and whether the modification resolves it |
|
Schedule flexibility |
Employee request or known need |
Whether the fixed schedule itself creates the barrier |
|
Remote work |
Employee request or known need |
Whether physical presence is an essential function of the specific role |
|
Employer-initiated review |
Employer's own awareness of disability and workplace difficulty |
Same interactive process, started without waiting for a formal request |
A governed accommodation request workflow
Every request enters through a consistent intake, not a manager's informal judgment call
Whether the request comes from the employee directly or is initiated by the institution because a need is apparent, it enters the same documented process.
The interactive process is structured, not improvised
The specific limitation, the essential functions of the role, and the potential accommodations considered are captured as the conversation happens, not reconstructed afterward if the arrangement is ever questioned.
Essential functions are evaluated against the actual role, not assumed generically
A remote work request is assessed against what that specific position actually requires, rather than a blanket policy that treats every role the same way.
The outcome and its rationale are documented and retained
Whether the accommodation is granted, modified, or denied, the reasoning is recorded, protecting both the employee's record and the institution's ability to explain the decision later.
Accommodations are reviewed, not set permanently and forgotten
As a role or an employee's circumstances change, the workflow flags the accommodation for review rather than leaving an outdated informal arrangement in place indefinitely.
Employer-initiated cases are tracked the same way as employee-initiated ones
When the institution has reason to start the interactive process itself, that process gets the same documentation and follow-through as a request the employee submitted directly.
Kissflow and the accommodation request stack
Kissflow is the governed execution layer at the edges of the accommodation request stack. It does not replace HR's judgment about what accommodation is appropriate or the manager's conversation with the employee. It replaces the informal, undocumented arrangement that currently stands in for a real interactive process, the one that works fine until it needs to be explained or defended later.
If your institution runs Workday or another HR system of record, Kissflow does not compete with it for employee records. It sits alongside it as the layer that structures the interactive process, ties the essential functions analysis to the specific role, and keeps a documented record of every accommodation decision and its rationale.
The differentiation that matters to an HR or operations office: when EEOC guidance shifts, as it did with the federal sector telework FAQs, or the institution updates its own essential functions documentation for a role, the office that owns accommodations updates the workflow directly, instead of retraining every manager on a change a generic HR ticketing system was never built to reflect.
Frequently asked questions
1. Does an employer have to grant the exact accommodation an employee requests?
No. The employer has to provide an effective reasonable accommodation, not necessarily the employee's preferred one, as long as the accommodation actually addresses the limitation and enables the employee to perform the job's essential functions.
2. Can an employer be found non-compliant even if it eventually offered a reasonable accommodation?
Yes, if it never engaged in a genuine interactive process to get there. The process itself, not just the final outcome, is part of what the ADA requires.
3. When does an employer have to start the accommodation conversation without being asked?
When it knows the employee has a disability, knows the employee is having workplace difficulty connected to it, and has reason to know the disability itself is preventing the employee from making a request.
4. Is remote work always a required accommodation for a qualifying disability?
No. It depends on whether physical presence is an essential function of that specific role. Where it is not essential, remote work may be required. Where it is essential, the employer is not required to eliminate it.
5. Does Kissflow replace our HR system for accommodation records?
No. Kissflow is the workflow layer that structures the interactive process and documents the essential functions analysis and outcome. Your HR system of record remains the system for the underlying employee record.
Request a 30-minute walkthrough to see how Kissflow structures the ADA interactive process and documents every accommodation decision from request to outcome.