Executive summary
Every submission is routed by someone. In many departments that routing is informal: whoever opens the file, or whoever has capacity, or a rota that ignores complexity. The result is uneven queues and specialists spending time on files that did not need them.
Structured triage assigns each file a route based on permit type, completeness, complexity indicators and required disciplines. It does not decide compliance; it decides sequence and ownership, and it is one of the few improvements available without any change to review standards.
Why triage carries so much leverage
Technical reviewer capacity is the scarce resource in almost every building department. Anything that puts an unreviewable or misrouted file in front of a specialist consumes that resource twice: once to discover the problem and again after it is corrected.
Triage also determines fairness. Without explicit rules, small applications can sit behind large ones indefinitely, which is visible to applicants and hard to defend. Documented routing rules make the queue explainable, and explainability is a recurring theme in guidance on automated support for administrative processes [1].
A triage model
Triage runs after the completeness gate and before technical assignment. It reads five signals, all of which are administrative rather than interpretive.
The routes are department-specific. What matters is that they are named, that each has an owner, and that the assignment reason is recorded with the file.
Operating rules that keep triage honest
| Rule | Purpose |
|---|---|
| Triage never determines compliance | Routing is an administrative decision; it must not pre-judge a technical finding |
| Every route has a named owner and a target | An unowned queue becomes the slowest queue |
| Assignment reason is recorded | Makes the queue explainable to applicants and auditable internally |
| A fast lane requires eligibility criteria, not discretion | Prevents informal preference and perceived favouritism |
| Reviewers can re-triage with a reason | Complexity is sometimes only visible once review starts |
| Triage rules are reviewed on a schedule | Volumes and permit mixes change |
Implications for authorities having jurisdiction
Start by measuring the current distribution: how many files land with a specialist that did not require one, and how many wait behind larger applications. That measurement usually justifies the work on its own.
A fast lane for small, repeatable work has a second benefit: it removes the volume that generates the most applicant frustration relative to its technical content, which improves service perception without touching complex review.
Implications for applicants and professionals
Published eligibility criteria let applicants know which lane a project will enter, and what would move it out of that lane. Where a fast lane exists, meeting its criteria becomes a design and documentation objective.
Clear routing also improves communication: an applicant told that their file is in multi-discipline coordination understands the timeline differently from one told only that it is "in review".
Risks, limitations and safeguards
- Automated triage that uses proxy signals can systematically disadvantage certain applicant types; monitor the distribution of routes.
- A fast lane can become a pressure point for approval shortcuts; eligibility must be criteria-based and audited.
- Complexity indicators derived from extraction may be wrong; re-triage must be easy.
- Routing metadata is operational data, not a compliance record; keep the two separate.
- Triage cannot fix understaffing; it reallocates a constraint rather than removing it.
PermitAssure perspective
PermitAssure treats triage as configuration: signals, routes, owners and targets are set by the jurisdiction, and every assignment carries its reason. The platform surfaces complexity indicators extracted from the submission, and reviewers can re-route with a recorded reason at any point.
Five key takeaways
- Triage is an administrative decision about sequence and ownership, never about compliance.
- Five administrative signals are usually enough: type, completeness, complexity, disciplines, revision status.
- Every route needs a named owner, a target and a recorded assignment reason.
- Fast lanes require published eligibility criteria rather than discretion.
- Route distribution should be monitored for unintended disadvantage.
References
- Directive on Automated Decision-Making. Treasury Board of Canada Secretariat. www.tbs-sct.canada.ca. Accessed 3 August 2026.
- National Building Code of Canada 2025. National Research Council Canada. nrc.canada.ca. Accessed 3 August 2026.
- Illustrated User’s Guide: NBC 2020 Part 9, Division B — Housing and Small Buildings. National Research Council Canada. nrc.canada.ca. Accessed 3 August 2026.
- Housing Accelerator Fund Best Practices. Canada Mortgage and Housing Corporation. www.cmhc-schl.gc.ca. Accessed 3 August 2026.
Cited statements follow the sources above. Frameworks, diagrams and interpretation in this article are PermitAssure's own.
Related resources
Next step
Measure how many files currently reach a specialist unnecessarily, then define two routes and their eligibility criteria.
Discuss triage designPermitAssure provides digital review, workflow and decision-support capabilities. This resource is educational and does not constitute regulatory, legal, architectural or engineering advice. Final interpretations, approvals and regulatory decisions remain the responsibility of the applicable Authority Having Jurisdiction and its authorized professionals.