Community Facility Consultation Preparation Checklist

List the properties whose windows, gardens or boundaries face the site, and treat each of them as somebody to speak to directly.

Nearby residents are affected most and usually hear about a proposal last, which is how a modest project becomes a local dispute.

Name the groups already using the site, including any who use it informally, and add them to the list before the proposal is drafted.

Existing users left out of consultation tend to reappear as objectors, and their support would otherwise have been the easiest to keep.

Write down who owns the land and who manages it, and note that both may need to be involved whatever the community thinks of the idea.

Land ownership, tenancy and management responsibilities are legal matters to establish with a suitably qualified adviser and the local authority.

Consider parts of the community who do not use the site now but might, such as older residents or families with very young children.

A consultation that reaches only current users produces a proposal that serves only current users.

Include the people who would have to run, clean, open and maintain the facility, and ask them separately from the users.

The people who do the work notice things a design conversation misses, and they are usually consulted last if at all.

Write the list down and keep it, noting who was contacted, how they were contacted and whether they replied.

A consultation without a record of who was asked cannot answer the question that always follows, which is who was left out.

Write a plain description of what is proposed, in language somebody with no involvement in the project could follow.

Technical or promotional wording makes readers assume something is being concealed, and it usually is not.

Show who would use the facility and when, because that is the question neighbours actually care about.

Most objections are about hours, noise and comings and goings rather than about the structure itself.

Avoid presenting the proposal as settled if it is not, and say clearly which parts remain open to change.

Consultation on a decision already taken is quickly recognised, and it drains the goodwill the group needs later on.

State plainly which questions the group cannot answer yet and who will be answering them.

Questions about noise, traffic, drainage, overlooking and consent are answered by qualified professionals and the local authority, never by the group on their behalf.

Leave out any figure the group cannot stand behind, and say so rather than filling a gap with something approximate.

A single unsupported number becomes the focus of the whole consultation and undermines everything else on the page.

Consider how the material reaches people who do not use a screen, do not read English easily or do not attend meetings.

The people least likely to see a notice are often the ones a community facility is intended to serve.

Ask open questions about how people use the site now, rather than asking whether they support a proposal.

Descriptions of current use are reliable, while expressions of support given in a hall on the night usually are not.

Ask directly what would worry people about the proposal, and make it easy for them to say so.

Concerns raised early can be designed around, while the same concerns raised late arrive as formal objections.

Read every question back and take out any wording that hints at the answer the group is hoping for.

Leading questions are obvious to the people answering them, and they make the whole exercise easy to dismiss afterwards.

Keep questions about what happens now separate from questions about what people would like to see.

Facts and wishes have to be handled differently afterwards, and mixing them makes both harder to use.

Offer a way to respond without speaking in front of neighbours, and say how those responses will be treated.

How personal details are collected, held and shared is subject to requirements to confirm with a suitably qualified adviser before anything is gathered.

Ask anybody who objects what would make the proposal acceptable to them, and write down exactly what they say.

The answer is often small and achievable, and it is only ever discovered by asking the question directly.

Consider when the people you most need to hear from could realistically attend, rather than when the committee usually meets.

A meeting held at the committee's convenience hears from the committee's circle, which is not consultation.

Decide who chairs the session, and consider whether that should be somebody with no stake in the outcome.

A chair who is also the proposer struggles to appear even handed even when they are being entirely fair.

Arrange for somebody other than the chair to take notes, and say at the start that notes are being taken.

A chair cannot both run a room and record it, and the record is the part that outlasts the evening.

Agree in advance how a strongly worded objection will be handled, so that it is recorded rather than argued with in the room.

Arguing with an objector in public turns one unhappy neighbour into several, regardless of who is right.

Agree that questions about consent, drainage, noise or access are written down for professionals rather than answered on the night.

Statements made at a public meeting about permissions or requirements are relied on afterwards, so route them to the local authority and qualified professionals.

Tell people what will be done with what they have said and how they will hear anything further, without promising a date.

Consultation loses trust in the silence afterwards far more often than in the meeting itself.

Write responses down in the words people used, rather than summarising them into the group's own language.

Paraphrase quietly removes the sharp edges, and the sharp edges are the part a designer most needs to see.

Avoid describing a level of support the record does not show, and report what was received rather than how strong the feeling seemed.

Overstated support is the easiest claim to disprove and the most damaging one to be caught making.

Keep objections in the record in full, including the ones the group disagrees with or finds unfair.

An objection removed from the record reappears later with more force, and its absence is what people remember.

Group responses by theme, such as noise, parking, hours or upkeep, so that patterns are visible without conclusions being drawn.

Themes show where the real pressure sits, and they translate directly into questions for qualified professionals.

Decide how names and addresses will be handled in anything shared, and tell people that before they respond.

What may be published about a respondent is confirmed with a suitably qualified adviser and the relevant authority before anything is circulated.

Keep the raw record as well as any summary, and decide who holds it when the committee changes.

The raw record is what allows a later question to be answered, and it is usually the first thing to be lost.

Decide how respondents will be told what was done with their comments, including where nothing changed as a result.

People accept a decision they disagree with far more readily when they can see that their point was understood.

Record which parts of the proposal changed because of the consultation, and which did not and for what reason.

A visible link between comment and change is the strongest evidence that the exercise was genuine.

Note where disagreement remains that the group cannot resolve, and pass it to the people who are able to address it.

Unresolved objections about use, noise or access are considered by the local authority and qualified professionals on their own terms, not by the group.

Record that community support is not consent, and keep the two clearly separate in every document the group produces.

Support from a community authorises nothing, and whether the proposal may proceed is confirmed with the landowner and the local authority.

Consider whether a changed proposal needs to go back to the same people, and decide that deliberately rather than by default.

A design that has moved substantially since consultation is effectively unconsulted, and that tends to be noticed.

Agree how nearby residents will be kept informed once anything begins on site, and who their point of contact would be.

The neighbour who has a name to call rarely becomes the neighbour who makes a formal complaint.

Pull out every question the consultation raised that the group cannot answer, and take that list to qualified professionals and the local authority.

This list is the most valuable product of a consultation, and it is usually left buried in the notes.

Turn what users said they need into plain statements for a designer, keeping their own wording attached to each one.

A designer can work with a description of need, but not with a committee's solution to it.

Write down the constraints neighbours identified, such as hours or lines of sight, as constraints rather than as objections.

Framed as constraints, the same points become design information instead of a dispute to be won.

Keep a separate note of everything that must be confirmed locally before anything is promised to anyone.

Whether consultation of any particular kind is required here, and what form it must take, is confirmed with the local authority.

Note which points came from which interest, so a professional can see whether a concern is widespread or particular to one household.

One strongly held concern from a single household is handled differently from the same point raised across a whole street.

Decide who takes the consultation material to the next meeting with professionals, and what they are asking for when they do.

Material nobody has been asked to carry forward stops at the committee, which is where most consultations quietly end.