What to put in a planning application covering letter

A covering letter is not a formality on a portal submission, and it is not a report type PlanScope generates. It is a short document you write yourself, and it does one job: it tells the validation officer what has been sent, so the application is registered rather than held in a queue with a query. The case officer reads it afterwards, which makes it also the first opportunity to explain anything odd about the submission before they find it themselves.

Keep it to one or two pages. Everything that argues the policy case belongs in the Planning Statement instead.

Why it still matters on a portal submission

The validation officer and the case officer are usually different people with different jobs. Validation checks that the national and local information requirements have been met, that the fee is right, that the certificates are completed and that the drawings carry the numbers referred to in the forms.

Most validation queries are administrative. A drawing referenced on the form but not uploaded. A fee calculated on the wrong floor area. A certificate signed by the agent where notice should have been served on a leaseholder. Each generates an email, and each email costs a week.

A letter that lists what has been sent and pre-empts the obvious questions removes most of those exchanges. The letter is also on the public register, so anyone reading the file later, including an inspector, sees it.

Identifying the application and the fee

Open with the facts, in a block the validation officer can check against the form:

1. Site address and, where the site has no postal address, the national grid reference or the nearest postcode with a description.
2. The application type in the words the authority uses, for example householder application for planning permission, or full application for planning permission.
3. The description of development, word for word as entered on the form.
4. The applicant's and agent's names, and who correspondence should go to.
5. The fee, the amount, how it was calculated and how it was paid.
6. Any related applications, with their references, including a linked listed building consent or advertisement consent.

Where the fee calculation is unusual, show the working in a sentence. A fee based on a site area of 0.42 hectares, or on 148 square metres of new floorspace, can be checked in seconds if you state the figure and where it comes from.

Listing the documents so validation is straightforward

This is the part of the letter that earns its keep. Set out every document and drawing with its title, its drawing number and its revision, in the order you want them read.

Group them: application forms and certificates, plans and drawings, then supporting documents. Use the exact file names where the portal displays them, because a validation officer working from a file list cannot match "proposed plans" to "P-103 Rev C" without asking.

Where a document on the authority's local list has not been provided, say so in this section rather than leaving a gap. Give the reason and, if you have one, the reference of the email in which an officer confirmed it was not required. That single line prevents an invalidation.

Flagging pre-application advice

If there was a pre-application enquiry, give its reference and the date of the response, then summarise in three or four lines how the scheme responds to the advice.

Do not reproduce the advice. Say what the officer asked for, what changed, and where in the submission the change is shown. Where the advice has not been followed, say that too, with the reason in one sentence. Officers notice a silent departure and treat it as evasive, and there is nothing wrong with a reasoned disagreement stated plainly.

Where a Planning Performance Agreement or a formal note of meeting exists, reference it and attach it if the authority expects that.

Explaining anything unusual before the officer finds it

The purpose here is to control how a discrepancy is read. A few examples of things worth a sentence:

1. A red line boundary that includes a strip of adopted highway because access works are proposed.
2. Ownership certificate B, with the date notice was served and on whom.
3. A site area that differs from the area on an earlier application, with the reason.
4. A survey drawing dated two years ago, with a statement that nothing has changed on site.
5. An existing building shown differently from the council's records, with an explanation such as an unauthorised outbuilding since removed.
6. A technical report prepared for a previous application and resubmitted, with a note on why it remains valid.

Anything that would otherwise look like an error is better explained by you than discovered by someone else. And where a document is deliberately short, for example a brief heritage note because the nearest listed building is 80 metres away behind a barn, say why.

What not to put in the letter

Four things belong elsewhere or nowhere.

The policy case. A covering letter that argues the tilted balance is a Planning Statement in the wrong place, and the argument gets lost. Our note on a planning statement for a Green Belt householder extension shows the difference in structure.

Personal circumstances that are not material, and any that are should be set out deliberately in the Planning Statement with an explanation of their relevance.

Comments about neighbours or previous disputes. The letter is published, and a paragraph about a boundary argument invites the objection it was meant to pre-empt.

Confidential or sensitive information of any kind, including anything about the occupants of the property, because the letter goes onto a public register and stays there.

A short worked structure

The following outline is illustrative, and the lengths are a guide rather than a rule.

A one-line heading with the site address and the application type. A first paragraph identifying the applicant, the description of development and the fee. A second paragraph giving the pre-application reference and the response to advice. A list of enclosures grouped as forms, drawings and supporting documents, with numbers and revisions. A short section headed with a neutral label such as matters to note, covering the discrepancies and the local list items. A closing sentence confirming who to contact and confirming the applicant's willingness to discuss amendments.

One more point on tone. A covering letter written as a list of facts reads better than one written as advocacy, and it is quicker for both officers to use. Resist the temptation to describe the scheme as high quality or policy compliant, because neither statement helps validation and both will be tested elsewhere.

Two habits worth adopting. Write the enclosure list last, generated from the portal upload screen rather than from your project folder, because those two lists diverge. And read the authority's validation checklist alongside the letter before submitting, item by item.

Where several documents are needed, the PlanScope report index sets out the 66 report types by category so you can check which ones the project engages before the letter is written. For most householder and minor applications the answer is a Design and Access Statement where one is required, a Planning Statement, and the technical items on the local list.

This is general guidance, not legal advice. Check your authority's published validation requirements before submitting. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.