An internal quality check before anything leaves the office

Most validation rejections are arithmetic, not judgement. The site area on the form does not match the red line on the location plan, the drawing schedule lists a revision that was never uploaded, or the transport statement counts four parking spaces where the layout shows three. None of those is a design failure and all of them cost a fortnight.

The fix is a twenty minute cross-check carried out by somebody who did not draw or write any of it. What follows is the routine, in the order that catches the most errors soonest.

The five numbers that must agree everywhere

Pick these five out of the pack first, write them on one sheet, then go looking for every place each appears.

1. Site area, in hectares and in square metres, as stated on the application form, measured from the red line, and quoted in every report.
2. Number of units, by tenure and by bedroom count, on the form, in the accommodation schedule, on the floor plans and in every supporting statement.
3. Gross internal floorspace, existing and proposed, with the net change. This drives the fee, the levy position and several report thresholds.
4. Parking and cycle spaces, counted on the layout drawing rather than taken from the transport report.
5. Building height, in metres above finished floor level and in storeys, consistent between elevations, sections and any tall-building or fire statement.

Where any of the five disagrees, resolve it in the document that governs. The drawings govern dimensions. The form governs what is being applied for. The reports follow both.

A disagreement in the site area is the one that changes the application rather than merely embarrassing it. Crossing 0.5 hectares turns a residential scheme into major development, with a different fee band, a different determination period and a different publicity requirement, as our note on the 0.5 hectare rule sets out.

Red line against the stated site area

Measure the red line area from the digital file, not from the printed sheet. Three checks:

• Does the red line include everything needed to carry out the development, including the access, visibility splays, any new footway crossing and any land required for drainage or a turning head. Land outside the red line but within the applicant's ownership goes blue.
• Does the measured area match the figure on the form to a sensible precision. Two decimal places in hectares is enough, and a discrepancy of more than a few per cent means one of the two is wrong.
• Is the plan at 1:1250 or 1:2500, with a scale bar, a north point and enough surrounding context for the site to be located.

Ordnance Survey-based location plans from most suppliers carry the scale bar and north point automatically. The red line is the part somebody draws by hand, which is why it is the part that goes wrong. Our note on site location plans councils accept covers the conventions in detail.

Drawing numbers against the schedule and the portal

Three lists have to match: the drawing schedule in the submission, the drawings actually uploaded, and the list of plans typed into the application form.

• Every drawing carries a unique number and a revision suffix, and the suffix on the sheet matches the suffix in the schedule.
• No superseded revision is in the upload. A portal file list showing both revision C and revision D of the same plan is a request for further information waiting to happen, and worse, the council may condition the wrong one.
• File names on the portal begin with the drawing number, so the council's document viewer sorts them usefully.
• Every drawing has a scale bar, because "do not scale" title blocks are rejected by some authorities and because printed plans are reduced.
• Existing and proposed are clearly distinguished in the title, not only in the content.

Check the north point on every plan drawing, not just the location plan. A site plan with the north point rotated from the location plan is the error that makes a daylight or overshadowing argument look wrong.

Report conclusions against the covering letter

Read the executive summary of each technical report and then read the covering letter. They should say the same thing in different words. Common mismatches:

• The flood risk assessment sets a finished floor level that the sections do not achieve.
• The biodiversity net gain figure in the metric differs from the percentage quoted in the planning statement.
• The transport statement relies on a trip rate for a use class the application does not seek.
• The energy statement models a building fabric that the drawings and the specification do not match.
• The arboricultural report protects a tree that the layout removes, usually because it was written against an earlier revision.

Every technical report should name, on its cover or in its first page, the drawing numbers and revisions it was prepared against. Where that reference is to a superseded revision, either update the report or explain the difference in the covering letter. Do not leave the officer to notice.

The same discipline applies to the Planning Statement, which pulls all the conclusions together and is where a contradiction is most visible.

Policy references and their editions

Templates carry old policy references forward, and an officer who spots a superseded policy number stops trusting the rest of the document.

Check four things:

1. The National Planning Policy Framework edition is stated, and the references match that edition. The Framework was renumbered in December 2024 and re-issued on 17 August 2026 with policy-coded chapters in place of paragraph numbers, so a document citing paragraph numbers is citing an older edition.
2. The adopted local plan is named with its adoption date, and each policy cited still exists in that plan. Where a new plan has been adopted, saved policies from the old one may or may not have survived.
3. Supplementary planning documents are cited with their version and date.
4. Any emerging policy is labelled as emerging, with its stage, rather than presented as adopted.

For a Design and Access Statement, add a check that the design guidance cited is the current local design guide or code rather than a superseded one.

Certificates, notices and the fee

These are the mechanical items that reject applications outright.

• The right ownership certificate, A, B, C or D, matching the actual ownership position on the day of submission.
• Notice served on every other owner, with the date, and 21 days allowed before the council determines the application.
• The agricultural holdings certificate completed, including where the answer is that there is no agricultural tenant.
• The fee checked against the current schedule rather than the last invoice. Fees are indexed annually, and a shortfall means the application is not valid.
• The biodiversity gain statement, where required, since a statement about whether the biodiversity gain condition applies is now part of the national requirements for most applications. Check the current requirement before submitting.

Who signs off and when

The person who checks is not the person who produced. That single rule catches more than any list, because the author reads what they meant rather than what is on the page.

A workable arrangement for a small practice:

The overnight gap is the part that gets dropped under deadline pressure and the part that most improves the result. Where a certificate B, C or D applies, or where the fee is substantial, put the sign-off with someone who can carry the consequence of getting it wrong.

A one page check sheet

Print this and initial each line.

• Site area consistent: form, red line, all reports
• Unit numbers consistent: form, schedule, plans, statements
• Floorspace figures consistent, existing and proposed, with net change stated
• Parking and cycle counts taken from the layout
• Heights consistent across elevations and sections
• Red line includes access and all land needed
• Location plan at 1:1250 or 1:2500 with scale bar and north point
• Drawing schedule matches uploads and matches the form
• No superseded revisions uploaded
• Every report names the drawing revisions it used
• Framework edition stated and references matched to it
• Local plan named with adoption date, policies verified
• Ownership certificate correct, notices served and dated
• Fee checked against the current schedule
• Biodiversity gain statement included where required
• Checked by someone other than the author, and initialled

Architects and agents doing this across several applications a month gain most from having the statements drafted to a consistent structure, so the cross-check finds real errors rather than formatting differences. See PlanScope pricing for the Professional tier, which removes branding and adds your own logo. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.