A neighbour consultation record template for applicants

A neighbour consultation record is a short document you write before you submit, showing who you contacted about your proposal, what they said, and what you changed as a result. It has no statutory status. The council's own publicity under article 15 of the Development Management Procedure Order 2015 happens after validation and is a different exercise entirely. What the record does is give the case officer and any ward councillor a factual account of your engagement, which matters most on the schemes that end up in front of a committee.

For a single new dwelling or a large extension, two pages is enough. What follows is the structure that works, and the points where this kind of document does more harm than good.

Why a record helps at committee

Councillors ask two questions about a contested householder or small-site application: have the neighbours been spoken to, and did the applicant listen. A written record answers both in a form the officer can quote in the report.

It also protects you against a specific problem. Objections arriving during the statutory consultation period are often about things you already addressed: a window you moved, a ridge you lowered, a boundary you agreed to keep. Without a record, the objection stands unanswered and the officer has no basis for saying the point was resolved. With one, the officer can write that the scheme was amended in response to a concern raised before submission.

The record is not a substitute for the statutory process and should never be presented as one. Councils occasionally get applications claiming that neighbours have been consulted and therefore no further publicity is needed. That misreads the law and irritates the officer.

What to send neighbours and when

Three to four weeks before you intend to submit is about right. Earlier and the drawings change; later and you cannot act on what you hear.

Send a short pack to the immediately adjoining owners and occupiers, plus anyone whose outlook or access is affected:

• A one-page letter in plain language saying what you propose, when you expect to submit and how to respond
• A location plan with the site outlined
• The proposed elevations and a block plan, at a size that can be read on a kitchen table
• A single sketch or photomontage from the street or from the most affected boundary
• A response date, three weeks out, and one contact route

Keep the letter free of planning vocabulary. "We want to build a single-storey extension across the back of the house, 3.5 metres deep, with a flat roof and a rooflight" communicates. "A rear extension in accordance with Class A of the GPDO" does not.

Deliver by hand where you can and post where you cannot, and note the date of each delivery. Photograph the pack you delivered so there is no argument later about what was shown.

Recording responses fairly

The log is the heart of the document. Keep it in one table and keep it neutral in tone.

Identify properties by number and relationship rather than by resident name, and do not reproduce anyone's contact details, signature or the full text of a private message. The comments are personal data, so handle them in line with data protection law and keep the published version summarised and anonymised. If a neighbour asks you not to include their comment at all, leave it out and note in the record that one response has been withheld at the respondent's request.

Summarise accurately, including the comments that went against you. A log with three supportive entries and no objections from a street of eight houses reads as selective, and an officer who receives four objections during the consultation period will treat the whole document as unreliable.

Distinguishing objections from queries

Most of what neighbours raise is a question, not an objection. Sorting them matters because it changes what you have to do.

A query is answered. Where will the skip go, how long will the scaffolding be up, will the party wall be affected. Answer in writing, note the answer in the log, and move on. Many of these are not material planning considerations at all, and saying so politely is fine as long as you still answer the practical question.

An objection engages a planning issue: overlooking, loss of light, loss of outlook, parking, noise, the effect on a conservation area. These need a decision from you. Either change the scheme, explain why you have not, or offer a mitigating measure such as a screen, a boundary treatment or an obscure-glazed window.

The third category is a demand you cannot meet, usually about land ownership, a right of way or a covenant. Record it, state plainly that it is a private legal matter outside the planning system, and do not argue it in the record. A Planning Statement is the right place to address the material planning objections in policy terms, with the consultation record as its factual appendix.

Showing what changed in the scheme

This is the part that earns the document its place. Add a short table listing each change made in response to engagement, with the drawing revision that carries it.

Three or four entries is plenty. A lowered ridge, a repositioned window, a relocated bin store, a retained hedge. Reference the revision number and the date so the officer can see the sequence: original sketch, neighbour comment, revised drawing.

Where you made no changes, say why in one sentence per point. "The rear extension depth was not reduced because at 3.5 metres it remains within the 45-degree line taken from the neighbouring window, as shown on drawing 104 revision B." That is a defensible answer. Silence is not.

A Design and Access Statement can carry the same material in its design evolution section for a scheme that needs one, which avoids duplicating it in two documents.

Including the record in the application

Submit it as a named document, not as an unlabelled attachment. "Pre-submission neighbour engagement record" is clear. Keep it to two or three pages plus the log.

Where the scheme is a major application, the equivalent document is a Statement of Community Involvement, which is a fuller exercise covering public exhibitions, website material and a wider consultation area. Councils commonly ask for one on schemes of 50 or more units, and some local validation lists require it below that. Check the council's validation checklist before deciding which document you are producing, because submitting a two-page record where the checklist demands a community involvement statement can hold up validation.

One practical point on timing. Submit the record with the application rather than sending it later, because a document arriving mid-consultation looks like a reaction to the objections rather than a record of what happened before them.

Where engagement can backfire

It is worth being honest that this is not always the right move.

Contacting neighbours about a proposal that would otherwise have attracted no attention can generate the objections you were trying to avoid, particularly on a street with no history of applications. On a scheme that is plainly policy compliant and causes no amenity harm, the statutory notification may be the better route.

Two other risks. Promising something you cannot deliver, such as a construction timetable or a boundary fence you do not own, creates a grievance and sometimes an unenforceable expectation at committee. And engaging selectively, contacting the neighbour you expect to support you and not the one you expect to object, is the single fastest way to lose an officer's confidence.

Judge it on the scheme. Contested extension in a terrace with close neighbours, engage. Replacement garage at the end of a long drive, do not bother.

Scope which supporting documents your project actually needs by entering the postcode on PlanScope and flagging neighbour concerns in the guided questions.

This is general guidance, not legal advice. Check your council's validation checklist and current publicity requirements 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.