Participatory Budget Review¶

Participatory process — instantiates Revenue–Accountability Coupling Design

Hands a ring-fenced slice of the budget to the served constituency to allocate directly through an open propose-deliberate-vote cycle, so the people the money is meant to serve — not just the funders — decide where it goes.

Voice and a vote-of-one still leave the agent holding the purse. Participatory Budget Review goes further: it transfers allocation authority over a defined slice of the budget to the served constituency at large, who propose, deliberate, and vote directly on how that money is spent. Its distinguishing move is breadth of transferred power — not consultation like a Beneficiary Feedback Gate, not a single representative like a Constituency Board Seat, but a layer of the budget the whole constituency governs. That is what couples spending to the served population's own priorities rather than the agent's or the funder's, and it enfranchises the constituency as the actual decider over that slice. The practice has a real named lineage in participatory budgeting.^[1]

Example¶

A public university's student activity fee — roughly $4M a year — has always been allocated by an administrative committee. Students are captive payers of the fee but direct none of it, so the money answers to the administration, not the payers. A Participatory Budget Review opens 30% of the fund: registered student groups submit proposals, the whole student body deliberates them at open sessions and online, and the winning allocations are binding for the year. Spending shifts away from legacy line items toward what students actually use, and the administration now answers, over that slice, to the fee-payers it previously bypassed. The other 70% stays under the committee — the review couples one ring-fenced layer, not the whole budget, which is exactly what keeps it workable and honest about its scope.

How it works¶

What distinguishes it from a comment exercise is real authority over a bounded pool, run as an open cycle:

A ring-fenced slice. A defined portion of the budget is set aside for the constituency to allocate, so the stakes are concrete and the rest of the budget stays governed elsewhere.
An open propose–deliberate–vote cycle. Anyone in the constituency can put forward a proposal; the group deliberates and then votes — the participation is structural, not a survey.
Binding (or strongly presumptive) outcomes. The winning allocations actually spend the money; advisory-only versions decay into theatre, so the transfer of power has to be real.

Tuning parameters¶

Slice size — what fraction of the budget is opened. Small is safe but symbolic; large is real coupling but risks short-horizon or populist allocation of core funds.
Bindingness — advisory versus binding vote. Advisory decays into theatre; binding actually transfers power.
Participation design — open assembly, sortition, or a delegate model. Guards against capture by the most organized faction rather than the broad constituency.
Eligibility and weighting — who may participate and whether votes weight by stake. This is where the constituency gets defined in practice.
Cycle cadence — annual round versus continuous portfolio, trading deliberative depth against responsiveness.

When it helps, and when it misleads¶

Its strength is that it couples spending directly to the served population, educates and legitimizes as it goes, and surfaces priorities the funder or the agency would never have chosen on the constituency's behalf.

It misleads through majoritarian neglect — the numerous within the constituency steering money away from minorities inside it — and through capture by organized blocs or short-term thinking about long-lived assets. The classic misuse is opening a token slice for the optics while the real budget stays closed, a kind of participation-washing. The disciplines are a slice large enough to matter, genuinely binding outcomes, and inclusive participation design (sortition or reserved quotas) so the layer represents the whole constituency rather than the few with time to show up.

How it implements the components¶

Participatory Budget Review fills the shared-allocation slots of the archetype — what a constituency-run process can carry:

participatory_budget_layer — the process is the participatory layer over the budget; the slice the constituency directly governs.
principal_constituency_map — it operationalizes the constituency by convening and enfranchising a representative slice of the served population as the actual allocators, not a map on paper.

It does not map spending to the mandate on paper — that's the Budget-to-Mandate Crosswalk; it is not a single standing voting chair — that's Constituency Board Seat; and it is not the advisory feedback checkpoint — that's Beneficiary Feedback Gate.

Instantiates: Revenue–Accountability Coupling Design — it hands allocation of part of the resource back to the served constituency.
Consumes: Budget-to-Mandate Crosswalk frames which portion of the budget is opened for the constituency to allocate.
Sibling mechanisms: Constituency Board Seat · Beneficiary Feedback Gate · Public Accountability Hearing · Budget-to-Mandate Crosswalk · Funding Dependency Register · Performance-Linked Renewal · Clawback or Reversion Clause · Revenue Source Audit · Rent-Stream Drift Dashboard · Sponsor Influence Firewall · Sunset Reauthorization Vote

Notes¶

The review transfers power over a slice, not the whole budget; its legitimacy depends on that slice being real and the participation being representative — otherwise it launders a closed budget behind a participatory veneer. It pairs naturally with the Budget-to-Mandate Crosswalk, which governs the accountability of the portion the constituency does not directly allocate.

References¶

[1] Participatory budgeting — the practice, first adopted at municipal scale in Porto Alegre, Brazil, in 1989 and since taken up by cities and institutions worldwide, of letting residents decide directly how to spend part of a public budget. The Review is the archetype's use of that form to re-couple spending to the served constituency. ↩