Appendices that get a technical report validated first time

Validation is an administrative check, and technical report appendices in a planning submission fail it for administrative reasons. The assessment is usually sound. What fails is the packaging: survey data summarised instead of supplied, a drawing reference superseded a fortnight before submission, a certificate the local validation list asks for that nobody requested from the laboratory. Every one of those is avoidable in an afternoon, and every one of them costs a fortnight when it happens.

So treat the appendices as a deliverable in their own right, with their own checklist, rather than as whatever ended up at the back of the document.

Why appendices decide validation

A validation officer is not assessing the merits of your acoustic model. They are checking the submission against the national requirements and the authority's own local validation list, item by item, and a report that does not visibly contain a listed item gets returned.

Local lists differ considerably between authorities, and they are the reason a report accepted in one district is invalid in the next. Download the list for the authority before the report is finalised, not after, and go through it with the author. Where the list asks for something in unfamiliar language, ask the validation team what they mean rather than guessing.

The second reason appendices matter is that they are how a case officer or a consultee tests the conclusion. An officer who can find the raw data will read the summary and move on. One who cannot will ask for it, and that request arrives as a formal request for further information with its own delay.

Raw data and calculation outputs

The rule is simple: if a number in the report was produced by a measurement, a model or a calculation, the output that produced it goes in an appendix.

For a noise assessment that means the measurement data with time history, the survey sheets with positions, dates, times and weather, and the calculation sheets for any prediction. For a daylight study it means the numerical results by room and window, not just a pass or fail table. For a drainage note it means the rainfall query output and the greenfield run-off calculation. For a traffic assessment it means the count data and the trip rate extract with its selection criteria.

Two practices make raw data usable rather than merely present. Label every appendix page with the report reference and the appendix number, because appendices get separated when a council splits a submission into separate files on its public register. And give tabular data in a form that can be read at the scale it will be printed, which usually means landscape orientation and a sensible font rather than a spreadsheet screenshot.

Where a model has been run, state the software and version. Not to advertise it, but because a consultee reproducing your result needs to know.

Calibration and accreditation certificates

This is the single most common validation gap on measurement based reports.

Instruments used for measurement need to be within calibration, and the evidence is a certificate showing the instrument serial number, the calibration date and the traceability of the calibration. For acoustic work, the field verification before and after the survey should also be recorded, with the calibrator's own certificate. For air quality monitoring, the certificate and any relevant scheme accreditation apply. For laboratory testing of soils or water, the accreditation status of the laboratory and of the specific test schedule matters, and a laboratory report will state which tests were accredited and which were not.

Three points worth insisting on:

• Serial numbers in the certificate must match the serial numbers quoted in the method section.
• Calibration dates must bracket the survey dates, so a certificate issued after the survey needs the previous one as well.
• Where a test was carried out outside an accredited schedule, the report should say so rather than leaving the reader to notice.

An Noise Impact Assessment submitted without the calibration evidence will usually be returned by an environmental health officer even if validation lets it through, which wastes more time than including it would have.

Correspondence with consultees and undertakers

Councils and consultees want to see that third parties were asked, and what they said.

The correspondence worth appending includes any pre-application response from the authority, responses from statutory consultees to pre-application enquiries, sewer records and capacity responses from the water and sewerage undertaker, highway authority correspondence on access and visibility, and records of any request that was refused or went unanswered.

That last category is the one people omit, and it is often the most useful. Where the drainage strategy relies on a connection the undertaker has declined, the declining email is evidence supporting your chosen solution. Where a consultee did not respond within a reasonable period, the record of the request shows the work was done.

Redact personal data before submission. Names, direct dial numbers and personal email addresses of individuals should come out, because the submission goes onto a public register. Keep the organisation, the reference and the date.

Drawing registers and revision control

More reports are invalidated by drawing references than by anything technical.

Include a drawing register in every technical report: drawing number, title, revision, date and the scale at which it was issued. Then check that every drawing referenced in the text appears in the register, that every drawing in the register is actually in the submission, and that the revision quoted in the text matches the revision submitted.

The organisational answer is to nominate one person to own the submission pack and to freeze the drawings at a stated revision, then to tell every specialist author what that revision is. It sounds bureaucratic until the alternative has been experienced once.

Where visual material is involved, the methodology appendix matters as much as the images, as our note on photomontage methodology in a landscape and visual assessment explains.

Cross referencing between reports

A submission pack containing eight technical reports is read as one document by a case officer, and inconsistencies between reports are noticed.

Cross check five things across the whole pack before submission: site area, floorspace figures, unit numbers and mix, the phasing assumed, and the drawing revisions relied upon. Then check that where two reports address the same issue from different disciplines, they reach compatible conclusions. An ecology report proposing a wildflower meadow where the drainage strategy shows an attenuation basin is the classic example, and both authors will have been given different drawings.

Add a short cross reference note to each report identifying which other documents in the pack it relies on. It takes ten minutes and it tells the officer how the evidence fits together. Our note on environmental zones and obtrusive light limits shows how one report's environmental zone classification can determine another's assessment criteria, which is exactly the kind of dependency worth recording.

A checklist before submission

Run this the day before, not the morning of.

1. Local validation list downloaded for the correct authority, and each item matched to a document or marked as not applicable with a reason.
2. Drawing register complete, revisions matched between text and submitted files, scale bars and north points present.
3. Raw data, survey sheets and calculation outputs appended, paginated and labelled with the report reference.
4. Calibration and accreditation certificates included, with serial numbers and dates matched to the method section.
5. Consultee and undertaker correspondence appended and redacted.
6. Figures for site area, floorspace, units and phasing consistent across every report.
7. File sizes within the authority's upload limits, and files named so a stranger can tell what each one is.
8. Every report dated, versioned and authored, with a signature or named author.

Item seven is duller than the rest and causes as many failures. Authorities set upload limits and some reject files above them without explanation, so check the limit and split large appendices sensibly, by appendix rather than by arbitrary page count.

One honest observation. No checklist prevents the problem where the design changes after the specialists have reported. The only real defence is a drawing freeze, agreed in writing, with a stated date after which changes trigger a report reissue. Browse the report types by category if you are still working out which documents the submission needs.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional before relying on it.

PlanScope drafts are structured to UK planning policy and flag missing site facts with a clear marker, which makes the appendix gaps visible before submission. For specialist technical reports, qualified professional input may be required.

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