Editorial & Corrections Policy

How Pages Are Produced

PlainCouncilTax's data pages are generated from the national Band D tables and the separate VOA stock release described in our methodology. We load source values into a structured database and render the pages and downloads from that database. Published rates and stock counts retain their source meaning; band schedules, ranks, means, spreads, changes, and weighted charges are calculations and are labeled as such.

This is a data-publishing model: the same template renders many pages so that every record is covered consistently. We are transparent that these data pages are produced programmatically from the source records rather than written individually. The editorial work goes into the pipeline, how data is sourced, normalized, deduplicated, and presented, into the methodology, and into the written guides.

Sourcing Standards

• Primary sources only. Published inputs come from MHCLG, the Scottish Government, Welsh Government / StatsWales, the VOA, or the statutory band framework, not third-party aggregators.
• Attribution in context. Pages name the source and link to it where applicable, and show the date the data reflects.
• Derived values are labeled. Numbers we compute ourselves, rankings, trends, ratios, are presented as our analysis of the source data, distinct from the publisher's own figures.
• No invented data. Where a field is unavailable for a record, the page says so rather than filling the gap with an estimate.

Update Cadence

Band D rates are reviewed against the national annual releases for each financial year. The VOA stock layer is refreshed on its own annual release cycle. Relevant pages identify the financial year or source vintage; an editorial page-review date is not presented as a data refresh.

Corrections Process

If a record on PlainCouncilTax looks wrong, please tell us. Because our pages are generated from the source datasets, a genuine error almost always traces back to either the source data or our processing of it, so this is how we handle a report:

1. Report. Use the contact page with the page URL and the value that looks off.
2. Verify. We compare the record against the published source.
3. Fix at the source. If the value is wrong on our side, we correct it in the database and pipeline that generate the page, not just on the single page, so every affected page is fixed at once. If the record faithfully reflects the published data, we explain that and point to the primary source.
4. Log it. Material corrections are added to the public changelog with the affected surface and date; routine source-release refreshes are also recorded there.

We aim to acknowledge data-error reports within a few business days.

View the public data and methodology changelog. Entries describe real shipped changes only; an empty period is not backfilled with invented activity.

Editorial Independence

PlainCouncilTax is an independent publisher and is not affiliated with the agencies or organizations that publish the underlying data. We do not accept payment, sponsorship, or promoted placement from any covered entity. If contextual advertising appears, advertisers do not influence what we cover or how we present it.

Appropriate Use

PlainCouncilTax is for informational purposes only and does not constitute financial, tax, investment, or other professional advice. Details can change after we ingest a record. For any important decision, confirm the current information with the primary source or a qualified professional (such as a licensed accountant or financial adviser). See our full disclaimer.