Where automated report recommendations come from

The honest answer to which reports does my site need is that no tool can give you a final list, because the definitive list is the one your local planning authority publishes on its validation checklist. What a rule-based recommendation engine can do is get you close in a couple of minutes, from three inputs: what you are proposing, what the site is near, and how big the scheme is. Understanding how those three inputs combine tells you where the output is reliable and where it needs checking.

This matters commercially. On a major application the evidence base is the largest pre-planning cost, and the difference between scoping nine documents and scoping fourteen is a real number. Scoping it wrong in either direction costs money.

What the project description triggers

The first layer is straightforward rule matching against the work type and property type. In PlanScope a Planning Statement and a Design and Access Statement come back for most projects, because most applications benefit from both and many validation lists require the second.

After that, the work type drives additions. A new build brings in biodiversity net gain, an energy statement, a sustainability statement, a construction management plan and a drainage strategy. A change of use brings in a transport assessment and a waste management strategy. A commercial proposal brings in retail impact, economic impact and a travel plan.

The known-issues answers do the rest. Declaring a listed building or conservation area adds a heritage statement, an archaeological desk-based assessment and a townscape and visual impact assessment. Trees nearby adds an arboricultural impact assessment and a landscape strategy. Flood risk adds a flood risk assessment, a drainage strategy and a sequential test. Noise adds a noise impact assessment. Neighbour concerns add a statement of community involvement and an overshadowing study. Access and highways issues add a transport assessment and a parking survey.

That structure is deliberately generous. It over-includes rather than under-includes, on the reasoning that a document you did not need is a smaller problem than a document the authority refuses to validate without.

What constraint detection adds

The second layer does not rely on what you tell it. Once the property is confirmed, the site is checked against published datasets: Environment Agency flood data, Historic England records of listed buildings and conservation areas, and Natural England Sites of Special Scientific Interest layers.

That produces facts you might not have known. A conservation area boundary two doors away. A grade II listed terrace on the opposite side of the street, which engages setting even though your site is not itself listed. A flood zone that the postcode does not suggest.

Detection is not a substitute for a constraints search. Datasets lag. A conservation area extended last year, a Tree Preservation Order made last month, or an article 4 direction covering your street may not appear. Treat automated detection as a first pass that tells you what to verify rather than as a clean bill of health, and check the authority's own constraints map before you rely on the absence of a designation.

The thresholds used to flag major development

The third layer is numeric, and these are the figures PlanScope uses to flag reports.

Two of those need a caveat. The major development definition tracks the statutory definition closely, so it is dependable. The fire statement flag does not track the legal test. The statutory duty under article 9A of the Development Management Procedure Order turns on a building containing two or more dwellings or educational accommodation and meeting a height condition of 18 metres or seven storeys, not on floor area. A 900 m² nine-storey block needs a statement and would not be flagged by floorspace alone. Check the height condition yourself on anything tall.

Transport thresholds are the other place to be careful. The 50 units and 2,500 m² figures reflect common practice, and many highway authorities apply lower local triggers, particularly where a site is on a constrained access or within an air quality management area.

Why the authority's validation list still wins

Every local planning authority in England publishes a local list of validation requirements alongside the national requirements, and it is that document which determines whether your application is validated. Local lists diverge more than people expect. Some require a drainage strategy on any new dwelling. Some require a daylight and sunlight assessment for any development adjoining a residential boundary. Some require a construction management plan at validation rather than by condition.

National policy thresholds also take precedence over any tool's rules where the two differ. So the sequence is: use the recommendation to scope and budget, then read the local list, then reconcile the two, then ask the case officer about anything still ambiguous.

Where the local list demands something no automated rule produced, that is not a failure of the tool. It is the reason the check exists.

Required against recommended, and who must write it

A scoping list that does not distinguish legally required authorship from advisable authorship is misleading, so PlanScope labels report types as professional required or professional recommended with the governing legislation or standard.

The legally required set is short and firm. An Environmental Statement must be prepared by competent experts under the Town and Country Planning (Environmental Impact Assessment) Regulations 2017. Protected species survey work and any mitigation licence need a suitably licensed ecologist under the Wildlife and Countryside Act 1981 and the Conservation of Habitats and Species Regulations 2017. The statutory biodiversity metric under the Environment Act 2021 expects a competent person. Land contamination reporting is expected to follow BS 10175 and to be prepared by suitably qualified and experienced persons. A fire statement needs fire engineering competence.

The recommended set, which includes preliminary ecological appraisal, arboricultural impact assessment, air quality, noise, transport and viability work, is where councils usually expect a suitably qualified author even though no statute says so. Professional review is strongly advised for all of these, and the professional directory is the route to a reviewer who can sign off a draft.

Checking the output against the local list

A sequence that takes an hour and saves weeks:

1. Generate the recommendation and export it as a list.
2. Download the authority's local validation list and the national requirements.
3. Mark each recommended document as required by the local list, required by national policy, or discretionary.
4. Mark each local list item that the recommendation missed, and why.
5. Identify which of the required items need a licensed or competent author, and start those first because they have the longest lead time.
6. Take the reconciled list to pre-application and ask the case officer to confirm it.

Step five is the one that protects the programme. Ecology survey seasons do not move, and a protected species survey commissioned in October may not be completable until the following summer.

The verification habit is worth building into the practice rather than doing once. A short standing checklist of the kind described in building an internal review checklist for submissions catches most of what a scoping exercise misses.

Turning a recommendation into a budget

Each recommended report has a typical consultant range and a difficulty rating, so a scoping list converts into a budget with two columns: what a consultant would charge, and what a drafted starting point costs. The index of the 66 report types by category sets out what each one covers and who can prepare it.

Drafts are drafts. They cite policy, structure the document to what a validation officer expects, and insert a clear flag wherever a site-specific fact is missing rather than filling the gap with an invention. That flagging behaviour is the useful part, because an empty field is a question for the project team, and a plausible-looking invented figure is a problem in a submitted document. The errors to look for are set out in factual errors to look for in a drafted planning document.

To scope a specific site rather than a category, enter the postcode on PlanScope and work through the guided questions.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval. For specialist technical reports, qualified professional input may be required. This is general guidance, not legal advice. Check the position with your local planning authority before relying on it.