Why your impact report dies the day it's published
- Jul 17
- 4 min read
Most impact reports get read once, in the week they're published, usually by the people who wrote them. After that they sit in a folder until next year's version replaces them.
We spent a morning at the Royal Society of Arts in London unpacking why that happens. The session was hosted jointly with Ethical Good, who work on evidence, evaluation and organisational learning, and it brought together charity leaders, funders and evaluation specialists who see the same problem from different angles. This is what came out of it.

More evidence isn't producing more influence
New Philanthropy Capital found that 75% of organisations have increased their investment in impact measurement over the last five years. The Charity Commission's 2024 research found that 53% of people link their trust in an organisation directly to seeing its impact demonstrated.
So the evidence exists, and organisations are investing seriously in producing it. What's missing is the second half of the job: making sure it changes anything once it's out. Most reports follow a familiar pattern. Work happens, evidence gets captured, a report gets written, it gets published, and attention moves on to the next thing almost immediately.
A report has one real competitor: everything else on the reader's desk
Funders, trustees and partners are already buried in information by the time your report reaches them. A report can hold genuinely valuable insight and still fail completely if the right person never comes across it at the right moment. That's a shelf-life problem more than a writing problem. A PDF is finished the day it's published. It doesn't get easier to find six months later, and it doesn't get more relevant as your programme changes. It just gets older.
Pick one kind of influence, not three
The clearest idea from the session was a simple distinction: influence isn't one thing. There are three levels, and most reports quietly try to hit all of them at once.
Behaviour is what a person does differently. Systems is how an organisation allocates resources or makes decisions. Norms is what a community accepts as normal. The strongest examples we looked at picked one of these on purpose rather than chasing all three.
Breast Cancer Now's Real Self Checkout campaign changed behaviour by putting the message inside a routine people already had, rather than asking them to go looking for information. The Tampon Book, from The Female Company, changed a system by exposing a contradiction the system itself couldn't defend: menstrual products taxed at nearly three times the rate of books. Channel 4's Meet the Superhumans changed a norm by reframing how an entire television audience saw disability ahead of the London 2012 Paralympics.
Ask which one your next report is actually aiming for. If the honest answer is all three, it's probably landing none of them.
What this looks like when nobody's watching
Picture a mid-sized charity finishing its annual report. The comms lead has spent three weeks pulling together case studies, finance has signed off the figures, and the whole thing goes out to funders, trustees, staff and supporters on the same day, in the same format.
Six months later a funder asks what's changed since the report was published. Nobody has an easy answer, because the report was never built to be checked back against. Trustees read a summary. The funder skimmed the outcomes section. Frontline staff, who are arguably best placed to act on the findings, mostly never opened it. The report itself is well made. It's simply built for a single moment rather than the eighteen months of decisions that follow it, which is exactly the gap the session kept circling back to.
Take this back to your next team meeting
The practical part of the session was a five-question audit you can run on a report you've already published, no rebuild required.
Audience: who actually needs this, and does each group have a version that fits them? Influence: what specific decision or behaviour is this meant to change? Visibility: where does it show up after launch week, once the email's been sent? Longevity: is it still useful in six months, or is it sitting unopened on a shared drive? Ownership: who's responsible for keeping it alive once your team has moved on?
Most organisations can answer maybe one of these with any confidence. That gap is where the value is currently being lost.
The fix is the shelf life, not the writing
This is the problem Yarra was built to solve. A PDF report is rebuilt from scratch every year and starts losing relevance the moment it's sent. We replace it with a web-based report your own team can update, extend and publish whenever something changes, living behind one link instead of a new file every cycle.
It isn't a better-written report. It's a different shape: one that stays current instead of going stale, and gets richer every time you use it instead of resetting each year.
If your organisation is still rebuilding the same report from zero every year, it's worth a conversation. Book a call and we'll show you what a living version of your report could actually look like.
.png)