Twelve weeks, sixty questions, one policy officer
A department publishes a consultation that matters to your sector: sixty questions, some technical, some about costs, a closing date twelve weeks out. The policy officer circulates it to members with a request for views. Replies trickle in. A large member sends a detailed letter that answers a third of the questions in its own order. A smaller firm replies to the email with three lines. The technical committee discusses it and the minutes capture a few points. Two members phone.
Three weeks before the deadline the policy officer sits down with all of it and starts sorting: which view relates to which question, who said it, whether the large member's point is shared or is theirs alone, and what can be said publicly. The draft gets written in a rush, and sign-off happens the night before it is due.
Why member input is so hard to use
The consultation has a structure, but the request to members does not. Views come back in whatever form each member prefers, and the structure has to be imposed afterwards.
- The request is 'please send us your views', not the consultation's questions.
- Input comes through email, committee minutes, calls and marked-up PDFs, with no single place for it.
- Nothing records whether a member is happy to be named or quoted.
- Nobody can see which questions have no member input yet, until drafting begins.
- Evidence (costs, examples, data) arrives mixed with opinion and gets lost.
What a rushed response costs
A thinner response than your members deserve, and a weaker position with the department. Members who took time to contribute see their point missing from the final submission and wonder why they bothered. Sign-off pressure means less time for your board or policy committee to consider difficult trade-offs between members with different interests.
It also means the next consultation starts from nothing, because the input from this one is buried in an inbox.
A workspace built around the consultation's questions
We build a response workspace for your policy team that turns each consultation into a structured request and keeps everything members send attached to the right question.
- The policy officer loads the consultation's questions, and chooses which ones to put to members, with a short plain-English note on each.
- Members get a form where they can answer the questions that matter to them and skip the rest, attach evidence, and say whether they may be named, quoted or kept anonymous.
- Letters, minutes and emails that arrive another way can be forwarded in; an AI model suggests which question each passage relates to, and the policy officer confirms.
- A question-by-question view shows every member input, grouped by member size, region or activity, with a flag where members disagree.
- A coverage board shows which questions have no input yet, so the policy officer can target specific members or committees early.
- The draft response is written in the workspace or exported to Word, with each point linked back to the input behind it, and sign-off steps recorded.
| Input type | How it arrives | Where it ends up |
|---|---|---|
| Member answer to a question | Consultation form | Under that question, with member type and naming preference |
| Long letter from a member | Forwarded email | Split by question after officer confirms |
| Committee discussion | Minutes added | Linked to the questions it covered |
| Evidence (costs, data, examples) | Attachment on the form | Evidence list for that question |
| Phone call | Officer's note | Logged under the relevant question |
Drafting week, reorganised
The policy officer starts drafting with every member view already sorted by question. Gaps were spotted weeks ago and filled through calls to the right members. Where members disagree, the committee has the split in front of it and can decide how the association will respond. When a member later asks whether their point made it in, you can show them where.
The input stays searchable, so when a follow-up consultation arrives next year, you start from what members already told you.
Does your consultation process look like this?
- You ask members for 'views' rather than answers to specific questions.
- Member input sits across inboxes, minutes and call notes.
- You only find the gaps when drafting starts.
- Nobody records whether a member is happy to be named.
- Sign-off happens the day before the deadline.