Skip to main content
PermitAssure — Permits Made Simple
EN FR
Request a Demo
Process & Productivity Practical Guide

Lean Permitting: Reducing Rework, Queues and Avoidable Review Cycles

Permit review is knowledge work moving through queues. The flow concepts that apply to any queue apply here, with one hard constraint: review depth is not negotiable.

Editorial owner
PermitAssure Editorial Team
Published
3 Aug 2026
Last reviewed
3 Aug 2026
Reading time
10 minutes
Audience
Government & AHJs, Building Officials
A magnifier held over a permit drawing beside a stylised digital building model.
Most of the calendar is queue time, not review time. Photo: licensed stock imagery (iStock); licence confirmation pending.

Executive summary

A permit file spends most of its life waiting: for a complete package, for a reviewer, for a referral, for an applicant response, for reconciliation. Review itself is a minority of elapsed time in most departments.

This article applies flow thinking to permitting and pairs each common waste with a countermeasure that does not reduce the depth of technical review.

Why flow rather than effort

Adding reviewer hours to a process with large queue times produces modest improvement, because the constraint is not review capacity alone — it is the arrival quality and the number of handoffs. Reducing rework releases capacity without new hiring.

This is also the safest framing politically. Approval-time targets in housing programmes can create pressure on review depth [1]; flow improvements are the improvements that do not.

Where the time goes, and what to do about it

Table 1 — Common wastes in permit review and countermeasures.
WasteAppears asCountermeasure
ReworkDeficiency cycles caused by predictable omissionsPublished checklist, intake completeness gate, coded deficiency profile
WaitingFile sits in a queue with no ownerNamed owner and target per route; visible queue position
HandoffsSerialised departmental reviewsParallel routing with one shared record and a reconciliation step
Re-readingFull re-review of a minor revisionChange detection focused on what differs
Re-entryFacts transcribed from drawings repeatedlyStructured extraction validated once, reused downstream
BatchingReviews performed only on set daysContinuous flow where volume permits
Over-processingDetailed technical review of an incomplete fileCompleteness gate before technical assignment
Permit rework loop and intervention pointsA four-step loop: an incomplete or unclear submission arrives; review identifies deficiencies; a notice is issued; the applicant responds and the file re-enters review. Interventions: publish requirements and gate completeness at intake; write specific evidence-based notices; detect changes so re-review is focused; and feed recurring deficiency causes back into applicant guidance.The rework loop, and where to break it1. Submission arrivesQuality varies; some files are not yetreviewable2. Deficiencies identifiedSome are administrative, some technical,some avoidable3. Notice issuedSpecific evidence and location, oranother cycle follows4. Response and re-reviewFocused on what changed, then fed backto guidance
Original PermitAssure diagram. Text description: submissions arrive with varying quality; review identifies administrative, technical and avoidable deficiencies; a notice is issued that either enables a complete response or triggers another cycle; the response is re-reviewed focusing on changes, and recurring causes feed back into published guidance and checklists.

Measuring flow honestly

Three measures reveal flow: elapsed time distribution, not the mean; cycles per application; and share of files complete on first submission. Together they show whether an intervention improved flow or moved the delay somewhere less visible.

Implications for authorities having jurisdiction

Start with rework because it is the waste applicants also feel. A published checklist plus coded deficiencies produces a prevention list within one cycle of applications, and prevention is cheaper than any review-side change.

Avoid targets on elapsed time alone. Pair them with cycles per application and first-pass completeness, so the incentive is to prevent rework rather than to defer or split files.

Implications for applicants and professionals

Applicants control the largest waste. A pre-submission self-check against the published requirement list removes most administrative deficiencies, and for repeat applicants the effort amortises quickly.

On revisions, clouding and listing changes explicitly lets the department focus re-review, which shortens the loop for everyone.

Risks, limitations and safeguards

  • Flow language can be read as pressure to approve faster; state explicitly that review depth is out of scope.
  • Continuous flow may not suit small departments with part-time specialists; batching can be rational.
  • Deficiency coding adds a small burden at source and must be kept simple to survive.
  • Change detection is an aid, not a determination of materiality; the reviewer decides.
  • Measuring only what is easy encourages deferral behaviours; keep quality measures alongside timeliness.

PermitAssure perspective

PermitAssure targets the two largest wastes directly: rework, through completeness gating and specific evidence-linked deficiency notices, and re-reading, through revision comparison that focuses re-review. Neither changes the depth of professional review, and neither substitutes for it.

Five key takeaways

  • Queue time, not review time, dominates elapsed time in most departments.
  • Rework and re-reading are the two wastes with the largest available reduction.
  • Measure distribution, cycles per application and first-pass completeness together.
  • Elapsed-time targets alone create deferral incentives.
  • Flow improvements must never be framed as reductions in review depth.

References

  1. Housing Accelerator Fund Best Practices. Canada Mortgage and Housing Corporation. www.cmhc-schl.gc.ca. Accessed 3 August 2026.
  2. Infrastructure Sectoral Regulatory Review Roadmap. Government of Canada. housing-infrastructure.canada.ca. Accessed 3 August 2026.
  3. Building Permits Interactive Dashboard (71-607-X2021005). Statistics Canada. www150.statcan.gc.ca. Accessed 3 August 2026.
  4. 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.

Cited statements follow the sources above. Frameworks, diagrams and interpretation in this article are PermitAssure's own.

Related resources

Process & ProductivityMapping the Current Building-Permit Process Before Automating ItProcess & ProductivityRevision Intelligence: Reviewing What Changed Instead of Starting Over

Next step

Code deficiencies by cause for one permit type for a month, then publish the top five to applicants.

Discuss a rework review

PermitAssure 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.