Keeping a drafted document consistent with the drawings

Most validation queries on otherwise sound applications come down to one thing: the written documents and the drawings say different things. A floorspace figure that appears three ways, a drawing referenced in the design statement that is not on the schedule, a description of development that no longer matches the layout. None of it reflects on the quality of the scheme, and all of it costs time.

Report and drawings consistency is a checking discipline rather than a design skill, which is why it is worth systemising. Do it once as a routine and it takes twenty minutes on every subsequent job.

Why inconsistency causes invalidity

A local planning authority validates against the national requirements and its own published local list. Validation officers work through a checklist, and where a document contradicts a drawing they cannot resolve which version is being applied for.

That has a practical consequence beyond delay. The description of development and the approved drawings define what the permission authorises. If the documents are inconsistent, the permission may be ambiguous, and ambiguity in a permission surfaces years later when someone tries to discharge a condition, sell a plot or amend a detail.

Consultees compound the problem. A highways officer given a floorspace figure that differs from the one in the transport work will assume the transport work is wrong, and the response arrives as an objection rather than a query.

The description of development is the anchor

Everything else should be checked against the description, and the description should be written once and copied everywhere.

It appears on the application form, in the covering letter, in the Planning Statement, in the design statement, in any specialist report and frequently on the drawing title blocks. One version, copied and pasted, with no editorial improvement along the way.

Write it to match what the drawings show. The common failures are a description mentioning works that were removed during design, a description omitting an element that appears on the plans, a description using a use class that does not match the schedule, and a description quoting a unit count that changed after the last design review.

Where the description needs to change after submission, that is a formal step handled with the case officer, not a quiet correction in a later document.

Numbers that must agree everywhere

Three sets of figures cause most of the trouble.

Floorspace is the first. Decide whether the application reports gross internal area or gross external area, state which, and use the same basis in every document. A transport assessment using one basis and an energy statement using the other produces two different buildings on paper. Fee calculations, threshold tests and policy triggers all depend on the figure, so an error here can be substantive rather than presentational.

Unit numbers and mix are the second. The total, the split by bedroom count, the affordable proportion and the tenure mix should be identical in the planning statement, the affordable housing evidence, the drawings schedule and the form. Where a scheme has both flats and houses, check the sub-totals as well as the total.

Site area is the third. The red line area drives major development thresholds, biodiversity requirements, fee bands and several policy tests. Measure it from the submitted location plan rather than from a masterplan drawn at a different stage, and state it in hectares to a consistent number of decimal places.

The drawing schedule and revision letters

A drawing schedule listing every submitted drawing by number, title, scale and revision is the single most useful page in an application pack. Build it from the drawings themselves rather than from the previous job's schedule.

1. Export the drawing list from the file names of what is actually being uploaded.
2. Open each drawing and check that the number and revision in the title block match the file name.
3. Check the scale stated on the drawing against the scale bar.
4. Check that every drawing referenced in any written document appears on the schedule.
5. Check that every drawing on the schedule is referenced somewhere, or remove it.
6. Lock the schedule once the pack is assembled, and reissue it in full if anything changes.

Revision letters are where packs come apart. A design statement referring to revision C while revision E is submitted tells the officer the narrative was written against a superseded design, and they will read the rest of it with that in mind.

Levels, heights and boundaries

Level information is the most common source of substantive inconsistency, because it appears on the topographic survey, the proposed site plan, the sections and often in the drainage and flood risk work.

Fix one datum and state it. Existing and proposed finished floor levels, ridge heights, eaves heights and external ground levels should all be expressed against that datum, and the relationship between them should be checkable by arithmetic on the drawings.

Flood risk work is the place this matters most, because a finished floor level quoted in a Flood Risk Assessment that differs from the one on the sections will be picked up by the Environment Agency or the lead local flood authority, and the resulting condition may fix the wrong number.

Boundary treatments deserve a check of their own. Heights and materials stated in a design statement, shown on elevations and listed on a boundary treatment plan frequently disagree, and a neighbour reading the consultation documents will spot it.

A cross check routine before submission

Run this as a fixed sequence rather than reading the documents through.

• Read the description of development aloud against the proposed site plan.
• Search every document for the floorspace figure and confirm one number and one basis.
• Search every document for the unit count and confirm one number.
• Compare the drawing schedule against the upload folder, file by file.
• Search each written document for drawing references and tick them off on the schedule.
• Check levels on the sections against the levels quoted in the flood risk and drainage documents.
• Check the red line on the location plan against the site area stated in the documents.
• Check the Design and Access Statement describes the scheme as submitted, not as designed three months ago.

The wider set of errors worth hunting for in a draft, including policy citations and site facts, is covered in factual errors to look for in a drafted planning document, and turning these checks into a standing document is the point of building an internal review checklist for submissions.

Amendments after validation

Once an application is validated, changes have to be managed rather than uploaded. Send amended drawings to the case officer with a covering note listing what changed and why, an updated drawing schedule, and revised extracts from any written document affected.

Expect re-consultation where the change is material, which resets part of the publicity period. Minor corrections to a drawing number or a typographical error usually do not, but that is the officer's decision rather than yours.

Keep a record of which version was consulted on. Where a scheme is amended twice during determination, the decision notice should list the final drawings, and checking the list on the notice against your own schedule takes two minutes and occasionally saves a section 96A application later.

An AI-assisted draft can produce a consistent narrative from the facts it is given, and it will reproduce whatever figures you supply. It cannot open the drawings and check them. That comparison is a human task, and it is the one worth doing last, slowly, on paper.

PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.