Briefing a drafting tool with your site constraints
A document drafted from thin inputs looks finished and says nothing specific. What to establish first, and the six checks to run on any draft that comes back.
The quality of a drafted planning document is set before any drafting happens. Brief ai tool site constraints badly and you get a document that cites the wrong policies against a site description that does not match your drawings, which is worse than a blank page because it looks finished. Brief it properly and you get a first draft that addresses the tests a case officer will actually apply.
The work is the same work you would do for a junior colleague writing their first Planning Statement. Establish what the site is, what is proposed, and what constrains it.
The constraints worth establishing first
Some constraints change which reports are needed. Others change the policy tests. Both need settling before drafting.
The ones that change the report list are flood zone, surface water flow paths, listed building status including curtilage, conservation area, Tree Preservation Orders, protected sites for nature conservation, ancient woodland, Air Quality Management Areas, contaminated land history and coal mining legacy. The ones that change the policy tests are Green Belt, National Landscape or National Park, settlement boundary position, site allocation, neighbourhood plan area and any Article 4 direction.
Then there are the thresholds. Site area in hectares, gross internal floorspace, unit numbers, parking spaces and building height all trigger requirements at fixed points, and a scheme sitting just below one is a different submission from one sitting just above.
PlanScope checks a site automatically against Environment Agency flood data, Historic England listed buildings and conservation areas, and Natural England protected site layers, and feeds the results into a rule-based engine that suggests which of the 66 report types the project is likely to need. That covers the common constraints, and it does not cover everything, which is why the manual checks below still matter.
Where each dataset actually lives
Work from the primary source rather than a summary, and record where each answer came from.
| Constraint | Primary source |
|---|---|
| Flood zones for planning | Environment Agency Flood Map for Planning |
| Surface water and reservoir risk | The long term flood risk service |
| Listed buildings and scheduled monuments | The National Heritage List for England |
| Protected sites, priority habitats, ancient woodland | The MAGIC map |
| Conservation areas, article 4 directions, allocations | The council's own mapping and planning.data.gov.uk |
| Air Quality Management Areas | The council's annual status report and Defra data |
| Tree Preservation Orders | The council's TPO register |
Two of these are frequently got wrong. Conservation area boundaries are published by councils and the national dataset coverage varies by authority, so check the council map for the boundary and the appraisal document for the character description. And a listed building entry gives the list description, which is evidence about significance rather than a definition of what is protected, since protection extends to the whole building and to curtilage structures.
Feeding drawings and documents in
PlanScope accepts uploaded documents in PDF, image and Word formats through the guided flow, and it can take a site photograph and read the coordinates where the image carries them. There are three entry routes: enter a location and confirm the property, upload a photo, or upload documents.
What to give it, in rough order of value: the existing and proposed plans and elevations, the site location plan with the red line, the survey drawing if there is one, any pre-application response, the decision notices for relevant planning history, and the relevant extracts of the adopted local plan policies.
The property picker offers automatic footprint selection, a dropped pin or a drawn outline. Draw the footprint yourself where the automatic match is wrong, which happens on rear plots, subdivided buildings and recently built properties that predate the mapping refresh. A red line that does not match your application drawings produces a site description that contradicts them.
Describing the proposal so a policy test can bite
This is where most briefs fail. The description has to contain the facts the tests need, not a summary of the design intent.
For a change of use, that means the existing use class, the proposed use class, the floorspace affected and whether any operational development is involved. For a residential scheme, the number and mix of units, the site area, the density, the storey heights and the parking provision. For an extension, the depth, the height at eaves and ridge, the distance to the boundary, the position relative to the original rear wall and whether the property is an original dwellinghouse.
Those are the numbers that determine whether a proposal is a householder application or a minor, whether it is major development, whether it crosses a Transport Assessment threshold, and whether a permitted development route is even available. A Planning Statement drafted without them will discuss policy in general terms, which is exactly what a case officer skips.
Say what is not known as well. A site with no measured survey has an uncertain area, and stating that is better than letting a figure be inferred.
What a vague description produces
A drafting tool grounded in policy will produce structurally correct prose from thin inputs. That is the danger. The document will have the right headings, cite the right framework, and say very little that is specific to your site.
PlanScope's drafting inserts a to be confirmed flag wherever a site-specific fact is missing rather than filling the gap with plausible text. Treat every one of those flags as a task rather than an annoyance. They are the honest record of what the brief did not contain.
The failure that costs real money is subtler. A document that describes the scheme slightly differently from the drawings, with a floorspace figure from an earlier iteration or a unit count that predates a design change, creates an inconsistency that a validation officer will find. Then the application sits invalid while somebody reconciles the two.
Checking the output against the inputs
Read a draft with a checklist rather than as prose.
- Does the site description match the red line and the survey, including area and boundaries?
- Does the proposal description match the drawing schedule, figure for figure?
- Are the national policy references current? The Framework was re-issued on 17 August 2026 with policy-coded chapters, so any paragraph number carried over from an older edition needs replacing.
- Are the local plan policy numbers from the adopted plan, and is it still the adopted plan?
- Does each constraint mentioned have a source you checked yourself?
- Are the to be confirmed flags resolved or deliberately left for a specialist?
That fourth check catches more errors than the rest combined, because local plans are replaced and policy numbering changes with them.
Keeping the brief in the project file
Save the inputs alongside the output. The constraint checks with their dates, the drawings issued, the assumptions made and the flags resolved.
Two reasons. Constraints change, and a scheme that sits dormant for eighteen months may be facing a new local plan, a new flood map release or a new Article 4 direction. And when a case officer asks where a figure came from, the answer should take a minute rather than an afternoon.
Where a report needs a qualified author, the brief is also what the reviewer receives. PlanScope's professional directory is the route for requesting that review, with a request and sign-off flow, and a reviewer given a clear brief and a set of resolved flags will turn a draft around faster than one handed a document with thirty open questions. For report types where a licensed or competent professional is legally required, the draft is a starting point for that professional rather than a substitute. The same discipline applies to a Design and Access Statement, where the design rationale has to match what the drawings show.
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.
Enter your postcode on PlanScope to see the constraints picked up for a site and which reports follow from them.
Frequently asked questions
Which constraints should I check before drafting anything?
Those that change the report list, including flood zone, surface water risk, listed status, conservation area, Tree Preservation Orders, protected nature conservation sites, ancient woodland, air quality areas and ground conditions. Then those that change the policy tests, including Green Belt, National Landscape, settlement boundary, site allocation, neighbourhood plan area and any Article 4 direction.
Where should constraint data come from?
The primary source in each case. The Environment Agency Flood Map for Planning for flood zones, the long term flood risk service for surface water, the National Heritage List for England for listed buildings, the MAGIC map for protected sites and habitats, and the council's own mapping for conservation areas, Article 4 directions and Tree Preservation Orders.
What does PlanScope check automatically?
It checks a site against Environment Agency flood data, Historic England listed buildings and conservation areas, and Natural England protected site layers, then feeds the results into a rule-based engine that suggests which of the 66 report types the project is likely to need. That covers the common constraints and does not replace the manual checks for local designations.
Why does a vague proposal description matter so much?
Because the policy tests run on numbers. Use classes before and after, floorspace, unit numbers, site area, heights, boundary distances and parking all determine which application type applies, whether a scheme is major development and whether permitted development is available. Without them a draft discusses policy in general terms, which is what officers skip.
What are the to be confirmed flags for?
They mark places where a site-specific fact was missing, rather than filling the gap with plausible text. Each one is a task: either resolve it from your own information or pass it to the specialist who can. Leaving them unresolved in a submitted document is what makes a draft look unfinished to a validation officer.
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.