The Evidence Burden: When Proving Your Need Becomes Another Form of Harm

Trying to work out how to document problems with a service or provider? A good record doesn’t need to be a mountain of paperwork. Here’s what a system actually needs to make a fair decision.

Here’s something worth saying plainly: needing support is not something to prove your way out of over and over again. And yet that’s exactly what so many systems ask for, the same permanent condition explained again, the same hard experience retold again, another costly report gathered just to say what was already said last time.

There’s a better way to do this, and it starts with a simple idea. A system only needs enough evidence to make a fair decision. Not a mountain of it. Not proof stacked on proof. Enough.

When proving something becomes its own cost

Every request for more evidence carries a price tag that doesn’t always show up on paper. There’s the money, specialist reports rarely come cheap. There’s the time, chasing appointments and paperwork instead of getting on with life. And there’s the emotional toll of explaining, again, something that was never going to change or get better with retelling. None of that shows up as a line item anywhere. It just gets absorbed, quietly, by the person doing all the proving.

Why this hits some people harder than others

Not everyone starts this process from the same place. Some people have the money for another report without blinking. Others have to choose between that report and something else they need. Some people find it easy to gather documents and fill in forms. Others find that kind of admin exhausting on a good day, and close to impossible on a hard one. A requirement that looks the same on paper for everyone can land completely differently depending on what someone’s already carrying.

The good news: there’s already a better model

This isn’t a problem without an answer, plenty of good thinking already exists on how to fix it. Evidence gathered once for one service can often be trusted and reused by another, instead of collected fresh every single time. Requirements can be built with proportion in mind, asking only what’s genuinely needed for that specific decision, not the maximum a system could theoretically request. And trauma-aware design means asking for evidence in a way that doesn’t force someone to relive their hardest moments just to be believed.

What good evidence design actually looks like

Good systems ask once and trust what they’re given, rather than treating every fresh request as reason to doubt the last answer. They recognise that a permanent condition doesn’t need re-proving on a rolling basis, because permanent means permanent. They accept a reasonable range of evidence types instead of insisting on one specific, expensive version. And they design the request itself with care, so asking for proof doesn’t come at the cost of someone’s dignity.

Knowledge is the advantage here

Here’s the part that matters for anyone navigating this right now: knowing this is how it should work is itself a kind of power. It means you can ask why a piece of evidence is genuinely needed. It means you can push back when a request feels excessive rather than proportionate. It means you’re not just accepting every demand as the price of getting help, you’re able to recognise which requests are reasonable and which ones have simply become habit.

The bit that matters most

A system should gather enough evidence to make a fair decision, not so much that accessing help becomes another hardship.

Proving a genuine need should never cost more than the support it unlocks. The people designing these systems can build something better, and the people navigating them deserve to know exactly what fair actually looks like.

Madeleine x