Workplace accommodations:
draft your request.

How do you ask for an accommodation?

Most people imagine the ask as a formal event: a meeting, a form, a doctor's letter, HR taking notes. Sometimes it is. Far more often it's an email that takes four minutes to read and gets a one-line reply saying yes, fine, let's try it.

The reason people stall isn't the process. It's the blank page. Putting your own working difficulties into words is uncomfortable, and doing it while worrying about how it'll be received makes it harder still. So the request stays in your head for months, the friction stays in your week, and nothing changes.

That's what the builder above is for. It gives you a first draft to react to, which is a far easier task than writing one. Edit it, cut half of it, change the tone—the point is having something on the page to argue with.

One structural choice worth making before you write: informal or formal. An informal ask goes to your manager, describes what would help, and needs no paperwork. A formal request goes through HR, usually names something about you, and creates a record. Most people should try the informal version first, because it's faster and it works more often than the fear of it suggests. The formal route is there if that doesn't land.

What makes a request land?

Specificity, mostly. "I need more support" is unanswerable—the person reading it has no idea what to do on Monday morning. "Send the agenda the day before" is a thing someone can agree to in ten seconds. The research on workplace accommodations keeps circling the same observation: the adjustments that get made tend to be small, cheap, and concrete. Grand restructuring is rare. A different chair, a written brief, a shifted start time is the usual shape of it.

Pair each friction with the fix. Naming a difficulty on its own puts the problem on the other person's desk and leaves them to invent a solution, which they'll do badly or not at all. Naming the difficulty and the adjustment together turns you into the person who already thought it through.

Keep the list short. Two or three asks read as considered. Eight read as a person in crisis, however calmly they're written, and the reply gets deferred to a meeting that never gets booked. Start with whichever two would give you the most back, and go again in three months once those are unremarkable.

Frame it around the work. Not because your comfort doesn't matter, but because the person reading has a job to do and a budget to defend. An adjustment described as something that makes your output more consistent is an easier yes than one described as something that makes your day more bearable, even when they're the same request.

And leave the door open. A line saying you'd rather hear that something can't work than have the whole request stall costs you nothing and makes refusal feel less final to the person weighing it up.

Should you tell them you're neurodivergent?

There's no answer to this that holds for everyone, and anyone who gives you one is selling something. What the research on disclosure does suggest is that outcomes track the workplace more than the wording. The same sentence lands differently in a team with a track record of handling this well and a team without one. You know which of those you're in better than any page can.

What naming a diagnosis gets you: access to whatever formal process exists where you work, which usually depends on something being on record. A shared explanation, so the adjustments don't look like preferences someone can quietly drop. And, for some people, the relief of stopping the management of an open secret.

What it costs: control of the information. Once it's said it can't be unsaid, and it travels — to your next manager, into the way a difficult week gets interpreted, into who gets offered the stretch project. Studies of autistic adults' disclosure experiences find outcomes running in both directions, which is the honest summary rather than a discouraging one.

The middle option gets overlooked. You can describe how you work and what you need without naming anything at all, and most everyday adjustments are available on that basis. A manager who agrees to written briefs doesn't need to know why. That route keeps your information yours and still changes your week, which for a lot of people is the whole objective.

Whatever you choose, choose it deliberately. The worst version is disclosing by accident halfway through a difficult conversation, when you're tired and the framing gets away from you. Deciding in advance—including deciding not to—is what keeps it yours.

What if they say no?

First, work out which no it is. A no that means "I don't understand what you're asking for" is common and fixable—go smaller and more concrete. A no that means "this costs money we don't have" can sometimes be met halfway. A no that means "we don't do that here" is a different animal, and it tells you something about the employer rather than the request.

Ask for the reason in writing, without heat. Something like: could you let me know what didn't work about this, so I can suggest an alternative? It's a reasonable question, it invites a solution rather than a verdict, and it leaves a trail if you need one later.

Then get someone else involved. Depending on where you work that's a union rep, HR, an employee network, or a local disability advocacy organisation—many of which answer questions for free and know what your employer is required to do far better than we do. This page can draft you a message. It can't tell you what you're entitled to, and it isn't going to guess.

Keep your own record either way. Dates, what was asked, what came back, kept somewhere that isn't a work laptop. Most of the time you'll never need it. When you do need it, nothing else substitutes.

And hold on to the possibility that the answer isn't in this job. If specific, modest, well-framed requests get refused on repeat, you've learned something real. Plenty of people spend years trying to earn an accommodation from an employer who was never going to give it, when the same energy spent looking elsewhere would have solved it.

Common questions