Keeping constraint data current over a long project
Constraint evidence expires quietly over a multi-year programme. The datasets that change, the review points that catch them, and what to do when a designation lands mid-application.
Constraint evidence has a shelf life, and on a three year programme it expires quietly. The flood map you downloaded at option stage has been reissued, a tree in the corner of the site has been made the subject of a preservation order, the council has adopted a new local plan, and your policy compliance table still refers to the old one. None of that generates an email. It surfaces when a case officer asks a question you cannot answer.
The fix is procedural rather than technical. Decide which datasets you will re-check, at which points in the programme, and who owns each one. Then keep the dated downloads so you can prove what the position was when you designed the scheme.
Which datasets change and how often
Frequency varies enormously, and the useful distinction is between datasets with a publication rhythm and datasets that change on an event.
| Dataset | Pattern of change | Practical consequence |
|---|---|---|
| Flood zones and flood mapping | Reissued periodically by the Environment Agency | A zone boundary can move across part of a site |
| National heritage list entries | New listings and amendments at any time | A neighbouring building can become listed mid-application |
| Conservation area boundaries | Designated or extended by the council at any time | Permitted development rights and design policy change |
| Article 4 directions | Made by the council after consultation | A route you relied on can close |
| Tree preservation orders | Often made in response to an application | Immediate effect from a provisional order |
| Local plan and policies map | On adoption, after examination | The whole policy basis of your statement shifts |
| Housing land supply and delivery figures | Annual | The weight of policy arguments changes |
| Biodiversity metric version | On release of a new version | Baseline calculations may need redoing |
| Charging schedules and fees | Indexed annually | Liability changes between permission and the start of work |
The event-driven items are the dangerous ones, because nothing tells you they have happened. A provisional tree preservation order takes effect from service, and if it lands on the tree your layout was going to remove, the scheme changes.
Setting a review point in the programme
Put the reviews in the programme as tasks with dates, not as a standing intention. Five points cover most schemes:
- After the option appraisal, when the scheme starts to commit money to design
- Six to eight weeks before submission, when there is still time to act on a change
- At validation, as a light check that nothing moved during the pack assembly
- Before determination, or before committee where the scheme is going to one
- Before implementation, particularly for levy liability, conditions and survey validity
For a phased scheme, add a review before each reserved matters or discharge submission. Phase four of a masterplan can be six years from the original evidence base, and reviewers rarely believe a data table with no date on it.
What to re-check before submission
This is the substantive check, and it should have a named owner and a written output. Cover the designations that drive the document schedule and the policy position that drives the argument.
- Flood zone and surface water mapping, and the council's strategic flood risk assessment if it has been updated
- Heritage designations within the study area, including new listings and boundary amendments
- Conservation area and article 4 direction status for the site and its immediate context
- Tree preservation orders, checked with the council rather than a web viewer alone
- Ecological designations, habitat inventories and any new impact risk zone
- Development plan status, including any plan adopted or withdrawn since the appraisal
- Survey validity dates, since ecology and traffic data age faster than most people assume
Write the output as a short note in the project file recording what was checked, on what date, and whether anything changed. That note is what you send the case officer later if the point is raised. Our note on downloading the biodiversity metric and version control covers the version question for that particular calculation, and finding housing land supply and delivery test figures deals with the annual numbers.
What to re-check before determination
Narrower, and focused on what would change the decision. The application is determined on the policy and designations in force at the date of the decision, so a change during determination matters even if your submission was correct when made.
Check plan adoption, any new designation affecting the site, and any material change in national policy. Then check whether your own documents still say the right thing. A flood risk assessment referring to a superseded climate change allowance is a straightforward point for a consultee to raise, and the answer is an addendum rather than an argument.
Where the scheme is going to committee, do this before the report is drafted rather than after. Officers dislike late corrections, and a change discovered by an objector reads worse than the same change reported by you.
Recording a change that affects the scheme
Keep it short and factual. A technical note to the case officer identifying the change, the source and date, its effect on the submitted documents, and what you propose to do about it.
The three usual outcomes are that nothing changes, that an existing document needs an addendum, or that a new document is needed. A new heritage designation nearby may bring a Heritage Statement into scope where none was required. A revised flood zone may require the Flood Risk Assessment to be reworked with a sequential approach to layout.
Resist the instinct to say nothing and hope determination arrives first. If the change is material and comes out later, the permission is weaker for it.
Datasets that are updated without notice
Several of the layers you rely on change silently. Treat them accordingly.
Keep the raw download, not just the extracted polygon, with the download date in the filename. Where a publisher offers a change notification or a version history, use it. Where none exists, the only defence is the dated snapshot plus a scheduled re-check.
Highway network data is worth a specific mention, because the status of a route and the interest of the strategic network operator can both change, as covered in our note on whether the strategic road network is engaged.
Handling a designation made mid-application
Three situations come up repeatedly.
A tree preservation order served during determination applies from service, so any removal shown on your layout now requires consent. Amend the layout or make the case for consent, and do it as a drawing revision rather than leaving the inconsistency in the pack.
A new conservation area or an article 4 direction changes the policy framework and may remove a permitted development fallback you were relying on in the planning balance. If your case depended on that fallback, the case has to be rebuilt.
An adopted local plan replaces the policies your statement cites. The efficient response is a short policy addendum mapping old policies to new ones, with the assessment unchanged where the tests are the same and expanded where they are not.
As an illustrative example, a 60 unit scheme submitted in the spring, determined the following February, sits across a period in which the council adopted a new local plan, declared an air quality management area two streets away and made a tree preservation order on a boundary oak. All three were discoverable. None generated a notification. The project that had a February review point caught all three; the project that checked once at submission caught none.
Where a change brings new documents into scope, the 66 report types by category is the quickest way to see what the scheme now needs.
This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.
Frequently asked questions
Which constraint datasets change most often?
Event-driven ones are the risk: tree preservation orders, new listings, conservation area designations and article 4 directions can all happen without notice to an applicant. Datasets with a publication rhythm, such as flood mapping, housing land supply figures, metric versions and indexed charging schedules, are easier to diary because their timing is broadly predictable.
When should constraints be re-checked?
Set review points at the end of option appraisal, six to eight weeks before submission, at validation, before determination or committee, and before implementation. Phased schemes need an additional review before each reserved matters or condition discharge submission, because later phases can be years from the original evidence base.
Does a designation made after submission affect my application?
Yes. The application is determined on the policy and designations in force at the date of the decision, not the date of submission. A tree preservation order served during determination applies from service, and a newly adopted local plan replaces the policies your statement cites, which usually calls for a short policy addendum.
How should a change be reported to the case officer?
Send a short technical note identifying the change, its source and date, the effect on the submitted documents and what you propose to do. The usual outcomes are no change, an addendum to an existing document, or a new document. Reporting it yourself reads better than an objector finding it first.
How long do survey results stay valid?
It varies by discipline and by council, and the honest answer is to check with the local planning authority. Ecological survey data and traffic counts age faster than people expect, and a consultee may ask for an update where the data predates the submission by a long interval. Record survey dates in the constraints register.
Sources and further reading
This article is general guidance about the planning system in England and, where stated, the rest of the UK. It is not legal or professional advice. Check your local planning authority’s validation requirements and take professional advice for your specific site.