Skip to main content

How to Meet the Transparency Code on Your Council Website

Which transparency code applies to your council by size, what each one says the website must publish and when, plus the accessibility duty. A clerk's checklist.

Category Operational
Read Time 10 min read
Updated October 2026
Steps 6 steps

Who This Guide Is For

This guide is for the clerk, RFO or councillor at a town or parish council in England who has to answer one question before the next annual review: does our website publish everything it should? It sits with our other operational guides. The answer depends on the size of the council, because two different transparency codes and two sets of audit regulations apply at different turnovers, and the accessibility rules sit on top of all of them. By the end you will know which rules apply to your council, what each one expects to see online and by when, and how to check your own site against them.

Everything here is taken from the codes and regulations as published on GOV.UK and legislation.gov.uk, checked in October 2026. Wales and Scotland have their own arrangements, so this guide covers English councils only. If you want a quick automated look at your site first, our free council website check reads your homepage and a few linked pages and lists what it could find.

Before You Start

You need two numbers from last year’s annual governance and accountability return (AGAR): gross income and gross expenditure. Turnover, for every rule below, means whichever of the two is higher. Have the URL of your website to hand, and the login for whoever edits it. If nobody on the council can edit the site any more, sort that out first, because none of the steps below can be done without it. Our guide on taking over a website from a previous developer covers getting the domain and logins back.

Step 1: Work Out Which Band Your Council Is In

There are three bands that matter for the website.

Turnover Transparency code that applies
£25,000 or less Transparency Code for Smaller Authorities
Over £25,000 to £200,000 None required by law
Over £200,000 Local Government Transparency Code 2015

The Accounts and Audit Regulations 2015 apply in every band, with a lighter version for councils at £25,000 or less (Step 3).

The smaller-authorities code was issued on 17 December 2014. The code itself calls its contents “recommended practice”, which is why some clerks treat it as optional, but the Smaller Authorities (Transparency Requirements) (England) Regulations 2015 have required those councils to publish the information it specifies since 1 April 2015. The 2015 code for larger bodies names parish councils with gross annual income or expenditure above £200,000 alongside the principal councils.

A council near a boundary should check each year. A one-off grant or a capital project can push turnover over £25,000 for a single year, and that changes which rules apply for that year’s publication.

Step 2: Councils at £25,000 or Less, Publish the Code’s Items by 1 July

The smaller-authorities code asks for the following, each year, by 1 July after the end of the financial year:

  • Every item of expenditure over £100, with the date, a summary of what it was for and the amount, plus any VAT that can’t be recovered. Measure the £100 net of recoverable VAT where you can.
  • The end-of-year accounts in the annual return format, with the bank reconciliation and explanations of significant variances.
  • The annual governance statement and the internal audit report, both in the annual return format.
  • A list of councillors with their committee memberships and any outside bodies they represent the council on.
  • The land and building assets the council owns or looks after, with location, acquisition date, cost or a proxy value, and what each is used for now.

Two items run all year rather than once: draft minutes of formal meetings within one month of the meeting, and agendas and papers at least three clear days before it.

The code lets you publish on your own website or on your billing authority’s. If the district council hosts your documents, link to them from your own site anyway. A resident looking for last year’s payments starts at the parish council’s homepage, and so does any checker.

Here is what a compliant expenditure page can look like in practice: a page called “Payments over £100” with one table per financial year, each row holding the date, payee, what it was for, the net amount and any irrecoverable VAT. A scanned PDF of the cashbook signed at a meeting is legal, but it’s much harder for anyone to read and for a screen reader to use, which matters in Step 5.

Step 3: Every Council, Publish the Audit Documents on the Website

The Accounts and Audit Regulations 2015 put duties on every council, whatever its turnover, and several of them name the website directly: publication “must include publication on the authority’s website”.

  • The public rights period. The accounts are open for inspection for a set period, which must include the first ten working days of July. When it starts, publish the unaudited accounts, the annual governance statement and a notice saying when the period runs, how to arrange an inspection and who the external auditor is. If the timing slips, the regulations ask for a notice on the website explaining why.
  • After the audit (councils over £25,000). Publish the accounts with the auditor’s certificate or opinion, plus the approved annual governance statement, no later than 30 September. Then publish a notice that the audit has concluded, with the details of how electors can inspect the documents.
  • Exempt councils (£25,000 or less). Exemption isn’t automatic. Under regulation 9 of the Local Audit (Smaller Authorities) Regulations 2015, a council at or under £25,000 (and past its first three years) can certify itself exempt for the year, and it then has to publish a notice on its website saying so and explaining what that means for the audit. An exempt council skips the 30 September step, and must keep the accounts it published for the public rights period on the website for five years.

Every council has to keep these documents available for at least five years. In practice that means one page per year, never overwritten. A common slip is replacing last year’s AGAR with this year’s at the same address, which removes the earlier year from public view.

Step 4: Councils Over £200,000, Add the 2015 Code’s Data

A council over £200,000 has a longer list under the Local Government Transparency Code 2015. Quarterly, within a month of the quarter ending:

  • every item of expenditure over £500
  • every Government Procurement Card transaction, with no threshold
  • invitations to tender and contracts over £5,000

