---
name: planning-application-statement
description: "Write the design and access statement that supports a planning application — the site analysis, the design rationale, the policy compliance, and the answers to the objections the case officer will receive. Use when asked to write a design and access statement, planning statement, or supporting statement for a planning application, or to respond to a planning objection or refusal. Produces the site and context analysis, the design evolution narrative, the policy-by-policy compliance table, the access and amenity assessment, and the pre-empted objections. Not planning or legal advice; local policy and procedure govern."
homepage: https://mohitagw15856.github.io/pm-claude-skills/skill/planning-application-statement.html
metadata:
  {
    "openclaw": { "emoji": "🧠" }
  }
---

# Planning Application Statement

A case officer reads dozens of these. What they need is to find, quickly, that you have understood the site, that the design follows from that understanding, and that each relevant policy is addressed by name. What they get is usually a description of the proposal. This writes the version that answers their report for them — and pre-empts the objections that will land in the consultation period.

## What This Skill Produces

- **Site and context analysis** — what is actually there, what characterises it, and what the site can take
- **The design rationale** — how the proposal follows from the analysis, including what was tried and rejected
- **A policy compliance table** — each relevant local and national policy, named, with how the scheme complies
- **Access and amenity assessment** — inclusive access, overlooking, overshadowing, noise, parking, and refuse
- **Pre-empted objections** — the concerns neighbours will raise, addressed before they are raised
- **The consultation record** — pre-application advice and any engagement already undertaken

## Required Inputs

Ask for these if not provided:
- **The proposal** — what is being applied for, with areas, heights, and materials
- **The site** — location, existing use, constraints, designations, boundaries, and neighbouring context
- **The policy framework** — the local plan policies and any supplementary guidance that apply
- **Pre-application history** — any advice received, and previous applications or refusals on the site
- **The known sensitivities** — what neighbours or the parish have objected to before

## Framework: Analysis, Then Rationale, Then Policy by Name

1. **Analyse the site before describing the scheme.** Character, scale, materials, topography, boundaries, and how the site is actually used. A rationale unearned by analysis reads as post-hoc justification.
2. **Show the design evolving.** Including the option you rejected and why. Officers trust a scheme that visibly responded to constraints more than one presented as inevitable.
3. **Address policies by their number and name.** A general claim of compliance forces the officer to do the work, and they will do it less generously than you would.
4. **Answer amenity concretely.** Distances, angles, and hours — not 'no undue impact'. Overlooking and overshadowing are measurable and should be measured.
5. **Pre-empt the objections you know are coming.** Parking, overlooking, precedent, construction disturbance. Addressed in the statement, they arrive at the officer already answered.
6. **Be accurate about what is proposed.** A discrepancy between the statement and the drawings costs credibility for the whole application.

## Output Format

### Design & access statement: [proposal] · [site] · [date]

**Proposal:** [precise description matching the application form and drawings]

**Site & context:** [existing use, area, boundaries, topography, access] · **Character:** [what defines the surrounding area — scale, materials, grain, roofline] · **Designations:** [conservation area, listed, flood zone, TPO, green belt, or none]

**Design evolution**
| Option considered | Why rejected |
|---|---|
| [option] | [reason] |
**Adopted approach:** [how it responds to the analysis above — scale, siting, materials, roofline]

**Policy compliance**
| Policy | Requirement | How the proposal complies |
|---|---|---|
| [ref & name] | [what it requires] | [specific response] |

**Access:** [inclusive access, approach, entrance, level changes, parking including accessible spaces, refuse and cycle storage]

**Amenity:** overlooking [distances, window positions, screening] · overshadowing [orientation, separation, any daylight assessment] · noise [source, mitigation] · construction [hours, access, management]

**Anticipated concerns, addressed**
- *[likely objection]* — [the specific response]

**Pre-application:** [advice received, reference, and how the scheme responded] · **Engagement:** [what was done]

> Supporting-document drafting only, not planning or legal advice. Local plan policies, validation requirements, consultation procedure and appeal rights differ by authority and change — verify everything against the current local plan and the authority's own validation checklist before submission.

## Quality Checks
- [ ] Site analysis precedes and demonstrably drives the design rationale
- [ ] At least one rejected option is shown, with its reason
- [ ] Every relevant policy is named by reference, not addressed generically
- [ ] Amenity impacts are quantified with distances and orientation
- [ ] The likely objections are answered inside the statement
- [ ] The description matches the drawings and application form exactly

## Anti-Patterns
- **Describing the proposal instead of justifying it.** The officer already has the drawings.
- **Claiming policy compliance in general.** Unnamed policies get assessed without your help.
- **'No undue impact on amenity'.** Meaningless without distances; objectors will supply their own numbers.
- **A design with no rejected options.** Reads as unconsidered, however good it is.
- **Ignoring the obvious objection.** It arrives anyway, and now unanswered.
- **Statement and drawings disagreeing.** One discrepancy undermines everything else in the document.

## Example Trigger Phrases
- "Write a design and access statement for a rear extension"
- "Draft a planning statement for this application"
- "How do I address the local plan policies in my statement?"
- "Neighbours are objecting about overlooking — how do I answer that?"
- "Write a supporting statement for a change of use"