The most frustrating planning portal mistake is not a dramatic one. It is the quiet, administrative kind. A homeowner uploads a PDF they believe is a valid location plan, submits the application, and then waits for the confirmation email. A few days later the authority comes back with a short note: the site cannot be identified properly, the scale is unclear, the file is not suitable for validation, or the red-line boundary does not cover the full application land.
When people search for a planning portal location plan, what they usually want is not a theory lesson about planning law. They want to know exactly what file the portal expects, what the map must contain, and how to avoid wasting another week at validation.
This guide answers that buying question directly. If you need the compliant file now, go straight to the site location plan page. If you also need the full map pack with the matching detailed plan, start on Ordnance Survey planning maps.
Need a planning portal location plan?
What does the planning portal expect from a location plan?
The short answer is that the portal expects a planning-compliant site location plan, not a general map screenshot.
For most householder and small commercial applications, that means a file that:
- Uses licensed Ordnance Survey mapping
- Shows the full application site edged in red
- Shows any other nearby land owned or controlled by the applicant in blue
- Includes a north point
- Includes a scale bar
- Uses the correct scale for the site, usually 1:1250
- Shows enough surrounding context to identify the site clearly
In other words, the planning portal is not just asking for "something that looks like a map". It is asking for a formal location document that the council can validate, publish, and cross-check against its own GIS systems.
That is why the quickest safe route is to buy a proper location plan for planning permission rather than trying to adapt a consumer map after the fact.
Quick checklist: the right file before you upload
| Portal requirement | What the officer is checking | Common failure |
|---|---|---|
| Correct map type | Is this a genuine location plan? | Applicant uploads a block plan or screenshot instead |
| Correct scale | Is it suitable for identifying the site? | File is too zoomed in or too zoomed out |
| Red-line boundary | Does it cover the full application land? | Driveway or access strip is missing |
| Context | Can the site be identified unambiguously? | Not enough road names or surrounding detail |
| Required map elements | North point, scale bar, OS wording present? | Missing basic validation elements |
| Clean upload file | Is the PDF legible and ready for review? | Low-resolution image, cropped page, unclear printing scale |
If those six points are right, the planning portal step becomes straightforward. If one is wrong, the application can stall before the design is ever reviewed.
What a planning portal location plan is actually for
Applicants sometimes assume the location plan is a lightweight upload step. It is not. It does real work within the validation process.
It identifies the land legally
The red line on the location plan helps define the land to which the application relates. If the wrong area is shown, the application can be ambiguous from the outset.
It helps the authority find the site in its own systems
Planning teams use GIS layers, aerial mapping, listed-building records, flood data, highway data, and previous planning history. The location plan is the bridge between your upload and those internal systems.
It supports consultation and publication
The authority needs a map it can publish and use to understand how the site relates to neighbouring land and roads. That is another reason consumer screenshots are not enough.
It sets the baseline for the rest of the submission
Your block plan, drawings, and supporting documents should all align with the same site boundary. If the location plan is wrong, the rest of the application pack becomes harder to trust.
Which scale should you use on the portal?
For most urban and suburban planning submissions, the standard answer is 1:1250.
That scale is typically right because it shows:
- The application site clearly
- Nearby roads and neighbouring plots
- Enough context for the authority to identify the land quickly
For rural or larger sites, 1:2500 may be more suitable. That is common where:
- The property is set back far from the road
- The access route is long
- A 1:1250 sheet does not show sufficient named-road context
- The site spans a broader parcel of land
The important point is not to choose the scale at random. The portal is not checking whether you know a technical rule by heart. It is checking whether the site can be identified clearly and measured reliably on a compliant map.
What the portal does not want you to upload
This is where many invalid applications begin.
Google Maps or Apple Maps screenshots
These may help you explain the location to a friend, but they are not the correct planning map document. They do not solve the licensing issue, and they are not prepared as planning-compliant location plans.
A block plan in place of a location plan
Applicants sometimes upload only the more detailed plan because it looks more informative. But a detailed 1:500 plan can still fail as the portal location document if it does not identify the site in its wider context.
A low-resolution image exported from another drawing
If the page is blurred, cropped, or clearly not intended as a standalone location plan, the upload can be challenged even if the boundary itself looks roughly correct.
A PDF that has been rescaled incorrectly
Printing or exporting at the wrong size can break the intended scale relationship. That matters because the officer needs to trust the scale bar and printed scale reference.
Quick checklist: the right file before you upload.
Upload traps that cause avoidable rejection
The map itself may be fine, but the uploaded file can still create trouble.
1. Cropping off the scale bar or north point
Applicants sometimes trim the PDF to "make it neat". In doing so, they cut off the exact elements the council needs to validate.
2. Uploading the wrong document under the wrong label
If the portal asks for a location plan and the applicant uploads the detailed block plan instead, the file may be legible but still wrong for that document slot.
3. Boundary mismatch across the pack
The portal might receive a location plan with one red line and a site plan / block plan with another. That inconsistency can trigger a validation query immediately.
4. Using a file that looked fine on screen but prints badly
The authority may view the file digitally, print it, publish it, or share it internally. If the file does not reproduce cleanly, that creates friction at validation.
5. Forgetting the access to the public highway
This is still the classic planning map error. If the route to the road is part of the application land or essential to accessing the site, it usually needs to be included within the red line.
Why councils reject location plans on the portal
When a planning portal location plan is rejected, it is usually for one of a small number of repeat reasons.
The site cannot be identified clearly
The map is cropped too tightly, there are too few surrounding reference points, or the scale is not suitable for the site context.
The map is not based on planning-compliant OS mapping
This is the licensing and suitability problem. A map that is fine for browsing may still be wrong for a planning submission.
The red line is incomplete
The house is shown, but the drive is not. The garden is shown, but the access strip is missing. The boundary stops short of the highway. These are common and very fixable errors.
Mandatory elements are missing
No north point. No scale bar. No clear scale reference. No OS wording. These are small omissions with big consequences.
The file does not match the rest of the submission
If the location plan boundary, block plan boundary, and application description do not line up, the council may stop the submission until the inconsistency is resolved.
The safest way to create the right file first time
If you want the portal-ready file without the back-and-forth, the safest route is:
- Open the site location plan workflow
- Search for the property using the address finder
- Review the surrounding context and property boundary overlay carefully
- Draw the red-line boundary to include the full application land and access
- Choose the scale that actually fits the site, usually 1:1250
- Download the compliant PDF with the north point, scale bar, and OS details already in place
If your application also includes building work, add the matching block plan or start from the broader planning map pack so both documents stay aligned.
Practical scenarios: which route should you take?
Standard house extension
Use a 1:1250 location plan for the portal and pair it with a 1:500 block plan for the detailed submission.
Loft conversion
The location plan still identifies the property for validation. You will usually need the detailed plan as part of the wider pack as well, especially where roof or site context drawings sit alongside the mapping.
Dropped kerb or altered access
Be especially careful with the red line and the connection to the highway. Access-based projects are where incomplete boundaries are often spotted.
Rural property
Check whether 1:1250 shows enough surrounding roads and context. If not, choose 1:2500 so the site can be identified clearly.
Architect-led project
Use the portal-ready location plan for the upload requirement, then add CAD planning maps if the design team needs editable base mapping for the rest of the pack.
FAQ: planning portal location plan
Q: Is a planning portal location plan the same as a site location plan?
A: Yes. In most cases the phrase "planning portal location plan" simply means the formal site location plan uploaded with the planning application.
Q: What scale should a planning portal location plan be?
A: Usually 1:1250 for urban and suburban sites. For larger or rural sites, 1:2500 may be more suitable if the site needs more surrounding context.
Q: Can I upload a screenshot from Google Maps to the portal?
A: No. A planning submission needs a compliant map prepared on licensed Ordnance Survey mapping with the correct scale and required map elements.
Q: Why did the council say my location plan was invalid?
A: The usual reasons are incomplete red-line boundaries, insufficient context, wrong scale, missing north point or scale bar, or uploading the wrong type of map for the portal requirement.
Q: Do I also need a block plan?
A: If the project includes building work, very often yes. The location plan identifies the site; the block plan shows the detailed site layout and proposal relationship.
Q: What is the easiest way to avoid upload mistakes?
A: Generate the PDF specifically for planning use, keep the page untrimmed, and order the location plan and any matching planning maps through the same workflow so the whole pack stays consistent.
Conclusion
If you are searching for a planning portal location plan, you do not need a generic map. You need a planning-compliant site location plan that identifies the site clearly, uses licensed OS mapping, shows the correct red-line boundary, and uploads cleanly without losing the required validation elements.
That is why the safest starting point is the site location plan page. If the application also needs the detailed site drawing, move straight from there into the broader planning maps pack so the portal upload and the rest of the submission stay aligned.
Create your planning portal location plan now and avoid losing time to preventable validation queries.