Autistic shutdown at work

How shutdowns show up at work

The workplace version of shutdown rarely looks like the textbook image of someone curled up in a corner. Most autistic adults at work have spent years learning to absorb overload without showing it, so the shutdown that happens in the office is often a quieter, harder-to-spot version of what would be obvious at home.

Common shapes:

• The quiet meeting. You stop contributing midway through. Camera stays on but the face goes neutral. People notice but don't say anything until later.
• The autopilot afternoon. You keep working on the task you were already on, looking functional, while inside, capacity has dropped to near zero. New requests don't land. Email stops being readable.
• The bathroom break that becomes twenty minutes. The body knows it needs the room. You don't, until you're in there with the door closed and the lights off.
• The day-after fog. The shutdown that happened yesterday is gone, but the recovery is still running. Today's deadlines feel impossible in a way you can't explain to your manager.

From the outside, all of these often get misread as disengagement, attitude, or performance problems. The story most autistic adults tell about workplace shutdowns is some version of "people thought I was being rude, and I didn't know what was happening either." That's the gap this page is trying to close.

The impossible position

Workplace shutdowns put you in a position with no clean exit. Recovery wants quiet, low input, and time. The job wants engagement, output, and presence. The thing your body needs and the thing your role demands are in direct conflict.

Pretending that conflict doesn't exist is what makes shutdowns at work expensive. The compounding cost of pushing through one shutdown after another shows up later as autistic burnout — a much harder thing to recover from than any single bad afternoon.

The work, then, isn't heroic-ing through. It's getting honest with yourself about which moves are available — emergency, preventive, structural — and using them before the bill compounds.

Emergency moves when it's already happening

Once a shutdown has started, the goal is to stop the bleed. Not fix it. Not push back into full functioning. Just lower the load enough that the system can stabilize.

Get to a quieter room

Bathroom, stairwell, your car, an empty conference room, outside. Anywhere with less input than where you currently are. Five minutes is sometimes enough to keep the shutdown from going deeper.

Cancel one thing

The next non-critical meeting, the lunch you'd said yes to, the call that could be an email. A short message — "Need to reschedule, can we move this to tomorrow?" — closes a loop and frees up resources you don't have to spare. People reschedule all the time. You don't owe a medical explanation.

Switch to written-only mode

If speech is sticky, drop verbal communication for the rest of the day. Slack, email, written notes. Most knowledge work runs through text already. "Quick brain — can we move this to email?" is a sentence most colleagues accept without comment.

Leave if you can

"Not feeling well, going to head home and pick this up tomorrow" is a thing employed humans say. You have used this sentence before for non-shutdown reasons. It works for this one too. Going home before the shutdown deepens often saves a full day of recovery on the back end.

Eat and hydrate before driving anywhere

Shutdowns tank blood sugar and slow reaction time. Sit somewhere safe for fifteen minutes before getting behind the wheel.

Preventive moves across the week

The cheaper version of all this is not getting to the shutdown in the first place. That's a structural game, not an emergency one.

• Front-load the brutal stuff. If your capacity is highest in the morning, put hard meetings and hard tasks there, not at 4pm when the reserves are thin.
• Build buffer between meetings. Back-to-back is a recipe for accumulated load. Even a 10-minute gap to walk away from the screen and reset between calls reduces the day's total cost.
• Skip optional meetings without guilt. Most of them. Most of the time. The "should I be there" instinct is calibrated for neurotypical capacity, not yours.
• Lunch alone is medicine. Eating at your desk while reading something easy isn't antisocial; it's the cheapest sensory reset available in the workday.
• Watch the social meetings, not only the work meetings. Team lunches, all-hands, after-work drinks — the small talk and group dynamics often drain more than the work itself does.

None of this is heroic. It's the kind of small structural choice that, taken together over a quarter, changes how often the workday ends in a shutdown.

The disclosure question

At some point, if shutdowns are happening more than rarely, the question of disclosure shows up. There's no clean answer, and the right answer for you depends on factors only you can weigh.

Reasons people disclose:

• Access to formal accommodations.
• Lower masking load — being able to stop performing neurotypical-ness all day.
• Protection in the rare cases where shutdown patterns get misread as performance issues.
• A more honest working relationship with people you trust.

Reasons people don't, or wait:

• Bias in the specific company or industry.
• A manager who'd handle the information badly.
• Fear of being managed differently — given less stretch, more careful handling, fewer opportunities.
• Job market reality where leaving for somewhere better isn't immediate.

Partial disclosure is also a thing. You can tell HR for accommodation purposes without telling your team. You can tell one trusted manager and no one else. You can name a need ("I work better with camera off in long meetings") without naming the diagnosis behind it.

Whatever you decide, decide deliberately. Drift into disclosure during a shutdown — explaining yourself in the middle of an episode — is the version most people regret.

Accommodations worth asking for

If you've disclosed (or you're at a company that's open to accommodation requests without formal disclosure), the ones that tend to make the biggest difference for shutdown patterns:

• Camera-off as default for video calls. Performing engagement on camera is one of the most expensive things a remote-working autistic adult does all day.
• Written-first communication. Being allowed to follow up on questions by email rather than answering on the spot in meetings.
• A quiet workspace. A private office, a permitted seat in a quiet zone, or noise-canceling headphones approved for use in meetings.
• Reduced unscheduled-meeting load. Calendar protected from ad hoc invites, with a written intake process for new requests.
• Flexible start times. The morning after a shutdown is rarely a 9am-sharp morning. Flex on start, with the same end-of-day deliverables, often costs an employer nothing.
• Permission to step out of meetings. Without explanation, with the understanding that you'll catch up via notes.

None of these are unusual. Many large employers have approved versions of all of them under existing accommodation frameworks. If you're in the US, the Job Accommodation Network (askjan.org) has plain-language guides on how to request accommodations for autism.

Frequently asked questions