Support Library

Support Library

Capacity & Demand

Making hidden demand, background load, competing demands and trade-offs visible — so the true cost of a day can be seen and shaped on purpose.

Quick View

  • Everything competes for one budget — whatever category it looks like.
  • Invisible load is real load: waiting, uncertainty, monitoring, sensory background.
  • Two 'manageable' things in the same window may not be manageable together.
  • Judge the day as a whole, not each item alone.
  • Trade-offs are not failure — they are the whole skill.

Overview

With ME/CFS, everything draws on one limited budget — visible tasks and invisible ones alike. Holding plans in your head, waiting for a call, monitoring your own symptoms, background discomfort, the hum of a busy room: all of it spends before a single 'real' task begins.

This collection exists to make that hidden demand visible. Most overload does not come from one big thing; it comes from several manageable things landing in the same window, plus the invisible load nobody counts. Once the true cost is on paper, it can be weighed, spaced, reshaped and traded deliberately.

This is a companion to Pacing & Energy, not a repeat of it: pacing is how you match activity to capacity, this is how you see what actually landed on the day.

Full Guide

Total demand, not individual tasks

The question 'can I do X?' has no honest answer on its own. The honest question is 'can the day hold X, given everything else it already holds — including the invisible parts?' A shower is one demand; a shower on a morning that already holds a phone call, a hospital letter and a poor night's sleep is a different demand entirely.

This is why checking a to-do list against individual items keeps failing: every item passes the test on its own, and the day still collapses. The unit of planning is the day (or week), not the task.

Hidden demand

The most expensive parts of a day are often the ones nobody counts. Waiting for a delivery window. Holding a plan in mind all morning so it isn't forgotten. Deciding what to wear. Rehearsing what to say at an appointment. Monitoring symptoms and quietly calculating all day whether the plan still fits.

Hidden demand is not weakness or anxiety — it is real cognitive work that happens because life keeps asking questions of you. Naming it is the first step, because you cannot weigh a demand you have not noticed.

A medical appointment, for example, is rarely just the appointment: travel, waiting, sitting upright, following and answering questions, plus the days of preparation, the paperwork, and the processing afterwards. The visible part is often the smallest part.

Find the costs that rarely get counted — waiting, rehearsing, aftermath.

Open Tool

Background load

