Organized plan review methodology, checklist development, review sequence, and comment documentation. Covers thorough and consistent code compliance evaluation.
3
hours
0.3
CEUs
Design Professional Related
1.7.5
This course covers material relevant to the following ICC certification exams:
Organized plan review methodology, checklist development, review sequence, and comment documentation. Covers thorough and consistent code compliance evaluation.
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 teamDevelop systematic plan review procedures and checklists
A reviewer who works a submittal in whatever order the sheets happen to be stapled will eventually miss something interrelated — not from a lack of knowledge, but because an unordered review has no built-in way to guarantee coverage. A systematic method fixes that: the same categories of requirement get checked on every project, by every reviewer, regardless of how the week has gone. An ad hoc review that catches everything on one project and misses something connected on the next is hard to defend once the gap surfaces in an appeal.
The method also protects a narrower boundary: verifying that the design, as documented, meets the applicable code — not improving on it or quietly redesigning a detail. That boundary is the same one that shapes how a department works with registered design professionals generally: the design professional owns the engineering judgment, the reviewer owns confirming it produced a compliant result. The sequence runs classify, then size, then protect, then detail — occupancy and construction type first, then allowable height and area, then life-safety systems and accessibility, and finally the technical layer of structural, mechanical, electrical, and plumbing detail. Reading the design-criteria or general-notes sheet first establishes the assumptions the rest of the set depends on. A checklist built to mirror that order supports the sequence without replacing it — a floor, not a ceiling.
Two reviewers handle similar tenant-improvement projects the same week. The first works the classify-size-protect-detail sequence: confirms the occupancy classification changed from the prior tenant's use, checks that against the allowable-area limit, then moves into egress — where the occupancy change turns out to affect the required exit count. One coordinated comment covers it. The second, working a general checklist out of sequence, checks egress first, approves it as shown, and only catches the occupancy question after the applicant has revised drawings around an exit count the change was always going to invalidate. The systematic reviewer caught a cascading error before it multiplied; the other generated an extra round of corrections for the same issue.
The most common failure is skipping to the sheets a reviewer finds most familiar before occupancy classification and construction type are confirmed, risking a correction cycle built on an assumption that later turns out wrong. A close second is reviewing each sheet in isolation, so a change on one sheet never gets checked against what another depends on. The fix is procedural: commit to the classify-size-protect-detail order every time, and read the general-notes sheet first, not last.
Code Reference: IBC 107 (Construction Documents) - The code establishes minimum requirements for a systematic plan review method and the checklists that support it to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Apply consistent code interpretation across projects
Consistency is not a courtesy extended to applicants; it is what makes plan review defensible. Two similar projects held to two different standards is not professional judgment at work, it is a process that cannot explain itself — and the moment an applicant or an attorney notices, the department's credibility is on the line. Standard work is the discipline that prevents it: the same requirement, under the same conditions, applied the same way regardless of which reviewer is assigned or which day the review lands on.
That discipline leans on the checklist from Module 1, but its role here differs: where a systematic sequence protects one project against a skipped step, a shared checklist protects many projects against reviewer-to-reviewer drift, naming the same checkpoints in the same order for whoever picks it up. Consistency also has to run within a single project's own sheets — a fire-resistance rating on one sheet has to match the assembly detailed on another, and an occupant load used for egress has to match the figure used elsewhere in the set. Confirming each sheet individually without cross-checking the numbers they share verifies a pile of plausible sheets, not a consistent design.
A reviewer is assigned a restaurant tenant improvement similar to one a colleague reviewed months earlier, but recalls the two being handled a little differently. Rather than guessing from memory, the reviewer pulls the prior file and the department's documented interpretation for that condition, confirms whether the current conditions genuinely match, and applies the same basis if they do — or documents exactly what differs and why the outcome changes, rather than leaving an unexplained inconsistency between two similar projects.
The most damaging mistake is applying a personal read of an ambiguous requirement without checking how the department has handled the same condition before — exactly the drift consistency is meant to prevent. A related mistake is verifying each sheet against its own code section without cross-checking the numbers sheets share. The fix: check the documented interpretation or a comparable prior project first, and record any new resolution for the next reviewer.
Code Reference: IBC 107 (Construction Documents) - The code establishes minimum requirements for consistent code interpretation across projects to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Document plan review findings clearly and comprehensively
A plan review comment does three jobs at once, and one that does only two creates work instead of resolving it: identify the specific requirement, state clearly how the submittal falls short, and point to the compliance path. A comment that says a dimension is "too small," or just "see the code," forces the designer to guess — and a wrong guess costs an entire extra review cycle a complete comment would have prevented. Name the requirement, describe the gap, state the fix, on the first pass rather than the third.
That discipline has to hold across an entire correction letter, and across every reviewer's comments on a multi-discipline project. The same consolidation habit that keeps mechanical, electrical, and plumbing findings from contradicting each other in coordinated MEP plan review applies at the level of the whole project: before anything goes out, someone reads the full set for internal conflicts, confirms the code references, and organizes comments by sheet or discipline. Documentation does not end when corrections are resolved — the reasoning behind each finding belongs in the project file, and the approved, stamped set stands as the record of what was reviewed and later verified in the field.
A plans examiner finishes reviewing a mid-size project with forty-some comments ready to send. Before releasing them, the examiner reads the full set: two comments conflict, one requiring a wall moved in a direction that violates a dimension required elsewhere, and a third cites a section number that does not match what it describes. Catching these before the letter goes out means the applicant receives one coherent set of corrections instead of a confused call and a delay while the examiner sorts out the contradiction afterward.
The most frequent mistake is a comment that identifies a deficiency without stating the compliance path, leaving the designer to guess wrong and turning one finding into an extra resubmittal cycle. A second is releasing a comment set without reading it end to end, so contradictions between comments or reviewers reach the applicant. A third is treating the approved set as paperwork rather than a record a future reviewer might need. The fix is the same three-part discipline every time, then a second read of the whole set before it goes out.
Code Reference: IBC 107 (Construction Documents) - The code establishes minimum requirements for documenting plan review findings clearly and comprehensively to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Develop systematic plan review procedures and checklists
A systematic method only produces systematic results if the department's workflow supports it, and that starts before technical review begins. A submittal missing a required drawing or a design-criteria sheet is not ready for the sequence from Module 1 — reviewing it anyway means checking occupancy and construction type against information that may change once the missing pieces show up. A completeness screen, run against a defined list before a submittal enters the technical-review queue, catches that gap before reviewer time is spent on a moving target.
Procedure also has to account for volume without letting volume compress the method. A department under submittal pressure faces a real temptation to shorten the sequence — skip the general-notes sheet, spot-check instead of tracing dependencies — because it feels faster. It rarely is: a submittal pushed through incomplete generates a longer, messier correction cycle than the time it saved going in, simply relocating the delay from intake to resubmittal. Managing volume well means adjusting staffing and sequencing instead — not shortening the method itself when the queue is long.
A large mixed-use submittal arrives on a day the review queue is already full. Rather than assigning it straight into technical review, the intake reviewer runs it against the completeness checklist first and finds the structural drawings reference a geotechnical report that was never included, and one sheet lists a code edition that does not match the rest of the set. Holding the project at intake, with a specific list of what is missing, takes less time overall than a reviewer discovering the same gaps partway into technical review.
The most common mistake is treating completeness screening as optional under time pressure, accepting a submittal on the assumption missing items will surface naturally — usually meaning a reviewer discovers the gap only after investing real time in a review that has to be paused. A second is compressing the review sequence itself when the queue is long. The fix: treat the completeness screen as a fixed gate every submittal passes through, and manage volume by adjusting staffing rather than shortening the method.
Code Reference: IBC 107 (Construction Documents) - The code establishes minimum requirements for developing systematic plan review procedures and checklists to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Apply consistent code interpretation across projects
Consistency does not end when the first round of comments goes out; it has to survive the resubmittal, where it is most often quietly lost. A common failure checks only the items flagged in the original letter and treats everything else as unchanged and not worth a second look. But a design team addressing one comment often touches more than the flagged item — a wall moved to fix an egress-width comment can change a room's area — so consistency requires evaluating the whole resubmitted set for what actually changed.
The same question extends to coordination — with other disciplines and with the inspector who eventually verifies the project in the field. A change accepted on one sheet during a resubmittal can affect another discipline's sheet that was already approved and is not part of this round, so consistency means checking whether the change ripples outward anyway. And because plan review sometimes resolves a condition through documented interpretation rather than a drawing change, that interpretation needs to travel with the approved set to the field — an inspector who does not know a condition was resolved by interpretation cannot verify what was actually built against what plan review intended.
An architect resubmits corrected drawings for an office build-out, addressing the two comments from the original letter. Comparing the sets, the reviewer notices the architect also relocated an interior partition that nobody flagged. Rather than checking only the two corrected items and approving the rest by default, the reviewer traces the partition's effect on the room it now encloses and confirms occupant load and exit access still comply. The move turns out fine, but confirming that took the same scrutiny as the original comments, not a lighter pass because the flagged items were already resolved.
The most common mistake at resubmittal is reviewing only the flagged items and approving everything else as unchanged, missing new deficiencies introduced while addressing the originals. A second is failing to check whether a resubmittal change affects another discipline's already-approved sheet. A third is resolving a condition through interpretation without documenting it anywhere the field will see it. The fix: treat every resubmittal as a full review of what changed, and carry documented interpretations forward to the field.
Code Reference: IBC 107 (Construction Documents) - The code establishes minimum requirements for applying consistent code interpretation through resubmittal and field verification to ensure public health, safety, and welfare. Requirements vary based on occupancy classification, construction type, and building height and area.
Systematic plan review is a small number of disciplines applied consistently rather than a single technique: a fixed method that classifies, sizes, protects, and details a project in that order; a standard-work commitment that applies the same interpretation to the same condition regardless of reviewer or day; documentation that names the requirement, the gap, and the fix in every comment; and procedures — completeness screening, coordinated correction letters, full-scope resubmittal review — that keep the method intact when volume is high. A sequence not applied consistently between reviewers is not actually systematic, and a documented finding that never reaches the field inspector does not close the loop it was written to close. Participants develop the habits that hold it together: working the code path in order, checking the whole set rather than one sheet at a time, and writing comments that resolve rather than create more work.