A council's “local plan” is not always one document. A property may be affected by an adopted borough or district plan, a strategic plan, a made neighbourhood plan and other development-plan documents. Separate policy maps and supplementary guidance can contain information you need to understand the proposal.
This guide shows how to assemble a usable policy file for a property in England. Use it before commissioning a design or preparing an application statement, and refresh it before submission because plan status can change.
1. Confirm the planning authority for the site
Start with the exact address and site boundary. A postal town or a nearby council's name is not enough. Check the authority's planning service and any special planning boundary affecting the site.
In London, a development corporation can have planning responsibilities within a defined area. The Ealing profile, for example, explains why the Old Oak and Park Royal Development Corporation boundary matters. Do not assume every Ealing postal address is handled through the same policy and application route.
The local-plan directory links to our council profiles and their official sources. These are research starting points; the authority's adopted documents and maps are the evidence to carry into a project file.
2. Open the adopted development-plan register
Find the council's page identifying its adopted development plan. Record the title, version or adoption date and link for each relevant document. Check whether a newer document replaced the whole previous plan or only specified policies.
Section 38(6) of the Planning and Compulsory Purchase Act 2004 sets the development-plan starting point for relevant determinations, unless material considerations indicate otherwise. That makes document status consequential: a consultation draft and an adopted policy are not interchangeable.
A plan's end year is not, by itself, proof that it has ceased to be the adopted plan. Equally, an old PDF found through a search engine may have been superseded. Resolve status against the authority's register, adoption statement and replacement-policy information.
3. Keep document types distinct
| Document | How to use it |
|---|---|
| Adopted local or strategic plan | Identify the policies forming part of the development plan and their geographic scope |
| Adopted Supplementary Plan under the new system | Forms part of the development plan; check its adopted status and scope separately from an SPD |
| Made neighbourhood plan | Check whether the property falls within its area and which policies apply |
| Adopted policies map | Locate designations and allocations, then read the associated policy wording |
| Emerging plan | Record its exact stage and consider weight in the context of current national policy |
| Supplementary planning document or design guidance | Use its detailed guidance with the policies it supports; do not label it an adopted local-plan policy |
| Evidence study or consultation response | Understand the evidence or issue; do not assume the document itself sets adopted policy |
The government's plan-making guidance explains the roles of plans and supporting documents. For plans prepared under the new system, use the government’s new-system guidance. Its statutory Supplementary Plans are distinct from the older supplementary planning documents. Our local-plan examinations guide covers submission, examination and modifications in more detail.
4. Check the map at the actual site boundary
Turn on relevant policy layers, identify the property and save the map reference or an appropriate extract with its date. Then open the policy or allocation linked to each designation. A coloured area alone does not tell you what development is acceptable.
A useful record might include a conservation area, a site allocation, an employment designation or a town-centre boundary. Other constraints may be recorded in separate official systems. Check the council's heritage information, Article 4 directions and relevant environmental evidence rather than assuming the policies map contains everything.
Do not treat a profile's summary as a property-level constraint search. An allocation covering a larger site can also have requirements that cannot sensibly be applied to one plot in isolation.
5. Build a short policy-to-design checklist
For each issue, record the policy reference, the relevant requirement, the evidence needed and the design response. Keep quotations short and preserve links to the complete wording, including exceptions and supporting text.
| Example issue | Project evidence | Design question |
|---|---|---|
| Neighbour amenity | Measured plans, sections and relevant window positions | How does the proposal affect privacy, daylight and enclosure? |
| Character and heritage | Site photos, street context and any relevant designation | How do scale, roof form and materials respond to the setting? |
| Access and servicing | Existing and proposed access arrangements | Can the site operate acceptably under the relevant policies? |
These are hypothetical checklist entries, not a universal application-document list. A modest extension and a new housing site require different levels of assessment. The validation guide explains how to distinguish required submission information from the merits of the proposal.
6. Record emerging policy without calling it adopted
Open the council's current progress or examination page. Record whether the plan is being consulted on, submitted, examined, modified or adopted. An Inspector's report, committee recommendation or scheduled adoption meeting is not the same event as adoption.
Where dates conflict, prefer the relevant dated primary record and make the unresolved point explicit. A timetable is an intention and may change. Do not turn a target adoption month into a completed milestone.
Read the current National Planning Policy Framework alongside the development plan. Our NPPF guide explains the current framework and why its decision-making and plan-making provisions need to be distinguished. Avoid carrying paragraph numbers or policy tests forward from an older edition without checking them.
A practical handover file
Give your designer the confirmed planning authority, adopted document list, relevant maps, policy checklist, emerging-plan status and a list of unresolved questions. Include a “checked on” date and links so someone else can reproduce the research.
For example, an Ealing project file should not simply say “use Ealing Local Plan 2026” because a plan title or horizon contains that year. It should identify the adopted documents relevant to the site, check the emerging replacement separately, and resolve any OPDC boundary issue. The source-checked Ealing profile shows that separation.
Update the file if a plan is adopted, revised drawings materially change the proposal, or the application remains undecided through a policy change. Pre-application advice can help identify important local issues, but it does not replace the eventual planning decision.
Sources and review
The linked legislation, national guidance and Ealing profile sources were checked on 8 September 2026 with AI assistance. This is a method for organising policy research, not a site-specific conclusion that a proposal complies with the development plan.