Draft an accommodation request around a barrier and a concrete change. Keep two decisions separate: what the legitimate recipient needs to consider the request, and what you may disclose to an AI provider. These are not the same audience.
Decide where the information belongs
A functional description can reveal health or disability information even without a diagnosis. Keep real details and supporting records private. For a general chatbot, use the fictional example below or blank placeholders. Use real information only in an environment explicitly approved for that data and purpose.
You choose your identity language and how to describe your experience. The applicable process may still require supporting information. Do not assume every request succeeds with functional details alone. The US EEOC accommodation guidance describes requests and documentation in its employment-law context, including that a request can begin a further discussion. School, service and other jurisdictions’ processes differ. Use the recipient’s designated confidential channel for any required evidence.
This article helps with wording. It does not determine entitlement, legal reasonableness, deadlines or what a recipient must provide. A local disability-rights adviser or relevant qualified professional can help with those questions.
Build the request privately
Write four fields in the request builder:
- The setting and the barrier you actually experience.
- A specific change you want considered.
- How it would help you participate or do the task.
- An alternative you would genuinely accept, if you have one.
An alternative is optional; do not offer a fallback that would not meet your needs merely to sound cooperative. Avoid adding medical explanations or promises you cannot support.
A complete fictional draft
Teaching example, not an actual accommodation decision:
“In group discussions, I miss information when several people speak together. Could we use one speaker at a time and circulate the written action points? This would help me follow the decisions and contribute. If that arrangement is not feasible, could we discuss another way to make the discussion accessible?”
A weak rewrite would say “I sometimes find meetings challenging; any help would be appreciated.” It removes both the specific barrier and requested changes. Another weak rewrite would add a diagnosis, a legal threat or “this is all the documentation you may request.” None follows from the example.
Review only this fictional accommodation-request draft [use the
invented paragraph above]. Identify the stated barrier, requested
changes and intended benefit. Quote support for each. Flag anything
missing without supplying a diagnosis, legal claim or new personal
fact. Suggest a shorter version only if those elements survive.
Do not ask for my real circumstances or documents.
Check the output against the fictional input. When you draft your actual request, transfer the useful structure manually into your private document. Add only the details needed for the actual recipient and process; do not paste the completed request back into general chat for polish.
Review and follow up
Read for accuracy, disclosure and feasibility. Does the draft describe your experience as you intend? Did it preserve your preferred identity language? Does the proposed alternative really help? Remove any model-added statement about law, symptoms or the recipient’s motives.
Save the version sent, date and response in a private record. If no response arrives, follow the applicable process and any actual deadline. A follow-up can simply reference the request and ask who is handling it. If the request is refused or the process is unclear, use the relevant disability-services office, advocate or local adviser. More persuasive AI wording cannot settle a legal or practical disagreement.



