How to help someone in an autistic shutdown

What not to do

The instincts that come up watching someone shut down are loving instincts, and almost all of them make it worse. Worth saying that plainly — not as criticism, but because the gap between intention and effect is wide here, and a lot of relationships have been hurt by people doing what felt like the right thing.

Don't ask questions

"Are you okay?" "What's wrong?" "Did I do something?" "Can you just tell me what you need?" Each question is a request for output from a system that's run out of output. Even simple questions cost more than they would on a normal day. Repeated questions — even gentle ones, even concerned ones — pile up as demand and deepen the shutdown.

Don't push for a verbal answer

Speech is often the first thing to go in a shutdown. The person can hear you. They understand. They can't make the words come out. Standing there waiting for a sentence — or worse, getting frustrated when one doesn't arrive — adds load to the exact system that needs to come back online. If you have to ask anything, make it a yes/no with a thumbs up or thumbs down option.

Don't take it personally

This is the hardest one, and the one most worth holding onto. Their silence isn't about you. It isn't punishment, it isn't a relationship problem, it isn't a comment on whether they love you. It's a body in low-power mode, doing what it has to do to protect itself. Reading it as rejection turns the shutdown into a relationship event when it doesn't have to be one.

Don't try to talk them out of it

Reassurance, reasoning, problem-solving, perspective — none of it lands during a shutdown. The capacity to take in language, weigh it, and respond has temporarily gone down. Words you say now mostly produce more load. Save them for later.

Don't make it about your discomfort

Watching someone shut down is genuinely uncomfortable, and the urge to relieve that discomfort — by getting them to engage, by fixing it, by getting reassurance from them that things are okay — is real. The shutdown is a bad time to ask the shut-down person to manage how you feel. That part is yours to hold for now. There's room to talk about it together later.

What helps

Most of what helps is subtraction, not addition. The single most useful thing you can do is reduce the input load in the room and stop asking the person to produce anything.

Lower the inputs in the room

Dim the lights. Turn off the TV or the music. Move kids and pets to another room if you can. Close the door. The same triage that helps the shut-down person also lowers the cost of being in the room together.

Offer low-demand presence

Sit nearby without expecting anything. Read a book, work on your laptop with the volume off, do whatever quiet thing you'd be doing anyway. Many people in shutdown find a calm presence steadying, as long as nothing's being asked of them. Some prefer the room cleared. If you don't know which, default to nearby-but-quiet and adjust based on the signal you get.

Bring the practical things

A glass of water, a blanket, a snack you know they like, their headphones, a phone charger. Set them down within reach without making a production of it. They might not use any of them; bringing them anyway removes the decision-making demand of having to ask.

Take over one logistical thing

The dinner, the email reply, the kid pickup, the call to cancel something. Pick one and do it without asking. "I've got pickup, you don't have to think about it" is the kind of thing you can say even into silence — they'll register it.

Offer a no-language exit

"Thumbs up if you want me to stay, thumbs down if you want space" is one example. So is "tap once for water, twice for blanket." So is leaving a notepad and pen on the bed and stepping out. Anything that lets them communicate without having to produce speech reduces the cost of being a person in the room.

How to ask later what they actually need

Once they've recovered — usually a day or two after the shutdown — there's room to learn what works for them specifically. People differ on this more than you might expect, and the conversation tends to go better if you treat it as research rather than relationship repair.

A few questions that work in this kind of conversation:

• "When that happens, what helps most? What hurts?" Open question, no judgment. Let them think.
• "Do you want me in the room or not in the room?" Many people don't know until you ask. Give them permission to say either.
• "What do you want me to do about food / kids / work stuff while you're recovering?" Practical, easy to answer. Sets up a plan for next time without requiring anyone to predict the future.
• "Is there a signal you'd like to use so I know what's happening without asking?" Some couples and families set up a word, a hand sign, or a colored card. Putting it in place when both of you are calm is much easier than inventing it during a shutdown.

What to skip: questions about why it happened, requests for them to predict when the next one will be, or asking them to promise it won't happen again. None of those have answers they can reliably give, and the asking itself can feel like blame.

Repair after the shutdown

Sometimes a shutdown lands inside something hard — an argument, a stressful trip, a moment that mattered to both of you. The shutdown doesn't erase the underlying thing, and the temptation to either let it go entirely or pile back into the conflict are both common. Neither tends to work.

What works better is two separate conversations. The first is about the shutdown itself — what they needed, what you did or didn't do, what to try differently next time. Short, low-stakes, focused on the future.

The second is about whatever the original conflict was. Held later, with the shutdown not as a topic but as a fact you've already acknowledged. The conflict gets to be about itself rather than getting tangled up in the question of who handled the shutdown well.

If you handled the shutdown badly — got frustrated, asked too many questions, took it personally — say so once, briefly, and ask what would have helped. Lengthy apology and self-criticism tend to put the shut-down person in the position of reassuring you, which isn't where they need to be. "I didn't get it right earlier and I want to do better. What would have helped?" covers most of it.

The long game — learning their patterns

If shutdowns happen more than rarely in your relationship, the work isn't only about handling each one well — it's about getting to know the shape of them over time. Most autistic adults have triggers, warning signs, and recovery patterns that become legible once someone close to them is paying attention.

Things worth noticing across multiple episodes:

• Early warning signs. Speech getting shorter, eye contact dropping, the face going neutral. Catching these early sometimes lets you both prevent the deeper drop.
• Recurring triggers. Long social events, certain family members, particular sensory environments, accumulated tiredness across the week. Patterns become legible after three or four episodes that wouldn't be from one.
• What recovery actually needs. Some people need to be alone for hours; others need a quiet presence nearby. Some need food; some can't eat for a while. Their version isn't yours.
• The aftermath shape. The day after often feels off in specific ways. Knowing in advance that they'll be quieter, slower, and more sensitive helps both of you plan around it rather than treat it as a new problem.

If shutdowns are escalating in frequency or duration, that's often the early shape of autistic burnout, and the conversation moves from "how do we handle the next one" to "what's draining capacity faster than it's coming back." That's a bigger conversation, and it sometimes needs a clinician familiar with autism in adults to help shape it.

Worth saying directly: being the support person for someone who shuts down often is hard, and your needs in this don't have to disappear. Your own therapy, your own friendships, your own rest — those aren't selfish, they're how you stay someone who can show up well for the next one.

Frequently asked questions