Where each fact comes from
Every fact on a park page has a numbered source and the date we last looked at it. The sources are public records and the park's own published material.
| Fact | Source | How we check it | How often |
|---|---|---|---|
| Season and months open | Council caravan site licence register | Read from the licence conditions, or from the council's reply to a freedom of information request | Yearly, and when a park reports a change |
| Flood zone | Environment Agency flood map for planning | The park boundary from OpenStreetMap is laid over the flood zones. If any pitch is in a higher zone, the page says which part | Yearly |
| Coastal erosion | National Coastal Erosion Risk Map | The park boundary is compared with the 2055 and 2105 erosion lines | Yearly |
| Operator | Companies House and The Gazette | Status, accounts due dates, charges and insolvency notices are read from the register. Exact matches are published automatically | Monthly |
| Site fee, age policy, commission | The park's own website, price list or licence terms | The data refresher bot proposes a change with the page it found it on. The admin reads the page before publishing | Monthly |
| Owner-reported figures | Structured owner reports | See below | As reports arrive |
Bots propose, the admin publishes
Two automated helpers run on a schedule. The data refresher browses park websites and public sources each month and proposes changes, each with the page it found the value on. The submission moderator reads owner reports and flags any that are out of line with the others. Neither can publish. Every proposed change waits in a queue until the admin publishes or rejects it, and every decision is written to an audit log with who, what, source and when. The one exception is an exact match that the server confirms itself against an official source such as Companies House, which is published automatically and logged as such. Council licence registers are always read by the admin.
Text that a bot reads from a web page is treated as untrusted. It is shown to the admin as plain text, never as a web page, and nothing in it can change what the bots do.
How owner reports are moderated
Owners can report their site fee, past fees by year, the age policy, the commission rate and the months they can stay. The form has no free text and no uploads.
- Each report is checked against the park's published figures and against other reports for the same park.
- A report that is more than 15% away from the others, or from a published figure, is flagged for a closer look.
- The admin publishes a figure only once at least one report agrees with a published figure or two reports agree with each other.
- Published owner-reported figures always say so, with the number of reports and the date of the latest.
The risk key
Every mark is a shape, a word and a colour together, so it reads the same in print, in greyscale and with a screen reader. There are four levels and no more. The plate on each park page always shows the same four marks in the same order.
| Mark | Coastal erosion | Flood | Operator | Age policy |
|---|---|---|---|---|
| High | Part of the site is inside the 2055 erosion line | Flood Zone 3 | An insolvency or strike-off notice, or the company is dissolved | Not used |
| Check | Part of the site is inside the 2105 line but outside the 2055 line | Flood Zone 2 | Overdue accounts or charges registered against the company | The park publishes an age limit. Ask when it bites |
| Low | The whole site is outside the 2105 line | Flood Zone 1 | Active, accounts on time, no notices, no charges | The park publishes that there is no age limit |
| Not published | We have not checked the map yet | We have not checked the map yet | Not used | The park does not publish an age policy |
Corrections
Anyone can report a correction, including the park.