When I Can’t Use My Words: The Scripts I Send Instead

On the days my speech layer goes offline, I send one pre-written line, and the people who love me know exactly what it means.

Some days I can’t use my words. Not “don’t want to” - can’t.

I used to handle this by completely disappearing out of sight. Now, I send a single pre-written message, and the people who love me instantly know exactly what it means.

A few years ago, my partner came home and found me sitting flat on the bedroom floor with my back pressed against the wardrobe and the lights completely off. I had been sitting there for about three hours. I had not eaten. I could hear them coming through the front door, calling out to ask if I was okay, getting closer to the room, and getting noticeably more worried by the silence.

I knew exactly what was happening in the house. I understood the distress my silence was causing. But I could not say a single thing back to stop it.

This structural breakdown is the reality of autistic shutdown communication failures. It is not a “panic attack” the way most people use the phrase; it is a literal hardware collapse on the speech layer. The internal thoughts remain entirely intact. The vocabulary is completely intact. But the physical transmission line between thinking the word and vocally delivering it has vanished.

If you have never experienced it, the closest analogy is being deeply concussed: you know exactly what you want to say, you can feel its distinct shape in your head, but you cannot make your mouth deliver it to the room.

The next morning, I opened my devices and made a Notes-app file called the “Bad-Day Protocol.” I drafted four short scripts for my partner to reference when this happened again, plus a one-line message I could send to activate the framework myself.

It completely transformed our relationship. Not because the bad days magically stopped happening - they didn’t, although they became significantly less frequent - but because we both finally possessed a shared script for them. Neither of us had to improvise inside a crisis.

#Why “just say it” doesn’t work

Most mainstream communication advice operates on the assumption that you always possess two fundamental things: immediate access to your spoken vocabulary, and the metabolic energy required to use it. On a bad day, you have neither.

The standard recommendations - tell people what you need, be entirely clear about your boundaries, use objective “I” statements - all collapse under their own weight when the act of speaking itself is the barrier.

These tips also tend to carry an unspoken, toxic assumption that if you truly cared enough about the other person, you’d find a way to break the silence. They treat the issue as a failure of motivation, rather than a total depletion of neurological bandwidth.

It isn’t motivation. It’s bandwidth. And the answer is never to brutally push through and force the words out under load; it is to deliberately prepare your text in advance, when your system is cool and functional, so the bad-day version of your brain doesn’t have to manufacture language from nothing.

#What’s in the Bad-Day Protocol

I maintain three distinct layers of communication for hard days. Every single one is drafted well in advance. I never attempt to write them in the middle of a collapse.

Layer 1: The Signal: A single emoji or microscopic message sent to the people who matter most. It communicates: I am in a non-verbal space, please initiate the protocol. Mine is simply 🌑. My partner’s signal to me is a specific, pre-saved GIF. It requires zero sentence composition. It simply triggers the framework.

Layer 2: The Status Update: Three or four blunt, pre-written sentences I can copy-paste into a chat window without thinking. They cover immediate operational logistics:

Layer 3: The Full Script: Longer, pre-written paragraphs designed for formal scenarios outside the house. These cover telling a manager I need a mental health day, informing a friend I have to cancel plans, or letting family know I won’t be joining the weekly phone call.

These exist permanently as raw drafts in my notes app. I copy, paste, and hit send. There is no drafting, no tailoring, and no exhausting path of apologising. The entire setup takes a couple of hours to compile when you are well, and then sits quietly waiting to protect you. The first time I used it, I burst into tears with sheer relief.

#How to write your own

You do not need to copy my exact vocabulary. You need your own unique scripts, written in your natural voice, tailored for your specific people. Follow this sequence to build them from scratch:

1. Identify your top three high-load situations:

Locate the bottlenecks.

Isolate the exact scenarios where spoken language has failed you or felt impossibly expensive in the past. Work check-ins, family events, or asking a partner for domestic help. Do not list your feelings - list the specific external situations.

1. Write the message you actually need someone to receive:

Draft without apologies.

For each scenario, write the exact line you wish you had been capable of sending. Keep it to one paragraph maximum, using plain, blunt language. Remove all unnecessary apologies; your nervous system does not owe an apology for running out of resource.

1. Select your unmistakable signal:

The one-tap trigger.

Pick an emoji, a GIF, or a single capitalised word that can be dispatched in one tap. Tell your inner circle exactly what it means. Ensure it is entirely unmistakable and requires zero context to understand.

1. Brief your circle well in advance:

The good-day alignment.

The protocol fails completely if nobody knows the rulebook exists. Have a brief conversation on a high-energy day: “Sometimes my speech layer goes entirely offline. When that happens, you will receive this signal. It means X, and I need you to execute action Y so I can recover.”

1. Consolidate everything into a single pinned file:

Zero friction access.

Save your scripts where they can be reached within two seconds without thinking. Pin the folder to the top of your notes application, keep a shortcut on your desktop, or print it out. If it takes effort to find, you won’t use it under load.

#What having a protocol does to a relationship

The conversation in step 4 is undeniably the hardest part of the entire process. It feels intensely uncomfortable to sit across from someone you love and openly explain that there will be days when your body will refuse to speak to them.

It is also, in my lived experience, the single most relationship-improving conversation I have ever executed. Twice.

Here is what it actually changes: it permanently removes the interpretation gap. On a bad day, without a protocol in place, the person who loves you is left guessing in the dark. Are you angry at them? Did they hurt your feelings? Are you intentionally avoiding them? Should they push for answers, or back away completely?

Their nervous system begins to violently spiral while yours is already in total collapse. Now, you have two people in serious trouble.

With a protocol, that terrifying gap closes instantly. They see the 🌑 emoji. They know exactly what it means. They execute the pre-agreed tasks. They don’t have to interpret your mood when you can least afford the energy to be interpreted. And you don’t have to frantically manufacture clarity from a place where clarity has gone completely offline.

It also gently reframes your design in their eyes. You stop being viewed as someone who unpredictably shuts down on them, and start being seen as someone who actively prepares for the shutdowns. That distinction is monumental. It moved me, in my partner’s view, from being “moody and unpredictable” to “running vital maintenance on a system they understand, navigate, and respect.”

Which is, in fact, what was always happening - I just hadn’t given them the manual yet.

The protocol is not actually for the bad days. The bad days are going to arrive regardless of your organisation. The protocol is for the relationships. It decides exactly what those hard days do to the people around you, and how much of yourself is left over afterwards.

— Ollie