A pre-application meeting is not a blank sheet. The council already has a position. Officers have approved, refused and conditioned dozens of applications in the same postcode cluster — and that history tells you, before you walk in, what arguments they have accepted and what they have consistently refused. Knowing that picture changes what you say in the room.
A postcode cluster pull gives you the full history of planning decisions in the immediate area — not just for the site in question, but for every comparable property within the cluster. That history tells you several things a standard search will not. First, the weight the LPA has actually given to the policies it applies — not the policy as written, but the policy as applied in decisions you can cite. Second, the specific conditions attached to approved applications — which means you know, before the meeting, what the council is likely to require if it approves. Third, any pattern of withdrawals that signals where the authority draws a line it will not cross without significant evidence.
For planning consultants, that intelligence does not change the legal position. It changes the preparation — the specific wording in your heritage assessment, the comparable you cite, the concession you are willing to offer on materials. Those are the details that move a pre-app outcome from a blocking response to a manageable one.
Officers do not volunteer the information that a similar application was withdrawn five years ago, ahead of what looked like an inevitable refusal. That withdrawal is not indexed by most portal search tools. But it exists in the database — and it tells you that the council considered that type of development on a comparable site and concluded it would fail. That is precisely the intelligence that shapes a credible pre-application submission.
We retrieve withdrawn applications as part of every cluster pull. For planning consultants, the withdrawn application history is often the most telling part of the picture — because it shows the attempts that did not get as far as a decision, and the reasons they were pulled.
When an officer approves an application in an AONB, the officer report does not just say yes. It explains the weight given to the landscape impact, the justification for the exception to the general policy, the conditions imposed and why. That language — that specific reasoning pattern — is what you replicate in your own submission for a comparable application.
We extract officer wording from committee reports where they exist, and include the relevant sections in the site intelligence report. For planning consultants building a heritage or landscape case, the officer reasoning from a comparable approved application is often worth more than any amount of general policy analysis.
We pull every approved, refused and withdrawn application in the postcode cluster — including officer wording and committee minutes. Delivered 48 hours before your pre-application meeting.
Commission a pre-application intelligence report →Download a sample planning intelligence report. Real case, anonymised.
See sample reports →