How to Run Community Consultations That People Actually Trust

If you’ve ever sat through a town hall meeting where the decision was clearly made weeks ago, you know the particular exhaustion of a consultation that’s just theatre. I’ve been on both sides of that table. Over twenty-odd years working across Scotland’s public and voluntary sectors, I’ve seen processes that genuinely shifted how a council spent its money—and others that simply filled a statutory obligation while burning goodwill by the bucketload. This guide is for the real thing: consultations that are practical to run and principled enough that people come back next time.

What Makes a Consultation Genuinely Useful?

Forget the glossy feedback reports for a moment. A useful consultation shapes the actual decision because the evidence holds up, the process reached beyond the usual suspects, and the community can see its fingerprints on what happened next. Three things sit underneath all of that: knowing why you’re consulting, listening for real, and feeding back with a straight face.

Knowing your purpose means being blunt about what’s up for grabs and what’s already set in stone. If the budget envelope is sealed or the site is chosen, say so in the first paragraph. Nothing sours a room faster than being invited to opine on a settled question. Listening for real demands methods that go where people actually are—not just the confident regulars who’ll turn up to anything with free biscuits. And feeding back means a proper loop: here’s what you told us, here’s what we decided, and here’s the honest reason why.

Map Out Who Decides What—Before You Book a Chair

Before you send a single invite, sit down and sketch the decision pathway. Who’s got the final pen? What yardsticks are they using? How much heft will the consultation findings actually carry? Get this onto a single page that everyone—staff, members, community partners—can see. This one discipline stops the miserable drift where you gather a mountain of input that can’t, in practice, budge anything.

I keep coming back to a simple scale: inform (we’re telling you what’s happening), consult (we want your views to shape our call), co-design (we’ll build options together), co-decide (we share the final say). Most of the time you’ll land squarely on “consult.” That’s fine—just don’t dress it up as something bigger.

Designing the Process So It Actually Fits the People

One size does not fit all, and one method will miss huge chunks of your community. Mix numbers with stories, online with face-to-face, and budget for the unglamorous stuff: interpreters, travel costs, childcare.

Find a Cross-Section, Not Just the Loudest Voices

Public meetings skew old, confident, and already plugged in. That’s not a judgement; it’s an observation repeated in enough community halls I could wallpaper one with it. You have to go looking for the people who don’t show up: young folk, shift workers, carers, those whose first language isn’t English, and anyone who’s learned through hard experience that authorities don’t listen.

Things that actually work:

• Ask the local mosque, the community pantry, the parent-and-toddler group to host the conversation on their turf, at their normal time.
• Put short, jargon-free surveys in the places life already takes people—GP waiting rooms, launderettes, the post office queue.
• Offer a bus ticket, a crèche spot, a hot drink and a sandwich. Small things remove real barriers.
• Run sessions when shift patterns allow: a Tuesday at 2 p.m. works for some, a Thursday at 7 p.m. for others, a Saturday morning for yet another slice.

Match the Method to the Question You’re Actually Asking

Not everything needs a public meeting. If you’re after the texture of lived experience—how it feels to use a service, what the daily friction points are—small groups or one-to-one chats will get you further than a room of forty with a microphone. Testing a specific proposal? Pull out maps, Lego, budget simulators, anything tactile that gets people pointing and arguing constructively. Online surveys give you breadth but rarely depth; treat them as a net, not a diagnosis, and follow up with a sample of respondents by phone.

A format I reach for again and again is the World Café: set up three or four tables, each with a different question stuck to the tablecloth, and rotate groups every fifteen minutes. It keeps the energy from sagging, mixes up who talks to whom, and stops the chap with the loudest voice from colonising the whole evening. A host stays at each table to catch the themes as they surface.

Write Questions That Don’t Nudge People Toward Your Preferred Answer