Annually, within a month of the year ending, the code lists land, grants to voluntary and community organisations, an organisation chart of the top three levels of staff, trade union facility time, the parking account and spaces where you run parking, senior salaries, the constitution, the pay multiple and fraud data. Many of these won’t apply to a parish council (few run car parks or employ senior staff above the code’s salary threshold). Note which ones don’t and say so on the page, so a reader knows the gap is deliberate.

The 2015 code also asks for this data in open, machine-readable formats under an open licence. A spreadsheet saved as CSV meets that. A photographed page of the payments book doesn’t.

Step 5: Check the Accessibility Statement, Whatever Your Size

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 apply to “regional or local authorities”. A town or parish council is a local authority, and the regulations have no exemption for small councils, so a £5,000-a-year parish council is covered in the same way as a county.

GOV.UK’s guidance, last updated on 30 September 2024, asks public sector sites to meet WCAG 2.2 at level AA and to publish an accessibility statement on the site. The statement explains how accessible the site is, what doesn’t work and why, how to report a problem or ask for a document in another format, and any part of the site you’re claiming is a disproportionate burden. Claiming that burden needs a written assessment, and lack of time or knowledge doesn’t count.

Some content is outside the regulations: office documents such as PDFs published before 23 September 2018 (unless people still need them to use a service), pre-recorded video from before 23 September 2020, and content that qualifies as an archive. Your minutes from 2016 can stay as they are. This year’s payments PDF and agendas can’t.

To check your own statement, open it and look for three things. First, the standard it names: a statement written in 2019 or 2020 will usually say WCAG 2.1, which is worth updating when you next review it. Second, the date it was last reviewed. Third, a working contact for accessibility problems. If you don’t have a statement at all, GOV.UK publishes a sample accessibility statement you can adapt. For a deeper audit than a statement review, our accessibility testing page explains what automated tools catch and what needs a person.

Step 6: Make Every Item Findable From the Homepage

Publishing a document deep in a folder structure meets the letter of the codes, but a resident or auditor has to be able to find it. Aim for every item in Steps 2 to 4 to be no more than two clicks from the homepage, under link text a resident would recognise: “Transparency”, “Finance”, “Payments over £100”, “Annual return 2025/26”, “Meetings”.

A good test is to hand your homepage to someone who has never seen it and ask them to find last year’s internal audit report. If they open three menus and give up, the item needs a better link. Our council website check follows links the same way and reports what it couldn’t reach, which makes it a quick way to see the site as an outsider does.

The Checklist by Council Size

Tick off the list for your band. Every council also does the “All councils” list.

All councils:

  • Accessibility statement on the site, naming WCAG 2.2 AA, reviewed this year, with a working contact
  • Public rights notice, unaudited accounts and annual governance statement up when the inspection period starts
  • Each year’s audit documents kept online for five years
  • Every item no more than two clicks from the homepage

£25,000 or less (Transparency Code for Smaller Authorities):

  • Payments over £100 for last year, by 1 July
  • Accounts, annual governance statement and internal audit report in the annual return format, by 1 July
  • Councillor list with responsibilities, and the land and buildings list
  • Draft minutes within a month of each meeting, agendas three clear days before
  • If you’ve certified the council exempt, the exemption notice

Over £25,000 to £200,000:

  • Audited accounts and annual governance statement by 30 September
  • Notice of the conclusion of the audit

Over £200,000 (Local Government Transparency Code 2015), on top of the band above:

  • Payments over £500, card transactions, tenders and contracts over £5,000, each quarter within a month
  • The annual items that apply to you, within a month of the year end, with a note on the ones that don’t
  • Data in an open format such as CSV

Common Mistakes

  • Treating the smaller-authorities code as optional because the code itself calls its contents “recommended practice”. The 2015 regulations made it a requirement.
  • Overwriting last year’s AGAR, payments list or audit notice with this year’s, when each must stay up for five years.
  • Publishing payments, minutes and agendas only as scanned images inside PDFs. They count as published, but they fail the accessibility rules for anything put up after September 2018.
  • An accessibility statement from 2019 that names WCAG 2.1, lists issues the site no longer has and gives a former clerk’s email address for problems.
  • Relying on the billing authority’s website without any link from the council’s own homepage.
  • Forgetting the public rights notice in June, so the inspection period starts with nothing on the website to tell electors about it.

What Good Looks Like

A resident lands on the homepage and finds a “Transparency” or “Finance” link in the main menu. Behind it is one page per financial year holding the payments list, the accounts, the annual governance statement, the internal audit report and the audit notices, with five years kept. The councillor list and asset register are current. This year’s agendas went up three clear days before each meeting, and the draft minutes within a month. The accessibility statement names WCAG 2.2 AA, was reviewed this year and has a contact address that someone reads. Nothing on the list is more than two clicks from the homepage.

Next Steps

Run your site through the free council website check and treat anything it can’t find as a prompt to look. If the site is hard to edit, slow on a phone, or held by someone you can no longer reach, that’s the point to think about a replacement. Our website service explains how we build and host small sites, and a council site we build can carry its transparency section laid out the way this guide describes.

Written by

Alex

CEO

I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.