Proposal Pipeline
Part of Institutional Design
A structured pathway for ideas to move from initial suggestion through deliberation to formal decision.
Why This Matters
Every community generates more ideas than it can act on. Without a structured pipeline, governance deteriorates in predictable ways: vocal individuals dominate discussion, similar proposals are debated repeatedly without resolution, good ideas die because no one knew how to advance them, and bad ideas get implemented because they happened to be presented at the right moment by the right person.
The pipeline’s core function is to separate the generation of ideas from their evaluation and adoption. When these phases are tangled together — when anyone can propose anything at any meeting and immediate debate follows — the loudest voices dominate and the quality of the idea matters less than the social standing of the proposer. A structured pipeline creates equal access by establishing clear rules about how proposals enter the system, what happens to them at each stage, and what criteria determine whether they advance.
Beyond fairness, the pipeline improves the quality of decisions. Proposals that must pass through review, revision, and deliberation stages arrive at the decision point in better shape than raw ideas debated in the heat of a public meeting. Problems get identified early, alternatives get considered, and affected parties get consulted before commitments are made.
Intake and Initial Screening
The pipeline begins with intake: a designated person or body receives written proposals from any community member. Written submission is important because it forces the proposer to articulate the idea clearly enough to communicate it to someone who was not inside their head. Many vague proposals collapse at this stage, which is a feature, not a bug — fuzzy ideas should not consume collective deliberation time.
An intake officer reviews submissions for basic completeness: Does the proposal state clearly what change is requested? Does it identify who would be affected? Does it explain the problem it addresses? Proposals that fail these tests are returned with specific guidance on what is missing, not simply rejected.
Screening should also check for duplication. If a substantially similar proposal was considered and rejected within the past year, the new submission should note what has changed that warrants reconsideration. This prevents the same argument from being relitigated endlessly while allowing genuine new circumstances to reopen settled questions.
Review and Consultation
Proposals that pass intake move into review. The proposal is distributed to relevant specialists and affected parties for written comment. A proposal affecting water distribution goes to those who manage the water system and those who depend on it. A proposal changing leadership selection procedures goes to all current leadership members and a sample of the general population.
The review period should have a fixed deadline — typically two to four weeks for most proposals, longer for those with major resource or rights implications. Comments received within that period are compiled and attached to the proposal. The proposer then has an opportunity to revise their submission in light of the comments, producing a second-draft proposal that reflects what was learned in review.
This stage often reveals problems invisible to the original proposer. Ideas that seem clean in the abstract frequently have complicated interactions with existing arrangements that only affected parties recognize. The review process surfaces these complications before the community commits to a course of action.
Deliberation and Amendment
With review complete, the proposal enters formal deliberation. A well-prepared proposal that arrives with a clear problem statement, a specific proposed solution, and documented responses to anticipated objections requires much less debate time than a raw idea.
Deliberation should follow structured rules: a fixed total time for discussion, equal speaking opportunities for supporters and critics, and a formal amendment process that allows the proposal to be modified rather than simply accepted or rejected wholesale. Many good proposals fail because the community is forced to vote on a binary when a modified version would command wide support. An amendment process captures this middle ground.
After deliberation, the presiding officer calls for a vote or consensus determination according to the community’s adopted decision procedure. The outcome — adoption, rejection, or referral back for further revision — is recorded in the precedent file along with the vote count and a summary of the main arguments made.
Implementation Tracking
A proposal pipeline that ends at adoption has accomplished only half its work. Adopted proposals must be implemented, and the pipeline should include a tracking mechanism to ensure that decisions result in action. Each adopted proposal should be assigned to a specific person or body responsible for implementation, with a target completion date.
Status updates on open implementations should appear as a standing agenda item at regular governance meetings. When implementations fall behind schedule, the delay and its reasons should be formally noted. This accountability mechanism prevents the common dysfunction of communities that make decisions enthusiastically and then allow them to quietly die during implementation.
When implementation reveals that an adopted proposal has unforeseen problems, there should be a clear path to bring that information back through the pipeline for amendment. The pipeline is not a one-way door — it is a feedback loop that connects decisions to outcomes and allows institutional learning.
Maintaining Pipeline Health
Over time, pipelines accumulate clutter. Old review categories become outdated, submission forms grow cumbersome, screening criteria drift from their original purpose. Periodic review of the pipeline itself keeps it functional.
Once or twice a year, the community should examine the pipeline’s performance: How many proposals entered? How many were adopted? How many were implemented successfully? Where are proposals getting stuck? This review, conducted openly with results shared publicly, demonstrates that the governance structure is itself subject to improvement — which is perhaps the most important signal a legitimate institution can send.