Lean management principles, process mapping, waste elimination, and continuous improvement methodologies. Covers implementation of efficiency improvements in permitting and inspection workflows.
3
hours
0.3
CEUs
Administrative, Legal & Management
1.7.4
Lean management principles, process mapping, waste elimination, and continuous improvement methodologies. Covers implementation of efficiency improvements in permitting and inspection workflows.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamMap current workflows and identify process inefficiencies
A building department is, at its core, a service operation: every day it converts a fixed budget and staff into permits reviewed, inspections performed, and complaints resolved, and the public feels the results directly. A contractor whose permit sits idle for three weeks carries financing costs on a stalled project; a homeowner who gets three different answers from three staff members loses confidence before a reviewer opens the file. Multiplied across every applicant in a growing jurisdiction, a slow or inconsistent process is a real cost to the local economy, not just an internal inconvenience.
The starting discipline is mapping the process as it actually runs, not as the procedures manual describes it — tracing an application from intake through completeness screening, assignment, review, corrections, approval, issuance, inspection, and closeout, and timing each step including the informal workarounds staff use when the official process doesn't fit. Building Department Administration describes a 2004 audit in which King County, Washington studied nine jurisdictions known for well-run permitting specifically to see what they were doing differently — understanding the process well enough to see where it broke down, before proposing any fix.
Mapped honestly, most departments find that delay concentrates in the gaps between steps — a file waiting in a queue, sitting between one reviewer's sign-off and the next pickup — more than in the technical review itself.
A newly appointed building official keeps hearing that plan review "just takes a long time" but can't get anything more specific from staff. Rather than accept the vague complaint, or the equally vague fix of hiring another reviewer, the official pulls twenty recent files and times every stage by hand: received, assigned, first reviewed, returned, resubmitted, approved. Technical review turns out to be a small fraction of the total; most elapsed time is spent waiting — in an unassigned queue, or between a completed step and the next one starting.
The most common mistake is prescribing a fix — more staff, new software, a stricter deadline — before mapping where time actually goes, risking a solution to a problem the department doesn't have. A related error is speeding up one visible step while ignoring the rest of the flow; the bottleneck just reappears elsewhere. The correction is the same in both cases: map the complete workflow and measure total time across it before deciding what to change.
Apply Lean principles to eliminate waste and streamline operations
Lean thinking starts from a simple question: what does the applicant actually value? Not paperwork, not meetings, not a file moving desk to desk — a defensible decision that the plans and construction meet code. Anything that doesn't move an application toward that decision is waste, no matter how normal it feels.
Waste shows up in recognizable patterns. Waiting waste is an application sitting untouched in a queue while the clock runs. Transportation and motion waste is an inspector's day consumed by inefficient driving because routes were built in request order rather than by geography. Over-processing waste is effort spent on steps that add nothing — printing a digital submittal to walk paper copies around the office, or keying the same information into three disconnected systems. Defects and rework waste is a submittal cycling through review two or three times because each pass turns up something the last pass missed. Unclear requirements hide waste too: when "what do I need to submit" depends on which staff member answers, every inconsistent answer plants a future resubmittal.
None of this justifies cutting positions. Lean targets non-value-added steps, not the people performing them. A department that treats "eliminate waste" as code for "reduce headcount" teaches staff to hide problems rather than report them — destroying the honest information improvement depends on. The better framing is redirection: remove the step, redeploy the time it frees toward work that matters.
A new department head spends a day shadowing rather than reading reports. By early afternoon the pattern is visible: an inspector drives forty minutes to a site five minutes from the last one because the route followed request order, not location. Two applications have sat in an unassigned queue since the previous afternoon. A counter employee rejects a submittal for a missing site plan — the same item the last three submittals for that permit type were rejected for. Each observation is a distinct, nameable waste.
The most damaging mistake is letting "eliminate waste" be heard as "eliminate positions" — once staff believe that, they stop reporting inefficiencies for fear of pointing at their own job. A second mistake is naming a problem generically ("we're slow") instead of naming the specific waste category, which makes the right fix hard to find. The correction: waste elimination targets steps, not staff, and naming the waste type precisely points directly at the fix that will work.
Measure and monitor improvements in processing time and quality
Once a workflow is mapped and its waste named accurately, the next step is matching each problem to the lever that fixes it — then measuring to confirm it worked. Several levers show up repeatedly in well-run departments.
Completeness screening at intake addresses defect and rework waste directly. Building Department Administration is specific: when counter staff don't catch missing information before a submittal moves forward, a reviewer is left to reject the plans or approve something incomplete — and either way, an inspector typically finds the gap in the field, the most expensive and latest point to catch it. A standard checklist by permit type catches the same gaps far earlier.
Concurrent review addresses a different waste: sequential handoffs. When a commercial submittal needs sign-off from building, fire, and site review, routing it to all three at once rather than making each wait for the last one can cut elapsed calendar time substantially without adding a single review hour.
Standard, written procedures address inconsistency between reviewers. Building Department Administration recommends documenting the process in enough detail that every employee knows what happens and in what order — the discipline that keeps four reviewers from citing four different requirements on the same kind of project.
Self-service technology addresses counter and phone volume: posting requirements online and routing routine status checks through a portal — the kind of system covered in Introduction to Permit Software for New Staff — frees reviewers for technical work. A single point of contact for a project reduces handoff waste the same way: one coordinator accountable for a submittal beats routing it desk to desk with no one owning the whole thing.
A department notices its four plan reviewers, all reviewing the same class of residential remodels, cite different deficiencies for the same recurring issues — one flags missing smoke-alarm locations consistently, another rarely does. Applicants who draw the more thorough reviewer face more correction cycles, and several have complained about the inconsistency. Rather than retrain reviewers individually, the department builds one written checklist from the recurring issues all four have separately been catching, and requires every reviewer to work from it. Correction cycles drop, and the complaints stop.
A frequent mistake is applying a lever to the wrong problem — a checklist does nothing for a sequential handoff delay. A second is rolling out a fix and never checking whether the metric it was meant to move actually moved. The correction is to match the lever to the specific waste found during mapping, then track that metric before and after, so the department knows the change worked rather than assuming it did.
Engage frontline staff and sustain continuous improvement over time
The people running the process every day see its waste before a manager or outside consultant does. A reviewer already knows which items applicants get wrong most often; a counter employee knows which explanation never seems to stick. Improvement designed in a manager's office and handed down skips that knowledge — and predictably meets resistance, not because staff oppose improvement but because an unexplained change threatens routines they've spent years building. Leading Organizational Change in Government covers the broader toolkit for managing that resistance.
The most reliable approach is testing in small, reversible steps rather than announcing an overhaul: plan a change, run it on one permit type for a defined period, check whether the target metric moved, then keep, adjust, or drop it. That check step depends on the same before-and-after discipline a performance dashboard is built to support — Data Analytics and Performance Dashboards covers building and reading those metrics.
The same logic applies to technology. A new online permit system is not, by itself, an improvement — it only becomes one if the old parallel step is retired alongside it. A department that adopts a portal but keeps printing every submittal to route paper copies by hand hasn't removed waste; it has added a step on top of the old one.
Finally, when something goes wrong — a missed item, a permit issued without a required review — the more useful question is what about the process allowed the gap, not who to blame. A process that only works when one person never has an off day will keep failing.
A department rolls out online document submittal. Six months later, an efficiency review finds front-counter staff are still printing every online submittal and routing paper copies through the same process used before — the digital submittal exists, but none of the old handling was removed. Reviewers now check both the paper file and, occasionally, the online copy, and the two aren't always consistent. The department added a new intake channel without redesigning what happened after intake, so the waste it meant to eliminate kept running in parallel.
A common mistake is imposing a change without asking the staff who will run it, which breeds avoidable resistance. A related mistake is adopting new technology without retiring the manual process it was meant to replace. A third is treating improvement as a one-quarter initiative that quietly lapses once attention moves elsewhere. The correction in all three: involve frontline staff in designing and piloting changes, and keep a standing, lightweight review of whether each one stuck.
Balance efficiency gains with code-compliance review quality
Speed is not the goal by itself. The goal is a department that is faster and still catches the structural error on paper before it becomes a field problem. A turnaround number that improves because a review step got quietly skipped, or a reviewer skims to hit a target, hasn't gotten more efficient — it has shifted risk from the department's calendar onto the public. That is why every lever in this course pairs a speed measure with a quality measure: resubmittal rate alongside turnaround time, reinspection rate alongside inspections completed, so a good-looking number can't be produced simply by checking less.
Seen this way, process improvement is a core competency of building department management, not a side project. A manager who maps the real workflow, names its waste accurately, applies the matching lever, and tracks a paired quality-and-speed metric to confirm it worked is doing exactly what the position exists to do: turning a fixed budget and staff into predictable, defensible service. The four preceding modules are one integrated management practice, not four separate tricks.
A mid-size jurisdiction's plan-review turnaround has drifted from a published ten-day goal to more than twenty days over several months, and the pressure from the public and governing body points to two familiar responses: hire more reviewers, or push the existing ones harder. Before committing to either, a newly appointed manager first maps the workflow and pulls a sample of recent files to see where the time actually goes. The pattern is clear once mapped: most submittals cycle through review two or three times, each cycle catching a different missing item, rather than moving through once. The bottleneck isn't review capacity or effort — it's rework caused by incomplete submittals at intake.
Instead of hiring or mandating overtime, the manager builds a standard completeness checklist for each common permit type, posts it online, and adds a short pre-application meeting for larger commercial projects so applicants know what a complete package looks like before finalizing their design, not after. Resubmittal cycles drop, and turnaround recovers toward the published goal without adding staff, without lowering what reviewers check, and without asking anyone to work faster.
The costliest mistake is treating turnaround time as the only success measure and quietly trading away review depth to improve it. A related mistake is assuming the fix for a backlog must be more staff or more pressure on current staff, without first diagnosing where time is actually lost. The correction: keep a quality measure beside every speed measure, and diagnose before prescribing — the real fix is rarely about working harder.
This course provides comprehensive professional development in process improvement and lean operations. Lean management principles, process mapping, waste elimination, and continuous improvement methodologies. Covers implementation of efficiency improvements in permitting and inspection workflows. The through-line across all five modules: speed and quality are not in tension once the process is fixed. Mapping finds where time really goes, naming waste points to the right lever, engaging frontline staff makes a fix stick, and pairing every speed metric with a quality metric proves a gain is real. A department that treats this as ongoing practice, not a one-time project, often finds its worst backlogs were rework problems wearing a staffing costume.