Court & POA
Provincial Offences Act court administration — charge intake (Part I/II/III), court scheduling, proceedings, fine management, MTO licence suspension, ICON integration, online dispute resolution, and digital justice for municipalities operating POA courts.
Charge Filing
Docket Assembly
Fine Accuracy
Virtual Court
Purpose-Built for Canadian Municipalities
Purpose & Scope
What this module owns
Clear ownership boundaries prevent duplication and ensure every capability has exactly one authoritative home.
Owns
18Delegated to
9Shared case lifecycle
Fine payment processing
Court date reminders & fine notices
Approval workflows & escalation
Evidence & court records
GL integration, revenue accounts, trust accounts
Defendant self-service & public access
Scheduling optimization & hearing prediction
Court record integrity
These capabilities are handled by dedicated modules and consumed via stable API contracts — keeping boundaries clean and ownership unambiguous.
Core Capabilities
What it does
4 capability groups comprising 12 discrete capabilities — each with API surface, business rules, and data ownership.
Part I (Certificate of Offence/tickets): municipal bylaw, HTA, MNR, MOL. Part II (summons): serious offences with service tracking. Part III (information): pre-trial conferences and disclosure. Batch/electronic filing with limitation period validation.
Part I
Certificate of Offence/tickets for municipal bylaw, HTA, MNR, and MOL violations.
Part II
Summons for serious offences with personal service tracking.
Part III
Information laid for serious matters — pre-trial conferences, disclosure management.
Batch Filing
Electronic batch filing with ticket image management and limitation period validation.
Name, DOB, address, driver's licence, offence history, and corporate defendants. Cross-reference with municipal records.
Individual
Name, DOB, address, driver's licence — with offence history cross-referencing.
Corporate
Corporate defendants with company name and authorized representative.
History
Complete offence history with all charges and dispositions.
Cross-Reference
Cross-reference with municipal records for address and identity verification.
Every module owns a single bounded context, exposes stable APIs, and can be composed into any Civic product — that's the architecture that scales.
Krutik Parikh
Creator of Civic
Data Model
Entity Architecture
5 entities with 5 relationships — the authoritative schema for this bounded context.
Entities
Select an entity to explore its fields and relationships
API Surface
Integration Endpoints
15 RESTful endpoints across 9 resource groups — plus 6 domain events for async integration.
/api/v1/court/charges
File charge(s)
/api/v1/court/charges/{id}
Charge details
Ecosystem
Products that depend on this module
2 Civic products consume Court & POA — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
Charge Filing (batch)
Docket Assembly
Fine Payment Processing
ICON Sync
ODR Response Time
Virtual Court Latency
Fine Calculation Accuracy
Court Record Retention
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Court & POA
Request an architecture brief, integration guide, or live demo environment for your team.