A cover letter structure for a planning submission

A planning submission cover letter has one primary reader and one secondary reader, and they want different things. The validation officer opens it first and uses it to check that every document on the council's list is present and correctly named. The case officer reads it second and uses it to work out what the application is, what has already been agreed, and what you are asking for. A letter that serves both is two pages long and contains almost no argument.

Keep the policy case in the Planning Statement. The cover letter is an administrative document that happens to set the tone.

What the letter is for and who reads it

Validation is a separate function from assessment in almost every authority, often carried out by a technical support team working from a checklist. Their questions are mechanical: is the fee correct, is the right form used, are the ownership certificates signed, are the drawings scaled and numbered, is the description consistent.

Answer those questions in the letter and validation gets faster. Every day saved at validation is a day earned on the eight-week or thirteen-week clock, which only starts once the application is valid.

The case officer's opening question is different: what am I looking at, and has anyone here seen it before. Tell them in the first paragraph. Site address, applicant, description of development as written on the form, application type, and the pre-application reference if there is one.

The document schedule and version control

This is the part of the letter that does the most work. List every document you are submitting, in a table, with its title, its drawing or document number, its revision letter and its date.

Three rules make the schedule useful. Number every drawing, including the location plan, because a decision notice lists permissions by drawing number and an unnumbered drawing cannot be conditioned cleanly. Use revision letters and keep the revision on the drawing itself as well as in the schedule. And never submit two versions of the same drawing, even where the earlier one is marked superseded, because the council will upload both and an objector will comment on the wrong one.

Match the document titles to the council's validation checklist wording where you can. If the checklist asks for a "Biodiversity Net Gain statement and metric" then use that phrase, even if your own file is named something else.

Describing the development consistently

The description of development has to be identical in four places: the application form, the cover letter, the fee calculation and the site notice the council will draft from it. Any inconsistency is a validation query.

Write it as a single sentence, in the present tense, naming the works and the resulting use. Include the demolition if there is demolition. Include the number of units if there are units. Avoid marketing language, avoid "high quality", and avoid the word "sustainable", all of which invite an officer to test the claim.

Where you want flexibility, build it into the description deliberately. "Up to 42 dwellings" gives you a ceiling. "Erection of 42 dwellings" gives you an obligation. On an outline application, state which matters are reserved in the description itself, because the decision notice will reproduce it.

One practical trap. If the description changes during the application, the council may need to reconsult, which adds three weeks. Getting it right at the front is cheaper than being flexible later.

Referring to pre-application advice

Where you have had pre-application advice, cite it properly: the reference number, the date of the written response, the officer's name if the advice was in writing, and any meeting dates.

Then do the useful thing, which is a short table setting out each substantive point the officer raised and how the submitted scheme responds. Three columns: the advice, the response, and the document where the evidence sits.

This does two things. It shows the officer that the advice was taken seriously, which matters because pre-application charging regimes are justified on the basis that they speed determination. And it protects you where you have declined to follow a piece of advice, by putting your reason on record at the outset rather than in a defensive email four weeks later.

Be straightforward about disagreement. "The officer advised a two-storey element to the rear. The scheme retains three storeys, because the daylight assessment at appendix 4 shows no breach of the guidelines and reducing the height would lose two of the affordable units." That is a professional response. Silence on a point the officer raised is not.

Flagging constraints and how they are addressed

List the constraints affecting the site and, against each, the document that deals with it. Flood zone, conservation area, listed building within a stated distance, Tree Preservation Order, Air Quality Management Area, Article 4 direction, protected species records.

The officer will run the constraint check anyway. Doing it first and openly saves a round of correspondence and signals that nothing has been left out. It also catches your own gaps: a constraint with no document against it is a validation refusal waiting to happen.

Where a constraint does not require a report, say why in one line. "The site lies within Flood Zone 1 and is below 1 hectare, so no flood risk assessment is submitted." That is a defensible position stated once, rather than an omission the officer has to query.

A Design and Access Statement is required for certain application types and not for others, so state explicitly whether one is submitted and on what basis, since its absence is a common validation query on householder and minor applications.

Requests about conditions and timing

The letter is the right place for procedural requests, kept short and reasonable.

1. An offer to agree draft conditions before the decision, with a named contact and an undertaking to respond within a stated period.
2. A request that pre-commencement conditions be kept to the minimum, noting that your written agreement is required under section 100ZA of the Town and Country Planning Act 1990.
3. A request for a specific determination date where there is a commercial or funding deadline, with the reason.
4. An offer of a site visit, with access arrangements and a contact.
5. Confirmation of who should be contacted about the application, and confirmation that correspondence should go to the agent.

Do not ask for an extension of time in the cover letter. Extensions are negotiated when the pressure arrives, and offering one at the start reads as an expectation of difficulty.

Length and tone

Two pages plus the document schedule. If the letter runs to five pages you are writing the planning statement twice, and the officer will read neither properly.

Keep the tone flat and factual. The letter is not the place to argue the planning balance, to complain about a previous refusal, or to characterise the neighbours. Everything in it should be checkable.

Sign it as the agent, give a direct phone number and an email address, and state the date. Then read the whole pack once more against the council's validation checklist before you upload, because the single most common cause of delay is not a bad letter but a missing form.

Work out which supporting documents your application needs by entering the postcode on PlanScope and answering the guided questions, or browse the full report list to build the schedule.

This is general guidance, not legal advice. Validation requirements differ between councils, so check the current local list before relying on it. PlanScope provides AI-assisted draft reports for planning applications. Reports should be reviewed before submission. We do not guarantee planning approval.