UK Decline converts public releases into static pages, cached data snapshots, calculators and local tools. This page explains the method behind those pages and the limits of the figures.
Source hierarchy
The site gives priority to official statistics, government registers and named public datasets. The preferred source is the original publisher, not a media report about the release. Where the original data is a spreadsheet, CSV, API, statistical bulletin or public register, UK Decline should link or label that source near the relevant figure.
ONS, OBR, Bank of England, Insolvency Service and HM Treasury datasets are used for debt, borrowing, inflation, GDP, wages, insolvencies and fiscal forecasts.
DWP Stat-Xplore, OBR welfare forecasts, NHS England statistics and related official releases are used for benefit, disability and health-pressure pages.
Home Office, Police.uk, Companies House, local-authority and public-register data support asylum, crime, business-stress and local-area tools.
Cached snapshots
Most pages are built from cached snapshots rather than calling every upstream source while a visitor is browsing. This keeps pages fast and avoids presenting a broken upstream API as if it were a change in the underlying statistic.
A snapshot is a local copy of the relevant public data plus metadata such as source name, publication period, refresh time and status. When a data refresh fails validation, the page should either keep using the last valid snapshot with a clear freshness label or fail closed rather than inventing a fallback value.
Refresh cadence depends on the source. Daily or faster sources can update more frequently. Weekly, monthly, quarterly and annual releases update when the official publisher provides new data and the snapshot checks pass.
Calculations and estimates
Some pages show direct official values. Others show calculations derived from official values. Examples include per-second counters, salary-equivalent comparisons, local rankings, period changes and share-of-total figures.
- Per-second counters divide a published annual or forecast total across the relevant year.
- Local rankings compare places only within the available dataset and should not be read as street-level proof.
- Calculator outputs use the rates, bands and assumptions stated on the relevant page.
- Live estimates should be labelled as estimates and tied back to a named official baseline.
Calculated values are useful for context, but they do not replace the official source period. The source period matters because UK public datasets often update monthly, quarterly or annually rather than in real time.
Local lookup and maps
Local tools use public geography, postcode, local-authority or nearby-service matches to return area-level signals. A postcode can identify a local authority, NHS trust, police area or nearby public-service context, but that does not make every statistic address-specific.
Map points and choropleths should be read according to their source granularity. A council-level asylum figure is not a hotel address. A registered-office postcode district is not necessarily a trading location. A crime or health-area signal is a public-area indicator, not a claim about an individual household.
AI assistance
AI helps with engineering, research organisation, parsing public releases, writing tests and drafting page copy. It is not used as an authority for figures. A statistic should come from a named source, a checked snapshot, a documented calculation or a public record that a reader can inspect.
This distinction matters. AI can help build the machinery, but it cannot substitute for source receipts, caveats and validation checks.
Corrections and review
Corrections are welcome. The fastest useful report includes the page URL, the exact value or claim, the source link you are comparing it with and the corrected wording or figure if known.
Email contact@ukdecline.co.uk. Factual corrections are prioritised over feature requests because the site’s value depends on traceable figures and clear caveats.
Send a correction