A community engagement plan for a contested scheme

A community engagement plan is worth writing before the first exhibition board is designed, because the decisions that determine whether the exercise is useful are made at the start. Who you talk to, when you talk to them, and whether anything can still change as a result. On a scheme that will be opposed, the consultation report is read closely by objectors and by committee members looking for the gap between what people said and what the applicant claims they said.

There is no general statutory duty to consult before submitting a planning application in England. What there is instead is a set of expectations: national policy encouraging early engagement, the local planning authority's own statement of community involvement, and frequently a requirement on the validation list for major applications.

Working out what is actually expected

Start with two documents. The authority's statement of community involvement, prepared under the Planning and Compulsory Purchase Act 2004, sets out how that council expects applicants to engage and how it will publicise applications itself. The local validation list says whether a consultation report is a submission requirement and what it must contain.

Read the publicity requirements in the Development Management Procedure Order alongside them, because the council's own statutory publicity, site notices, neighbour letters and the 21-day period, is separate from anything you do and does not replace it.

Then be honest about scale. A 12-unit infill scheme does not need a three-round programme. A 300-unit urban extension next to a village that has fought two previous applications does, and a Statement of Community Involvement will be expected as a submission document.

Mapping the audiences

Most engagement plans start by drawing a radius on a plan. That produces a distribution area, not an audience map.

Work instead from how people are affected and how they can realistically take part:

• Immediate neighbours, who care about construction, overlooking, parking and access, and who will read every drawing.
• The wider settlement, which cares about school places, GP appointments, traffic through the centre and whether the fields flood.
• The parish or town council and ward councillors, who need enough information early to answer questions without guessing.
• Amenity and civic societies, local history groups and any active residents association, who often hold the best site knowledge.
• Businesses affected by construction traffic or by a change in footfall.
• Groups easily missed, including private tenants, people without internet access, shift workers, younger residents and households where English is not the first language.

Each group needs a different approach. Posting a leaflet to 400 addresses and putting a website up reaches the people who were always going to engage.

Choosing methods

The test for any method is whether it produces feedback you can use. A drop-in session at 2pm on a Tuesday produces a room of retired residents and nothing from anyone who works.

A workable mix for a contested scheme usually includes an in-person exhibition at two different times, including one weekend or evening slot, a project website with the same boards available to download, a freepost feedback form for people who will not comment online, a staffed phone line or email address with a named person answering it, and a follow-up session showing what changed.

Two things to avoid. Online-only engagement, which quietly excludes the households most affected by construction. And feedback forms built entirely from agree or disagree scales, which generate percentages nobody believes and capture none of the local knowledge that actually improves a scheme.

Say clearly how personal data collected through the exercise will be used, and stick to it.

Timing against the design programme

Consultation only means something while the answer can still change. Run the first round when the constraints and the broad options are settled but the layout is not, and say plainly what is fixed and what is open. People accept that the principle of development may be settled by an allocation. They resent being asked for views on a scheme that is clearly finished.

A workable sequence for a major application:

1. Early briefing for the parish or town council and ward members, before anything is public.
2. Round one, on constraints, options and the issues that matter locally, several months before submission.
3. Design development, during which the design and access narrative records what moved and why.
4. Round two, showing the proposals and the response to round one.
5. Submission, with the consultation report.
6. Continued contact during determination, particularly with the parish council and any group that engaged constructively.

The design evolution that comes out of this belongs in the design and access statement, where each change can be tied to the comment that prompted it.

Recording, and the "we did not change this" section

Log everything. Every comment card, email, phone note and conversation at an exhibition, with a date, a theme and a location where relevant. Themes emerge quickly and they are usually not the ones the project team expected.

Then write the response in two halves. The changes made, tied to specific comments. And the points raised that did not lead to a change, with the reason. That second half is the one applicants leave out and the one that earns credibility. An objector who sees their point recorded accurately and answered honestly is a different proposition from one who believes they were ignored.

Illustrative example: on a scheme where the dominant comment was about a single junction, the layout could not move the access, but the applicant commissioned additional queue modelling, published it, and explained what it showed. The objection did not disappear. It stopped being an accusation of concealment. That example is illustrative.

Organised opposition

Well-run opposition groups are a normal feature of contested schemes, and treating them as an obstacle to be managed is both wrong and counterproductive.

Offer them the same access as anyone else. Meet them if they ask. Correct factual errors once, in public, politely, and then stop. Do not run arguments in comment threads, do not disparage individuals, and do not organise or commission apparent grassroots support. Each of those produces material that will be quoted back at committee.

Where a group raises a technical point you had not considered, say so and deal with it. On more than one scheme the local objection has identified a drainage problem the consultants missed.

Reporting it in the submission

The consultation report should let a case officer verify what happened without ringing you. Include the methods and the reasoning behind them, dates, the notification area with a plan, the materials shown as an appendix, response numbers by channel, a categorised summary of comments, the changes made, and the points not taken forward with reasons.

Resist two temptations. Do not report attendance as approval. And do not present the exercise as producing consensus where it did not, because the planning statement then has to carry an argument the consultation report does not support.

You can see the documents a major application needs and start drafting the supporting statements while the engagement programme is still running.

This is general guidance, not legal advice; check the position with your local planning authority or a qualified professional 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.