The subject line usually lands after the hopeful part of the application process has already begun. The fee is paid. The portal says submitted. The applicant has told themselves the hard part is over. Then the council reply arrives: the application is invalid because the maps are incomplete, inconsistent, unclear, or not prepared to the required standard.
That message feels bigger than it is. In many cases, the council is not saying the proposal itself is unacceptable. It is saying the submission pack cannot yet be processed because the location plan, block plan, or related mapping documents do not meet validation requirements.
This guide is written for the recovery stage: the moment you need to work out exactly what to fix and re-upload. If you already know the wider context map is the problem, start with the site location plan. If the issue is the detailed site drawing, go to the block plan. If you want the safest route to rebuild the pack together, start on Ordnance Survey planning maps.
If your council rejected a location plan or block plan, this guide shows the exact map problems to fix before you resubmit and lose more time.
What should you fix first after a map rejection?
The short answer is: do not guess and do not redraw everything blindly.
Start by identifying which of these five failure types the council is pointing at:
- The red-line boundary is wrong or incomplete
- The wrong map type or scale was uploaded
- The file is not on the correct OS mapping base
- The plan is missing key validation elements such as scale bar or north point
- The map pack is internally inconsistent
Once you identify which category applies, the fix is usually straightforward. The expensive part is not the map itself. It is the delay caused by re-uploading the wrong correction.
Fast diagnosis table: invalid reason and likely fix
| Rejection clue from the council | What it usually means | Most likely fix |
|---|---|---|
| "Boundary incomplete" or "red line does not include access" | The application land has been drawn too tightly | Rebuild the site location plan boundary and keep it consistent across the pack |
| "Site cannot be identified" | Wrong scale or insufficient context | Regenerate the location plan at the right scale, often 1:1250 or 1:2500 |
| "Block plan required" or "detailed site plan missing" | Only the wider map was supplied | Add the block plan at 1:500 |
| "Map not suitable" or "base map unacceptable" | Wrong source or licensing problem | Replace screenshots or informal plans with compliant OS-based mapping |
| "Inconsistent plans" | The location plan, block plan, or application form do not align | Rebuild the pack through one planning maps workflow |
Do that diagnosis first. It stops a vague rejection from turning into another vague fix.
Rejection reason 1: the red-line boundary is wrong
This is the most common map failure and the most important one to fix properly.
What the council is reacting to
The authority believes the application land has not been defined correctly. That might mean:
- The boundary only wraps the new extension instead of the wider planning unit
- The driveway or access strip is missing
- The line stops short of the public highway where access matters
- The boundary differs between the location plan and block plan
Why it matters
The red line is not decorative markup. It helps define the land to which the application relates. If that is unclear, the authority cannot confidently validate the submission.
What to do now
Rebuild the boundary carefully:
- Start from the wider site location plan
- Include the full application land, not just the new works
- Include access to the road where relevant
- Mirror the exact same boundary on the block plan
If you own nearby land not included in the application, review whether it should be edged in blue as well.
Rejection reason 2: the wrong map type or scale was uploaded
Applicants often think in terms of "a map". Councils think in terms of map purpose.
Common mistakes here
- Uploading a block plan where the portal wanted the wider location plan
- Uploading only the location plan when the application also needs a detailed 1:500 site plan
- Using 1:1250 where 1:500 detail is needed
- Using a tight 1:1250 plan on a rural site that really needs 1:2500
Why it matters
Each planning map answers a different question:
- The location plan says where the site is
- The block plan says how the site is arranged and what sits where
If the wrong question is being answered, the map may be technically legible but still invalid for the document requirement.
What to do now
Check whether the rejection is actually telling you one of these:
- "You supplied only one of the two normal maps"
- "You supplied the detailed plan in the location plan slot"
- "You used the wrong scale for the site"
Then rebuild the missing or incorrect file rather than re-uploading the same document under a different label.
Rejection reason 3: the map is not on the right base mapping
This is the classic "Google Maps problem", but it includes more than that.
The issue
The map is not prepared on suitable licensed Ordnance Survey mapping for a planning submission. The authority may phrase this as:
- unacceptable base map
- no OS copyright or licence wording
- map not suitable for planning use
Why it matters
Planning maps are formal submission documents. The council expects a map source that is both suitable and licensable for that context.
What to do now
Replace the map with a compliant OS-based file rather than trying to decorate or annotate the rejected one. If the wider site reference is the problem, generate a fresh site location plan. If the detailed file is wrong too, rebuild the pair through Ordnance Survey planning maps.
Rejection reason 4: mandatory validation elements are missing
Sometimes the map is broadly right, but small missing details make it invalid.
Typical missing elements
- No north point
- No scale bar
- Scale unclear or broken by bad export/printing
- Not enough surrounding context to identify the site
- Road names or orientation cues missing
Why it matters
Validation officers are not being pedantic for the sake of it. They need to be able to orient themselves, trust the scale, and understand the site without making assumptions.
What to do now
Do not manually crop or "tidy up" the PDF. Regenerate the compliant file with the required elements intact. This is especially important where the rejection suggests the plan looked acceptable at first glance but still failed basic validation.
Fast diagnosis table: invalid reason and likely fix.
Rejection reason 5: the pack is internally inconsistent
This is the failure mode people least expect, because each document may look fine on its own.
Typical inconsistencies
- The red line on the location plan differs from the block plan
- The block plan shows a different access arrangement from the rest of the submission
- The site description on the application form does not match the mapped land
- The proposal shown on the detailed plan conflicts with other drawings
Why it matters
Planning officers and validation teams need the application pack to tell one coherent story. If one document says "this land" and another says "that land", the authority cannot safely proceed.
What to do now
Rebuild the pack from one source of truth. In practice that often means:
- Confirm the correct boundary on the location plan
- Mirror it on the block plan
- Check the application description against both
- Replace mismatched files rather than mixing old and new versions
Re-submission checklist: fix the pack before you upload again
Before re-uploading, run through this list in order:
- Confirm the exact council wording describing the invalidity
- Decide whether the issue is boundary, scale, base mapping, missing elements, or inconsistency
- Regenerate the correct site location plan if the wider site reference is affected
- Regenerate the block plan if the detailed layout document is affected
- Check that both maps use the same red-line boundary
- Check that the access to the public highway is included where required
- Review the whole pack together before uploading, not each file in isolation
This sounds basic, but it is the difference between one corrective upload and a second invalidation.
What not to do after an invalid notice
Applicants often lose more time by over-correcting than by fixing the exact issue.
Avoid these reactions:
- re-uploading the same file under a different label
- mixing a newly corrected location plan with an old block plan where the boundary affects both
- cropping or annotating the PDF manually when the real issue is scale, context, or map suitability
- redrawing the whole site from memory without checking the specific council wording first
The safest correction is targeted. Fix the precise failure, then review the whole pack once before you submit again.
Real scenarios: what usually fixes the problem?
"The council said the red line does not include access"
Rebuild the location plan boundary and make sure the same change appears on the detailed site plan as well.
"The portal says a block plan is missing"
The wider map alone is not enough. Add the block plan rather than re-uploading the same location plan twice.
"They said the map is not acceptable for planning purposes"
That is usually a base-mapping or format problem. Replace informal or screenshot-based maps with compliant OS-based planning maps.
"They said the site cannot be identified properly"
Review the scale and surrounding context. A rural or larger site may need a wider location plan.
"They said the plans do not match"
Treat it as a full-pack problem, not a single-file problem, and rebuild the pack so the boundaries and site story align.
FAQ: fixing rejected planning maps
Q: Does an invalid map mean the planning application is refused?
A: No. Usually it means the application is not yet valid for processing. The design itself may not have been assessed at all.
Q: What is the most common reason councils reject planning maps?
A: Red-line boundary problems are among the most common, especially where access to the highway or the full site extent is missing.
Q: If the location plan is wrong, do I need to replace the block plan too?
A: Often yes, because both documents need to show a consistent site boundary. Check the pack together, not just the single rejected file.
Q: Can I just annotate the old PDF and re-upload it?
A: Sometimes minor issues can be corrected, but where the council has questioned the boundary, scale, or base map, the safer route is usually to regenerate the compliant file properly.
Q: What is the fastest way to avoid a second invalidation?
A: Rebuild the correct site location plan and block plan from one workflow, check them side by side, and only then re-upload.
Q: Should I order a full pack again?
A: If the rejection points to wider inconsistency, yes. Rebuilding through Ordnance Survey planning maps is often faster and safer than trying to patch a mixed set of old files.
Conclusion
If your council rejected the maps, the right response is not panic. It is diagnosis. Most planning map rejections fall into a short list of repeat problems: wrong boundary, wrong map type, wrong scale, wrong base, or inconsistent pack.
Fix the correct problem, rebuild the correct file, and keep the wider map and detailed plan aligned. That is why the quickest recovery route usually starts with the site location plan, the matching block plan, or the full planning maps pack if the whole submission needs tightening up.
Fix your planning maps now and get the application back into validation instead of back into limbo.