A pre-application meeting is only as useful as the preparation that precedes it. The planning record — comparable consents, refusal patterns, enforcement history, conservation constraints — is the foundation of any intelligent pre-application submission. Most of it is inaccessible to standard portal searches. Here is what to look for and why it matters before you draw a line.
A client brief tells you what they want. The planning record tells you what the LPA will accept, what it has consistently refused, and what constraints bind the site regardless of the design approach. These are different things — and confusing them is the most common source of wasted pre-application time and abortive Stage 1 fees.
The specific information that shapes a pre-application position includes: comparable applications approved within the postcode cluster and the officer wording applied to them; comparable refusals and the specific policy tests used to refuse; any withdrawn applications on the subject site itself (which reveal the LPA's informal position without a formal record); enforcement history; and conservation or heritage constraints that are material but sit outside the portal.
Planning decisions are not consistent. What one conservation officer approved on a similar site two years ago is directly relevant to what a current case officer will accept today — and citing it correctly changes the nature of the pre-application meeting. But comparable decisions are only useful if you can find them, and finding them requires full cluster analysis across all applications in the surrounding postcode area, including applications that may have been withdrawn, refused and re-submitted, or decided under a predecessor authority.
Standard portal searches return results for the subject property and, at best, a handful of nearby applications visible in the public interface. This is not cluster analysis. A proper cluster sweep retrieves every application — approved, refused, withdrawn — across the full postcode cluster, with officer wording extracted for the most relevant comparables. That is the difference between knowing what the LPA has done and hoping.
A withdrawn application does not result in a formal decision. It does not appear on a CON29 search. It may or may not be findable through the standard portal search interface depending on the council's system. But it is often the most revealing intelligence on a site: an application that was withdrawn because the applicant knew the LPA was going to refuse tells you exactly where the policy boundary sits, without a formal refusal on the record.
Conservation area designation, listed building adjacency, Article 4 Directions, AONB boundaries, heritage setting case law — these constraints shape the design brief before Stage 1 begins. Some are visible in the planning portal. Many are not. Land Registry title constraints, in particular, sit entirely outside the planning portal and are only accessible through direct title register analysis.
A 1949 National Trust covenant or a 1982 Secretary of State restriction in the title register is material to any development proposal on an AONB site. It is also invisible to any standard planning search. We retrieve it as part of every site intelligence report.
An enforcement notice on the subject site, or on comparable properties in the cluster, changes the design brief in ways that a client rarely anticipates. A site with unresolved enforcement history may have constraints on permitted development, on use class, or on the lawfulness of existing works that are material to any extension, conversion or new build proposal.
Pre-merger enforcement history — from councils that were reorganised or merged before current portal systems were implemented — is particularly inaccessible through standard searches and particularly relevant for rural and coastal sites where planning history goes back decades. We retrieve it.
A site intelligence report is most useful between client instruction and the pre-application meeting. It tells you what comparable sites have been approved for, what the LPA has refused and why, and what constraints sit on the site that will shape the design brief. It takes 48 hours to deliver and costs £149–249 — less than one day of your practice's time.
The report can be used in three ways: as briefing material for your own preparation; as a document presented to your client as part of your feasibility service (white-label versions available); or as the evidential basis for a pre-application submission that cites comparable precedent directly.
Tell us the postcode and what you need to know. We scope the report and confirm turnaround. Payment by Stripe before we start. White-label available.
Commission a report →