Planning Application
Complete Ontario Planning Act application management — pre-consultation, statutory completeness determination, internal/external circulation, indigenous consultation, public notice, committee/council decisions, OLT appeals, conditions clearance, agreements, and securities management.
Application Submission
Completeness Check
Statutory Tracking
Public Tracker
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
20Delegated to
8Shared intake infrastructure
Review routing, approval workflows
Statutory notices, deadline reminders, public notifications
Studies, plans, agreements, reports
Property data, zoning, mailing radius, activity map
Public meeting management, comment collection
Public-facing tracker, online submission
All application activity logging
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 16 discrete capabilities — each with API surface, business rules, and data ownership.
Online pre-consultation request, staff scheduling, meeting records, and submission requirements checklist generation.
Online Request
Submit pre-consultation request online with project description; staff schedule meeting based on project type.
Meeting Records
Record attendees, discussion items, and required studies/plans. Generate submission requirements checklist for applicant.
Pre-Application Circulation
Circulate pre-application to departments and agencies for early input; development inquiry tracking.
All Planning Act application types with online submission, document upload, fee payment, and completeness validation.
Application Types
OPA, ZBA, plan of subdivision, plan of condominium, site plan control, minor variance, consent/severance, part-lot control, and combined.
Online Submission
Online submission with required documents, studies, and fee payment validated against permit configuration rules.
Combined Applications
Multi-application management (OPA + ZBA + subdivision) linked for coordinated processing and combined public meeting.
Statutory completeness per Planning Act s.22(4), s.34(10.1) with deficiency letters and statutory clock start.
Statutory Completeness
Per Planning Act s.22(4), s.34(10.1): verify all required materials submitted within 30-day target.
Deficiency Letter
Generate deficiency letter with specific missing items if application is incomplete.
Clock Start
Acknowledgement letter with statutory clock start date issued when application deemed complete.
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 11 resource groups — plus 8 domain events for async integration.
/api/v1/planning/pre-consultation
Submit pre-consultation request
Ecosystem
Products that depend on this module
1 Civic products consume Planning Application — making it one of the most critical platform services in the ecosystem.
Technical Specifications
Performance, Compliance & Configuration
Application Submission
Completeness Check
Statutory Timeline Tracking
Circulation Delivery
Public Tracker Update
Policy Analysis Auto-Population
Mailing List Generation
Agreement Registration Tracking
FAQ
Frequently Asked Questions
Ready to Integrate
Build on Planning Application
Request an architecture brief, integration guide, or live demo environment for your team.