Every organization — a school board, a corporate committee, a neighborhood council, a nonprofit board, an advocacy group — requires oversight. Someone must ensure that decisions are made, that they reflect the interests of those affected, and that they are carried out. This is governance: not a bureaucratic add-on, but the core operating system of any collective endeavor.
Governance is not the exclusive function of large institutions or formal bodies. It is present wherever a group of people must make decisions together and be accountable for them. Most of the time it is invisible — happening through habit, hierarchy, and whoever called the meeting. That invisibility is precisely where accountability breaks down.
The problem is not governance itself. The problem is overhead: the accumulated process, ceremony, and friction that obscures rather than serves the oversight function. Meetings multiply. Email threads proliferate. Accountability diffuses. The overhead grows while the oversight weakens.
The goal of this framework is oversight without overhead — governance that is rigorous, accountable, and inclusive, without requiring bureaucratic machinery, professional facilitators, or enterprise software budgets to operate.
"Participatory Governance is a formalized way to ensure meaningful participation and community engagement in decision-making processes." (US EPA)
Participatory governance asserts that oversight is strongest when the people affected by decisions have a structured role in shaping them. This is not a novel idea — it is the operating principle behind democratic institutions, cooperative organizations, and community boards of every kind. What is new is the opportunity to make it work better: more inclusively, more transparently, and with far less overhead than conventional practice has assumed.
Participatory governance is distinct from governance-as-service-delivery (how a government provides services to citizens) and from governance-as- compliance (how an organization follows rules). It is specifically concerned with how a governance body — a board, committee, or leadership team — engages its stakeholders in the decisions that affect them, and then acts accountably on what it hears.
The Participatory Governance Framework is a theoretical framework: a structured description of the distinct processes through which participatory governance operates. It is not a software product, a methodology manual, or a prescribed set of tools.
Its primary purpose is to provide vocabulary — a common language for describing what governance bodies do, what software tools support those activities, and where gaps exist. This vocabulary makes it possible to evaluate, compare, and improve the tools and practices used for governance work.
Just as importantly, the framework is an act of unification. Task management, community consultation, prioritization, and formal decision-making are usually treated as unrelated categories of software, built by unrelated vendors, marketed to unrelated buyers. This framework asserts that they are not unrelated at all — they are stages of a single governance workflow that has simply never been described as one thing before.
The framework defines a set of capability functions — each describing a distinct governance function. These functions are:
Governance methodology has a gap. Agile brought rigor to execution but left stakeholder participation undefined. Civic technology opened participation but rarely connects it to execution. Professional facilitation methods work but depend on trained experts and synchronous rooms. The Participatory Governance Framework defines what none of them do alone: the complete operational workflow from community inquiry through deliberation, decision, and execution — modality-independent, applicable to any body that governs on behalf of others.
The six capability functions cluster into three anchor pairs. Each pair spans the same underlying activity across two moments — a broad, open moment and a narrower, decisive one — and each anchor has historically been addressed by a different, disconnected part of the software industry.
| Anchor | Broad / Open Function | Narrow / Decisive Function | Historically addressed by |
| Execution | Inquiry Handling | Task & Project Management | Enterprise workflow vendors (ServiceNow, Jira, Monday, Trello) |
| Discovery | Sense Making | Ideation & Proposal Development | Civic-tech and consultation platforms (Decidim, Pol.is, Go Vocal) |
| Resolution | Prioritization | Voting & Decision Affirmation | Civic-tech voting tools and, informally, meetings |
This framework's central claim is that these three anchors are not separate product categories — they are three stages of one governance workflow. Even where a vendor's feature set happens to touch all three, no existing methodology names them as a single, connected workflow with its own vocabulary and maturity model. That naming — and the connective tissue between the anchors — is what this framework contributes.
Execution is the most mature anchor from a tooling standpoint. Enterprise vendors solved inquiry intake and task management years ago. But that maturity has not translated into adoption by small and volunteer organizations — the tools are built and priced for full-time enterprise teams, and a school board or advocacy group perceives them as overhead rather than help, even when the underlying capability is exactly what they need.
Discovery and Resolution are where civic technology has concentrated its efforts — and for good reason. These are the anchors where meetings and paper-based processes fail most visibly: a town hall poorly captures the range of community sentiment, and a show of hands poorly captures a considered, auditable decision. Civic-tech vendors emerged specifically to solve these failures, which is why the Participation-layer vendor landscape is comparatively rich.
No vendor category has emerged to connect all three. That connective layer — the sequencing and hand-offs between Execution, Discovery, and Resolution — is what this framework names and what the accompanying capability matrix is designed to measure.
Jira and ServiceNow are built around known work — someone defines a task, assigns it, and tracks it to completion. Governance is fundamentally about contested decisions — the work itself is undefined until stakeholders participate in shaping it. A Jira ticket assumes someone already knows what needs to be done. A governance process exists precisely because nobody does yet. The Discovery and Resolution anchors are what transform ambiguous community input into defined, assignable work. Execution-anchor tools have no model for that upstream process.
The functions of this framework are modality-independent. Each describes a governance function that predates software entirely — performed in person with pen and paper long before computers existed in the workplace. Technology does not change what governance bodies need to do. It changes how well, how inclusively, how transparently, and how asynchronously they can do it.
The traditional / current / emerging structure for each function describes how the function has been performed across eras of practice. "Traditional" describes well-established approaches that remain in wide use. "Current" describes practices and tools in active adoption today. "Emerging" describes practices and tools that exist and are in use in leading organizations, but are not yet widely adopted.
How a governance body receives, acknowledges, routes, and responds to questions and concerns from stakeholders.
| Traditional | Written letters, public comment periods, open office hours, suggestion boxes. A constituent mailed a letter to their alderman. Response was slow, inconsistent, and rarely tracked. |
| Current | Email, help desk tickets (ServiceNow, Zendesk), online forms, social media mentions. Mature tooling exists but is rarely integrated with governance workflows downstream. |
| Emerging | AI-powered triage that routes incoming inquiries into the appropriate governance function — triggering a discovery process, a proposal, or a direct task assignment. Automatic acknowledgment, status tracking, and closed-loop reporting back to the inquirer. |
How a governance body assigns, tracks, and completes the work that decisions generate. Without this layer, governance produces deliberation but not results.
| Traditional | To-do lists, meeting minutes with action items, verbal delegations. Accountability depended entirely on the chair's memory and follow-through. |
| Current | Jira, Trello, Monday, Asana — mature, widely adopted, and well-understood. Rarely integrated with participation tools; the connection between "we decided X" and "here are the tasks X generated" is almost always manual. |
| Emerging | Tasks auto-generated from ratified decisions, linked back to the originating inquiry, with progress visible to stakeholders. Closed-loop reporting: the community that raised the issue can see what was decided and what is being done about it. |
How the governance body and its stakeholders explore options, surface trade-offs, and develop a shared understanding of a problem before deciding.
| Traditional | Public hearings, town halls, committee debate, expert testimony. Participation was limited by geography, time, and who received an invitation. |
| Current | Online surveys, Pol.is (real-time consensus mapping), structured consultation platforms (Go Vocal, Citizen Space), AI-assisted sentiment analysis. |
| Emerging | AI synthesis of large-scale community input across multiple channels, real-time visualization of where consensus and disagreement lie, bridging algorithms that surface common ground across divergent viewpoints. |
How raw ideas are surfaced, structured, and refined into proposals ready for deliberation. Includes both individual submission (idea collection) and collaborative co-creation (proposal drafting).
| Traditional | Brainstorming sessions, written proposals submitted to a committee, drafting meetings where a small group shaped a document for wider consideration. |
| Current | Idea boards (Decidim, Your Priorities), collaborative document editing, platforms like Loomio and Adhocracy+. Significant variation in how well tools support the refinement stage versus just the submission stage. |
| Emerging | AI-assisted proposal refinement, automatic detection of duplicate or related ideas, structured templates that guide submitters toward actionable proposals, full version history linked to the governance record. |
How a governance body decides what to work on next — allocating finite attention, time, or resources across competing proposals.
| Traditional | Chair discretion, informal consensus, first-come-first-served agenda setting. Prioritization was often invisible and unaccountable. |
| Current | Planning poker (Agile), dot voting, participatory budgeting tools (Balancing Act, Decidim). Better than traditional practice but rarely connected to a structured criteria framework or audit trail. |
| Emerging | Weighted community input feeding directly into a ranked backlog, with transparent criteria, documented rationale, and a full audit trail of how priorities were set and by whom. |
How stakeholders formally express preferences among defined options, and how the governance body ratifies, documents, and communicates the resulting decision. The moment where deliberation becomes commitment.
| Traditional | Show of hands and written ballots (Robert's Rules motions and recorded votes), followed by the gavel, signed minutes, and a posted public notice. Formal but limited to those physically present, and the record existed as a disconnected physical artifact. |
| Current | Online polls, ranked-choice tools, liquid democracy platforms (LiquidFeedback, Loomio), and encrypted e-voting (Belenios, Sequent) for casting preferences; email approval chains, DocuSign, and published meeting minutes for ratification. More accessible but fragmented — the decision record rarely links back to the deliberation or vote that produced it. |
| Emerging | Verified, auditable digital voting with adaptive formats by decision type, integrated end-to-end with formal ratification — traceable from the originating inquiry through discovery and voting to the signed decision and the tasks it spawned. Decisions become navigable records, not isolated documents. |
This framework is not anti-meeting. Synchronous gatherings serve real psychological and social functions — particularly for decision affirmation, where the felt sense of shared presence builds commitment and accountability that async tools have not yet fully replicated.
The framework's position is: meetings where necessary, async everywhere else. A governed meeting is one where the agenda is drawn from the structured workflow, the discussion is bounded by a defined function, outputs are formally captured, and results are routed back into the appropriate next function.
Current AI meeting tools (Otter.ai, Fireflies, Read.ai, Fellow) address transcription and action-item extraction well, and adoption of this category is already widespread. Our expectation is that most governance bodies — even small, volunteer-run ones — will adopt some form of Virtual Meeting Assistant as a matter of course over the next several years, the same way email and video calling became default infrastructure rather than optional tools.
A Virtual Meeting Assistant will earn its place through transcription and action-item capture, and that support grows more valuable as the assistant learns to tell which function a given stretch of discussion is serving. The condition for that is on the group's side, not the vendor's. A body that knows its own functions — that can recognize when it has shifted from sensemaking into deciding, and name the output each moment should leave behind — gives the assistant something to attach to. The clearer a group is about how it governs, the more an assistant can do to help it govern well.
| Approach | Strengths | Gaps addressed by PGF |
| Meeting-based | Familiar; flexible; good for decision affirmation; provides social commitment | No structured upstream process; no execution layer; no audit trail; excludes async participants |
| Agile / Scrum | Strong execution and task management; introduced team-level prioritization | Stakeholder prioritization is a black box; no discovery layer; rigid time structures; designed for known work |
| Facilitation methods | Effective for structured deliberation; skilled practitioners produce real results | Expert-dependent; synchronous only; no persistent record; not scalable; tacit and proprietary |
| Civic-tech tools | Strong Discovery and Resolution features; open-source options available | Rarely connect to Execution; priced for enterprise, not volunteers |
| Gartner e-gov model | Government IT maturity roadmap | Focused on service delivery by government, not decision-making by governance bodies |
Ask a board at year's end how many ideas it considered, how many it delivered, or how many people it answered, and for many of these, no one kept count. The work happened, and then it dispersed, leaving no record anyone could total. A body running on connected domains can reconstruct that record, because each idea it heard, each decision it reached, and each task it finished left an artifact behind. The measures are simple because the accounting finally exists to fill them.
Key rating and database sources used in developing the companion capability matrix:
A full vendor capability matrix, generated via the Ordinizer tool against the functions defined in this framework, is maintained as a companion document.