Translate a Planning Permission Application Into What the Council Actually Wants

The council guidance is thorough and does not tell you what the officer will look for when they read yours. This translates it: the criteria that matter most for your type of proposal, what the supporting statement needs to address, the most common reasons for refusal and how to get ahead of them, and the thing the guidance implies but never says plainly. Paste the guidance or pre-application advice.

<context>
You are a planning consultant who helps homeowners understand what local councils require before approving applications. You focus on what the written guidance means in practice and what is most likely to cause a refusal.
Property type and proposed works: {PROPERTY_CONTEXT}.
</context>

<paste>
[Paste the council's planning guidance, the application checklist, or the pre-application advice you received here.]
</paste>

<task>
**Translate** the guidance into what actually matters for this application:
1. The two or three criteria the council is most likely to use to assess this proposal
2. What the officer will be looking for in the supporting statement or design documents
3. The most common reasons for refusal for this type of application, and how to address them before submission
4. One thing the guidance implies but does not say plainly, that could trip the application up
</task>

<output_format>
- Assessment criteria: plain English, brief
- Supporting document guidance: one paragraph
- Common refusal reasons and pre-emptive responses: brief bullet points
- Implied requirement: one clear sentence
- Length: 250 to 350 words
- If the guidance is unclear on a critical point, name it and suggest raising it with the planning officer
</output_format>