Coordinating Building, Planning, Fire, Engineering and Other Municipal Reviews

Executive summary

A building permit rarely involves one reviewer. Planning, fire, engineering, water and wastewater, transportation and sometimes conservation authorities each hold a piece of the answer, and each works from the same submission for a different purpose.

When those reviews are serialised, elapsed time multiplies. When they run in parallel without a shared record, applicants receive contradictory comments. The design problem is coordination, not review capacity.

Why coordination dominates elapsed time

Serial routing means every wait is additive: the file sits in each queue in turn, and a deficiency discovered late restarts part of the chain. Parallel routing removes the additive wait but introduces a new requirement — someone must reconcile positions before comments reach the applicant.

Federal work on approval efficiency in the infrastructure sector and CMHC’s municipal action-plan material both treat inter-departmental process as part of the approval problem rather than an internal detail [1][2].

A coordinated review model

Three elements make this work: one submission record all departments read, a defined reconciliation step with an owner, and a single outbound response. Without the third, the applicant becomes the integrator.

Handling conflicting positions

Implications for authorities having jurisdiction

Name a coordinator role with authority to convene, not merely to forward files. Publish per-department service targets, and measure the reconciliation step separately — it is often where files sit longest and it is invisible in start-to-issue metrics.

Where interpretations differ, write the resolution down. An unpublished interpretation resolves one file and repeats the argument on the next.

Implications for applicants and professionals

A consolidated response allows a single coordinated resubmission rather than sequential partial fixes. For applicants, that is usually the largest available reduction in elapsed time, and it depends on the municipality’s process rather than on the design.

Applicants can help by submitting discipline-complete packages with consistent sheet identifiers, so departments are demonstrably reading the same document set.

Risks, limitations and safeguards

• Parallel routing without reconciliation produces contradictory comments and erodes trust faster than slow serial review.
• A coordinator without authority becomes a message relay and adds a queue.
• Shared records raise access-control questions; department-appropriate views are required.
• Service targets per department can encourage premature comments; pair them with quality measures.
• Coordination cannot resolve genuine policy conflict; that needs a decision at a higher level, documented.

PermitAssure perspective

PermitAssure holds one application record with role-based views, so each department reviews the same submission and revision while seeing what is relevant to it. Findings carry their department, evidence and rule reference, and the consolidation step produces a single response record for the applicant.