I’ve seen surveys that all but wink at the respondent. “Do you agree our award-winning park is a treasured community asset?” is not a question; it’s a plea. Try instead: “How do you use the park, and what would make it better for you?” Open-ended questions take longer to sift through, but they surface what actually matters to people—not what you assumed mattered.

Pilot your questions with a small, mixed group before you launch. They’ll find the jargon you’ve stopped noticing, the ambiguous wording, and the phrase that lands differently than you imagined. One council I worked beside discovered that “active travel” meant precisely nothing to most residents. “Walking, wheeling, and cycling” got nods and actual answers.

In the Room: Facilitation That Gets You Somewhere Honest

How you hold the space shapes what you’ll hear. A facilitator’s job isn’t to sell the scheme. It’s to make it safe enough for disagreement, to notice who’s gone quiet, and to keep the thread from unravelling into anecdotes about dog bins.

Ground Rules That Build Safety, Not Just Order

Start every session by saying plainly why you’re there and naming a few rules you’ll stick to. “One voice at a time.” “Disagreement is fine; personal digs are not.” “We’re here to listen, not to win.” If the subject is raw, name the rawness. People settle when they sense the facilitator knows the temperature in the room.

Online, the same principles hold. Have someone dedicated to watching the chat so quieter participants can type a thought instead of unmuting. Use breakout rooms for the real talk—plenary on Zoom is a graveyard for candour. Tech will glitch. Have a backup link, a phone number, and a tech host who doesn’t flap.

Capture What Was Said Without Ironing Out the Meaning

Take verbatim notes or record (with clear consent). If you paraphrase in real time, your own filters creep in—you’ll write down the tidy version, not the messy, revealing one. Use the same recording template across facilitators so you can compare like with like later. After each session, grab your team for fifteen minutes and note down initial themes, body language you noticed, and anything that caught you off guard. Memory is slippery; write it now.

Anonymise unless someone has given you explicit, written permission to name them—and even then, ask yourself whether attribution could hurt. A critical comment about a local service might be fair, but the person who made it still has to live in that community.

Analysis: Turning the Pile of Paper into Something You Can Use

This is where many well-intentioned consultations quietly die. Teams collect hundreds of pages, then go quote-hunting for the bits that back up their existing plans. Principled analysis means treating every piece of feedback as data, not decoration.

Thematic Analysis, Not Just a Word Cloud That Looks Nice in a Slide Deck

Code each comment into a category, then group those categories into broader themes. “Dog mess,” “broken swing,” and “brambles over the path” might all sit under “park upkeep.” A remark about feeling unsafe after dark could touch both upkeep and a separate strand of “personal safety.” Tag it to both.

Count how often themes appear, but don’t stop at the tally. Note the temperature of the language, the range of voices raising an issue, and any trade-offs people described. A theme flagged by 40% of respondents carries weight; a deeply felt concern from a small, marginalised group may carry an ethical weight beyond its frequency. Both belong in the report.

Notice What Isn’t There

Absence is a finding too. If nobody under 30 responded, that’s not just a data gap—it’s a statement about your reach. Say so in the report, plainly. The results cannot claim to speak for that generation, and pretending otherwise is a quiet dishonesty.

Closing the Loop: Telling People What Happened Next

This stage gets skipped more often than any other, and it’s the one that builds or breaks your reputation for next time. People lent you their time and a bit of trust. They deserve to know what came of it. A “you said, we did” page is a start, but it can’t just be a marketing exercise with bullet points.

Write a Public Report That Tells the Whole Story

A proper report covers:

• Why you consulted and what was in scope.
• Who you reached—and who you missed, honestly.
• Key themes and direct, anonymised quotes that give the flavour.
• Specific ways the findings changed the decision.
• Where the decision went a different way, and the real reason why.

Put it out in formats people can actually use: plain text, easy-read, translated if your community needs that. Email it to everyone who left an address, and drop paper copies where people gather—the library, the chippy, the bus shelter noticeboard.

When You Can’t Do What People Asked For

