Prepare for Plans Examiner II by reviewing plans in dependency order: (1) occupancy classification, (2) construction type and fire-resistance, (3) means of egress, (4) fire protection systems, (5) water supply and access, (6) documentation and conditions of approval. Verify each layer before moving on, practice with realistic submittals containing a plausible error, and self-check whether you can state which downstream requirements each upstream decision changes.
Occupancy Classification Is the Decision Every Other Check Inherits
Occupancy classification determines allowable area, height, fire-resistance demands, egress capacity factors, and sprinkler thresholds. Verifying it first, including mixed and accessory occupancies, prevents downstream errors from compounding.
On a submittal, the stated occupancy is an applicant claim, not a fact. A layered reviewer re-derives it from the floor plan: what activities occur in each space, how they are separated, and whether any area qualifies as accessory or incidental. NFPA 1031 expects plan examiners to evaluate a submittal against applicable codes and standards rather than accept its cover sheet, so the classification check is a skills-based task, not a formality.
Practically, classify each major space, note proposed separations between occupancies, and record which code chapter governs each portion. If the applicant claims a single classification but the plan shows two distinct uses, stop and resolve that conflict before computing anything. Write the determination in your review notes with the reasoning, because later layers will cite it and a reviewer returning to the file must reconstruct your logic.
- Classify each space from its depicted use, not the cover-sheet label
- Identify mixed occupancies and whether separation or nonseparated provisions apply
- Check accessory and incidental-use areas that could be misfiled into the main classification
- Record the governing code basis for each determination before downstream review
Scenario: The Mixed-Occupancy Tenant That Was Reviewed as One Use
A submittal labeled a 6,000 sq ft retail suite, but the plan showed a 900 sq ft food-prep area with cooking equipment and seating. Reviewing it as pure mercantile missed changed requirements.
The plausible mistake is approving the plan on the mercantile checklist: the applicant's stated classification is internally consistent, the egress widths look adequate for retail, and nothing on the drawing obviously fails. The error surfaces only if you independently classified each area. A cooking line with assembly seating suggests a second occupancy and possibly incidental-use provisions for commercial cooking, each carrying its own construction, egress, and system implications.
The better decision is to pause at layer one and require clarification: is this a mixed occupancy, and if so, are the separations shown and rated as required? If the applicant revises to a nonseparated mixed-occupancy design, several earlier 'pass' results may change, including allowable area and egress capacity. It matters because an approval built on an unexamined classification is difficult to unwind after permits are issued, and the correction cost falls on a building that already committed to a design.
Tracing Construction Type and Fire-Resistance Ratings Through the Set
Construction type fixes the required fire-resistance of structural elements and assemblies. Compare the stated type against the drawings and verify that rated assemblies are actually detailed, not merely labeled.
Once occupancy is settled, construction type becomes the hinge between classification and everything physical. The stated type should be consistent with the occupancy's permitted area and height, and the architectural sheets should show the assemblies that deliver the required ratings: wall types, floor-ceiling assemblies, and opening protectives. A layered reviewer cross-checks the stated type against the depicted assemblies and flags any rating that has a label but no supporting detail.
Trace the ratings spatially: rated corridors, shaft enclosures, fire barriers between occupancies, and exterior wall ratings based on fire separation distance. Each of these supports a later check, egress capacity depends on corridor construction, and system design may depend on whether walls are fire barriers or fire partitions. If a rating requirement is not reflected in the details, generate a comment requesting the assembly design; do not defer it to inspection, because by then the structural design is built around the omission.
Means of Egress: Applying Capacity and Travel Checks to the Drawing
Egress review applies occupant-load factors to depicted room areas, sums branch and main capacities, and checks travel distances and arrangement against the limits the occupancy classification triggers.
Start each room: area times the occupant-load factor for that use yields the design load, which drives required number of exits, capacity of doors and aisles, and whether a single exit is permissible. On the drawing, measure the elements actually shown. A corridor drawn at 44 inches supplies a different capacity than the applicant's note claiming 48 inches, and the layered rule applies here too: your occupant loads from the prior paragraph are the input, so re-derive them if the occupancy determination changed.
Then check arrangement and length: common travel distance, dead-end corridors, remoteness of exits, and continuity to the public way. This is where the drawing and the code interact most tightly, because distances depend on depicted geometry, not on narrative. Practice by measuring a plan set with a scale ruler and writing each capacity number next to the element on the drawing; the annotation becomes your documentation and lets a second reviewer verify the arithmetic path without re-measuring.
Scenario: Hydraulic Numbers That Pass While the Hazard Is Wrong
A sprinkler submittal showed hydraulic calculations meeting Ordinary Hazard Group 2 criteria. The plan sheets depicted high-piled storage. Approving on the numbers alone would certify a mismatched design basis.
The plausible mistake is treating system review as arithmetic: density, design area, hose stream allowance, and water supply all satisfy the stated design criteria, so the submittal passes. The layered check comes first and costs one minute: what is the commodity, how high is it stored, and does the stated hazard classification match what the drawing depicts? Here the storage array is inconsistent with the design basis the calculations assume.
The better decision is to comment that the calculations are technically sound for the stated hazard but the stated hazard does not match the depicted storage, and to request a revised design basis or documented justification. It matters because a sprinkler system designed for the wrong hazard can be fully compliant on paper and inadequate in the fire it actually faces. The general lesson: in system submittals, evaluate the design inputs before the design outputs, and route hazard-classification questions back to the applicant rather than choosing one yourself.
- Verify the hazard or commodity classification against depicted contents and storage heights
- Confirm design criteria match that classification before reading the calculations
- Check that point-of-connection and water supply data are consistent across sheets
- Return classification disputes to the applicant with a specific comment
Water Supply, Apparatus Access, and the Reviews That Coordinate Across Sheets
Fire flow, hydrant locations, and apparatus access are plan-examiner concerns because site plans and system submittals must agree. Compare the civil, architectural, and fire protection sheets as one set, not separate approvals.
A common pattern in real submittals is internal inconsistency between disciplines: the civil sheet shows a hydrant where the fire protection sheet's point of connection assumes different available pressure, or the apparatus access route on the site plan does not reach the side of the building the fire protection sheet relies on. Layered review treats these as cross-checks: after the system layer, verify that the supply assumptions in the hydraulic calculations trace to a flow test whose date, location, and results are stated on the drawings.
Build the habit of tabulating cross-sheet references: fire flow demand versus supply, hydrant spacing claims versus depicted locations, and access route dimensions versus the depicted building footprint. When a number appears on two sheets and differs, that is a comment even if either value alone would pass. This coordination function is a distinctive part of the Plans Examiner II scope, which extends beyond reviewing individual drawings to evaluating the completeness and consistency of the submittal as a package.
| Review layer | What it determines downstream | Documents to examine | Trigger to re-verify later layers |
|---|---|---|---|
| Occupancy classification | Area/height limits, egress factors, system thresholds | Floor plans, cover sheet, use descriptions | Any change in use or added secondary use |
| Construction type | Required fire-resistance, allowable area credit | Architectural sheets, assembly details | Change of type or added mezzanine/story |
| Means of egress | Exit count, capacity, travel limits | Dimensioned plans, door schedules | Occupancy change or wall relocation |
| Fire protection systems | Suppression/alarm coverage and design basis | Hydraulic calcs, system drawings, sequences | Hazard, commodity, or occupancy change |
| Water supply and access | Flow availability, hydrant and access adequacy | Site plan, flow test data, civil sheets | Building expansion or supply modification |
Conditions of Approval: Documentation That Makes a Review Auditable
A Plans Examiner II communicates results in writing: identify deficiencies by code section, distinguish corrections from clarifications, and state conditions of approval that bind field work to the reviewed drawings.
Review notes and comment letters are examinable skills, not paperwork afterthoughts. Each comment should name the sheet and detail, state the observed condition, cite the applicable requirement, and say what resolution is needed. Compare two comments: 'egress deficient' gives an applicant nothing to act on; 'corridor serves an occupant load of 95 but is drawn at 42 inches; provide 44 inches minimum or demonstrate compliance by an alternative' identifies the condition, the discrepancy, and two acceptable paths.
Conditions of approval close the loop between plan review and inspection. If you approved the system on the condition that a specific valve arrangement or signage be provided, that condition must appear in the approval record so the inspector can verify it. Practice writing an approval summary for a completed mock review: scope reviewed, documents received, determinations made, conditions imposed, and items deferred with justification. If a colleague cannot reconstruct your reasoning from that summary alone, the documentation layer has failed even if every technical check was correct.
A Preparation Sequence and Readiness Self-Check
Sequence study by layer, practicing each with a small plan set containing one seeded error. Track readiness with a rubric on reasoning quality, not with a score that predicts passing.
A realistic adaptable sequence: weeks one and two, work occupancy classification cases from floor-plan sketches you draw or obtain from open practice sets, writing a determination paragraph for each. Weeks three and four, add construction and egress layers to the same cases, deliberately changing one upstream input and observing which downstream results move; this drills the dependency structure that makes plan examination hard. Week five, review a system submittal end to end using the inputs-before-outputs order. Week six, write comment letters and conditions of approval for everything you flagged.
Self-check rubric, scored per mock review: (1) you independently derived occupancy classification without reading the label; (2) you can list three downstream requirements each upstream decision changed; (3) you located a seeded error within one layer of its cause rather than at the approval stage; (4) your comments name sheet, condition, requirement, and requested resolution; (5) a peer reading your approval summary can reconstruct the review. Aim to reach all five on two consecutive mock reviews. Treat this as a learning milestone only, not a passing prediction, and confirm current scope, edition, and administrative requirements through the credential issuer rather than secondary sources.
- Weeks 1-2: classification cases with written determinations
- Weeks 3-4: layered reviews on the same cases, changing one input each run
- Week 5: full system submittal review, inputs before outputs
- Week 6: comment letters and approval summaries for prior mock reviews
- Milestone: rubric met on two consecutive reviews before exam-style timed practice
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.