For many leaders in not-for-profit organisations, justifying digital spend can feel like a recurring battle. You are asked to defend a budget line item to a board or a funder, and the default evidence offered is often a spike in page views or a rise in social media likes. But as we all know, a page view does not move a board motion, and a like does not fund a program.
This post is for leaders who need to turn their website from a perceived cost center into a source of evidence. We will explore a more rigorous way to prove impact by moving beyond vanity metrics and focusing on mission-shaped measures. You will learn how to identify and report on the specific measures that matter most. We will cover why page views fail to persuade, the language your board already governs by, and the key website metrics that map to mission outcomes. We will look specifically at how quickly people find services, donation completion rates, and the volume of volunteer and referral enquiries. Finally, we will outline how to set a baseline before a new build and report your findings in the plain, familiar language your board and funders will understand.
Why Page Views Do Not Move a Board Motion
Picture the board room. A slide with a large page-view number tells members nothing about whether someone in crisis found the right service, whether a donation was completed, or whether a volunteer signed up for a shift.
As a recommendation, not a published finding: page views measure attention, not mission, and attention is not what a board votes on.
The disconnect is structural. Page views rise whenever traffic rises for any reason: a media mention, a grant announcement, a viral post or automated bot traffic. None of it traces back to the website’s design, content or structure, so the number cannot defend the spend.
NFP leaders feel the consequence. When digital spend cannot be connected to outcomes, the website stays in the budget as a cost line, and cost lines get trimmed first when money tightens. The pattern spans not-for-profit organisations of every shape, from volunteer-run groups to large providers, so it is a reporting problem rather than a weak marketing team. It is also a question of ownership, which we explore in NFP website governance.
The fix is not more data. It is a smaller set of measures the board already has a reason to care about.
What Your Board Already Governs, and the Language It Uses
That smaller set only works if it fits the way your board already governs. Australian charities plan around the ACNC’s annual reporting cycle, including the 2026 Annual Information Statement hub, so website reporting should slot into that cadence rather than arrive mid-year as a surprise. The ACNC also publishes guidance on charities and administration costs; use that cost vocabulary when you discuss digital spend, rather than asking board members to learn analytics first.
Depth should match the organisation. Charity size as the ACNC defines it shapes what a board expects: a small not-for-profit organisation may need three numbers on one page, while a larger provider may want measures by program or service region. Funders and grant acquittals are a second audience, and measures tied to named programs tell a stronger reach and community benefit story than site-wide figures.
If new reporting rules apply to you, confirm the specifics with the ACNC or legislative sources before promising a new report. No regulator requires a page-view alternative, so argue the framework on mission grounds. A clear NFP website brief checklist helps you agree those measures before work starts, and the right custom web development partner can build tracking that supports them.
The Website Measures That Map to Mission Outcomes
The board paper needs a single test: a measure earns its place only if it answers a question the board already asks about mission, cost or risk. If it does not, it belongs in the internal dashboard, not the board pack.
Name the whole set up front so the board sees the framework at a glance:
- how quickly people find a service
- donation completion
- volunteer enquiries
- referral enquiries
- optionally, service page reach by program
Keep it to four or five measures at most, and repeat the same ones every reporting period so trends become visible and comparable. Translate each measure into plain language before it reaches the paper. No sessions, no bounce rate, no attribution windows, no funnel jargon.
This framework suits not for profit organisation websites built for service delivery and community benefit. It fits better than traffic reporting borrowed from retail or media, because it connects the site to what the organisation exists to do. The trade-off is less internal detail. Keep richer analytics behind the scenes for the team managing the site, and document the agreed measures in a clear brief: How to Write a Brand Brief That an Agency Can Actually Use explains why this protects budget.
How Quickly People Find the Service They Need
Take the first measure on that list: how quickly people find the service they need. In plain terms, it is the share of visitors who reach a service or program page from the homepage or site search in a small number of steps, and how long that journey takes.
For the board, the stakes are simple. Someone hunting for emergency accommodation, food relief or counselling loses patience in seconds, and that gap between searching and giving up sits far closer to mission than any traffic figure.
Measure it two ways: task success for a short list of real searches, and the number of clicks to each key service page. Site search terms add supporting evidence, because they show the words your community actually uses rather than the internal program names your organisation has grown used to.
Then run short task-based testing with clients, volunteers or frontline staff before launch, so the claim rests on behaviour rather than opinion. Clear information architecture and research are what lift this measure, and a structured UX design process is also how a redesign gets defended later in a funding or budget conversation.
Donation Completion, Not Traffic to the Donate Page
Findability answers whether people reach the right service. Donation completion answers whether they follow through, and it is calculated as donations completed as a share of donation journeys started. Traffic to the donate page counts intent, not outcome, so on its own it is a vanity number.
This is the closest website measure to revenue and to mission delivery, which makes it easy to defend in a room that thinks in dollars.
Track three things: form starts against completions, the step where people abandon most often, and mobile versus desktop completion, since community audiences are heavily mobile. Add a second line for recurring versus one-off giving, because monthly support is a sustainability signal that finance-minded board members read immediately.
Handle the awkward framing upfront. A large donation total can come from a single major gift and say nothing about whether the website works. Completion rate is the measure that reflects the site’s own contribution, and a better rate is a direct argument for delivering more with the same spend, sitting alongside the overhead conversation every board already has through the ACNC’s administration costs guidance.
Report it beside what changed on the site, from UX research before any build through to donation form changes, rather than claiming the website caused the shift.
Volunteer and Referral Enquiries
Donation completion proves the site can turn intent into revenue. Volunteer and referral enquiries prove it can turn intent into people and service pathways.
Track two measures: volunteer enquiry forms or applications submitted through the website, and referrals received through the site from partner organisations such as GPs, schools, hospitals, councils or other agencies.
Referrals deserve a place in the board pack because they arrive pre-qualified, often from organisations the funder already trusts. That makes them strong evidence of reputation and functioning service pathways.
Count form completions, but pair them with a quality check: did the enquiry become a volunteer shift or a service intake? For example, a hypothetical volunteer coordinator might find that of 40 applications, 12 were rostered. Form numbers alone will be questioned, and rightly so. A simple follow-through loop with the volunteer coordinator or intake team lets website enquiries be matched to placements and referrals over time.
This is efficient because volunteer capacity and referral pathways are commonly reported to funders and in grant acquittals. Website evidence plugs straight into reporting you already do.
Watch seasonality. Volunteering interest spikes around end-of-year and campaign periods for many not-for-profit organisations, so report a raw monthly figure with that context, never without it.
Setting a Baseline Before the Build Starts
Capture your volunteer and referral enquiry numbers before any redesign touches those forms. The same timing rule applies across the whole framework, and it is not negotiable: set the baseline before any build or redesign work begins. Once a new site launches, the old one’s behaviour cannot be reconstructed, and the comparison is lost.
Choose the four or five measures from the framework and record them over a defined window, long enough to include normal variation rather than a single quiet week. Agree the measures with whoever writes the board report, confirm that analytics and form tracking are actually firing, and record the numbers in one shared sheet with dates attached. If your project involves choosing between platforms or form tools, a framework for weighing custom against off-the-shelf options helps you flag comparability risks early.
Watch the comparability trap. If a form is replaced, a service is renamed or a donation platform changes mid-project, the before and after numbers stop being comparable. Note the change and adjust the claim. Record context beside every number, including campaigns, seasonality, staffing changes or a service closure, so the post-launch story is honest rather than flattering.
When there is no usable history, use a pilot, a soft launch or a small cohort of users as the baseline, and say so clearly in the report. Document the baseline in writing and share it with the board chair or finance lead before launch, so the comparison is agreed in advance and cannot be reframed afterwards.
Reporting It in the Board’s Own Language
From Cost Line to Evidence: What to Do Next
Once the report is in the board pack, the remaining step is discipline. Page views cannot move a motion because they describe attention, not mission. Mission-shaped measures can, because they describe what the organisation exists to do.
Pick four or five measures tied to services, donations, volunteers and referrals, then drop everything else from the board pack. Set the baseline before any build work begins, write it down, and share it with the board chair so the comparison is agreed in advance. Report the same measures in the same plain format, inside the board’s own calendar, and pair each one with a next step.
For a not-for-profit organisation, this is how a website stops being a recurring cost line. It becomes evidence that the organisation is delivering, which is exactly what boards and funders need to see.
الخاتمة
Proving website impact to a board starts with picking the right measures. Page views describe attention; service findability, donation completion, volunteer and referral enquiries describe mission. Four or five measures are enough for a board pack, and the rest can wait.
The second takeaway is timing. Set the baseline before any build work begins, write it down, and agree it with your board chair or finance lead so the comparison cannot be reframed later. Record context beside every number so the post-launch story stays honest.
Report in the board’s own language and calendar, pairing each measure with a next step.
Your next step: book a short baseline session before your next website project starts, and bring your four or five measures with you. Do that once, and your website stops being a cost line and starts being evidence of delivery.
