How Civic Citizen Engagement Compares

Purpose-built for Canadian municipalities (population 5,000–100,000+) — IAP2 spectrum alignment, Planning Act consultation compliance, AODA accessibility, and bilingual (en/fr) support are native to the platform.

Generic survey platforms designed for market research. No IAP2 framework, no municipal consultation workflows, no statutory compliance features.

General-purpose engagement platforms built for federal or international contexts. Canadian municipal requirements handled through custom configuration.

Full source code licence — perpetual software asset your municipality owns and controls. No recurring SaaS subscription. Optional managed hosting and support.

Per-seat SaaS subscription with annual escalation clauses. No source code access. Vendor lock-in risk.

Per-project or per-seat SaaS with complex tiers. Source code unavailable. Exit costs and data migration challenges.

10+ engagement methods built in: surveys, polls, interactive maps, idea boards, forums, Q&A, document review, virtual town halls, participatory budgeting, and story sharing — all integrated within a single project.

Primarily surveys and polls. Map engagement, participatory budgeting, and virtual town halls require separate tool subscriptions.

3–5 engagement methods with limited depth. Advanced tools like participatory budgeting and document review available as premium add-ons.

Built-in participatory budgeting with trade-off visualization, constraint enforcement, multi-round proposal/voting, and implementation tracking — included in the licence.

Not available. Requires a separate specialized tool (e.g., Citizenlab, Decidim) with additional subscription fees.

Basic budget allocation surveys without trade-off visualization, multi-round support, or implementation tracking.

Full map-based engagement with pin-drop, area-drawing, photo attachments, comment layers, GIS data integration (zoning, transit, parks), and GIS export for staff analysis.

Google Maps embed with basic pin-drop. No GIS integration, no photo attachments, no category-based analysis.

Map engagement available but limited GIS integration. Export formats may not be compatible with municipal planning tools.

Built-in AI sentiment analysis, theme clustering, word clouds, and key phrase extraction for open-ended responses — all included in the licence. No per-response AI fees.

No AI capabilities. Open-ended response analysis is entirely manual — staff code responses one by one.

AI analysis available as premium add-on at per-response pricing. Limited theme clustering. No municipal-specific training data.

Automatic comparison of participant demographics to census data with representativeness scoring. Ward-level analysis. Underrepresented group identification with targeted outreach recommendations.

Basic demographic collection without representativeness analysis. No census data comparison. No outreach recommendations.

Demographic reporting available but no Canadian census data integration. No ward-level analysis for municipal contexts.

Auto-generated 'What We Heard' reports with participation statistics, theme clustering, sentiment analysis, representative quotes, and configurable templates. Export as PDF, Word, or web page. ≤5 days from close to report.

Manual report compilation from exported CSV data. 3–4 weeks typical turnaround. No auto-generated reporting.

Basic report generation with limited customization. No municipal-specific 'What We Heard' format. Charts available but no theme clustering.

Built-in IAP2 spectrum alignment for every project. Compliance reporting documents engagement level promised vs. delivered. Input-to-decision tracking and feedback loop documentation.

No IAP2 framework support. Engagement levels are not tracked or reported against any participation standard.

Some platforms reference IAP2 but do not provide compliance reporting, input tracking, or feedback loop documentation.

WCAG 2.1 AA compliance for all engagement tools verified by third-party VPAT. Screen reader, keyboard navigation, high-contrast, adjustable fonts, multilingual (en/fr). Ensures all residents can participate regardless of ability.

Partial accessibility support. Survey tools may not meet Ontario public sector AODA obligations.

Varies by platform. Often claims AA compliance but lacks third-party verification for engagement-specific tools.

All data stored exclusively in Canadian data centres (Ontario + Quebec). Contractually guaranteed. Source code licence enables on-premises deployment for maximum sovereignty.

Data typically stored in US data centres. Canadian region may be available at premium tier pricing.

Canadian region available but may not guarantee all data and backups remain in-country.

Pre-built connectors for Civic CRM, CMS, council agenda systems, and open data portals. API-first architecture with full source code access for custom integrations.

Zapier-level integrations only. No municipal-specific connectors. Custom integration requires developer resources.

API available but all municipal integrations must be built from scratch at additional cost.

One-time source code licence with transparent pricing. No per-response fees, per-project surcharges, or participant limits. Optional managed hosting billed separately.

Per-response or per-seat pricing with limits on responses per survey. Overage charges for popular consultations. Annual escalation clauses.

Competitive base pricing but per-project fees, participant caps, and premium feature add-ons can double or triple annual cost.

Full data export at any time in CSV, JSON, GeoJSON, or PDF. No proprietary formats or export fees. Source code access means no vendor lock-in whatsoever.

CSV export available but may require per-export fees. Proprietary response formats can complicate migration. No GIS export.

API-based export available. Bulk export may require additional tooling or vendor support. Limited GIS data portability.