Some demand runs continuously rather than arriving as an event: sensory background (light, noise, a cluttered room, other people's movement), emotional background (worry, a tense relationship, an unresolved letter), and cognitive background (the half-dozen open loops your mind keeps alive).

Background load matters because it is invisible to plans. A day with 'nothing in it' can still be full — a fact that often leads to self-blame ('I did nothing today and I'm still exhausted') when the truth is that background load was doing the spending.

Reducing background load is often the cheapest capacity gain available: closing loops by writing them down, lowering sensory input, or moving one unresolved thing into a decided state.

Demand stacking

Demand stacks: a shower in the morning, a visitor at lunch, a phone call in the afternoon — three 'manageable' things that together are not. Stacking is how overload arrives without any single item looking guilty.

The habit that catches stacking is looking at the whole day before adding anything: the calendar, the background load, the quality of last night's sleep, what tomorrow holds. If the day already holds two demands, the next one needs a trade, a different day, or a smaller version.

Spacing is the simplest fix — moving the shower to the night before, the call to the next morning — not because any item was wrong, but because of where they sat.

See what's already in the window before adding anything.

Open Tool

Competing demands and trade-offs

When capacity is finite, something always gives. The meaningful choice is not 'can I avoid giving something up' but 'which thing gives, and who chooses'. A trade-off made deliberately is a plan; the same trade-off made by collapse is a crash.

Trade-offs get easier with a written list: what must happen, what matters today, what merely wants to happen. The Trade-Off Sheet puts two competing demands side by side and asks what actually gives the most relief — which is often not the option that looks most responsible on paper.

Households can trade too: the household day that cleans, cooks, shops and launders all in one go is a demand stack with a broom in its hand. Splitting it across days, or dropping a component entirely for now, is a trade — not a defeat.

Two competing demands, side by side, with the honest questions.

Open Tool

Before, during and after

Almost every demand has three phases: preparation, the event itself, and the aftermath. A family event costs the travel and dressing before, the social and sensory load during, and the processing, recovery and follow-up messages after. Planning only the 'during' is planning a third of the cost.

The practical version is to reserve recovery around real demand rather than hoping it will be available. The day before is quieter, the day after is protected, and the event itself is attended at the size that fits.

Waiting and uncertainty belong to these phases too: the week of anticipating a scan is demand, not just the scan day. Giving the wait its own smaller form (a written worry, a decided plan for either result) can shrink what is otherwise a week of background load.

Changing the shape of demand

Seeing demand honestly is only useful because demand can then be reshaped. Three moves cover most of it. Transfer: someone else carries the errand, the call, the paperwork. Compress: the same outcome in a smaller form — a phone appointment instead of travel, a delivery instead of a trip, one big shop instead of four small ones. Substitute: a different thing that meets the same need — a text instead of a visit, a gift voucher instead of a chosen-by-hand present.

These moves reduce load without assuming all activity can or should be avoided. The aim is not a shrinking life but a better-shaped one, where demand is spent where it is worth spending.

What is worth spending is genuinely individual: parenting, working, a friendship, a craft — for some people those are the point of the capacity, and the trade-offs go to the chores instead. That is the trade working correctly.

Core Frameworks

The Single Capacity Budget

All demands draw on one budget, whatever category they arrive wearing.

Hidden & Background Demand

The waiting, monitoring, sensory and emotional load that runs before the 'real' tasks begin.

Demand Stacking

Two or more manageable things in the same window — the most common source of overload.

The Deliberate Trade-Off

Choosing what gives, on purpose, instead of letting a collapse choose.

Before / During / After

Every demand has three phases; planning only the middle one plans a third of the cost.

Reshaping Demand

Transfer, compress, substitute — reducing load without emptying life.

Real-Life Examples

Jess 'rested all day' before a hospital appointment — but the rest contained a shower, choosing an outfit, packing a bag and rehearsing what to say. The appointment tipped her into PEM, and the confusing part was that the day had felt easy. Writing the day out made the hidden costs visible: four demands wearing a rest day's clothing.

The new plan moved the shower to the day before, chose the outfit a week earlier, and wrote her questions for the consultant on a card instead of rehearsing them. The appointment day held one demand instead of five — and the week after it looked different.

A second example from ordinary life: a day of 'just a few small things' — posting a parcel, one phone call, a delivery arriving, and cooking. Each item passed the 'manageable' test. Together, with a poor night behind them, they were a full day's spending, and the evening was lost to it. Spacing two of them to the next morning would have made the whole two days easier — nothing needed dropping, only moving.

Scripts

Short, reusable sentences for the situations that come round again. Written once, used many times.

Naming a trade-off to someone else

  • “I want to do both, but today holds more than it looks like — one of them needs to move.”
  • “If I do this today, something else has to come off. Which would you rather I kept?”

Practical Tools

Reflection

Gentle prompts for a day that allows them. Skippable by design — nothing here needs completing.

  • What did today actually hold — including the parts nobody would see on a list?
  • Which invisible cost repeats most often in my week, and what could it be moved into?
  • Where do my trade-offs currently go by default — and is that where I would choose them to go?
  • What is the last thing I did that was worth its full cost?

Low-Cognitive-Load Version

  • One budget. Everything spends from it.
  • Count the invisible things as real.
  • Two demands is already a full day.
  • Drop something on purpose.

Moderate / Severe / Very Severe Adaptation

Moderate

You can often move demands rather than drop them — spacing fixed commitments with protected recovery between them, and shifting preparation (showers, outfit choices, packing) to quieter days before. The skill is in the spacing as much as the choosing.

Severe

Fewer demands compete, but each one costs more. One demand per day may be the honest ceiling, and the invisible phases — preparation, aftermath, processing — can cost more than the visible event. Recovery after real demand may need to be measured in days, not hours.

Very Severe

Even 'small' inputs compete for what little capacity exists: light, sound, a conversation, being moved or touched. For some people, where appropriate and depending on tolerance, the demand map becomes a protection map — reducing inputs rather than scheduling them, and letting supporters carry the phases (before, during, after) that need carrying.

For Supporters

If someone helps you, this is the part written for them.

The most useful thing a supporter can do with demand is carry a phase of it — the shopping that removes a trip, the phone call made on someone's behalf, the quiet house during recovery after an event. What helps less is weighing in on whether a particular demand 'should' be too much; the whole point of the demand map is that costs are often invisible, including to the person who paid them.

Gentle Reframes

Instead of: “I should be able to manage all of this.”

Try: “Capacity is finite. Choosing is not failing.”

Instead of: “It's only a shower.”

Try: “'Only a shower' can be half the day's budget.”

Instead of: “I did nothing today and I'm still exhausted.”

Try: “Background load is load. It was never nothing.”

Collection Summary

Overload usually comes from stacking and invisible load, not from any single task. So the work is seeing honestly: map the whole day, count the hidden costs, notice the background load, and treat every demand as having a before, during and after. Then shape it — space, transfer, compress, substitute — and choose the trade-offs on purpose. The companion practice, matching activity to what you have, is Pacing & Energy.

Related in the Support Library

Bedside & Support Sheets

From the Bedside & Support Sheets collection — quick-use versions, built for the hardest days.