Residential building permit pre-review
Find permit issues before submission.
PlanPort reviews the complete package against applicable code and municipal requirements, with every finding tied back to evidence.
Example resolution cycle
Every issue moves toward a verified close.
Finding PP-019
Finding identified
Egress dimensions missing
Floor plan · A2.03
Action recommended
Add clear-opening dimensions
Width, height, and opening area
Owner assigned
Architectural designer
Responsible for the drawing revision
Evidence uploaded
Revised A2.03 received
Drawing revision 02
Finding closed
Reviewer confirmed
Evidence accepted · Resolved
One package
Drawings, forms, reports, and evidence
Shared sources
OBC, NBCC, and municipal requirements
Mapped controls
One check can satisfy overlapping rules
Traceable output
Every finding has a source and rationale
One connected workflow
From unstructured files to a reviewable submission.
PlanPort keeps intake, requirements, findings, and evidence in context. Your team can see what is ready, what is missing, and why it matters.
Build the package
Bring drawings, forms, reports, and supporting documents into one structured submission.
Run the pre-review
Check the package against applicable code, municipal, and submission requirements.
Resolve with evidence
Trace every finding to its requirement, supporting document, and mapped control.
Maintain rule sources once. Use them across every project.
Codes and municipal requirements live at the platform level, with project-specific scope applied during review. That keeps sources consistent without flattening jurisdictional differences.
Ontario Building Code
O. Reg. 332/12
National Building Code of Canada
2025
Municipal submission checklist
Project scope
Control mapping
Manage overlap without duplicating work.
Safe stair geometry
Life safety
Bedroom emergency egress
Means of egress
Spatial separation
Fire protection
A mapped control can support multiple rules while each source keeps its own citation, applicability, and legal authority.
Better handoffs
Give every reviewer the same clear picture.
The output is structured for action—not another static checklist that loses its connection to the package.
For applicants
Know what is missing before filing and keep every response in one submission package.
For reviewers
Inspect the requirement, evidence, and rationale behind every finding.
For municipalities
Receive more complete packages without giving up local rules or professional judgment.
Make readiness visible before the package leaves your desk.
Start with a residential submission, connect the applicable rule sources, and work through the evidence-backed findings.