Flagged gaps in a draft and how to close them properly
An AI draft that stops and flags a missing site fact is safer than one that estimates it. How to close each kind of flag from the source a council would check.
A draft that stops and says the figure is to be confirmed has done its job. To be confirmed flags planning draft text is there because the alternative is a number that reads plausibly and is wrong, and a wrong number in a Planning Statement is worse than a gap, because nobody looks for it.
The work is closing the flags properly. That means going to the source that the council itself would check, recording where the answer came from, and knowing which flags cannot be closed from a desk at all.
Why a flag beats an invented figure
An invented site area survives validation. It survives the officer's first read. It fails when the officer measures the red line on your location plan, or when a consultee notices that the area quoted in the statement does not match the area on the form, or when the figure is used to calculate a levy charge that is then disputed.
Every one of those failures costs more than the flag would have. Re-issuing a statement mid-determination is embarrassing. Having a permission challenged because the application described the site inaccurately is worse.
So the flag is a design decision rather than a limitation. A draft that refuses to guess at the distance to the nearest listed building is more useful than one that estimates it, because the estimate looks exactly like a researched fact.
The harder honesty is that a flag only works if someone closes it. A statement submitted with the brackets still in it tells the officer that nobody read the document, and it is one of the reasons applications come back, as our note on why planning applications are returned as invalid sets out.
The categories of fact that get flagged
Flags fall into five groups, and the routes to closing them are different enough that it pays to sort them before starting.
| Category | Examples | Closed from |
|---|---|---|
| Measurement | Site area, floor areas, ridge heights, distances to boundaries | Measured survey or scaled drawing |
| Designation | Flood zone, conservation area, listed building grade and distance, TPO | Public datasets and the council's map |
| Policy | Local plan policy numbers, NPPF policy codes, SPD titles and dates | The adopted plan and the current Framework |
| Site history | Previous applications, conditions, enforcement history, lawful use | The council's planning register |
| Survey result | Bat activity, tree categories, ground contamination, noise levels | A survey by a qualified person |
The last row is the one that matters most. No desk exercise closes a flag that asks what the bats are doing, and no amount of careful drafting substitutes for a site visit by someone competent.
Measurements and where to source them
Site area is the measurement most often wrong, and the usual cause is a red line drawn on a satellite image. Two sources are reliable: a measured topographical survey, and the title plan from the land registry read against the survey.
Three habits prevent the common errors. Give the area in square metres and hectares, both, because thresholds are expressed in each. State whether the area includes the access strip, the verge and any land over which only rights are held. And make the figure on the form, in the statement, on the location plan and in any levy calculation the same figure, which sounds obvious and fails on perhaps a third of applications.
Floor areas need the same discipline. Gross internal area and gross external area differ, and policies use both. Say which you have used. An existing floor area taken from an energy certificate is not a measured figure and should not be used to establish a baseline for a permitted development calculation.
Heights are measured from a datum, and the datum has to be stated. Ridge height above existing ground level at a specified point, not above the pavement, not above the lowest point on a sloping site unless you say so.
Designations and the primary datasets
The public datasets the product itself checks are the ones to verify against, and they are free.
Flood zone comes from the Flood Map for Planning service, which gives the zone and lets you print a result with a reference. Do not use the long-term flood risk postcode checker for a planning submission. It answers a different question and councils know the difference.
Statutory nature conservation designations, including sites of special scientific interest and priority habitat, come from the Defra MAGIC map. Listed buildings, scheduled monuments and registered parks come from the National Heritage List for England, which gives the grade, the list entry number and the date of listing.
Conservation area boundaries, Article 4 directions, tree preservation orders and local designations come from the council's own mapping, and from the national planning data platform where the council has published its data there. Air quality management areas come from the Defra air quality information resource.
Record three things for each designation: the dataset, the date you checked it and the result. A constraints table with those columns answers the officer's question before it is asked, and it protects you where a designation changes between submission and determination.
One caution. Absence of a designation on a national dataset is weaker evidence than its presence. Tree preservation orders in particular are patchily published, so a nil result should be phrased as no order identified on the council's published map rather than as no order exists.
Policy references and the edition problem
This is where drafts go stale fastest. The National Planning Policy Framework was renumbered in December 2024 and re-issued on 17 August 2026 with policy-coded chapters in place of paragraph numbers, so a paragraph number carried forward from an older document now points at different text.
Three rules keep policy references safe. Always state the edition alongside the reference, because readers hold older copies. Verify every code or paragraph against the published Framework at the moment of writing rather than trusting any secondary source, including a draft. And never carry a policy reference from a previous project without rechecking it, since local plans are replaced and policy numbers reused.
Local policy needs the same treatment. Name the plan, its adoption date and the policy reference, and check whether a newer plan or a partial update has superseded the one you know. Where a neighbourhood plan covers the site, it forms part of the development plan and its policies carry the same weight as the local plan's.
Supplementary planning documents are the ones most often cited from memory. Check the title and the date, because design guides get reissued and a reference to a withdrawn document invites the officer to discount the whole section.
Closing a flag without leaving a gap
Replacing the brackets with a number is half the job. The other half is making the surrounding sentence true.
An illustrative example. A draft reads that the site lies within Flood Zone [TO BE CONFIRMED] and that a flood risk assessment is therefore required. You check and the answer is Zone 1. Deleting the flag and inserting Zone 1 leaves a sentence saying a flood risk assessment is required when, on a site below one hectare in Zone 1, it probably is not. The flag was a placeholder for a fact and for the reasoning that depends on it.
So read the paragraph, not the gap. Where the inserted fact changes the conclusion, rewrite the conclusion. Where it changes which documents the application needs, change the document list. Where it removes a section's purpose entirely, delete the section rather than leaving an orphan paragraph.
Keep a record of what you changed and when. Where sections are regenerated after a flag is closed, the risk is reintroducing the placeholder, which is the problem our note on version control when report sections are regenerated deals with.
A final sweep before submission
Four checks, in this order, take about half an hour on a householder application and rather longer on a major:
- Search the document for the flag text, for square brackets, and for the words to be confirmed, assumed and approximately
- Cross-check every number that appears more than once, so the form, the statement, the drawings and the levy calculation agree
- Re-verify every designation and policy reference against its source, with the date recorded
- Read each conclusion and ask whether the facts now in the document support it
Anything that survives those four checks and still cannot be closed needs a professional. Where the gap is a survey result, a licensed or competent specialist is required rather than advisable, and the professional review route exists for exactly that handover. Our note on what AI drafts get right and wrong is candid about where the line sits.
See PlanScope pricing if you want to edit drafts in the platform and keep versions as flags are closed, since editing and saved versions are paid-tier features.
This is general guidance, not legal advice. 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.
Frequently asked questions
Why does a draft leave a placeholder instead of estimating?
Because an estimate reads exactly like a researched fact. An invented site area survives validation and fails later, when an officer measures the red line or a levy charge is disputed. A flag is visible and fixable. The limitation is that it only works if someone reads the document and closes it before submission.
Where should flood zone be checked?
On the Flood Map for Planning service, which gives the planning flood zone and produces a printable result with a reference. The long-term flood risk postcode checker answers a different question and is not an acceptable source for a planning submission. Councils are familiar with both and can tell them apart.
Can a desk check confirm there is no tree preservation order?
Not conclusively. Order data is published patchily, so a nil result should be recorded as no order identified on the council's published map rather than as no order existing. Where trees on or near the site matter to the scheme, ask the council's tree officer directly and keep the reply.
How should NPPF references be cited?
With the edition stated every time. The Framework was renumbered in December 2024 and re-issued on 17 August 2026 with policy-coded chapters replacing paragraph numbers, so an old paragraph number now points at different text. Verify each code against the published Framework at the time of writing rather than trusting a secondary source.
Which flags cannot be closed from a desk?
Anything that depends on a survey: bat activity, tree categories under BS 5837, ground contamination, measured noise levels, protected species presence. These need a site visit by someone competent, and for several report types a licensed or competent professional is legally required rather than merely advisable.
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.