Capacity & Demand

One-Page View

Before / During / After Map

Seeing the full arc of an event, and protecting the space around it.

A keep-close version. Read it here, or screenshot this page to have it on your phone — print and PDF copies will appear once final files are attached.

Almost every demand has three phases — and planning only the middle one plans a third of the cost. This maps a real event end to end, so recovery gets reserved instead of hoped for.

The event

What and when

e.g. Nephew's birthday, Saturday afternoon

Before

  • Dressing, packing, preparing
  • Travel there
  • The anticipation — the week of low-level bracing

During

  • Social load — company, conversation
  • Sensory load — noise, light, other people's movement
  • Upright time

After

  • Travel home
  • Processing and follow-up messages
  • Recovery — how much, and when

Where recovery gets reserved

The day before is deliberately quieterThe day after is protected — nothing bookedThe event itself is attended at a smaller sizeThe aftermath is handed to someone — messages, thank-yous, follow-upsRecovery is pencilled in but flexible

If there's a wait or an unknown involved

Waiting is demand too. Giving it its own smaller form can shrink a week of background load.

The wait, and its decided form

e.g. Scan results — a written plan for either answer, so it stops running all week

Reserving recovery isn't pessimism — it's what makes the next real demand survivable. Whatever size you chose, that was the size that fits.