A planning map can look perfectly reasonable and still cause a delay if one small detail is wrong. The address may be correct but the red line may omit the access. The scale bar may be present but the PDF may have been printed or exported at the wrong size. The block plan may show the extension accurately while the application form describes a different site.
This checklist turns the final review into a repeatable process. It is useful for homeowners, designers, builders and anyone submitting a planning application who wants to catch mapping issues before the validation team does.
A final side-by-side review helps catch boundary, scale and version inconsistencies.
1. Check the identity of the site
Start with the basic question: would another person be able to identify the correct property without asking you for help?
Review the property number or name, road, locality and surrounding road names. Compare the map with the address in the application form. Pay particular attention to corner plots, flats, new developments, rural properties and properties with long or shared access.
If two buildings could plausibly match the description, the plan needs more surrounding context or clearer site emphasis. A map should remove uncertainty, not make the reader infer which building you mean.
2. Check the red-line boundary
The red line defines the application site. It is one of the highest-priority checks because it affects the meaning of the entire application.
| Boundary question | Check |
|---|---|
| Does it include the land needed for the proposal? | Include the relevant garden, access, parking or works area. |
| Does it match the form? | Compare the drawn extent with the description and site address. |
| Is it closed and legible? | Avoid gaps, overlaps or a line hidden by labels. |
| Is it consistent elsewhere? | Repeat the same boundary on all relevant plans. |
| Does it wrongly include unrelated land? | Remove land that is not part of the application. |
Do not assume that the red line should surround only the new wall or building. The correct extent depends on the proposal and the land to which the application relates.
3. Check the map type and scale
Use the plan for the question it needs to answer. A location plan shows the site in its wider setting. A block or site plan shows the detailed arrangement of the plot.
| Plan | Typical use | Main question |
|---|---|---|
| Location plan | Wider context | Where is the site? |
| Block plan | Detailed site context | What is around the proposal? |
| Proposed site layout | Design arrangement | What will change on the plot? |
The exact scale depends on the authority and the site, but the plan must remain readable. If a scale bar is present, check that it remains accurate after export, resizing or printing. Never assume that “Fit to Page” preserves scale.
4. Check access and movement
Look beyond the building footprint. Many applications affect how people, vehicles or services reach the site.
Check for:
- the public road or route leading to the property;
- driveways and shared access strips;
- gates, parking and turning areas;
- proposed dropped kerbs or changes to visibility;
- footpaths or cycle routes where relevant; and
- access needed for construction or servicing.
If the access is long or the property is rural, a single view may not show everything well. Use a wider location view and a more detailed plan where necessary. The important point is to make the route understandable without making the detailed site impossible to read.
5. Check existing and proposed features
The planning map should give the reader a dependable base for the design drawings. Compare the existing house, garages, sheds, walls, fences, hedges, trees and hardstanding against the drawings and photographs.
Then check the proposed footprint. Is the extension on the correct side? Is the outbuilding in the right corner? Does the new access start where the plan says it does? Small positional differences can undermine confidence even when the overall proposal is clear.
Avoid adding features that have not been verified. A map is evidence, so clarity is more valuable than decoration.
6. Check labels and presentation
Labels should explain the plan rather than compete with it. The red boundary, north point, scale bar and key site features should be easy to find. Remove notes that cover buildings, boundaries or road names.
Use a consistent visual language across the pack. For example, make existing features neutral, proposed features distinct and the application boundary prominent. Keep the page title and file name descriptive so the correct document is easy to select in an online portal.
7. Check the PDF itself
Open the final PDF on screen at normal size, zoom in to inspect detail and print a test page if the authority requires a printed pack. Check that:
- the page is not blank or clipped;
- the red line has not disappeared during export;
- text and map labels are legible;
- the scale bar is still present;
- the PDF opens without a password;
- the file name identifies the plan type; and
- the file size is acceptable for the portal.
Do not rely on the file preview alone. A preview can hide missing layers, clipping or an incorrect page size.
8. Compare the complete application
The final check should be comparative, not isolated. Put the form, location plan, block plan, proposed layout and drawings side by side. Use the same questions for every document:
| Item | Location plan | Block plan | Drawing/form |
|---|---|---|---|
| Site address | Correct? | Correct? | Matches? |
| Red boundary | Present? | Same extent? | Described consistently? |
| Proposal position | Context shown? | Accurate? | Same footprint? |
| Access | Visible if relevant? | Detailed? | Described? |
| North and scale | Present? | Present? | Dimensions agree? |
This catches the errors that a single-document review misses.
Frequently overlooked issues
Some problems appear repeatedly because they happen late in the process:
- The map was ordered before the final site boundary was decided.
- The designer moved the proposal but the original plan was not updated.
- The PDF was renamed incorrectly and uploaded in the wrong portal slot.
- A title plan was used where a current licensed planning map was required.
- The map was cropped to save space and no longer shows the access route.
- A boundary or tree is visible in the photograph but absent from the plan.
- A map created for an earlier application was reused without checking its date and context.
A five-minute final routine
If time is limited, do these five checks in order:
- Point to the exact site and confirm the address.
- Trace the red line and ask what land it includes and excludes.
- Follow the access from the road to the proposal.
- Compare the proposed footprint with the latest drawing.
- Open the final PDF and confirm scale, north point, legibility and file name.
If any answer is uncertain, pause the upload and resolve it. The planning map pack workflow can help keep the core map information aligned, while the site location plan guide and block plan guide explain the purpose of each view.
Final thought
Good planning-map evidence is not about producing the busiest-looking page. It is about making the site, boundary and proposal easy to verify. A short, disciplined quality check can prevent a disproportionate amount of back-and-forth later.
Build the check around authoritative requirements
The national starting point is consistent: the Planning Portal says most applications require a location plan and a site or block plan, while each authority can set relevant local information requirements. The Portal’s map guidance describes typical location-plan scales of 1:1250 or 1:2500 and site-plan scales of 1:200 or 1:500. It also distinguishes the red application site from other nearby land in the applicant’s ownership shown in blue.
Turn that guidance into a small source-of-truth table for the project:
| Decision | Controlling source | Evidence to retain |
|---|---|---|
| Required document types | Current LPA validation list | Saved page or PDF and access date |
| Application boundary | Agreed proposal scope and access | Approved red-line sketch or issue note |
| Ownership certificate | Applicant’s actual ownership/notice position | Completed form and adviser confirmation |
| Drawing revision | Latest design issue | Drawing register or transmittal |
| Scale and paper | LPA requirement and legibility | Original PDF and print check |
This makes the review auditable. If somebody asks why a plan was included or why land was edged red, the answer is recorded rather than reconstructed from memory.
Separate facts, design proposals and legal conclusions
Strong evidence packs label what is known. Existing features should come from current mapping, site checks, surveys or photographs. Proposed features should match the latest design. Legal boundary conclusions should not be inferred from the thickness of a map line.
HM Land Registry’s boundary guidance warns that title plans usually show general boundaries rather than their exact legal position. If a proposed wall relies on a few centimetres of clearance, the map is a starting reference—not a substitute for the right survey or legal advice.
Check the failure path before submission
Imagine the authority says the application is invalid. Could you quickly identify which requirement they believe is unmet, locate the exact PDF submitted and compare it with the source drawing? If not, the pack needs better version control.
The Planning Portal notes that after submission, a site boundary cannot simply be edited in place; the applicant must go through the relevant amendment and resubmission process. That makes the final red-line check disproportionately valuable.
Questions an expert reviewer asks
- Could a person unfamiliar with the address locate the site from the page alone?
- Does the red line include land necessary to carry out and access the proposal?
- Are ownership implications reflected consistently in the certificate and notices?
- Does every report refer to features that can actually be found on a drawing?
- Are proposed and existing conditions visually distinct?
- Has the final exported file—not just the design workspace—been checked?
- Would the plan still make sense if printed in greyscale?
These questions go beyond a cosmetic checklist. They test whether the documents form one coherent account of the proposal, which is the real purpose of a pre-submission review.