An objection letter structure that officers can summarise

If you want to know how to write a planning objection that changes anything, start from what happens to it. A case officer reads every representation, then compresses the lot into a few paragraphs of an officer report under headings drawn from planning policy. Your letter survives only in that summary. So the job is to write something that summarises well: three points, each tied to a policy or a material consideration, each supported by something the officer can verify.

Long letters about the applicant's character, the vendor's motives and the state of the road for twenty years do not summarise. They get compressed into one line that says local residents raised concerns about traffic.

Start with the three points that carry weight

Pick the three strongest objections and put them in the first paragraph as a numbered list. Then expand each one in its own short section.

Three is not a magic number, it is a practical one. Officers weigh objections by substance rather than volume, and a letter raising eleven points dilutes the two that might have made a difference. If the eleventh point is the one that wins, put it first.

For each point, write one sentence that states the harm, one that names the policy or consideration engaged, and one that offers the evidence. That structure means your objection can be lifted into the report almost verbatim, which is the outcome you want.

Material and non-material, and why it decides everything

An officer can only take material planning considerations into account. Everything else, however genuine, is outside the decision.

The right-hand column is not a list of things you may not care about. It is a list of things that will be struck out of the summary. Where a concern sits close to the line, recast it: a lost view is not material, while a substantial increase in enclosure to a habitable room window is.

Two frequent misunderstandings. Loss of a view is not material, whereas being overlooked is. And the fact that a neighbour's own extension was refused is relevant as consistency of decision-making rather than as fairness.

Evidence that supports each point

Assertion loses. Evidence that the officer can check wins, and it does not have to be expert evidence.

• Measurements. The distance from the proposed rear wall to your window, taken with a tape and stated with the method, is worth more than an adjective.
• Photographs, dated, from a stated position, ideally showing the existing relationship the proposal would change.
• The council's own documents. A supplementary planning document on householder design, a conservation area appraisal, or an adopted parking standard, quoted with the page number.
• The application's own drawings. Inconsistencies between the site plan and the elevations, a missing section, or a datum that does not match the survey are the objections officers act on fastest.
• Planning history. A previous refusal on the same site, with its reference number, and the reasons given.
• Sun path or daylight geometry where the geometry is simple enough to set out, such as a 45-degree line taken across a plan.

Where the technical issue is beyond what a resident can reasonably evidence, say what you think the applicant should have submitted rather than attempting the analysis. A representation pointing out that no Daylight and Sunlight Assessment has been provided for a three-storey flank wall two metres from a neighbouring window is a stronger objection than an amateur calculation.

Length, and why shorter wins

Two pages is generous. One page is often better.

The reason is mechanical. Where an officer has forty representations to summarise, the ones with clear headings and short sections get summarised accurately, and the ones that ramble get summarised generically. A letter that mirrors the structure of an officer report gives the officer nothing to do but transfer it.

Practical formatting that helps:

1. Put the application reference and site address at the top, on their own line.
2. State in one sentence that you object, and to what.
3. List your three points.
4. Give each point a heading and three or four sentences.
5. End with what you are asking the council to do.

Avoid appendices unless they are photographs or council documents. A twenty-page appendix reduces the chance that any of it is read.

And write it yourself. Identical template letters signed by many households are recorded as a single point repeated, which carries less weight than the same number of individual letters making overlapping points in different words.

Ask for conditions as well as refusal

Most objectors ask only for refusal, which gives the officer a binary choice they will usually resolve in the applicant's favour. Asking for conditions in the alternative gives them a middle route, and it is frequently how objections actually achieve something.

Conditions worth asking for, where the harm they address is real:

• Obscure glazing and fixed lights to specified windows, secured by condition rather than left to goodwill.
• Removal of permitted development rights for further extensions where the cumulative effect is the concern.
• Restricted hours for deliveries, plant operation or opening.
• A construction management plan covering parking for operatives, wheel washing and working hours.
• Details of boundary treatment and screen planting to be approved before occupation.
• A restriction on use within a use class where the flexibility would cause the harm you are worried about.

Phrase the request as a condition, in the words you want to see. Officers draft conditions under time pressure and a workable form of words offered by an objector often survives into the decision notice.

Submitting it, and confirming it landed

Use the council's online comment form where one exists, because it attaches your representation to the application record automatically. Where you email, put the application reference in the subject line and ask for acknowledgement.

The consultation period is normally 21 days from the date of the site notice or neighbour letter, and comments received after it are still considered in practice provided the decision has not been made. Do not rely on that. Get it in during the period.

Then check the application record online a week later to confirm your representation is showing. Representations do go missing, and a polite email attaching the original with the send date resolves it.

Watch for the decision route as well. Most applications are decided by officers under delegated powers rather than at committee, and the threshold for a committee referral varies between authorities, as our note on delegated decisions and planning committee explains. If the application will be decided at committee, find out the deadline for registering to speak, which is usually several working days before the meeting.

An illustrative structure

The skeleton below is illustrative and should be rewritten in your own words.

Application reference and address. One sentence of objection. Then: overlooking from the proposed first floor rear windows, with the measured distance and the affected rooms named, referring to the council's householder design guidance. Then: parking, with the number of existing on-street spaces counted on three evenings and the dates given, referring to the adopted parking standard. Then: effect on the character of the street, with photographs showing the prevailing pattern of rear additions. Close by asking for refusal, and in the alternative for obscure glazing to the named windows and the removal of permitted development rights for further extensions.

Reading the officer's eventual report against your letter is the fastest way to write a better one next time, and our note on what a case officer writes in a delegation report sets out what those reports have to cover.

This is general guidance, not legal advice. Check the position with your local planning authority or a qualified professional before relying on it.