Tailored for Your Municipality
Tailored to Your Municipality
Every Canadian municipality runs elections differently — number of wards, voting channels, advance poll days, accessibility requirements, and local bylaws. Civic Internet & Telephone Voting provides a robust, MEA-compliant foundation — then adapts to your specific election configuration. With a full source code licence, your customization options are limitless.
The Journey
From Fragmentation to Clarity
Discover
Map your processes, pain points, and integration landscape
Configure
Build workflows, forms, and routing rules on existing modules
Deploy
Phased rollout with role-based training and hypercare support
Evolve
Quarterly reviews to refine and expand as your needs grow
Philosophy
Our Approach to Customization
Civic CRM is built on the principle of configuration over customization — empowering municipalities to tailor the platform without costly custom development.
Approach 01
Election-Specific Configuration
Every municipal election is unique — different offices, wards, voting periods, and channel preferences. Civic's configuration-driven approach adapts the platform to your election without modifying source code. Define offices, candidates, wards, voting period dates, channel availability, and language settings through the Election Configuration Console.
Configuration Patterns
How Municipalities Tailor Civic CRM
From bilingual interfaces to ward-based routing, explore configuration patterns designed for Canadian municipalities. Filter by base module to find relevant patterns.
Implementation
Your Customization Journey
A structured, transparent process that takes your municipality from requirements gathering to a fully tailored deployment. Click each phase to explore.
Phase 1 of 6
Election Planning Workshop
3-day workshop with the Clerk, election staff, and IT to define the election: offices, wards, voting period, channels, languages, accessibility requirements, help desk staffing, and communication plan. Output is the complete Election Configuration Document.
Phase 1 · 2–3 weeks
Election Planning Workshop
3-day workshop with the Clerk, election staff, and IT to define the election: offices, wards, voting period, channels, languages, accessibility requirements, help desk staffing, and communication plan. Output is the complete Election Configuration Document.
Phase 2 · 4–6 weeks
Platform Configuration
Configure the platform per the Election Configuration Document: election structure, branding, languages, credential formats, kiosk profiles, results presentation, and integration settings. Configuration is reviewed and approved by the Clerk before proceeding.
Phase 3 · 2–3 weeks
Test Election & Validation
Execute a complete test election with all configured settings — voter credential generation, all voting channels, help desk workflows, decryption ceremony, and results tabulation. Independent auditor observes. Issues identified and resolved.
Phase 4 · 2 weeks
Voter Education & Public Demo
Launch voter education materials and the public demo voting experience using the approved configuration and branding. Help desk staff trained on customized scripts. Accessible kiosks deployed and tested at designated locations.
Phase 5 · 2–3 weeks
Live Election with War Room
Live election operated with real-time war room monitoring. Customized dashboards show municipality-specific metrics. Help desk operates with customized scripts. ML anomaly detection tuned to municipality baselines. All configured channels active.
Phase 6 · Ongoing
Post-Election Review & Archival
Post-election review: results publication, decryption ceremony report, independent audit report, help desk metrics, turnout analysis by ward and channel, and lessons learned. All election data archived per municipal records retention policy. Configuration preserved for next election cycle.