How to Reduce Your Permit Review Backlog
Permit backlogs are not a volume problem — they are a capacity allocation problem. Here are the specific operational changes that actually reduce review cycle times, based on what high-performing departments do differently.
By Will Maclean
Every building department director has the same conversation with their city manager at least once a year: the backlog is growing, review times are climbing, and applicants are complaining. The proposed solutions are usually the same too — hire more staff, mandate overtime, or implement a new software platform. These are reasonable responses. They are also insufficient for most departments.
The backlog is rarely a simple shortage of labor. It is a misallocation of the labor that exists. Understanding where review time actually goes — and where it is wasted — is the prerequisite for reducing it.
Measure Before You Manage
Most departments can tell you how many applications they received last month and how long the average review takes. Few can tell you how that review time breaks down. Specifically:
- How many hours per application are spent on initial completeness checks versus substantive code review?
- What percentage of first-review corrections are for the same recurring issues?
- How much reviewer time goes to applicant communication — emails, phone calls, re-explaining correction items?
- What is the ratio of first-review applications to resubmissions in the active queue?
Without these numbers, any backlog reduction effort is a guess. A department that spends 40 percent of reviewer time on completeness checks has a different problem than one that spends 40 percent on resubmission reviews. The interventions are different.
Completeness Checks Are the Lowest-Hanging Fruit
In many departments, 20 to 30 percent of submitted applications are incomplete. Missing cover sheets, unsigned documents, incorrect occupancy designations on the code analysis, absent energy compliance forms. These incomplete submissions enter the review queue, get assigned to a reviewer, and consume reviewer time before any code analysis begins.
The reviewer opens the plans, discovers the submission is incomplete, writes a correction letter, and returns it. The application goes back to the applicant, gets revised, and reenters the queue. The reviewer has spent 30 to 60 minutes on an application that was never ready for review.
The fix is a structured completeness check at intake — before the application enters the review queue. This can be a checklist verified by administrative staff, a self-certification form signed by the applicant, or an automated check against required document types. The goal is to prevent incomplete submissions from consuming reviewer time.
Departments that implement rigorous intake screening consistently report 15 to 20 percent reductions in reviewer workload from this single change.
Batch Similar Project Types
Plan review is cognitively expensive in part because reviewers context-switch between project types. Checking egress compliance on a commercial office building requires a different mental framework than reviewing a residential addition. The code sections are different, the common violations are different, and the level of documentation varies significantly.
Departments that batch similar project types — assigning a reviewer to spend a full day on residential additions, then a full day on commercial tenant improvements — see measurable efficiency gains. The reviewer loads the relevant code sections once and applies them across multiple projects, rather than reloading context on every application.
This is not a new idea. Manufacturing figured out decades ago that batch processing reduces setup time. The same principle applies to cognitive work. A reviewer who checks ten residential egress designs in sequence will be faster on the tenth than the first because the relevant code sections, common violations, and documentation expectations are cached.
Reduce the Correction Cycle
The single largest contributor to backlog growth is not initial review time — it is the correction cycle. An application that requires three rounds of corrections occupies the queue three times as long as one that passes on the first review. Each round involves reviewer time, applicant response time, and queue time for reassignment.
The most effective departments reduce correction cycles through two approaches:
Front-load the feedback. Instead of issuing corrections as individual items found during sequential review, conduct the full review before issuing any corrections. A comprehensive first correction letter that identifies all issues at once produces fewer resubmission cycles than a letter that identifies five issues, waits for the revision, and then finds three more. Incomplete initial corrections are a leading cause of extended review timelines.
Standardize correction language. When correction items are ambiguous, applicants misinterpret them. A correction that says "provide fire-resistance rating for corridor walls per IBC 1020.1" is clear. A correction that says "address corridor issues" is not. Standardized correction libraries with specific code references reduce the back-and-forth that extends the correction cycle.
Automate the Mechanical Checks
Experienced plan reviewers spend a significant portion of their time on checks that are important but mechanical — measuring egress widths, counting plumbing fixtures, verifying door clearances, checking corridor ratings against Table 1020.1. These checks are essential for code compliance. They are not a good use of a reviewer's expertise.
The distinction matters. A reviewer's value is in judgment: evaluating complex fire protection strategies, assessing structural adequacy, making calls on alternative compliance methods. Every hour spent measuring corridor widths is an hour not spent on the analysis that actually requires professional expertise.
Automated pre-screening handles the mechanical checks and delivers flagged conditions to the reviewer. The reviewer starts with a list of potential issues rather than a blank set of plans. Their job shifts from finding problems to evaluating them.
The time savings are substantial. Departments using automated pre-screening report 30 to 50 percent reductions in first-review cycle times. More importantly, the consistency improves — automated checks apply the same standard to every submission, eliminating the variability that makes the process unpredictable.
Stop Treating Overtime as a Strategy
Overtime is a symptom response, not a solution. A department that relies on overtime to manage its backlog has a structural problem that additional hours will not solve. Overtime fatigues reviewers, increases error rates, and accelerates burnout — which increases turnover, which deepens the backlog.
The alternative is not to work less. It is to work on the right things. A department that eliminates incomplete submissions at intake, batches similar project types, reduces correction cycles through comprehensive first reviews, and automates mechanical checks will process more applications per reviewer-hour than one that simply asks reviewers to work more hours.
The backlog is not inevitable. It is the result of process choices that can be changed. The departments reducing their backlogs are not the ones with the biggest budgets or the most staff. They are the ones that measured where the time goes and redesigned the workflow to eliminate the waste.