Skills on AI

Active theme: Light

Government Public Consultation

Use when asked to design or run a public consultation — a structured, proactive process for gathering public input before a government decision is made — noting that the legal requirements, formats, and terminology vary by country and level of government (a UK government consultation, a US federal or state public-input process, and a local council consultation each follow their own rules for scope, notice, and duration).

A public consultation is a structured process a government body runs to gather public input before a decision is made, rather than after. It's proactive, not reactive: unlike a Freedom of Information Request, which is a request for records the government already holds, a consultation is an invitation for input on a decision that hasn't been made yet. What triggers a consultation requirement, how long it must run, and what form it takes vary by country and level of government — a UK government consultation, a US federal or state public-input process, and a local council consultation each have their own rules, so check the applicable requirement before relying on any one model as universal.

Key components

  • A clearly scoped question — a specific decision, proposal, or set of options the consultation is actually asking about, stated precisely enough that a response can be evaluated against it.
  • Genuinely accessible channels — ways to respond that reach people beyond those already following the issue: not just a webpage or online form, but outreach through channels the affected public actually uses (local notices, community organizations, in-person sessions, non-English-language materials where relevant).
  • A defined and adequate response period — enough time, clearly communicated, for people to become aware of the consultation, read the proposal, and respond, rather than a technically-open window too short or too obscure to generate meaningful participation.
  • A published summary of what was heard — the range of views received, including significant disagreement, made public rather than held internally.
  • A stated account of how the input influenced the decision — what changed as a result of what was heard, or a stated reason why it didn't, published alongside or shortly after the final decision.

Why publishing what changed (or didn't) matters for credibility

A consultation whose outcome was effectively decided before it opened, with input gathered only as a procedural formality, is recognized as such quickly — respondents notice when a final decision bears no visible relationship to what was said during the consultation. That recognition doesn't stay contained to the one decision; it teaches people that engaging with the next consultation is a waste of their time, which lowers response quality and participation on every future consultation that body runs. Publishing a clear account of what was heard and how it did or didn't change the outcome is what makes the next consultation worth responding to — it's the mechanism that keeps the process itself credible over time, not just this one decision.

Common pitfalls

  • A question posed so broadly that responses are unusable — an open invitation to comment on anything related to a broad topic produces a scattered set of responses that can't actually be weighed against each other or used to inform a specific decision.
  • Engagement limited to channels that reach only the already-engaged — publishing a consultation solely on a website or portal that only people already following the issue would think to check excludes the wider public the consultation is meant to reach, and skews the responses received toward existing stakeholders.
  • A response period too short or too obscure to generate real participation — technically satisfying a minimum notice period while giving affected people little practical chance to learn about it and respond defeats the purpose of consulting at all.
  • A decision announced afterward with no visible connection to what was heard — publishing a final decision without any account of the input received, or with only a token nod to "public feedback," leaves no way to tell whether the consultation actually mattered.
  • Treating a large but shallow response volume as if it settled the question — a high number of near-identical responses (for example, from a campaign) can look like strong support or opposition without reflecting the breadth of views actually held; volume isn't a substitute for weighing the substance of what was said.

Learn more

View government-public-consultation/SKILL.md on GitHub