An online public consultation is a structured, time-limited opportunity for the public to comment on a proposal before a decision is made, usually through a web form or survey, with the results published and explained afterwards. Learning how to run an online public consultation means following a clear sequence: define the decision, choose participants, pick tools and privacy settings, pilot, launch, moderate, analyse and report back. A six-week consultation needs roughly 60 to 100 hours of team time across that sequence.
The hardest part is not the software. It is being honest about what is still open to change, and then showing people which of their comments actually moved the decision.
Table of Contents
- What You Need
- Choosing a consultation platform: what to check
- Step-by-Step: How to Run an Online Public Consultation
- Step 1: Set the consultation purpose and decisions
- Step 2: Choose participants and access routes
- Step 3: Select tools, privacy settings, and moderation rules
- Step 4: Pilot the consultation
- Step 5: Launch and promote the consultation
- Step 6: Facilitate responses and maintain trust
- Step 7: Analyze feedback without overstating it
- Step 8: Report results and close the feedback loop
- How long should a public consultation run?
- Common Mistakes
- Frequently Asked Questions
- How to start an online consultation?
- What are the 7 steps of consultation?
- What are the four Gunning Principles for public consultations?
- How long should a public consultation run?
- Do I need GDPR for a public consultation?
- How do you report consultation results to the public?
- Conclusion
What You Need
Before you open a form, get nine things written down. Teams that skip this stage end up fielding questions they have no agreed answer for, mid-consultation.
- A specific objective. One sentence naming the decision under consultation. If you cannot write it in a single sentence, the scope is too wide.
- Named target participants. Who is affected, who is likely to respond anyway, and who is usually missing.
- Decision boundaries. A list of what is fixed, what is negotiable, and who makes the final call.
- A timeline with published start and end dates, including the reporting date.
- Accessible participation routes beyond the browser: paper, phone, an in-person session.
- Named moderation roles and the rules moderators will apply, published in advance.
- A privacy approach covering what you collect, why, and how long you keep it.
- Evidence requirements, if responses need supporting data, such as a postcode or a document.
- Your tools: a survey platform, a project page, a mailing list, and somewhere to publish the outcomes.
That last item deserves more attention than it usually gets. Tool choice affects who can respond at all, so it is not a procurement afterthought.
Choosing a consultation platform: what to check
| Feature | Why it matters | What to check before signing up |
|---|---|---|
| Accessibility conformance | Determines whether people using screen readers, magnification or keyboard-only navigation can respond | Ask for a current accessibility statement and a WCAG 2.2 AA conformance claim, then test the live form yourself |
| Mobile experience | A large share of responses arrive on a phone, often on mobile data | Load the form on a mid-range phone on a poor connection and complete it end to end |
| Anonymity settings | People answer differently when their name is attached | Confirm whether identity fields can be optional or omitted entirely |
| Skip logic and branching | Stops people seeing questions that do not apply to them | Check you can map every conditional path before you build the form |
| Open text with attachment upload | The richest responses usually arrive in free text | Check file type limits and total storage across a whole consultation |
| Data export | Analysis and public reporting depend on getting the raw data out | Confirm you get full CSV or spreadsheet export including free-text fields, not just charts |
| Moderation tools | Open text needs hiding, flagging and audit trails | Check whether removals are recorded and can be reviewed later |
| Data location and retention | Governs what your data protection obligations require | Ask where data is hosted and what the default deletion schedule is |
Buy versus build matters here. An off-the-shelf platform handles accessibility testing and security updates for you. A bespoke tool on your own site gives you control and a seamless look, but you inherit the accessibility work and the bot problem.
Step-by-Step: How to Run an Online Public Consultation
Step 1: Set the consultation purpose and decisions
Write one question you want answered, not five. Two or three well-designed questions produce usable data; a 30-question form produces drop-off after question four.
Then publish your boundaries. State plainly what is already decided, what can change as a result of feedback, and who signs off. Consultation Institute evidence submitted to Parliament singles out adequate time as the principle most often breached, which tells you where attention goes.
How to tell it worked: a member of the public can read your scope page and correctly describe, in one sentence, what they could change by responding.
Step 2: Choose participants and access routes
Map who is affected by the proposal rather than who lives nearest the office. Split the list into likely participants, unlikely participants and groups that rarely respond to any consultation.
Offer at least one non-digital route. A paper version with freepost return, a phone line staffed during working hours, or a tablet at a community centre meeting each reach a different slice. Keep the wording of paper and online versions identical so the data can be merged.
How to tell it worked: your response mix is not dominated by one demographic group, and at least one non-digital route received responses rather than sitting unused.
Step 3: Select tools, privacy settings, and moderation rules
Pick the platform against the criteria table above, then set privacy before you build the form. Ask the minimum you need. Collect postcode or neighbourhood rather than full address if that is all you will use, and make identity fields optional where you can.
Write the participation rules and publish them on the same page as the form. Cover what is out of scope, how long the window runs, how personal data and anonymous comments are handled, and what moderation can remove.
Assign named moderators and give them a written escalation route. Rules nobody can see are indistinguishable from arbitrary moderation.
How to tell it worked: a data protection review of your form, retention schedule and published rules raises no unresolved issues.
Step 4: Pilot the consultation
Run a pilot with 8 to 15 people, including at least one non-digital user. Test the questions for leading wording, the navigation on a phone, every translation, screen-reader compatibility, attachment uploads, and the moderation and reporting workflow end to end.
Pilot data is the fastest way to find the question nobody understands.
How to tell it worked: pilot respondents complete the form without asking you what a question means, and your own team can generate the final report from a test dataset.
Step 5: Launch and promote the consultation
Publish the launch with the full set: a plain-English summary, the scope and boundaries, the privacy notice, the participation rules, the dates, and every response route. Then promote across channels on a schedule rather than one burst on day one.
Your channel mix should cover your email list, partner organisations, community groups, local media, and targeted social posts aimed at the groups from Step 2. Community and voluntary groups often reach the residents who do not respond to official channels, so brief them with a short written outline: what the proposal is, why it matters locally, the closing date and where to respond.
Post updates weekly while the window is open, and share the running response count once participation passes a useful threshold. Visible progress is one of the cheapest trust signals available.
How to tell it worked: responses arrive from outside your core email list, and you can name the specific channel that produced each group of them.
Step 6: Facilitate responses and maintain trust
Acknowledge contributions while the window is open. Publish answers to recurring process questions in the same place as the form, dated, so people can see the answers rather than emailing you privately.
Moderate proportionately. Remove abuse, personal data about third parties, and duplicates. Keep disagreement. Forum threads about local consultations show the same recurring complaint: people assume the decision was made before the window opened, so a visible moderation log and an honest answer about what is still open does more than any amount of promotion.
Log every change you make mid-consultation. If you alter a question after launch, say so and explain why.
How to tell it worked: you can show a dated record of every moderation decision, and your removal rate stays low enough that the consultation still reads as open.
Step 7: Analyze feedback without overstating it
Clean the data, code open text into themes, and separate what people want from the evidence they gave you. Report counts honestly, including where a theme rests on two responses.
Then check who answered. Compare your response profile against the local population and against the groups the proposal affects, and name the gaps. Non-response bias matters: the people most affected are often the least likely to fill in a form.
Preserve minority positions rather than merging them into a summary that reads as consensus. A minority view that nobody raised is a finding worth reporting in its own right.
How to tell it worked: your report shows theme counts, the response profile against the affected population, and a clear statement of what the data cannot tell you.
Step 8: Report results and close the feedback loop
Publish a plain-language outcomes report within a stated timeframe. The structure that works: what we asked, who responded and who did not, what we heard, what we changed as a result, and what we could not change with the reason why.
That last part is where trust is won or lost. Explaining a constraint honestly beats a vague summary, and it is what distinguishes a consultation from a broadcast.
Tell participants what happens next and when. If a decision goes to a committee, name the committee and the date. Where a response challenged the consultation’s legitimacy, address it directly rather than leaving it in a comment thread.
How to tell it worked: someone who responded can find their comment, the team’s response and the outcome without having to ask you.
How long should a public consultation run?
Four to six weeks is the usual working range for a policy or service change, and twelve weeks or more for major infrastructure or planning proposals. Set the dates before you promote anything, publish them, and resist extending the window mid-flight unless you announce it. Short windows are the most common reason a consultation is challenged on fairness grounds.
Common Mistakes
- Vague questions. “Do you support the proposal?” produces noise. Ask what people think of specific options and what would make them support or oppose each one.
- Biased promotion. Pushing through one friendly channel only tells people the outcome is already settled. Spread the invitation and state your own position honestly if you hold one.
- Hidden moderation. Silently removing comments destroys trust when it surfaces. Publish the rules and keep an auditable log.
- Digital-only access. An online-only consultation systematically excludes people without reliable broadband or digital confidence. Fund an offline route with the same reach.
- Overclaiming results. A 200-response online form from a self-selecting group is a signal, not a verdict. Say who responded and who did not.
- Never reporting back. The most damaging failure is silence after the window closes. Publish outcomes with a date you can hold.
- Asking before deciding. Running a consultation on a decision already taken teaches people that consultation is theatre.
Frequently Asked Questions
How to start an online consultation?
Start by writing one sentence naming the exact decision open to public influence, then list what is already fixed and who makes the final call. Choose your response channels, set privacy and moderation rules, and publish dates before you promote anything. A two to three question form tested with 8 to 15 real people beats a long form built in a hurry.
What are the 7 steps of consultation?
Most practitioners describe seven core steps: define the purpose and decision, map the audience and access routes, choose tools, privacy and moderation rules, pilot the form, launch and promote, then moderate and answer questions. Analysis and reporting back follow, which brings the full cycle to eight stages when counted separately.
What are the four Gunning Principles for public consultations?
The four principles are the formative stage, meaning genuine influence on the proposal, sufficient information to understand it, adequate time to respond, and conscientious consideration of what came back. They come from UK case law and are widely adopted in council consultation strategies as a fairness test, though specific legal duties vary by country.
How long should a public consultation run?
Four to six weeks suits most policy and service changes, while major infrastructure or planning proposals usually need twelve weeks or more. Publish the start and end dates before the campaign starts and avoid quietly extending the window. Inadequate time to respond is the principle most frequently breached in practice.
Do I need GDPR for a public consultation?
Yes, in most European contexts you are processing personal data the moment someone submits a form. Apply data minimisation by collecting only what you need, make identity fields optional where possible, publish a retention period, and treat free-text comments carefully since people often volunteer identifying details about others. Requirements vary by country, so check your regulator’s guidance.
How do you report consultation results to the public?
Publish a plain-language report covering what you asked, who responded and who did not, what you heard, what changed as a result, and what could not change with the reason why. Include theme counts and the response profile, and name the next decision point and its date. Reporting the constraints honestly does more for trust than a purely positive summary.
Conclusion
Start with the sentence you have been avoiding: what exactly is open to change, and what is already decided. Publish that, the dates, the rules and the offline route before you build anything else, and the rest of the process becomes manageable.
The consultation steps themselves are straightforward. What builds a reputation for running one well is the unglamorous part: unbiased questions, visible moderation, honest reporting of who did not respond, and a published account of which comments changed the decision.
