Content Governance for Nonprofit Websites: Who Publishes, Who Approves, What Expires | Socialectric

The most common request a Communications Director receives is some version of "can you just add this to the website?" A programme update. A new staff bio. A campaign page. A PDF that needs to be downloadable. A news story the Executive Director saw and wants referenced. Each request takes ten minutes. None of them come with a plan for when the content should be reviewed, updated, or removed.

After three years of this, the website has 200 pages. Half of them describe activities that have ended, staff who have left, or campaigns that finished two funding cycles ago. Nobody knows what is current and what is not, because nobody was ever asked to check. The Communications Director knows the site is a mess but has no framework for prioritising what to fix, no authority to remove content without political consequences, and no documented process to prevent the same accumulation from happening again.

This is the content governance problem. It is not about writing better content. It is about having a system for managing what exists.

Why content accumulates and never gets removed

Adding content to a website is easy and politically safe. Removing content is difficult and politically dangerous. Every page on the site was put there by someone who thought it mattered. Removing it means telling that person, or their successor, that it no longer does.

Without a governance framework, removal feels like a judgment call rather than a process. So nothing gets removed. The site grows in one direction only. Pages that were relevant in 2019 sit alongside current content. Blog posts from a previous Executive Director's tenure remain published. Events from last year are still findable through search. The cumulative effect is a site that communicates institutional disorganisation to anyone paying close enough attention, and institutional funders always pay close enough attention.

The fix is not a one-time cleanup. Cleanups address symptoms. The fix is a content governance framework that prevents accumulation in the first place.

What content governance looks like in practice

Content governance answers three questions on an ongoing basis: what gets published, who approves it, and when does it expire?

The first question requires a publishing process. Not every piece of content needs the same level of approval. A blog post might need sign-off from the Communications Director alone. A new programme page might need input from the programme lead and approval from the Executive Director. A page that makes claims about impact or quotes a beneficiary might need legal or safeguarding review. The point is not to bureaucratise publishing. It is to ensure that the level of scrutiny matches the level of institutional risk.

The second question requires documented authority. The Communications Director needs the formal authority to approve, delay, or decline publishing requests based on agreed priorities. Without that authority documented in a website governance policy, every decision is a negotiation. The fundraising team wants the homepage to lead with a donation appeal. Programmes wants it to lead with a new initiative. The Executive Director wants it to feature a Board announcement. Without clear ownership, the loudest voice wins, and the homepage changes every time someone senior walks past the Communications Director's desk.

The third question is the one most organisations never ask. When does this content expire? Setting a review date at the point of publication changes the entire dynamic. It means content is no longer permanent by default. It means someone is responsible for checking whether a page is still accurate six months from now. It means the Communications Director has a governance reason to contact programme teams about their pages, rather than chasing people for updates they never volunteered to do.

The review cycle that actually works

The most practical approach I have seen is a tiered review cycle based on content type and institutional risk.

The homepage and primary landing pages should be reviewed before every major campaign or organisational change, and at minimum quarterly. These pages are what funders see first. If the homepage still references last year's annual report or a campaign that ended in March, that is a credibility problem that compounds with every day it remains live.

Programme and service pages should be reviewed quarterly. Programmes evolve faster than websites. Eligibility criteria change. Locations change. Staff responsible for delivery change. A quarterly review with the relevant programme lead ensures the website reflects current reality, not the reality described in a brief written eighteen months ago.

Governance documents should be reviewed annually, immediately after the new annual report and accounts are published. This includes trustee information, policies, financial summaries, and regulatory disclosures. Charity Commission requirements specify that certain information must be publicly available. An annual review ensures the website meets those obligations with current data.

Blog posts and news items should have a visible publication date and should be reviewed when they reach twelve months old. Not every old post needs to be removed. But posts making time-sensitive claims, referencing specific data, or describing current activities need to be checked for accuracy. A post titled "Our Plans for 2024" that is still live in 2026 tells visitors the site is not maintained.

Anything that refers to a specific event, campaign, or time-limited activity should have an expiry date set at the point of publication. When the event passes, the content is either archived, redirected, or removed. Not left to accumulate.

How to handle the "just add it to the website" requests

This is the daily reality. The solution is not to say no to everything. It is to have a framework that makes each request assessable rather than arbitrary.

When someone requests new content, three questions should be answered before it is published. First: which of our primary stakeholders does this serve? If the answer is "none of the top three," it may still be worth publishing, but it is lower priority. Second: who is responsible for keeping this content current after it goes live? If nobody can be named, the content has no owner, and unowned content becomes stale content. Third: when should this be reviewed or removed? Setting a date at creation prevents the accumulation problem entirely.

These three questions take thirty seconds to answer and they transform the publishing process from reactive ("someone asked, so I did it") to governed ("this content serves a defined stakeholder, has an owner, and has a review date").

Content governance is not content strategy

Content strategy is about what to create. Content governance is about what happens after it is created. Most nonprofit websites have been through some version of content strategy: someone decided what pages and sections the site should have, and content was written to fill them. Very few have content governance: a system for maintaining, reviewing, and retiring that content over time.

The distinction matters because a content strategy without content governance produces the exact situation most nonprofits find themselves in. A well-planned site that deteriorated over two to three years because nobody was responsible for maintaining it. The strategy was sound. The governance was absent. The result is a site that needs another strategy exercise, when what it actually needs is an operational framework for ongoing management.

Question 1: How do I get internal buy-in for a content review cycle?

Frame it as risk reduction, not extra work. Show the Executive Director three specific examples of outdated content on the live site and explain what each one signals to a funder or regulator. Outdated governance documents, lapsed programme descriptions, and stale team pages are not administrative oversights. They are governance failures with reputational consequences. Once leadership sees the risk, the review cycle becomes a risk mitigation measure rather than an administrative burden.

Question 2: What should I do with old blog posts?

Do not delete them by default. Assess each one against three criteria: is it still accurate, is it still findable through search, and does it reflect well on the organisation? Posts that are accurate and still generating traffic should stay. Posts with outdated information should be updated or redirected. Posts that no longer reflect the organisation's current work should be archived or removed with a 301 redirect to a relevant current page.

Question 3: Is a spreadsheet enough to manage content governance, or do I need a tool?

A spreadsheet is enough. Most nonprofits do not need a content management tool beyond their CMS and a shared document listing every page, its owner, its last review date, and its next review date. The value is in the process, not the tool. If a spreadsheet is maintained and acted on, it is more effective than an expensive platform that nobody logs into.

If your organisation has never audited its content or formalised how the website is managed, a Blueprint Audit includes a content assessment and produces governance recommendations your team can implement immediately.