Structuring appendices around a drafted narrative

An application bundle works when every assertion in the narrative can be traced to a numbered appendix in one step. That is the standard a reviewer applies, and it is the standard an inspector applies at appeal, where a statement that refers vaguely to "the submitted ecology information" costs you the point you were trying to make. The discipline is simple to describe and tedious to apply: number the appendices, cite them in the narrative by number and paragraph, and keep the numbering stable through revisions.

Where a drafted narrative is the starting point, the appendix structure needs to be imposed deliberately, because a draft will produce prose that reads well and references nothing.

Why appendix order matters

Three readers use the bundle, and they read it differently.

The case officer reads the narrative first and dips into appendices to verify specific claims. They need to find the right appendix in one move, which means the order should follow the narrative rather than the order documents happened to arrive.

The consultee reads only their own appendix, often without the narrative at all. The highways officer wants the transport statement and the swept-path drawings, and nothing else. Each appendix therefore has to stand alone, with its own title page, author, date and revision.

The inspector, if the case goes to appeal, reads the refusal reasons and then looks for the evidence on each. Anything that cannot be located quickly is treated as not having been put. A bundle organised by theme, with a contents page that maps appendices to issues, survives that reading. One organised chronologically does not.

What belongs in the narrative

The narrative carries argument, not evidence. It states the proposal, identifies the policy framework, works through each material consideration, and reaches a conclusion on the planning balance.

In practice that means the narrative should contain: the description of development and the drawing schedule, the site and surroundings in brief, planning history with application references, the development plan policies that apply with the test each sets, the assessment of each material consideration with a cross-reference to the supporting appendix, any planning obligations offered, and the balance.

What it should not contain: tables of data that belong in a technical report, extended quotation of policy, reproduction of consultee correspondence, or a summary of an appendix long enough to be read instead of it. A summary that substitutes for the appendix invites the officer to rely on your paraphrase, and your paraphrase is the thing an objector will attack.

Keep the narrative to argument and the appendices to evidence, and the bundle holds together under scrutiny.

What belongs in an appendix

Everything the narrative relies on and cannot contain. A typical minor residential bundle:

• Appendix A: drawings schedule and reduced-scale drawings
• Appendix B: site photographs, numbered and keyed to a viewpoint plan
• Appendix C: preliminary ecological appraisal and any protected species survey
• Appendix D: biodiversity metric output and the calculation file
• Appendix E: arboricultural report and tree protection plan
• Appendix F: flood risk assessment and drainage calculations
• Appendix G: transport statement and swept-path drawings
• Appendix H: contamination Phase 1 report
• Appendix I: pre-application correspondence and the officer's written advice
• Appendix J: planning history extracts and relevant decision notices

Two inclusions earn their place more often than people expect. Pre-application advice, where it was favourable or where the scheme has responded to it, is worth putting in, because an officer departing from their colleague's advice has to explain why. And photographs with a viewpoint plan answer more questions than any amount of description.

Cross-referencing that a reader can follow

A workable convention: cite the appendix letter and the paragraph or drawing number, in brackets, immediately after the claim. "The proposed access achieves visibility of the standard required for the recorded 85th percentile speed (Appendix G, paragraph 4.12 and drawing TS-02)."

Four rules keep it usable.

1. Cite at the point of the claim, not at the end of the section. A reader checking a sentence should not have to find the citation elsewhere.
2. Cite the paragraph, not just the document. "See the transport statement" is not a citation.
3. Never cite a page number, because pagination changes with every revision.
4. Where a claim rests on two appendices, cite both rather than the more convenient one.

Build a cross-reference table as you write, listing each assertion, its appendix and its paragraph. It takes minutes and nothing else reliably catches the claim that lost its evidence when an appendix was updated.

A worked bundle example

Take a single new dwelling on an infill plot with a mature oak on the boundary, a surface water constraint and a previous refusal on design grounds. The narrative runs to about twelve pages.

The design section cites the design and access statement for the response to the previous refusal, and the officer's pre-application advice for the roof form that was agreed. The amenity section cites the drawings for separation distances and a daylight sketch for the effect on the neighbouring kitchen window. The trees section cites the arboricultural report for the root protection area and the tree protection plan for the no-dig construction detail. The drainage section cites the drainage calculations for the discharge rate and the attenuation volume. The ecology section cites the preliminary ecological appraisal for the habitat baseline and the metric output for the gain figure.

Five sections, five appendices, each cited at the sentence that depends on it. Nothing in the narrative is asserted without a source, and nothing in an appendix is left unexplained. That example is illustrative, but the ratio holds: if a section of narrative cites no appendix, either it is pure policy argument or it is unevidenced.

Numbering, revisions and file naming

Revisions are where bundles come apart. A policy worth adopting from the start:

Reassigning appendix letters mid-process is the single most damaging thing you can do, because every citation in the narrative becomes wrong and the error is invisible until someone checks. If an appendix is withdrawn, leave the letter in the contents page marked as withdrawn rather than closing the gap.

Date and revision every document on its own title page. Version control matters more when sections are regenerated or redrafted, and our note on version control when report sections are regenerated sets out how to keep a drafted document traceable through that process.

A packaging checklist

Before the bundle is uploaded, work through this:

1. Contents page lists every appendix with author, date and revision, and matches what is attached.
2. Every appendix cited in the narrative exists, and every appendix attached is cited at least once.
3. Each citation names a paragraph or drawing, not a page.
4. Drawing numbers and revisions in the narrative match the drawings submitted.
5. Each appendix has its own title page with author and qualifications, because competence is checked on technical reports.
6. File sizes are within the authority's upload limits, with large appendices split logically rather than arbitrarily.
7. No document contains tracked changes, comments or placeholder text.
8. The cross-reference table has been checked against the final appendices.

Item seven is worth a separate pass. Placeholder text left in a submitted document is the fastest way to lose a reviewer's confidence, and drafted documents are particularly prone to it because the draft deliberately marks the facts it does not hold so that you can fill them in. Those markers are a safeguard during drafting and an embarrassment after submission.

PlanScope drafts the narrative and the report structure with the policy citations in place and flags the site-specific facts it cannot supply, and it is built so that the drafted sections can be edited and regenerated individually while you assemble the evidence around them. The judgement about what the bundle has to prove stays with you or your reviewer, and the professional directory is the route to a review before submission. Our notes on what drafts get right about structure and wrong about evidence and on drafting to an appeal deadline cover the two situations where this discipline is tested hardest.

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