Statement of community involvement: the council's or yours

Two different documents share almost the same name, and the confusion costs applicants time at validation. The council's statement of community involvement is a policy document prepared under section 18 of the Planning and Compulsory Purchase Act 2004, setting out how the authority will involve people in preparing its local plan and in dealing with applications. The applicant's statement, sometimes called a consultation statement, is submitted with a planning application and reports what engagement was carried out, what came back and what changed as a result.

On the statement of community involvement application vs council question, the short answer is that the council's document tells you the rules and the applicant's document tells the council what you did. One binds the authority. The other is evidence.

The council's document

Section 18 requires every local planning authority to prepare a statement of community involvement, and the Neighbourhood Planning Act 2017 added a duty to review it at least every five years. It covers plan-making and development management, and it is the document that records how long the authority consults for, who it notifies, whether it uses site notices, press notices or letters, and how it handles representations.

For an applicant, three parts of it matter.

First, the publicity the authority commits to, because that sets expectations neighbours will hold you to. Second, any expectation the authority states about pre-application engagement by applicants, which is where the two documents connect. Third, the arrangements for speaking at committee, including registration deadlines and speaking times.

It is a policy document, not a validation requirement, and it cannot itself require an applicant to do anything. What it can do is state what the authority expects, which then feeds into the local validation list where the authority has adopted one.

The applicant's document

This is the report submitted with an application describing the engagement undertaken. It has no single statutory basis for most development, which is why its content varies so much between authorities.

What a good one contains is settled by practice rather than by regulation:

1. Who was consulted, with a plan showing the area covered and the number of addresses.
2. What material was provided, with dates, and how it was made available.
3. What was said, reported fairly, including objections, grouped by theme rather than by individual.
4. What changed in the scheme as a result, with before and after drawings where a change was made.
5. What was raised and not acted on, with the reason.

Point five is the one applicants skip, and it is the one case officers read first. A statement that reports only praise reads as marketing and is discounted. A statement that says fourteen respondents objected to the height, the ridge was lowered by 600 millimetres in response, and the concern about parking was not accepted for the following reasons, gets used in the officer report.

PlanScope drafts a Statement of Community Involvement from your engagement record, and flags with a placeholder anything it cannot verify rather than inventing it.

Where statutory pre-application consultation applies

For most development there is no statutory duty on an applicant to consult anyone before applying. Three exceptions matter.

Nationally significant infrastructure projects are consented under the Planning Act 2008, which carries its own pre-application regime. That regime has been reformed more than once, so check the current legislation rather than relying on a description written for an earlier version of it. The consultation expected there is on a different scale from anything in the ordinary application system, with formal statutory consultees, publicity requirements and a report on how responses were taken into account.

Certain onshore wind development in England has carried a statutory pre-application consultation requirement under the Town and Country Planning Act 1990, introduced alongside the changes to how that development is consented.

And permission in principle, prior approval and some other alternative routes carry their own publicity requirements that sit with the authority rather than with the applicant.

Outside those, the duty comes from the local validation list. Many authorities require a consultation statement for major applications, and some set a threshold lower than the major development definition, commonly at ten dwellings or at a floorspace figure tied to their own validation list.

How the two documents interact at validation

A validation refusal on this point usually follows one of two patterns.

The authority's list requires a consultation statement for majors, the applicant submits nothing, and the application is invalid until one is produced. Two to three weeks lost, and the engagement now has to happen with the scheme already lodged, which satisfies nobody.

Or the applicant submits the council's own statement of community involvement, downloaded from the website, under the impression that it is a required document. That is the more common error, and it is obvious to the validation officer.

Engagement that actually changes a decision

The engagement worth doing is the engagement that happens while the scheme can still move. Consultation after the drawings are fixed produces a document about consultation rather than a better application.

On a contested site, the sequence that works is a small number of targeted conversations with immediate neighbours and the parish or ward councillor first, then a public event once the principle is settled, then a written round on the detailed design. Each stage produces a record, and the record becomes the statement.

Scale the effort to the scheme. A single dwelling on an infill plot needs a letter to the four adjoining owners and a note of what they said. Fifty homes on the edge of a village needs a staffed event, a website and a written response to themes. Our comparison of outline or full permission for a small site is worth reading alongside this, because the application route affects what there is to consult on.

One honest uncertainty: how much weight a case officer gives to engagement varies with the officer and the authority, and no amount of consultation converts an unacceptable scheme into an acceptable one.

Getting the language right in correspondence

Call the council's document the adopted statement of community involvement and the applicant's document the consultation statement, and say which you mean in every email. Where the validation list uses the same name for both, quote the list item number.

When the authority's own statement has not been reviewed within five years, that is worth noting politely in correspondence where the authority relies on it, because the review duty is statutory.

And keep the engagement record as you go: dated letters, event attendance sheets without personal details, the website analytics if you ran a page, and the drawings at each stage. Reconstructing it at the end is how inaccuracies get into a document that a committee will read aloud.

A Planning Statement then carries the policy case, with the consultation statement supporting it rather than duplicating it.

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.