Meltdowns and Shutdowns
A meltdown is what happens when the nervous system, having managed more than it can manage, finally lets go.
It can look like crying, shouting, running, covering ears, dropping to the ground, needing to leave immediately and with urgency. It can look frightening. It can look like a tantrum. It is not a tantrum.
The difference matters. A tantrum is what happens when a child wants something and is using the noise to try to get it. The noise gets bigger when they think they might lose, and smaller when they think they might win, because the noise has a job. A meltdown has no job. The person having one is not trying to get anything. There is nothing you can offer them that will make it stop faster, except for the meltdown to be over. They are in real distress, and at this point they are not the one in charge of what is happening, because by now nobody is.
A shutdown is the quieter version. The person becomes still, or silent, or somewhere unreachable. Speech may go small or stop altogether. From outside, a shutdown can look like sulking, or indifference, or stubbornness. From inside, it is none of those. It is the nervous system reducing what it is doing on the outside so that it can stay safe on the inside. The person in a shutdown is not absent. They are very much there, behind glass, waiting for the system to come back online.
Both states are the nervous system protecting itself. Neither is being done on purpose.
The most persistent misunderstanding of meltdowns is the tantrum comparison. The difference is functional: a tantrum is purposeful behaviour aimed at a goal, and it responds to the goal being addressed or withdrawn. A meltdown is not purposeful, does not have a goal, and will not resolve faster because demands are increased or consequences threatened. These responses make it worse, because they add input to a system that is already beyond capacity.
Understanding the relationship between overload and response changes the frame for intervention. By the time a meltdown or shutdown is visible, the overload that caused it has usually been accumulating for hours, sometimes across days. The car park was not the problem. The birthday party, and the day before it, and the week's sensory load up to that point, were the context. The car park was where the capacity finally ran out.
This means that intervention during a meltdown or shutdown is limited in what it can achieve. The most helpful responses are: reduce sensory demands (quiet the environment, reduce light, reduce people), remove additional requirements, and wait. Not passively or with visible impatience. With quiet presence or, if preferred, with space. The person will come back when they can.
After the event, many autistic people report shame, exhaustion, and sometimes a failure to remember parts of the meltdown clearly. This is not unusual; the emotional flooding involved is cognitively disrupting. The shame is not warranted but it is common. What helps is the same thing that helps during: matter-of-factness. It happened. The person is okay. Nothing has broken between you.
Prevention focuses on identifying and modifying the accumulation, not the endpoint. Tracking which environments and activities are high cost, building recovery into days before the tank is empty, and having exit strategies available are all effective at reducing the frequency and intensity of overload events.
- Lowering sensory input immediately: less noise, less light, fewer demands.
- Not requiring speech, explanation, or eye contact during or immediately after.
- Offering presence without pressure or visible impatience.
- Afterwards: matter-of-factness rather than analysis or consequence.
- "Calm down." (This is not available right now.)
- Adding explanations, reminders, or consequences during the event.
- Treating the event as the problem rather than the symptom.
- Requiring a debrief while the person is still recovering.