Intent
Treat the paperwork, proving, chasing and waiting that a system requires as a real cost it imposes on people — one the system chose, can measure, and can remove.
The Pattern
Every system that offers something also asks something to get it. Fill in the form. Provide the letter. Attend the assessment. Renew it annually. Appeal the refusal.
Pamela Herd and Donald Moynihan name these costs precisely. Their definition is the spine of this pattern: administrative burdens are the learning costs of finding out what exists and whether you qualify, the compliance costs of assembling evidence and meeting requirements, and the psychological costs — the stress, the loss of autonomy, the stigma — of the encounter itself.
Three properties make this a design problem rather than an inconvenience. Burdens are consequential: whether you get the benefit can depend entirely on whether you can bear them. They are distributive: they fall harder on some people than others, and in doing so reinforce the inequality they claim to address. And they are constructed — the product of deliberate choice, not a fact of nature.
That third one is the whole pattern. A burden is not weather. Someone decided the renewal would be annual, the form would be fourteen pages, the phone line would open at nine and be engaged until two.
For neurodivergent and Disabled people the costs land on precisely the capacities the system is asking about. Executive function is what the form demands and what the disability affects. The process tests the impairment while claiming to assess it.
As our glossary puts it plainly: it is a lot of work to be poor and disabled.
Why It Matters
When burden goes unnamed, people may:
- never learn a support exists, and be counted as not needing it
- abandon an application partway and be recorded as withdrawn
- lose an entitlement at renewal that they never stopped qualifying for
- spend the capacity the support was meant to restore on obtaining it
- be read as disorganised or uncommitted rather than as obstructed
- decline to apply at all, knowing what the process costs
Every one of those reads, in the system’s own data, as an absence of need.
Forces
- The process demands the executive function the support exists to compensate for.
- Burden is invisible to the institution and total for the person.
- Verification protects the budget; it also deters legitimate claims.
- Each step is individually defensible; the sum is not.
- Non-completion is indistinguishable from non-need in the records.
- The people most entitled are often least able to bear the process.
Problem
How do we stop the cost of obtaining support from exceeding the support, and from falling hardest on the people who need it most?
Solution
Count the burden as part of the design, not as something that happens after it. Name the three costs separately, because they have different remedies: learning costs fall to outreach and plain language, compliance costs to fewer and simpler requirements, psychological costs to how people are treated while complying.
Default to trust and verify by exception. Carry information forward instead of asking again. Make renewal automatic where the underlying condition is permanent, because asking someone to re-prove a lifelong disability is not fraud control, it is attrition.
Measure the drop-off, not just the intake. This works alongside Consent Over Compliance and Energy Accounting.
What This Looks Like
In physical spaces
- Do not require an in-person visit to prove something a document already proves.
- Offer the appointment at more than one time of day.
- Let someone bring a supporter without it counting against their competence.
- Say how long the wait is, and mean it.
- Do not make the accessible route the one with the extra step.
In digital spaces
- Let a form be saved and returned to, not completed in one sitting.
- State every requirement before the first field, not after the tenth.
- Pre-fill what you already hold, and never ask twice.
- Give a reference number and a real status, not silence.
- Do not make the only channel a phone call.
In social and organizational practice
- Publish what the process actually costs in time and steps.
- Audit who drops out and where, then fix that step.
- Make the default yes, with checks after, wherever the risk allows.
- Treat a missed deadline as a signal about the process, not the person.
- Never require someone to re-prove a condition that does not change.
Implementation Notes
Walk the process yourself, end to end, as a person with no inside knowledge.
Ask:
- How does someone find out this exists at all?
- How many separate pieces of evidence must they assemble, and from whom?
- How many times are they asked for the same fact?
- What happens if they cannot finish in one sitting?
- Where do people stop, and do we know?
- What does the process feel like if you are already exhausted?
A good test: if completing the application would be easier for a person who does not qualify than for one who does, the process is selecting for the wrong thing.
Signals of Misuse
This pattern is being violated when people hear:
- “We just need one more document.”
- “You’ll have to reapply from the beginning.”
- “If it mattered enough they’d have finished it.”
- “That’s just the process, everyone goes through it.”
- “The form is only available by post.”
- “You were sent a letter.”
The last one treats delivery as receipt, which is how entitlements quietly lapse.
Consequences
When this pattern is honored:
- support reaches the people it was designed for
- capacity is spent on living rather than on qualifying
- take-up stops being mistaken for need
- the process stops testing the impairment it is assessing
- trust in the institution survives the encounter
- inequality is not quietly reinforced by paperwork
When it is ignored, a system can deliver almost nothing while appearing, in its own figures, to be meeting demand in full.
Anti-Patterns
- Annual renewal of permanent conditions
- Proof demanded from a body that will not supply it
- Single-channel, single-sitting applications
- Requirements revealed one at a time
- Silence between submission and decision
- Appeals harder than the original application
- Treating low take-up as low need
Design Moves
Strategies for removing burden rather than redistributing it.
See recipes:
Related Environments
Environments where administrative burden decides who gets in:
Related Experiences
Experiences shaped by the cost of asking:
Patterns Below
Patterns Above
Metric fixation decides what the institution counts. Administrative burden is how that decision reaches a person’s kitchen table.
Related Patterns
- Pattern 10 — Energy Accounting
- Pattern 32 — Consent Over Compliance
- Pattern 39 — Average User Fallacy
- Pattern 49 — Environmental Weathering
Related Principles
- Broken Systems, Not Broken People
- Consent Beats Compliance
- Human Needs, Not Special Needs
- Access Is a Design Decision