For cities and regions letting residents propose and vote on spending: phases from proposals to voting and project tracking, vote rules and budgets per district, verifying eligible voters, and publishing results with Decidim's budgets and accountability components.
For governments consulting on plans, laws and policies: structured processes with phases, comments and proposals, surveys and in-person meetings recorded online, moderation, and publishing how input changed the outcome.
For bodies that accept petitions or citizen initiatives with signature thresholds: initiative types, signature collection with verified identities, deadlines and committee review, and how Decidim's initiatives space models each step.
For city councils and municipalities: hosting Decidim within municipal or national infrastructure, integration with the city's identity and census systems for verification, accessibility duties, staff roles and support after launch.
For universities running student budgets, governance consultations and assemblies: campus SSO for verification, separate spaces per faculty, moderation and publishing outcomes on a self-hosted Decidim.
For EU public bodies keeping participant identities and votes under EU jurisdiction: self-hosting Decidim with EU providers, maps, geocoding and social login services that send data abroad, and transfer documentation.
Running participation under the GDPR: lawful basis for public tasks, political opinions as special category data, pseudonymous participation, retention of proposals and votes, participant rights and data processing agreements with the host.
For EU public bodies: meeting EN 301 549 on a Decidim site, the accessibility statement and feedback mechanism the directive requires, accessible voting and proposal forms, and testing custom themes before launch.
For processes where only eligible residents may vote or sign: Decidim authorization handlers, census uploads, integration with government eID or SSO through OmniAuth, one person one vote controls and what verification data to keep.
A requirements checklist for a self-hosted citizen participation platform: functional must-haves, hosting and data residency, identity and access, privacy and retention, integrations, operations and support, so a team can compare self-hosted options before choosing a platform.
Questions to put in an RFP or vendor brief for a self-hosted citizen participation platform: platform and edition fit, licence obligations, migration of existing data, hosting model, security evidence, support terms after go-live and how the fixed scope is defined.
Cost structure for a self-hosted citizen participation platform: subscription pricing published by SaaS vendors against self-hosted infrastructure, implementation, support and internal staff time, which drivers move each line, and when bringing in an implementation partner costs less than building alone.