14.2 Processing Plan Review Applications & Performance-Based Design
Key Takeaways
- An incomplete plan review application is returned rather than reviewed, because a partial review implies approval of items that were never examined.
- The stamped, dated, approved plan set is the legal baseline for field inspection; field changes require a revision submittal, and verbal approvals have no standing.
- Verifying means of egress from a floor plan follows a fixed order — occupant load, number of exits, remoteness, capacity, travel and dead-end distances, discharge to a public way, door and hardware annotations, then signage and lighting.
- NFPA 101 permits a performance-based option in which the designer demonstrates by engineering analysis that stated goals and objectives are met, evaluated against a defined set of eight required design fire scenarios.
- In a performance-based building the inspector compares conditions to the approved design documents and the operations and maintenance manual rather than to code tables, because fuel load, smoke control performance, and occupant assumptions may be explicit design limitations.
14.2 Processing Plan Review Applications & Performance-Based Design
JPR 5.2.2 requires the Fire Inspector II to process a plan review application, given a specific request, so that the application is evaluated and processed in accordance with the applicable codes and standards and the policies of the jurisdiction. JPR 5.4.5 requires verifying that means of egress elements are provided from a floor plan rather than by walking the building. And JPR 5.3.11 requires verifying compliance with construction documents given a performance-based design, so that life safety systems and building services equipment perform as described in the engineering documents and the operations and maintenance manual. Together these define the desk half of Fire Inspector II work.
The Plan Review Application Workflow
| Stage | What Happens | The Inspector's Decision |
|---|---|---|
| 1. Intake and completeness screening | Application, fee, and documents logged and date-stamped | Is the submittal complete enough to review? An incomplete set is returned, not reviewed |
| 2. Code applicability determination | Establish which adopted code editions and local amendments govern | Normally the editions in effect on the date of a complete application, per the jurisdiction's policy |
| 3. Scope and discipline routing | Determine which reviews are required — fire, building, mechanical, health, zoning | Which items are the fire code official's jurisdiction and which are referrals |
| 4. Technical review | Compare the submittal against code, section by section | Each comment cites a specific code section and a specific sheet or detail |
| 5. Comment letter issued | Written deficiencies transmitted to the applicant | Comments must be objective, code-cited, and actionable |
| 6. Resubmittal and re-review | Applicant responds; reviewer verifies each comment is resolved | Only the changed items are re-reviewed, but consequences of changes are traced |
| 7. Approval and stamping | Approved set stamped, dated, and signed; one set retained, one kept on site | The stamped set becomes the legal baseline for field inspection |
| 8. Deferred submittals | Sprinkler, alarm, and specialty system shop drawings submitted later | The registered design professional in responsible charge must review deferred items before they reach the AHJ |
| 9. Field inspection against the approved set | Construction inspected against the stamped drawings | Field changes require a revision submittal, not a verbal approval |
Two policy points appear repeatedly on the exam. First, an incomplete application is returned rather than reviewed, because a partial review creates the impression of approval for items never examined. Second, verbal approvals do not exist. A field change discovered later without a revision on record is an unapproved modification regardless of what anyone remembers being told.
What a Complete Submittal Contains
- Code summary sheet: occupancy classification, construction type, allowable and actual height and area, sprinkler condition, occupant load
- Site plan showing fire apparatus access, hydrants, and the fire department connection
- Architectural floor plans with rated assemblies keyed to a legend and tested design numbers
- Means of egress plan with occupant loads, egress capacities, travel distances, and common path and dead-end dimensions annotated
- Fire protection system drawings and, where deferred, a note identifying the deferred submittal
- Hazardous materials inventory statement where applicable
Verifying Means of Egress from a Floor Plan
JPR 5.4.5 is field verification done on paper. A repeatable order of operations prevents missed items:
- Establish the occupant load for every space, using the correct net or gross basis and the correct occupant load factor. Do not accept the designer's number without recomputing at least the driving spaces.
- Determine the required number of exits for each space and each story from the occupant load, and confirm the plan provides them.
- Check exit remoteness by measuring the overall diagonal and applying the one-half rule, or one-third in a fully sprinklered building.
- Verify egress capacity by multiplying occupant load by the applicable capacity factor and comparing to the drawn widths of doors, corridors, and stairs.
- Scale the common path of travel, travel distance, and dead-end corridors and compare each to the occupancy limit for the sprinkler condition shown.
- Trace each exit through to a public way, confirming the exit discharge is drawn and is not through a space with a different occupancy or through a locked area.
- Check door swing, hardware, and clear width annotations at every egress door, and panic hardware where the occupant load triggers it.
- Confirm exit signage and emergency lighting are shown along the entire egress path, including at exit discharge.
The most common paper-review failure is item 6. Designers routinely draw exits that discharge into a courtyard, service corridor, or tenant space with no drawn continuation to the public way.
Performance-Based Design
NFPA 101 permits a building to be designed under either the prescriptive-based option — meeting each specific code requirement — or the performance-based option, in which the designer demonstrates by engineering analysis that the design meets the code's stated goals and objectives. Performance-based design is common for atria, large assembly venues, transportation terminals, and heritage buildings where prescriptive compliance is impossible or destructive.
What the Designer Must Produce
- Stated goals and objectives and the performance criteria used to judge success, such as tenability limits for temperature, visibility, and toxic gas exposure
- Design fire scenarios — NFPA 101 requires evaluation against a defined set of eight required design fire scenarios covering, among others, an occupancy-typical fire, an ultrafast fire in a primary means of egress, a fire in a concealed space, a smoldering fire near sleeping occupants, and a fire originating outside and spreading into the building
- Explicit assumptions and safety factors, including the assumed occupant characteristics and response times
- Documentation of the analysis and the limitations of the design
- An operations and maintenance manual stating what must remain true for the design to remain valid
The Fire Inspector's Continuing Role
This is the heart of JPR 5.3.11. A performance-based building is only as safe as the assumptions it was approved under, and those assumptions live in the O&M manual rather than in the code. The inspector's task is therefore different from a prescriptive inspection:
| Prescriptive Building | Performance-Based Building |
|---|---|
| Compare conditions to the code | Compare conditions to the approved design documents and the O&M manual |
| Travel distance limit comes from a table | Travel distance may exceed the table because the analysis justified it — but only under the stated conditions |
| Smoke control is required or not by occupancy | Smoke control may be the sole basis of tenability, so a failed fan is a life-safety impairment, not a maintenance item |
| Fuel load is generally unregulated | Fuel load may be an explicit design limitation — exceeding it invalidates the analysis |
| Occupant characteristics assumed by the code | Occupant characteristics such as staff ratios or occupant alertness may be assumed by the design |
Practical consequences follow. If an atrium's design assumed a maximum fuel load in the floor area and a retail tenant later fills it with merchandise, the building no longer complies even though nothing visibly "broke." If the design assumed a specific smoke exhaust rate, the periodic testing of those fans is a code-compliance inspection item with the same weight as a sprinkler test. And because these limitations are invisible to anyone who has not read the file, the inspector must obtain and retain the approved design documentation and O&M manual as part of the permanent property record — a performance-based building inspected without its file cannot meaningfully be inspected at all.
An applicant submits a plan review package missing the means of egress plan and the code summary sheet. What is the correct processing action?
An atrium was approved under the NFPA 101 performance-based option, with tenability maintained by a mechanical smoke exhaust system. During a routine inspection, one of the two exhaust fans is found inoperative. How should this be classified?
While verifying means of egress from a floor plan, which failure is most commonly missed by reviewers?