Complete overview of the permit application process, review procedures, issuance, construction phase inspections, final inspections, and certificate of occupancy requirements. Covers workflows and documentation standards.
2
hours
0.2
CEUs
Administrative, Legal & Management
1.7.4
This course covers material relevant to the following ICC certification exams:
Complete overview of the permit application process, review procedures, issuance, construction phase inspections, final inspections, and certificate of occupancy requirements. Covers workflows and documentation standards.
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 teamManage permit applications through complete life cycle
Seen from the department's side of the counter, the permit process is a single administrative chain, and every stage exists to make the next stage trustworthy. Intake establishes what is proposed and who is accountable. Completeness screening confirms the department has what it needs before committing reviewer time. Plan review tests the proposal against the adopted codes and routes corrections back to the applicant. Issuance converts an approved proposal into a legal authorization, with fees tied to the cost of the service. The inspection sequence verifies, stage by stage, that what gets built matches what was approved. The certificate of occupancy closes the loop by certifying the finished building complies and may be occupied. Records and closeout preserve the evidence for the life of the building. A breakdown at any link — an incomplete application let through, a correction nobody tracked, a skipped inspection — does not stay contained; it resurfaces downstream, where it is most expensive to fix. Building department administrators manage this as a system, because the hand-off between stages is where most of the process's real risk lives. (This module and the two that follow work through that chain from the department's operational view; readers who want the same process from the applicant's side should see Understanding the Permit Process for Contractors and Owners.)
Intake is where the chain either starts clean or starts in debt. Whether the point of contact is a physical counter or an online portal, intake staff perform two jobs that are easy to blur together: collecting the application and its supporting documents, and screening what came in for completeness before it is routed anywhere. A complete submittal identifies the property and applicant, describes the scope of work in enough detail to determine which disciplines review it, states a valuation used to calculate fees, and identifies who holds the license or owner-builder status the work proceeds under. The completeness screen exists specifically to catch a missing required piece — a structural calculation, an energy form, a signed application — before it consumes a plan reviewer's time; a submittal that fails the screen is returned or held rather than advanced into review. That is not the department being difficult — it is refusing to let a downstream specialist discover a gap intake staff were positioned to catch first. Skipping or rushing this screen is one of the most common sources of delay in the whole process, and the delay has nothing to do with code compliance — it is administrative churn a five-minute checklist would have prevented.
Valuation and fees follow the same principle that governs the rest of the process: they are tied to the department's actual cost of the service, not to an arbitrary schedule or the applicant's sense of the project's complexity. Getting the valuation right at intake — rather than accepting an obviously understated figure — avoids a fee dispute later, once the applicant has built expectations around a lower number. Increasingly, this hand-off runs through permit-tracking software rather than paper files, which is why staff new to these systems benefit from dedicated training on the tool itself, separate from training on the underlying process; Introduction to Permit Software for New Staff covers that onboarding. The software does not change what completeness means — it changes how consistently the screen gets applied and how visible a stalled application becomes before it turns into a complaint.
A permit technician receives a same-day submittal for a small commercial tenant improvement: an application form and a set of drawings, nothing else. Rather than let the plan review queue discover the gaps, the technician runs the jurisdiction's completeness checklist against the scope shown on the drawings — the proposed use indicates a change of occupancy classification, which should have triggered an accessibility narrative and a statement addressing structural work. Both are missing. The technician documents the specific gaps in writing and holds the application rather than routing it forward incomplete. The applicant returns two days later with both items attached, and review begins from a genuinely complete record instead of discovering the same gaps three weeks in.
The most consequential failure is treating intake as a mail slot rather than a screening function — accepting whatever arrives and letting plan review discover deficiencies a checklist would have caught immediately. A related error is describing the scope of work too narrowly, producing a review that does not actually cover what gets built; the fix is training intake staff to recognize when the stated scope and the depicted scope disagree. Fee and valuation errors compound quietly — an unchallenged low valuation understates the fee, and the gap usually surfaces only when someone reconciles collected fees against actual project cost, far too late to matter. Departments that rely on staff memory rather than a documented checklist also see inconsistent screening from one technician to the next, which applicants correctly perceive as unfairness. The correction in every case is the same: a written, applied-every-time checklist, a documented valuation basis, and staff trained to hold an incomplete application rather than pass the problem downstream.
Code Reference: IBC 105 (Permits) - The code establishes minimum requirements for manage permit applications through complete life cycle to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Coordinate multiple inspections and review phases
Once a complete application clears intake, coordination becomes the department's central job — first across plan review disciplines, then across the field inspections that follow issuance. A project of any complexity is rarely reviewed by one person; building, fire, mechanical, plumbing, electrical, and energy reviewers may each need to evaluate the same drawings for their own discipline. The efficient model routes copies to every applicable discipline in parallel, sets a target date for responses, and consolidates every discipline's comments into a single correction letter before it goes to the applicant. That consolidation step matters as much as the parallel routing: an applicant who receives several separate, sometimes contradictory comment sets cannot resolve them without going back to the department to referee, erasing the time parallel review was supposed to save. Resolving conflicts internally before the applicant sees them is what makes multi-discipline review actually faster, not merely simultaneous. (Electronic Plan Review: Tools and Best Practices covers the platforms that make simultaneous multi-discipline markup and comment consolidation practical at scale.) Some items are appropriately approved for later submittal rather than reviewed up front — specialty components whose final design depends on other trades. These deferred submittals still have to be logged, tracked to a defined trigger, and reviewed before the associated work is installed; an item that never gets tracked back into the queue is a compliance gap waiting to be found at inspection, after the component is already in place.
Issuance converts an approved set of plans into a legal authorization: the approved plan set and inspection card become the standard the department measures the built project against, and any condition attached at issuance — a pre-construction meeting, a phasing limitation, an outstanding deferred item — travels with the permit into the field. Fees are finalized at this point, calculated from the intake valuation, and structured to recover the review and inspection effort the project actually requires rather than functioning as a flat tax.
The inspection sequence that follows exists because each stage of construction becomes hard to verify once the next stage covers it: foundation and footing work before backfill, framing and mechanical/electrical/plumbing rough-in before insulation and drywall close them in, and further inspections through to a final covering the completed project. Scheduling and managing reinspections is a coordination function in its own right — an inspection called for the wrong stage wastes a visit that could have gone to a ready site, and any hold an earlier inspector noted has to be carried forward and confirmed at the next inspection rather than lost between visits. On projects involving structural or geotechnical elements the code requires an approved agency to monitor, the department also tracks the required statement of special inspections and its reports as a parallel record — a project can pass every field inspection and still not be ready to close if that reporting is incomplete. (IBC Special Inspections and Structural Tests covers that program; the point here is that the department has to track it to completion alongside the routine inspection sequence.)
A mixed-use project needs building, fire, mechanical, and accessibility review on one submittal, plus a deferred submittal for a curtain-wall system pending supplier selection. The coordinator routes the full set to all four disciplines simultaneously with a two-week target, logs the curtain wall as deferred with a date tied to a construction milestone, and holds the correction letter until every discipline has responded. Fire and accessibility flag related issues on the same stairwell; because the coordinator reviews all comments before release, the conflict is resolved internally and the applicant gets one letter with one consistent set of instructions instead of two partially conflicting notes. The curtain-wall submittal later arrives on schedule and is reviewed before the wall is installed, not after.
The recurring coordination failure is routing plans to multiple disciplines with no mechanism to reconcile their comments, producing the uncoordinated correction letters that frustrate applicants and generate repeat correspondence. A second failure is losing track of deferred submittals — logging the deferral but not tying it to a hard trigger, so the item surfaces only when a field inspector notices it already installed and unreviewed. On the inspection side, the common breakdown is scheduling before work is genuinely ready, wasting inspector capacity, and failing to carry forward a hold from one inspection to the next, so a documented issue quietly drops out of the file. The correction is the same discipline applied at each stage: consolidate before releasing, track deferred items to a hard trigger rather than memory, and carry every open condition forward until it is explicitly closed.
Code Reference: IBC 110 (Inspections) - The code establishes minimum requirements for coordinate multiple inspections to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Issue certificates of occupancy with appropriate conditions
The certificate of occupancy is the closeout gate for the entire process: issuing it is the building official's certification — to the owner, future owners, and the public — that the completed building complies with the approved plans and codes and may be legally occupied. That certification only means something if everything upstream actually closed out first. The final inspection has to be approved, but so does every inspection that preceded it; any required special inspection reports have to be complete, not merely started; outside agencies with jurisdiction over part of the scope have to have signed off in the file; and the occupancy classification on the certificate has to match what was actually reviewed, not simply what the applicant currently intends. A building official who signs before confirming that full record is treating the certificate as paperwork rather than as the certification it is. (Certificate of Occupancy: Requirements, Conditions, and Revocation covers the certificate itself — its legal effect, temporary and partial certificates, and revocation — in more depth than this module's closeout focus.) Once the final inspection is approved, the certificate is prepared, delivered, and a copy kept in the property's permanent file; permit-tracking systems can generate that document automatically once every required inspection and fee shows complete, one more reason the underlying records have to be accurate before that automation fires.
Closeout does not end when the certificate is handed over — it ends when the department's own record of the project is complete and retrievable. The permit, the review correction history, every inspection record, the special inspection reports where applicable, and the certificate itself together form the permanent record of the project for the life of the building; a future remodel, a real estate transaction, or a complaint years later will be answered from that file, not from memory. (Records Management and Document Retention for Building Departments covers how that permanent record should be organized, retained, and protected once the project closes.) A department that treats records as an afterthought will eventually be asked for a file it cannot reconstruct.
None of this closeout discipline is visible without measurement. Turnaround time on plan review, the open-application backlog, and the age of the oldest unresolved corrections or unscheduled finals are the figures that reveal whether the system is working or quietly drifting — a growing backlog is the administrative equivalent of a code violation, visible only if someone is looking at the numbers rather than only at individual files. (Data Analytics and Performance Dashboards covers building and reading those department-level metrics.) Reviewing them regularly is what lets a building official catch a coordination breakdown before it becomes a pattern of complaints.
Two similarly sized commercial buildouts move through the same department in the same quarter. The first arrives at intake complete, clears completeness screening on the first pass, receives one consolidated correction letter after parallel review, and moves through its inspection sequence with each inspection called only when work is genuinely ready; its one deferred submittal — a fire suppression shop drawing — is tracked to a milestone and reviewed before installation. When the final inspection passes, the file already shows every prior inspection closed and the special inspection reports complete, so the certificate is issued the same week. The second project was accepted incomplete at intake; its review comments arrived from three disciplines separately over different weeks, several in conflict; a deferred structural submittal was never tracked and surfaces only when a framing inspector finds it already covered; and by the time every open item is resolved, a fire department sign-off documented months earlier has to be reconfirmed because so much time has passed. The certificate is eventually issued, weeks later, only after staff time was spent reconstructing a record that better tracking would have kept current throughout. Both buildings meet the same code; only one project's file made that easy to confirm when it mattered.
The most serious closeout mistake is issuing a certificate without independently verifying the complete record — trusting that a passed final inspection means everything else is also closed, when corrections, special inspection reports, or an outside agency's sign-off may still be outstanding. A related error is letting the certificate's stated occupancy classification drift from what was actually reviewed, particularly when a project's use shifted slightly during construction without a corresponding review. On the records side, the common failure is treating the property file as complete once the certificate is issued, without confirming every record is actually filed and retrievable — a gap that costs nothing until someone needs that file years later. At the department level, the common systemic mistake is not tracking turnaround, backlog, and aging at all, so a breakdown in one discipline goes unnoticed until it becomes a pattern of complaints. The correction in each case is verification made routine rather than assumed: a closeout checklist confirmed before signing, a file audit before closing, and metrics reviewed on a regular cadence rather than only after something has gone wrong.
Code Reference: IBC 111 (Certificate of Occupancy) - The code establishes minimum requirements for issue certificates of occupancy with appropriate conditions to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
This course provides comprehensive professional development in the permit process: from application to certificate of occupancy. Complete overview of the permit application process, review procedures, issuance, construction phase inspections, final inspections, and certificate of occupancy requirements. Covers workflows and documentation standards. Taken as a whole, the permit process is a single administrative system viewed from the department's side of the counter: an incomplete intake, an uncoordinated review comment, a deferred item nobody tracked, or a certificate signed before the file was actually closed all have the same effect — a problem created early resurfaces later, where it costs the most to fix. Staff who apply the same discipline at every hand-off — genuine completeness screening, coordinated multi-discipline review, a properly sequenced inspection program, and a closeout that verifies the whole record before signing — move projects through with fewer surprises and a permanent record that still answers questions accurately years later.