There is a difference between giving information — 'I have ME/CFS, which means exertion of any kind can make me worse for days' — and giving justification, which is the endless proving that the information is legitimate: symptoms listed, history recited, the case defended.

Information is a gift you choose to give; justification is a tax others can imply you owe. In practice the test is simple: does the sentence inform ('here is what is true for me') or does it defend ('here is why I'm allowed')? The first closes in one line; the second never closes, because every justification invites the next question.

You are free to give information generously to people who matter and withhold it from people who don't. 'I can't make it this time' is a complete answer that contains all the information owed.

Even willing audiences cost: every retelling of the illness story is spent capacity. An explanation ceiling is a decided limit on how much explaining you will do for a given person or situation — one sentence for acquaintances, a short paragraph for close family, a written page for anyone who genuinely wants to understand.

The ceiling is not coldness; it is maintenance. People who deserve more depth can be given it in writing (see the Communication Preference Card), where it is written once, read many times, and never costs you the telling again.

When you feel the ceiling approaching — the third question, the story being told again, the flicker of resentment — that is the signal to close with a line: 'That's as much as I can usefully say today.'

Boundaries have a ladder of firmness, and it helps to know the rungs before you need them. The lowest rung is soft: 'I'd rather not, but thank you.' The next is clear: 'I can't do that.' The next is firm with a reason-sized line: 'I can't do that, and it isn't up for discussion today.' The top rungs are structural: not answering, not attending, letting a standing rule carry the answer.

Most boundaries hold on the first two rungs when delivered early and calmly. Boundaries fail when they start on a high rung after weeks of silence, or when a low rung is climbed mid-conversation out of exhaustion. Deciding in advance which rung a recurring situation deserves keeps the delivery short and the cost low.

A capacity-based boundary is simply a boundary set by capacity rather than by preference or social expectation: 'I can do lunches, not evenings', 'I can text, not call', 'One hour, then I need to go.' Because it is based on fact, it does not need defending — and repeating it calmly is not rudeness; it is accuracy.

Time boundaries protect the clock: when you reply, when you rest, how long a visit runs ('I'll be glad to see you — I'll need to lie down after an hour'). Access boundaries protect space and senses: which room the visitor sits in, whether the TV is on, what hours are quiet hours.

Advice boundaries protect against the relentless fixing: 'I'm not looking for suggestions at the moment — I have a plan and a team.' Medical-detail boundaries protect your story from becoming public property: which family members know what, whether the last test result is shared, whether the illness is discussed at family gatherings at all.

Each of these is information about what works for you — no medical debate required to deliver any of them.

Changing plans has a formula: one apology (or none), one clear statement, one alternative if there is one. 'I need to move our coffee — my body isn't going to manage tomorrow. Can we look at next week?' Long apologies cost you energy and teach the other person that cancellations are crises requiring management.

A delayed boundary is one that gets set later than it should have: you sat through the visit, took the call, answered the questions — and only afterwards realised it was too much. That is not a failure; it is information. The boundary can still be set, referencing the pattern rather than the moment: 'Visits longer than an hour leave me struggling for days, so I'm going to keep them to an hour from now on.'

A no-response boundary is legitimate too: on days when responding costs more than you have, not replying is a boundary made of silence — and a pre-written status message ('Not up to messages today — I'm okay') keeps it from being read as something worse.

Pushback is predictable — 'but you were fine last week', 'just this once', 'you're always ill' — and it does not require a new answer each time. The broken-record technique is answering pushback with the same calm line, as many times as needed: 'I can't, but thank you.' 'I can't, but thank you.' 'I understand — and I can't.'

The record is not aggression; it is refusal to be drawn into re-litigating a decision already made. Pushback that works is pushback that earns a renegotiation; pushback that meets a calm repeated line ends quickly because there is nothing to argue with.

Repairing a relationship after a boundary does not require withdrawing the boundary. Repair and the limit are separate conversations: 'I'm sorry the other night was tense — I care about you, and I'm keeping the one-hour visits.' Both things are true, and saying both is what keeps the relationship and the limit.

Brain fog changes the mechanics of communication: following a fast conversation, finding words mid-sentence, holding a topic while the other person jumps — all of it costs. One-topic communication is the adaptation: one subject at a time, slowly, in writing where possible, with no penalty for silence while the word is found.

Written communication (text, notes, email) is often genuinely cheaper than spoken: it can be answered from rest, in your own time, with no real-time processing. A preference made explicit — 'texts are better than calls for me' — spares everyone the mismatch of expectation.

For low-speech and non-speaking days, see Crash & Flare Support for yes/no cards and supporter-carried communication; the tools there are built for exactly that state, and they work on ordinary bad days too.

Family often needs the most repetition and receives the least benefit of the doubt — a written explainer given once ('here's what ME/CFS is, here's what helps') often outperforms years of retelling. Friends mostly need to know the plans will stay flexible and the friendship is not at risk. Partners need the practical version: what to watch for, what to take over, what not to take personally.

Work communication is a different genre: short, factual, about capacity and adjustments rather than symptoms ('I work best in short blocks with rest between', 'I can do this task by Thursday rather than all of it today'). Keep illness details out of it where they are not relevant; adjustments are about the working arrangement, not the diagnosis.

With healthcare providers, the script is prepared rather than improvised: the one-line summary, the top three issues, the ask, all written down in advance (see Crash & Flare Support's Appointment Rescue Sheet for the crash version). With supporters, the most useful script of all is the direct one: 'Thank you — what would help most is X.' That sentence is the bridge into Support, Asking for Help & Being Understood.