Sometimes the community’s preference is simply not possible: it’s unaffordable, it’s unlawful, or it clashes with other legal duties. Explain that without waffling or sounding defensive. People can handle constraints when they’re spoken to like adults. “We can’t lower the speed limit here because it’s a trunk road under Transport Scotland’s authority” is clear, honest, and points people toward the right door.

Traps Even Experienced Teams Fall Into

I’ve stumbled into most of these myself, so this list is confession as much as warning.

Consulting After the Train Has Left the Station

If the project plan is bolted down, your consultation becomes a sales pitch, and everybody smells it. Bring people in while options are still being shaped—that’s when their thinking can genuinely steer things. If you’re stuck consulting late, be explicit: “We’re asking how to implement this decision, not whether to proceed.” It won’t make everyone happy, but it’s clean.

Putting Everything Online and Calling It Done

Digital tools are cheap and handy, and they also exclude a chunk of the population that doesn’t have reliable internet, a device, or the confidence to use either. In rural areas and pockets of urban deprivation, that chunk is bigger than many comfortable professionals imagine. Always run paper surveys, telephone interviews, or drop-in sessions alongside the online channels. Yes, it’s more work. It’s also the difference between hearing from the whole community and hearing from the broadband-enabled slice of it.

Seeing What You Want to See in the Data

We all do it. Assign someone the job of hunting for evidence that contradicts your emerging story. Better yet, pull a handful of community members into the analysis itself—a participatory workshop where they can push back on your reading of the data. It’s humbling and immensely useful.

Was It Worth It? Evaluating Your Own Process

Build evaluation in from the start, not as an afterthought when the report’s already printed. After the process wraps, ask participants and staff: Did you feel heard? Could you access it easily? Would you bother taking part again? Then track the harder stuff: demographic spread, response rates, how many distinct themes surfaced, and—the question that should keep you up at night—whether the consultation actually changed anything. If it didn’t, be straight with yourself about why you did it.

Frequently Asked Questions

How long should a community consultation run?

No fixed rule, but six to eight weeks is common for straightforward public consultations. Go shorter and you’ll miss people on holiday or buried in caring duties; go much longer and momentum fizzles. For complex strategic plans, twelve weeks is standard in many places. Check your timeline against school holidays and big local events so you’re not competing with the gala day.

What if hardly anyone takes part?

Low turnout is data, not just a disappointment. It might signal distrust, consultation fatigue, or promotion that didn’t land. Record the numbers honestly, describe who did respond, and state clearly that the findings can’t be called representative. Think about targeted follow-up with specific groups rather than just extending the deadline into the void.

How do we handle someone who’s aggressive or disruptive in a meeting?

Set ground rules early and stick to them. If someone keeps talking over others or getting personal, a calm, firm word usually works: “I’m going to ask you to let others speak now; I’ll make time to talk with you afterwards.” Have a co-facilitator who can step out with someone who’s distressed. Abuse toward staff or participants is never acceptable. If it continues, end the session early and follow up one-to-one later.

Can we mix consultation with general community engagement?

Yes, and often you should. Consultation is about a specific decision; engagement is the longer, slower work of building relationships. A good consultation can strengthen those relationships if people see their input counted. But don’t stick a “consultation” label on a general PR event—it muddies expectations and chips away at trust in both.

In the End, It’s About Respect

Running effective consultations isn’t just a set of techniques. Underneath the methods is something simpler: respect, curiosity, and a willingness to be accountable. When you design a process that genuinely listens, you get better decisions—ones that stick because they fit the grain of people’s lives. You also build the kind of relationship that makes the next piece of work possible, because people remember being heard. Dr. Fiona Maclean’s experience points to one consistent pattern: the consultations that work best are the ones where the community can see its own fingerprints on the outcome. That takes a bit of nerve, because you have to let go of some control. But what you get back is worth it—decisions that last, services that actually work, and a public that hasn’t given up on the process.