How to respond to a government consultation: a practical guide

Knowing how to respond to a government consultation is one of the most useful skills in UK public affairs, and one of the least taught. Departments and regulators are required to seek views before they change policy, and the window is genuinely open: a well-argued response from a small charity sits in the same pile as one from a FTSE 100 public affairs team. What separates the responses that shape policy from the ones that get skimmed is evidence, and above all whether you brought the voices of the people the policy will affect. This guide covers the whole process.

What a government consultation actually is

A consultation is a formal invitation from a department, regulator or other public body to comment on a proposal before a decision is made. Some are required by statute. Others follow the Cabinet Office's Consultation Principles, which commit departments to consulting at a stage where views can still shape the outcome, in plain English, for a proportionate length of time.

That last point matters for your planning. There is no longer a fixed 12-week rule: consultation periods are set case by case, and some run for as little as four weeks. If a consultation touches your organisation's work, the clock starts the day it opens.

Where to find open consultations

• GOV.UK lists central government consultations, filterable by department and topic. This is the master list for Whitehall.
• Citizen Space platforms. Many bodies, including the Scottish Government and several regulators, run consultations on their own Citizen Space sites rather than GOV.UK.
• Regulators' own websites. Ofgem, Ofcom, the FCA, the Charity Commission and others publish consultations on their own sites, sometimes with little wider publicity.
• Select committee inquiries. Not consultations in the formal sense, but committees issue open calls for written evidence that work in a similar way.

The honest difficulty is not finding consultations once you know they exist. It is hearing about them in time, because a four-week window is easy to miss. Watch out too for parallel consultations: departments sometimes spin a significant technical question out into a separate, quieter consultation that gets far less attention than the headline one. If you spot that happening in your area, respond to both, and say in your response if the quieter one was hard to find or hard to understand.

Before you write: read the whole thing properly

Most weak responses fail here. Before drafting:

1. Read the actual questions. Consultations ask numbered questions, and officials analyse responses question by question. An eloquent essay that ignores the numbering is hard for them to use.
2. Check the scope. Consultations are often narrower than their titles suggest. Know what is in scope before you spend your word count.
3. Notice what the questions do not ask. The gaps are findings in themselves. Most consultations end with a catch-all question along the lines of "is there anything else you would like to say?", and that is the right place to raise issues the document should have covered but did not.
4. Check the proposal against the existing rules. Many proposals restate duties that already exist in legislation, guidance or codes of practice. If the real problem is that an existing duty is not being enforced, saying so, with the specific provision named, is one of the strongest points a response can make.

Ask the people the policy will affect

This is the single biggest difference between an average response and an influential one. A department can read your organisation's opinion anywhere. What it cannot get anywhere else is systematic evidence of what the people you support, employ or represent actually think about these specific proposals.

You do not need a research team:

• Run a short survey. Take the consultation's own questions and rewrite them in plain language, asking about lived experience rather than policy abstractions. Put it in front of your members, service users or supporters for a few weeks. Even 50 to 100 responses give you percentages worth quoting and testimony worth hearing.
• Hold a workshop with your frontline staff. The people delivering your services will spot practical consequences in a proposal that a policy team reads straight past.
• Go where the affected people already gather. Attend the sessions other organisations, forums and the department itself run on the proposals. You will learn how the proposals are landing and where your evidence fits.

Then put the results in the response itself: the numbers ("of the 90 parents we surveyed, 77% said…") and short verbatim quotes, clearly marked as the words of the people affected. Be honest about sample sizes, and where views were mixed, say they were mixed. A response that reports genuine disagreement among its own community reads as evidence. One that claims unanimity reads as lobbying.

How to write the response

Officials analysing responses are usually working through hundreds of them against a deadline. Everything below follows from that fact.

Open with who you are, in facts. How long you have operated, how many people you support or represent, what services you run, any inspection ratings or accreditations. Two or three bullet points of concrete facts do more for your credibility than a page of mission statement, and they tell the reader exactly why your evidence on each question deserves weight.

Add a short section on how you gathered views. List the survey, the workshops, the sessions you attended, with numbers. This tells the department your response carries other voices than your own, and it makes every statistic that follows trustworthy.

Answer in their structure, and number your points. Use the consultation's question numbers as your headings, and number your paragraphs beneath them (1.1, 1.2, and so on). It looks bureaucratic. It is also exactly what makes individual points easy to find, cite and count in the analysis. Skip questions where you have nothing to add.

Use three kinds of evidence, and label them. Your own service data (what your caseload, waiting lists or delivery experience shows). Your community's voice (the survey numbers and quotes). Published sources (official statistics, court judgments, sector research), cited so the reader can check them. A response that braids all three is very hard to dismiss.

Agree where agreement is deserved. If the proposal gets something right, say so before you set out your concerns. And when a question asks you to agree or disagree on a scale, pick the answer your evidence supports, even if that is the middle option, and explain why. Credibility on the points you concede buys attention for the points you contest.

End every answer with a recommendation. Not "this is concerning" but "the department should…", one specific change per point. Recommendations are what get lifted into the government response. Criticism without an alternative gets summarised as "some respondents disagreed".

Comment on the process where it fails. If a question cannot be answered without specialist legal knowledge, if the document is inaccessible to the people it most affects, or if the timetable is too short, say so in the response. Consultation quality is itself a legitimate subject of consultation.

A structure you can reuse

1. Introduction. Who you are, in concrete facts, and your interest in the proposals.
2. How we gathered views. Your survey, workshops and engagement, with numbers.
3. Answers to the consultation questions. Their numbering, your decimal-numbered points, evidence before opinion, a recommendation at the end of each.
4. The catch-all question. The gaps the consultation should have covered, raised concisely.
5. Offer and contact. An offer to share your full findings or discuss them, and a named person with their role and email address. Departments do take up offers like this, and the conversation that follows is often worth more than the submission itself.

Assume your response will be published or summarised publicly unless you mark it confidential.

Deadlines, and what happens after you respond

Submit before the closing date. Late responses are sometimes accepted, but there is no obligation to consider them, and online forms simply close.

After the consultation closes, the department analyses responses and publishes a government response, normally on the same page as the original consultation. The Consultation Principles say this should appear within 12 weeks of closing, or the department should explain why not. Read it even when the decision goes against you: it tells you which arguments moved the department, which is intelligence for the next round.

Then close the loop with the people who helped you. If members, service users or staff gave you their views, go back to them once the government response is out and tell them what happened: what the response said, where their evidence appeared, and what your organisation will do next. It is basic good practice, and it is also how you keep people willing to contribute. Someone who filled in your survey and then heard nothing will think twice next time. Someone who saw their words quoted in a submission, and got an honest account of the outcome, will bring others with them.

One more thing worth knowing: consultation is a legal duty in some cases, and the courts apply what are known as the Gunning principles. Consultation must happen while proposals are still at a formative stage, with enough information and time to respond intelligently, and responses must be conscientiously taken into account. If a consultation you care about is plainly a done deal, that is not just bad practice, it can be unlawful.

The short version

Find consultations early. Read the questions, the scope and the gaps. Ask the people the policy will affect, and bring their numbers and their words. Answer in the consultation's own structure, ground every point in evidence, concede what deserves conceding, and end every answer with a specific recommendation. Offer more, name a contact, and submit on time. When the outcome lands, tell the people who helped. Do that consistently and your responses stop being letters into the void and start being part of how policy gets made.