Position development before a comment deadline

When to use it

A regulator, ministry, or standards body has opened a consultation with a published closing date. An association, professional body, chamber, or union has to file a response, and the response is supposed to represent the membership. What usually happens is that a committee of five drafts it, circulates it for comment in the last week, receives four replies, and files it. The membership finds out what its position is by reading the submission.

This session puts the membership's input in front of the drafting rather than after it. Ninety minutes, once per consultation, and the group's own theme names become the structure of the submission.

The scheduling advantage here is unusual and worth building a practice on. Comment deadlines are published in advance, often months out, and most sectors have a predictable annual set of them. A facilitator who watches the relevant consultation calendars can book a year of these sessions ahead of time rather than waiting for the phone to ring.

Do not use it when the association's position is already settled and the submission is written. Running a session to decorate a finished document wastes the members' evening and they will recognize what happened. Also do not use it when the consultation is narrow and technical enough that the answer is a matter of expertise rather than of membership interest; three specialists and a document will serve better than thirty people and a session.

The question

The consultation document is written in the regulator's language. The question has to be in the members' language, and it has to ask about consequences rather than about the proposal.

Seeds, cultivate one against the specific consultation:

• If this change goes ahead as written, what happens in your practice or your business on the first day it takes effect?
• What does the proposal assume about how this work is done that is not true?
• What would make this workable, if it is going to happen anyway?
• What is the consequence nobody outside this room is going to raise?

The question that fails: "Do you support the proposed changes?" It produces a split the submission cannot use, it invites the session to be read as a vote, and it discards the entire reason to gather people: the specific operational consequences only they know about.

Session settings

• Participants: cap at expected headcount plus five
• Anonymous participation: on. Members who compete with each other, or who depend on the regulator being consulted, will not speak candidly with their name attached
• Raffle: off
• Blind gather: on
• Blind then reveal voting: on
• Shuffle order: on
• Access after finish: on, so members can see the input that fed the submission

Run of show

Ends at: Resolve, the closing segment, and the submission depends on it: the endorsements and reservations recorded there are what let the draft report agreement and dissent honestly.

Facilitator notes

Competition law, for industry associations. This is a hard rule, not a nuance. Keep price-adjacent and market-allocation questions off the board entirely. That means no question, and no permitted line of discussion, touching on what members charge, what they intend to charge, margins, discounting, how to respond to a competitor's pricing, which customers or territories members serve, or which ones they will not. An anonymous room full of competitors discussing pricing is the exact fact pattern competition regulators exist for, and anonymity makes it worse rather than better, because it removes the inhibition that would otherwise stop it. Brief the client on this before the question is cultivated, and if a contribution heads that way during Gather, hide it during Emerge and say why out loud. If the consultation itself is about pricing regulation, get the association's counsel to scope the question before you run anything.

Be exact about what the session is. It informs the position. It does not adopt it. The association's board or council adopts positions under its own governance, and the members in the room need to hear that at 0:00 and again at 1:22. If anyone leaves believing they voted the association's position into existence, you have created a governance problem for your client.

A split is a finding, not a failure. Consultations are frequently answered by associations whose membership genuinely disagrees, and a submission that reports "our members divide on this, here is the shape of the division and here is what each group is worried about" is more credible to a regulator than false unanimity. The Resolve step exists to capture that cleanly. Do not flatten it.

Watch the segment effect. A theme raised by a small number of members may reflect a segment of the membership that a proposal would hit hardest, not a fringe view. Check the unclustered pile for this specifically before it gets summarized away.

Turning the session into the submission

Export from the session overview, as CSV or JSON.

• The group's theme names become the submission's section headings. This is the single highest-value thing the session produces. The headings are the membership's words rather than the drafting committee's, and that is defensible in a way a committee's framing is not
• The pattern sheet becomes an appendix. It carries each theme, the AI's draft name beside the name the group chose, the number of contributions behind it, and its up, down, starred and comment totals. A regulator reading the appendix can see how the position was arrived at. The endorsements and reservations recorded in Resolve are not in the export; take those from the synthesis report
• The contributions sheet supplies the specifics. Regulatory submissions are stronger with concrete operational consequences than with general statements of concern, and this is where those are
• The export carries no member identities, which is what makes it safe to attach. Nobody's individual view is attributable, including to the association

Say in the submission how the input was gathered, including the number of participants and the fact that they were self-selected members rather than a survey of the membership. Regulators read a lot of submissions claiming to speak for a membership; the ones that describe their own method are treated differently.

What the group leaves with

The themes they named, which consequences are widely shared and which are specific, where the membership divides and on what, and a stated date for the draft submission. Members also leave knowing their input reached the drafting stage rather than the comment stage, which is usually the first time that has happened.

The failure mode

The committee's existing draft gets rubber-stamped, because the question was written from it. This is the same failure as the strategy offsite, and it looks the same: a smooth session, high agreement, themes that restate the brief, and nothing the drafting committee did not already believe.

Prevent it in the question, before the date is booked. If the client hands you a spark built from their draft position ("How should we make the case against the proposed licensing change?"), rewrite it with them into something that can produce an answer they did not expect ("What happens in your practice if the licensing change goes ahead as written?"). If you notice during Emerge that every theme is a restatement of the committee's position, say so to the room and ask directly what is missing. In a membership consultation that question almost always produces the segment whose interests the draft had overlooked, which is the finding that makes the session worth having.