Being Consulted Is Not the Same as Having the Decision Explained

An invitation to speak leaves important questions unanswered

A public institution opens a survey, holds a meeting or requests comments. Participation is visible, and the invitation may be useful. It does not yet establish what influence the contributions can have. Some parts of a proposal may be open to change while others are already fixed. The institution may be gathering experiences, choosing between options or testing how a decision will be communicated. These are different processes. People cannot assess their role well when the invitation uses the same broad language of having a voice for all of them.

This matters because disappointment is often interpreted too simply. Officials may assume that a person dissatisfied with the outcome refuses to accept democratic disagreement. Participants may assume that an outcome they opposed proves the consultation was fake. Either conclusion can miss the actual process. The more precise questions concern what was promised, which input was received, how it was considered and what reasons connect the final decision to that consideration. An accountable process need not adopt every preference. It should be intelligible about what participation was for.

Continue this question: How Public Power Works: From Promises to Accountability →

Read the scope before writing the response

Consider a hypothetical consultation on redesigning a public square. Residents are invited to comment, but the project budget and road boundary have already been set. Some submit detailed proposals requiring the road to be moved. If the fixed conditions were not clear, their effort may have been invited under a misleading impression of possibility. If the limits were clear, the response can still challenge their justification, but it should distinguish that challenge from feedback on the options actually under review. Clarity helps participants direct their effort rather than merely produce a larger collection of comments.

Ask what decision is being made, who holds authority and what can change through the process. Check the actual documents, timetable and submission requirements. Do not assume that a social media comment enters the official record. If a relevant group may struggle to participate, ask what accessible route exists rather than interpreting low response as agreement. These are general process questions, not a statement of particular legal rights. The applicable obligations and challenge mechanisms depend on the institution, jurisdiction and decision involved; consequential disputes may require appropriate professional advice.

Connect a contribution to the decision it could improve

A useful submission distinguishes experience, evidence, preference and proposed action. Describe the specific problem and why the suggested change addresses it. If you oppose a proposal, identify the consequence you are concerned about rather than relying entirely on a judgment about the officials' motives. Motives may matter, but an allegation without evidence can distract from a practical issue the institution could actually answer. A well-structured contribution should remain understandable to someone who does not already share your view.

Include uncertainty where it belongs. If a cost is an estimate, identify the basis and limits. If a claim depends on local experience, describe whose experience and which setting. If you suggest an alternative, consider the constraints it would encounter. This is not a requirement for citizens to become unpaid experts before they may speak. Lived experience and questions can be legitimate contributions. It is a way to make the relationship between your input and the decision as clear as possible, so that an eventual response has something more specific to address than general approval or disapproval.

Continue this question: Trust Needs Institutions That Can Be Questioned →

Follow the feedback loop after the closing date

OECD's guidelines emphasize clarity about expected results and communication about how input was used, including reasons when recommendations are not adopted. That provides a useful benchmark for examining a process. Look for a report, response or other appropriate account of what happened next. Does it identify the principal issues? Does it explain significant changes or the reasons for retaining the original approach? A count of responses is information about participation. It is not, by itself, an explanation of how the decision was assessed.

Keep your own evaluation proportionate. A decision can be reasoned and still be one you oppose. A consultation can improve a project while failing to include some relevant voices. Different limitations may require different forms of follow-up: a request for clarification, participation in a later review or use of an applicable complaint or challenge process. Avoid treating one disappointing outcome as proof that all participation is pointless. Equally, do not accept the mere existence of a meeting as sufficient evidence that public input had a meaningful role. Examine what the process actually made possible.

If an institution publishes a summary, compare it with the scope originally announced. A changed process may be justified, but the change itself should be visible enough for participants to understand why the expected influence differs.

The CyGuru lens concerns the structure through which authority becomes accountable. An institution gains little durable credibility from inviting expression that has no defined relationship to a decision. Citizens also need a clearer measure of influence than whether their preferred outcome won. Scope, consideration, reasons and feedback create that measure. A useful public process can say what it asked, what it heard, what it changed and why. Without those connections, participation risks becoming a ceremony whose most visible product is evidence that people were allowed to speak.