Developer consultation before a major application

Pre-application consultation by a developer is almost always voluntary. If a leaflet has come through your door inviting you to a public exhibition about a large scheme, nobody required that company to hold it, and nothing obliges them to change anything in response to what you say. That does not make the exercise pointless. It is the one stage where a scheme is still fluid, and comments made now land on a drawing board rather than on a submitted application.

Why a developer consults when the law does not require it

For most development in England there is no statutory duty on an applicant to consult the public before submitting. Section 61W of the Town and Country Planning Act 1990 created such a duty, but it applies only to descriptions of development prescribed in a development order, which in practice means certain onshore wind schemes. Everything else is voluntary.

Developers do it anyway for reasons that are commercial rather than civic. Early objection costs less to answer at sketch stage than after a refusal. A council officer will ask what engagement has taken place, and national policy encourages early discussion. Some authorities make it a condition of a planning performance agreement. And a scheme that reaches committee with evidence of genuine dialogue reads differently from one that arrives cold.

There is one more reason worth naming plainly: a well-run exhibition allows an applicant to say the community was consulted, whatever the community actually thought. That is not a reason to stay away. It is a reason to put your comments in writing rather than on a sticky note.

What the exhibition is, and what it is not

An exhibition is a presentation of a scheme at a chosen moment, with the material the applicant has chosen to show. Boards tend to show the best views. Comment cards are collected and summarised by the applicant's own consultants.

It is not a vote, and the number of cards for or against does not decide anything. It is not the formal consultation, which begins once the application is submitted and validated, runs for a set period, and is the stage at which your comments go on the public file and must be taken into account. And it is not a commitment, since drawings shown at exhibition routinely change before submission, sometimes substantially.

One confusion is worth clearing up because the same phrase means two things. A council's own statement of community involvement is a plan-making document setting out how that authority will engage people in preparing its local plan. The document an applicant submits with a major application, describing who it consulted and what it did in response, is a different thing with an unfortunately similar name, and you can see what one contains on the Statement of Community Involvement page.

Questions worth asking while the scheme is still drawings

Vague concerns produce vague answers. Specific questions produce either specific answers or a visible gap, and both are useful.

• How many homes, in what mix of sizes, and how many are proposed as affordable, under which tenures?
• What are the building heights in storeys and in metres above existing ground level, and where are the tallest elements?
• How many car parking spaces, how many cycle spaces, and against which standard?
• Where is the vehicular access, and has a transport assessment been commissioned yet?
• Which trees are being removed, and has a tree survey been done?
• How will surface water be dealt with, and does any part of the site flood?
• What is the construction programme, and which roads will heavy vehicles use?
• Who will own and maintain the open space, roads and play areas after completion?
• Which local plan policies does the applicant say the scheme complies with?
• When do you intend to submit, and will you publish the consultation feedback in full?

Ask for answers by email. A verbal answer at an exhibition is worth nothing three months later, and the person who gave it may not be on the project team by then.

How your responses are reported to the council

The applicant's consultants write a summary. That summary goes to the council as part of the submission, and the case officer reads it alongside the representations received during formal consultation.

Two things follow. First, the summary is written by the applicant, so it decides what counts as a theme and what counts as an outlier. Second, the weight given to pre-application engagement is limited: it is evidence of process and of design response, not a measure of public support. A planning decision rests on the development plan and other material considerations, and a petition does not change the policy test.

The practical consequence is that a point you want on record should also be made in the formal consultation period, in your own words, after the application is submitted. Our note on following an application through the public register sets out how to track when that window opens.

Organising a community response that officers can use

Scattered objections repeating the same sentence have less effect than a small number of well-evidenced ones. What works, in my experience of reading these files from both sides:

1. Agree a short list of the issues that matter most, and let individuals write their own letters on them rather than sending a template.
2. Tie each point to a policy in the adopted local plan or the neighbourhood plan, quoting the policy reference.
3. Gather evidence rather than impressions: dated photographs, parking counts taken over several evenings, records of flooding with dates, school admission correspondence.
4. Involve the parish or town council early, since its representation carries procedural weight and it may have its own budget for advice.
5. Decide who will speak at committee if the application goes there, and keep to the time allowed.
6. Ask the ward councillor what they can and cannot do, bearing in mind the rules on predetermination described in our note on what councillors may say to you.

Highway and parking concerns are the most common and the most often dismissed for lack of evidence, which is avoidable. Our piece on highways objections a neighbour can evidence covers the data that counts.

Keeping your own record of what was said

Boards come down and websites get taken offline. Build a file on the day.

Photograph every board, including the small print on the site layout and any figure showing heights or unit numbers. Take the leaflet and the comment card. Note the date, the venue, who was present and which organisations they represented. Send a short email afterwards setting out the questions you asked and the answers you were given, and ask for confirmation. That email becomes your evidence if the submitted scheme differs from what was presented.

Where a scheme changes materially between exhibition and submission, saying so in the formal consultation is legitimate and officers take note of it, particularly where the applicant's own summary claims the design responded to local comment.

What happens next, and when to act

After the exhibition the applicant finalises the scheme, often over several months, then submits. Validation follows, then publicity: site notices, neighbour letters where required, and a period for representations. The case officer reports, and the decision is either delegated or taken by committee.

Your comments carry formal weight in that window and not before, so diarise it. Engagement before submission shapes the drawing. Engagement after submission goes on the file that the decision maker has to consider.

To see what a major application is expected to contain, and therefore what to ask for when it appears on the register, browse the full set of report types by category.

This is general guidance about the English planning system rather than legal advice, and procedures vary between authorities, so check your council's published consultation arrangements before relying on it.