Assembly Structure
Part of Institutional Design
Designing forums where community members exercise collective voice in governance.
Why This Matters
The assembly — a gathering of community members to discuss and decide on shared matters — is the most direct expression of collective governance. In small communities, the assembly may be the primary decision-making body, with every adult having a direct voice. In larger communities, the assembly may be a periodic check on representative bodies, a space for community input on major decisions, or a forum for accountability.
Assemblies that function well are remarkable: they aggregate distributed knowledge, build community investment in decisions, expose poorly-reasoned proposals to scrutiny, and produce decisions with genuine legitimacy because participants have a real voice. Assemblies that function poorly waste enormous amounts of time, produce shouting matches rather than decisions, are captured by a few vocal individuals, and exhaust participants until attendance drops to nothing.
The difference lies almost entirely in structure. A well-run assembly has clear procedures, a defined purpose, effective facilitation, and mechanisms for ensuring that the range of voices in the community are heard — not just the loudest ones.
Assembly Types and Purposes
Not all assemblies serve the same purpose. Define which type you are convening and design the format accordingly.
Deliberative assembly: Purpose is to discuss and decide. Agenda includes specific proposals that will be voted on or accepted by consensus at the meeting. Requires preparation, structured discussion, and a clear decision process.
Informational assembly: Purpose is to communicate. Leadership reports on community status, recent decisions, upcoming plans. Members can ask questions and express concerns but decisions are not made at the gathering. Easier to run well; less powerful.
Consultative assembly: Purpose is to gather input before a decision is made elsewhere. Leadership presents a problem or proposal and solicits community views. No vote; results inform deliberations by decision-making bodies.
Accountability assembly: Purpose is to review the performance of governance bodies and officials. Reports, questions, and expressions of approval or concern. May include votes on whether to continue, modify, or remove specific arrangements.
Most communities need all four types at different times. Being clear about which type a given assembly is prevents the confusion that arises when deliberative forums turn into informational ones, or when members expect a consultative forum to produce binding decisions.
Sizing and Participation
Small community full assembly (under 100 people): Everyone participates directly. Direct democracy is feasible. Everyone speaks; consensus methods may work. The principal design challenge is ensuring that all voices are heard, not just the loudest or most socially dominant.
Medium community assembly (100-500): Full assembly possible but requires more structure. Agenda must be tightly managed. Discussion time per item must be limited. Representation methods (spokespeople for working groups or households) may be used for some items.
Large community (500+): Full assembly becomes logistically difficult and participatorily unequal — a few vocal people dominate in large groups. Consider: representative assemblies (elected or sortition-based delegates speak for constituencies), rotational participation (different community members attend each session), or tiered assembly (local-level meetings feed into community-wide meetings).
Designing Effective Procedures
Advance agenda: Circulate the agenda — with sufficient detail to allow preparation — at least one day before a deliberative assembly, longer for complex topics. Members who show up unprepared or uninformed cannot participate effectively.
Facilitation role: Designate a facilitator for each assembly. The facilitator is not a decider — they manage the process. They recognize speakers, enforce time limits, keep discussion on topic, summarize what has been said, check for agreement, and manage the transition between agenda items. Separate the facilitation role from participant roles; facilitators should not be advocates for specific positions.
Speaking protocols: Establish clear norms for who speaks and when. A speaking queue prevents a few people from monopolizing the floor. Time limits per contribution — typically two to five minutes — prevent filibustering. Distinguish between first contributions (hearing from new voices) and responses (clarifying or reacting to what has already been said).
Decision methods: Different situations call for different decision methods. Consensus is appropriate for smaller groups and matters requiring high buy-in. Majority vote is appropriate for clear binary choices. Supermajority requirements are appropriate for fundamental matters. Define in advance which method applies to which categories of decision.
Inclusion and Voice Distribution
The persistent failure of assemblies is domination by a few voices. Counter it actively:
Reserved speaking: Formally reserve some speaking time for those who have not yet spoken. A facilitation technique: before allowing second contributions, ensure everyone who wants to speak once has had the opportunity.
Small group discussion: For complex or contentious topics, break into groups of five to eight for 15-20 minutes before full assembly discussion. Small groups are more participatory; the full assembly then hears reports from each group. This ensures that quieter voices get heard at least in the smaller setting.
Written contribution: Allow members to submit written input before or during the assembly, to be read aloud or summarized by the facilitator. This enables participation from people who are not comfortable speaking publicly.
Child and elder participation: Define how the very young and very old participate. Some communities allow proxy participation through household representatives. Others create age-appropriate forums that feed into the main assembly.
Record-Keeping and Follow-Through
Every assembly must produce a written record: who attended, what was discussed, what was decided, and what follow-up actions are assigned to whom with what deadline. Without this record, decisions evaporate, assigned tasks go untracked, and the next assembly must reconstruct what was already agreed.
Designate a record-keeper for each assembly. Circulate the draft record to participants for correction within a day or two. Archive the final version in the community’s central records.