Convert a planning refusal into a point by point response strategy
Take a refusal notice and produce a table of every reason cited, what would answer it, and which drawing needs to change.
by Don black · published Sep 6, 2026
A refusal notice is written to be defensible, not to be actionable. Reasons are compressed into planning language and often bundle three separate objections into one paragraph. This splits them apart, ties each to the policy actually cited, and says plainly what evidence or drawing change would address it. The value is in separating the reasons you can design around from the ones you cannot.
Tools / stack
Inputs required
The refusal notice as text or PDF, plus the relevant local plan policies if you have them
Steps
- 1.Extract every numbered reason for refusal verbatim, without paraphrasing.
- 2.Split any reason that contains more than one distinct objection into separate rows.
- 3.For each row, quote the policy reference cited and state in plain language what it requires.
- 4.Classify each as design change, evidence gap, or fundamental. Fundamental means no drawing revision will fix it.
- 5.For design change and evidence gap rows, state the specific action and which drawing or document it lands on.
- 6.Rank the rows by how much of the refusal they carry, so the response effort goes where it counts.
Expected output
A table with reason number, verbatim text, policy cited, classification, proposed response, and owning drawing or document
Golden Example
Refusal notice with four numbered reasons, one of which bundles overlooking, massing, and materials into a single paragraph
Six rows returned after splitting. Overlooking classified as design change tied to the first floor plan, massing as design change on the section, materials as evidence gap needing a supplementary schedule. The parking reason classified fundamental because the shortfall is absolute