Why Your Annual Report Belongs on the Homepage, Not the PDF

Every year, the same ritual plays out inside mission-driven organisations. Months of work — impact data, financials, stories from the field, hard-won proof of progress — gets distilled into a beautifully designed PDF. It goes up on a "Reports" page buried three clicks deep. A few dozen people download it. And then it sits there, unread, until next year's version replaces it.

If you're a B Corp, a nonprofit, or any organisation that competes on trust rather than price, this is a missed opportunity. Your annual report isn't a compliance document. It's the single richest piece of proof you have that your mission is real — and right now, it's probably the least visible thing on your site.

The PDF was never built for the web

PDFs were designed to be printed, not browsed. They're static, they're slow to load on mobile, they're invisible to search engines, and they ask a visitor to do something most won't: stop what they're doing, download a file, and read it linearly, front to back, like a shareholder in 1998.

Meanwhile, the people who actually matter to your organisation — a potential funder doing five minutes of due diligence, a customer deciding whether your B Corp status is more than a badge, a journalist looking for a quotable stat — aren't going to download anything. They're going to skim your homepage and decide in about eight seconds whether you're worth their time.

If your best evidence is locked inside a PDF, it never gets that eight seconds.

Your homepage is where trust gets decided

Think about what a homepage actually does. It's not a brochure — it's an argument. It's making the case, in real time, for why someone should believe you, support you, or buy from you. For a mission-driven organisation, the most persuasive material you own is your impact data: the carbon avoided, the workers paid a living wage, the funds directed to programs versus overhead, the year-over-year trend line that shows you're not just talking about change, you're measuring it.

That's not supporting material. That's the argument.

When you pull the headline numbers and stories out of the PDF and build them directly into your website — as a living, browsable "Impact" section rather than a downloadable artifact — you're putting your proof exactly where the decision gets made. Not in a folder someone forgets to open.

What this actually looks like

Moving your report to the homepage doesn't mean deleting the PDF — some funders and auditors will always want the formal document. It means treating the PDF as an export, not the source of truth. In practice:

• Lead with three or four numbers that matter, not forty. A homepage isn't a spreadsheet. Pick the metrics that actually prove your mission and let them breathe.
• Show trends, not snapshots. A single year's data is a claim. Three years of data, visualised simply, is evidence.
• Use real language, not report language. "We diverted 40,000kg of waste from landfill" lands harder on a webpage than "Waste diversion metrics improved year-on-year," even though a report might phrase it that way.
• Make it scannable, then let people go deeper. A strong summary on the homepage, with a clear path to the full report for those who want it, respects both the skimmer and the diligence-doer.
• Update it more than once a year. A page that's part of your site can be refreshed quarterly. A PDF, by nature, gets published once and goes stale.

The deeper shift

This isn't really a design tweak — it's a statement about what you think your impact data is for. A PDF report says: here is what we did, filed for the record. A homepage built around the same data says: here is what we're doing, and we're not afraid to show you in real time.

For organisations whose whole premise is that they operate differently — more transparently, more accountably, more in service of something beyond profit — that difference matters. Your website is the one place a stranger will actually look. Your annual report deserves to live there too.