Asking for an accommodation — at work, at school, at an event, or from a service provider — is a specific kind of writing task that is easy to get wrong in two opposite directions. Too vague (“it would help if things were more accessible”) gives the recipient nothing concrete to act on. Too much medical detail turns a practical request into an oversharing of private health information that was never actually required to justify the ask. The useful middle is a request built around functional impact and a specific solution, with exactly as much disclosure as the situation calls for and not a sentence more.
A model is a genuinely useful drafting partner for finding that middle, because structuring “here is the barrier, here is what would fix it, here is a fallback if that is not possible” is a formatting and clarity task it does well. What it cannot do is tell you what you are legally entitled to request, whether a given accommodation is “reasonable” under your jurisdiction’s rules, or what language you should use to describe your own disability or condition — those are legal questions and personal choices, not drafting questions.
Do not ask a model whether you are legally entitled to an accommodation, whether a request is “reasonable” under disability law, or what a recipient is obligated to provide — these are legal questions specific to your jurisdiction, your relationship (employee, student, customer), and facts a model cannot verify. If you want to understand your legal position before making a request, or if a request is refused and you want to know your options, that conversation belongs with a disability rights organization, an employment or education advocate, or a lawyer, not a chat tool.
Step 1: Decide what to disclose before you start drafting — this stays your decision entirely
Before describing anything to a model, decide for yourself how much detail the request actually needs. Most accommodation requests only need the functional impact (what the barrier prevents you from doing) rather than a diagnosis or medical history — “I cannot sit for more than 20 minutes without significant pain” communicates what a recipient needs to act on without requiring a specific medical label at all. Choose your own language for describing your disability, condition, or identity; a model has no standing to decide this for you and should follow whatever terms you provide.
Disclose the minimum information the request actually needs to be actionable, and keep anything more detailed (a diagnosis, a specific medical history, a treatment plan) out of both the draft and any AI tool entirely unless the recipient’s process specifically and legitimately requires supporting medical documentation — in which case that documentation goes through the process’s own designated, confidential channel, not through a chat tool. You decide what to disclose; a model should never be asked to draft “the most convincing” or “most detailed” version if that means disclosing more than you have chosen to.
Step 2: Describe the barrier as a functional impact, not a diagnosis
Give the model a plain description of what the barrier prevents you from doing in the specific context (a meeting, a classroom, a checkout counter), using whatever level of medical detail you have already decided on.
Context: [workplace meeting / classroom / event / service counter].
Functional barrier: [what specifically becomes difficult or
impossible — e.g. "cannot process spoken instructions quickly in a
noisy room and need information in writing as well"]. Use only the
disclosure level I've given here — do not suggest adding a diagnosis
or more medical detail than what I've written.
Step 3: Ask for a specific request and a fallback alternative
An accommodation request lands better when it names a concrete solution rather than only describing the problem — it gives the recipient something to say yes to immediately, and a fallback shows you have thought about feasibility on their side too.
Based on this barrier [paste from Step 2], draft a short, direct
accommodation request for [recipient — manager / instructor / event
organizer / service provider]. Include: the functional barrier in
one sentence, a specific requested change, one alternative if the
first request is not feasible, and a brief note on how this helps
[me do X / participate in Y]. Keep the tone plain and professional,
not apologetic, and do not add any legal language about
entitlement or obligation.
Illustrative shape:
Subject: Meeting accommodation request
Hi [name], for meetings going forward, could written notes or a
shared agenda be provided alongside verbal discussion? I process
spoken information more reliably alongside text, especially in
group settings. If a shared document isn't practical for every
meeting, a brief written summary afterward would also work well.
This would help me follow decisions accurately and contribute fully.
Thanks for considering it — happy to discuss further.
Step 4: Refine the tone and confirm the identity language is yours
Read the draft back and adjust any phrasing that does not match how you actually want to describe yourself or your situation — a model’s default word choices are a starting point, not the final word on how you identify or how much confidence you want to project.
Revise this draft [paste] to use [person-first / identity-first /
no disability-specific language, per your preference] throughout,
and adjust the tone to be [more direct / warmer / more formal] while
keeping the same specific request and fallback.
Step 5: Keep a record and plan the follow-up
Save the request as sent, note the date, and decide in advance what you will do if there is no response within a reasonable window — a polite follow-up message, a request for a meeting, or escalating to HR, a disability services office, or a formal complaints process, depending on the context.
Draft a brief, polite follow-up message for this request [paste
original], to send if there has been no response after [timeframe].
Keep it short and assume good faith — a simple check-in, not an
escalation.
Common pitfalls
- Letting a draft include more medical detail than you decided on. Re-read every draft against your own disclosure decision from Step 1 before sending.
- Asking the model to argue for legal entitlement. This shifts the request from “here is what would help” to an unverifiable legal claim the model has no authority to make.
- Using the model’s default identity language without checking it. Person-first, identity-first, and no-label phrasing are all valid personal choices — the model should follow yours, not default to its own.
- Sending a vague request and hoping the recipient infers the right accommodation. A specific ask and a fallback give the recipient something concrete to respond to.
Validation and fallback
Before sending, re-read the request once specifically checking that it discloses no more than you intended — this is worth a deliberate, separate read, not just a general proofread. If the request is refused or ignored, that is a good moment to consult a disability rights organization, an employee resource group, or a formal complaints process for your specific context rather than trying to resolve it through another round of drafting.
Draft your request this week
Decide your disclosure level, then run the barrier, request, and follow-up prompts above using the accommodation request builder. For the surrounding email tone and structure, emails you actually want to send covers the general drafting workflow, and AI support for neurodivergent learners is a related read if the accommodation is learning-related.
