A community organisation asks for ideas, receives a thoughtful response and announces a decision with no explanation of what happened to the suggestions. Next time, fewer people bother to contribute.
The problem may be the process rather than the invitation. Useful community engagement tells people what they can influence, makes participation manageable and shows how their input affected the result.
This guide is for local organisations, clubs and nonprofit teams using social media alongside other ways of reaching their community.
Start with a decision that is still open
Before writing a post, identify the decision and its limits. Is the community choosing an event time, advising on priorities or deciding how a budget will be allocated? These are different levels of influence.
State the boundary plainly. For example, a hypothetical neighbourhood association could say: “We have funding for one weekend workshop. We are choosing between bicycle repairs and basic gardening. The venue and total budget are fixed.” That gives people a real question to answer.
Do not invite a broad redesign if the decision has already been made. An announcement can still be useful; dressing it up as participation creates an expectation you cannot meet.
Map who the decision affects
The people who follow your account are not necessarily the people most affected. Identify who uses the service, who cannot currently use it, who pays for it and who will carry out the work.
For the workshop example, an evening poll may miss shift workers, people without a reliable internet connection or carers who need advance notice. Use more than one route where practical: a social post, a notice at the venue and a short conversation at an existing event.
You do not need to claim that a small consultation is representative. Record who you reached and which voices remain missing. That limitation belongs in the decision record.
Make the invitation easy to understand
Explain the question, deadline and use of the answers in the post itself. Avoid sending readers through several pages to find basic details. Provide a way to ask for help or contribute privately if the subject is sensitive.
The W3C guidance on accessible writing recommends clear instructions and meaningful headings. Apply those principles to the invitation: explain unfamiliar terms, keep the essential information in text and make the requested action obvious.
For a multilingual community, assign someone who can review both the invitation and responses. The multilingual strategy guide covers this ongoing responsibility.
Run a bounded discussion
Name a facilitator and tell participants how the discussion will be handled. A small team can use a straightforward process:
- Collect input. Ask a focused question and allow enough time for the people affected to respond. Keep a record of themes without collecting unnecessary personal details.
- Clarify differences. Ask why a proposed option would or would not work. A preference without its constraint can conceal a practical problem such as access, cost or timing.
- Separate disagreement from abuse. Allow criticism of the idea. Apply a clear rule against harassment and disclosure of private information consistently, including to enthusiastic supporters.
- Check the missing information. If an answer depends on budget or venue access, get the fact from the owner. Do not ask participants to settle something only the organisation can verify.
Give volunteers authority to moderate within the agreed rules, but do not leave them responsible for decisions they cannot make.
Publish the result with a reason
A useful update explains what you heard, what you decided and what remains unresolved. Avoid publishing identifiable responses without permission.
For the hypothetical workshop, the update might explain that bicycle repairs received more support, but the venue lacks the safe space required. Gardening was selected for the first event, and a separate location is being investigated for repairs. This is an example of transparent reasoning, not evidence of an actual consultation.
If you promised a follow-up date, meet it even when the work is incomplete. A short update explaining the delay closes more of the loop than disappearing until you have good news.
Judge participation by the quality of the process
Count contributions and attendance, but also ask whether people understood the decision, whether the team reached those affected and whether any useful input changed the plan. Many comments do not prove that people had meaningful influence.
The community trust guide explains how dependable follow-through supports the relationship over time.
Before your next invitation, write three sentences: what can change, how people can contribute and when you will report back. If you cannot answer those yet, finish the participation process before launching the post.