Product Experience
Every role. One platform.
From front-counter staff handling resident requests to the CAO reviewing council-ready reports — every role has a purpose-built journey. Explore how Civic Court / POA works for your team.
Watch the 3-Minute Demo
See Civic Court / POA handle a complete resident service request — from intake through resolution and council reporting.
Request Video AccessTry It Now
Explore the Interface
Click through the actual Civic Court / POA interface. Navigate between the dashboard, resident profiles, service requests, and reports to see how everything connects.
47
Charges Filed
+8% vs last month94.2%
Court Utilization
+12% vs last month74.8%
Fine Collection
+18% vs last month102%
Clearance Rate
+6% vs last monthRecent Activity
Part I batch import: 34 parking tickets filed
Filing · 2 min ago
Fine payment $450 received via online portal
Finance · 5 min ago
ODR resolution accepted — minor HTA matter
Prosecution · 12 min ago
MTO licence suspension submitted — 3 defaulted fines
Collections · 18 min ago
Court session completed — 38 matters, Courtroom A
Court Ops · 25 min ago
Role-Based Journeys
One Platform, Every Perspective
Select a role to explore their complete journey through Civic CRM — from day-one onboarding to daily workflows and strategic outcomes.
Court Clerk
From Charge Intake to Courtroom Support
Follow the complete lifecycle of a provincial offence charge — from electronic filing through docket assembly, courtroom proceeding support, disposition recording, and fine account creation. Zero lost tickets, full audit compliance, automated calculations at every step.
Receive
Charge intake
Electronic filing from enforcement agencies — OPP, municipal bylaw, MNR, MOL — validated automatically for set fine, offence section, and limitation period. Manual entry available for paper tickets with barcode scanning.
The Electronic Filing Gateway (spec 1.5) receives ticket data from enforcement agencies via secure API or batch import. Each certificate of offence is validated against the provincial set fine schedule, confirmed for valid offence section code, and checked for filing within the limitation period. Parking ticket batch imports process 1,000+ records per job. Paper tickets are entered via the Ticket Data Entry Console with auto-complete for offence descriptions, officer lookup, and set fine auto-population. Every filing is timestamped and logged.
Validate
Charge verified
Automatic set fine validation catches incorrect amounts. Defendant record linked or created with identity matching across prior charges. Evidence and scanned documents attached to the charge record.
The system validates each charge against the provincial set fine schedule — flagging discrepancies before filing. The Identity Linking Engine (spec 1.4) matches the defendant against existing records using fuzzy matching on name + date of birth, driver's licence number, and address. If no match is found, a new defendant record is created. Prior charge history is immediately visible. Scanned tickets, photos, and officer statements are attached via the Evidence Repository with chain-of-custody tracking.
Schedule
Docket assembled
Charges assigned to court sessions via AI-optimized docket assembly. Interpreter requests coordinated. Witness notifications sent to enforcement officers. Capacity managed to prevent over-booking.
The Docket Builder (spec 2.2) assigns charges to scheduled sessions with AI capacity optimization. The system predicts hearing duration by charge type, plea type, and complexity indicators. Interpreter requests are matched with interpreter scheduling — grouping same-language matters within sessions for efficiency. The Witness Notification Manager (spec 2.3) sends automated notifications to enforcement officers and expert witnesses. Courtroom posting sheets are generated automatically.
Process
Courtroom support
In-court proceeding support — plea recording, disposition entry, sentence calculation (fine + VFS + costs), adjournment scheduling, and real-time docket progression visible to all courtroom participants.
The First Appearance Workflow (spec 3.1) guides the clerk through each matter: identity verification, plea recording (guilty, guilty with submissions, not guilty), and next-step assignment. For guilty pleas, the Sentencing Calculator auto-calculates fine + VFS + costs and generates the fine account. For not-guilty pleas, the Trial Scheduler assigns a trial date with officer notification. Adjournments are recorded with reason codes and new dates assigned. The docket display updates in real-time showing remaining matters and estimated completion time.
Record
Disposition captured
Guilty finding creates fine account with calculated total (fine + VFS + costs), due date, and payment instructions. Not guilty dismisses the charge. Withdrawn charges are recorded with reason. Every disposition reported to ICON.
Every disposition is recorded with finding, sentence details (if applicable), and the presiding JP. The Fine Calculation Engine (spec 4.1) creates the fine account with total owing, VFS breakdown, due date (30 days default or per sentence), and payment instructions. Conviction notices are queued for mailing. The ICON Data Exchange (spec 6.3) automatically transmits disposition data to the provincial system. If a licence suspension recommendation is part of the sentence, the MTO notification is generated. All events are logged to the immutable audit trail.
Collect
Fine payment
Process fine payments across all channels — counter (cash, debit, credit), online, mail, phone. Track partial payments, extensions, instalment plans, and defaults. Generate receipts and update fine account balances in real-time.
The Payment Processing Hub (spec 4.2) accepts payments across all channels with PCI DSS compliance. Partial payments are allocated correctly across fine, VFS, and costs per POA requirements. The fine account balance updates in real-time. Extension requests (POA s.66) are processed through the Extension Manager. Instalment plans are created and monitored for compliance. Overdue fines enter the default pipeline: default notices → MTO licence suspension → civil enforcement → collection agency. Every payment and default action is logged with full audit trail.
Clerk Journey
0 / 6
Step 01
Receive
Charge intake
Electronic filing from enforcement agencies — OPP, municipal bylaw, MNR, MOL — validated automatically for set fine, offence section, and limitation period. Manual entry available for paper tickets with barcode scanning.
The Electronic Filing Gateway (spec 1.5) receives ticket data from enforcement agencies via secure API or batch import. Each certificate of offence is validated against the provincial set fine schedule, confirmed for valid offence section code, and checked for filing within the limitation period. Parking ticket batch imports process 1,000+ records per job. Paper tickets are entered via the Ticket Data Entry Console with auto-complete for offence descriptions, officer lookup, and set fine auto-population. Every filing is timestamped and logged.
Step 02
Validate
Charge verified
Automatic set fine validation catches incorrect amounts. Defendant record linked or created with identity matching across prior charges. Evidence and scanned documents attached to the charge record.
The system validates each charge against the provincial set fine schedule — flagging discrepancies before filing. The Identity Linking Engine (spec 1.4) matches the defendant against existing records using fuzzy matching on name + date of birth, driver's licence number, and address. If no match is found, a new defendant record is created. Prior charge history is immediately visible. Scanned tickets, photos, and officer statements are attached via the Evidence Repository with chain-of-custody tracking.
Step 03
Schedule
Docket assembled
Charges assigned to court sessions via AI-optimized docket assembly. Interpreter requests coordinated. Witness notifications sent to enforcement officers. Capacity managed to prevent over-booking.
The Docket Builder (spec 2.2) assigns charges to scheduled sessions with AI capacity optimization. The system predicts hearing duration by charge type, plea type, and complexity indicators. Interpreter requests are matched with interpreter scheduling — grouping same-language matters within sessions for efficiency. The Witness Notification Manager (spec 2.3) sends automated notifications to enforcement officers and expert witnesses. Courtroom posting sheets are generated automatically.
Step 04
Process
Courtroom support
In-court proceeding support — plea recording, disposition entry, sentence calculation (fine + VFS + costs), adjournment scheduling, and real-time docket progression visible to all courtroom participants.
The First Appearance Workflow (spec 3.1) guides the clerk through each matter: identity verification, plea recording (guilty, guilty with submissions, not guilty), and next-step assignment. For guilty pleas, the Sentencing Calculator auto-calculates fine + VFS + costs and generates the fine account. For not-guilty pleas, the Trial Scheduler assigns a trial date with officer notification. Adjournments are recorded with reason codes and new dates assigned. The docket display updates in real-time showing remaining matters and estimated completion time.
Step 05
Record
Disposition captured
Guilty finding creates fine account with calculated total (fine + VFS + costs), due date, and payment instructions. Not guilty dismisses the charge. Withdrawn charges are recorded with reason. Every disposition reported to ICON.
Every disposition is recorded with finding, sentence details (if applicable), and the presiding JP. The Fine Calculation Engine (spec 4.1) creates the fine account with total owing, VFS breakdown, due date (30 days default or per sentence), and payment instructions. Conviction notices are queued for mailing. The ICON Data Exchange (spec 6.3) automatically transmits disposition data to the provincial system. If a licence suspension recommendation is part of the sentence, the MTO notification is generated. All events are logged to the immutable audit trail.
Step 06
Collect
Fine payment
Process fine payments across all channels — counter (cash, debit, credit), online, mail, phone. Track partial payments, extensions, instalment plans, and defaults. Generate receipts and update fine account balances in real-time.
The Payment Processing Hub (spec 4.2) accepts payments across all channels with PCI DSS compliance. Partial payments are allocated correctly across fine, VFS, and costs per POA requirements. The fine account balance updates in real-time. Extension requests (POA s.66) are processed through the Extension Manager. Instalment plans are created and monitored for compliance. Overdue fines enter the default pipeline: default notices → MTO licence suspension → civil enforcement → collection agency. Every payment and default action is logged with full audit trail.
Ready to Transform Your Municipality?
See Civic Court / POA in your environment
Schedule a personalized walkthrough with our municipal solutions team. We’ll configure a demo environment to match your municipality’s structure.