NFPA PACE / RP common mistakes
NFPA PACE / RP · Understand the traps and how to avoid them.
Treating the occupant load calculation as a single division of area by a factor, then using that number for every downstream requirement without checking whether the factor chosen matches the actual use and whether fixed seating or a different method is mandated.
Candidates memorize one or two load factors (e.g., 15 net for assembly unconcentrated, 7 net for concentrated tables) and apply them reflexively, forgetting that the factor selection drives egress width, exit count, and plumbing fixture counts, and that some occupancies require the greater of calculated or actual occupant load.
What to do instead
Before computing, write down: occupancy classification, whether the area is gross or net, the specific use descriptor that selects the factor, and whether fixed seating governs. Then recompute using the alternative method where the code requires 'greater of.' Practice with mixed-use floors where each area gets its own factor and the totals are summed per story.
Counting exits and measuring travel distance to the nearest exit only, without verifying remoteness of the two required exits and without checking the common path of travel limit.
The three concepts (number of exits, remoteness, common path, travel distance) are taught together but tested separately, and candidates conflate 'two exits exist' with 'two exits are adequately separated,' or measure travel distance while ignoring common path of egress travel.
What to do instead
Build a checklist per room or story: (1) required number of exits from occupant load and story height, (2) exit remoteness measured along the actual diagonal or the permitted alternative, (3) common path of egress travel limit for the occupancy, (4) total travel distance to an exit. Measure each independently and record the governing limit before deciding compliance.
Applying egress width requirements using only the occupant load of the room being evaluated, rather than the cumulative occupant load of all spaces whose egress passes through the component being sized.
Candidates evaluate components in isolation, so a corridor serving three assembly rooms is sized for one room's load; the cumulative nature of egress sizing is easy to state and easy to forget under time pressure.
What to do instead
Draw an egress path diagram from each remote corner to the public way, label each segment with the cumulative occupant load that uses it, then apply the width per occupant and the minimum width that governs. Redo the calculation for the segment with the highest cumulative load first.
Confusing the roles of the means of egress components (exit access, exit, exit discharge) and citing the wrong requirements for doors, corridors, and stairs because the component type was misidentified.
The same physical element can be exit access or exit depending on enclosure and protection; candidates label a corridor as an 'exit' and then apply exit enclosure requirements, or treat an exterior door as exit discharge when it opens onto a fenced courtyard.
What to do instead
For each element, ask: is it before the exit, the exit itself, or after the exit? Then apply only that component's requirements (fire resistance, opening protection, lighting, marking). Practice by classifying a full path from a back-of-house door to the street, labeling each segment.
Assuming a change of use, addition, or renovation is exempt from assembly requirements because the building footprint is unchanged, instead of evaluating occupancy classification and the applicable code for the scope of work.
Candidates focus on new construction and miss that a tenant improvement converting a warehouse to a banquet hall triggers assembly classification, occupant load increases, and possibly sprinkler or exit upgrades.
What to do instead
For any project, first determine occupancy classification under the current use, then compare occupant load and hazard to the prior condition, then identify which code edition and which existing-building provisions govern. State the classification explicitly before analyzing any other requirement.
Treating the residential property inspection as a cosmetic walkthrough and reporting only obvious damage, without evaluating the specific systems and conditions the standard requires to be observed and documented.
Candidates without field experience default to describing what looks bad rather than following a systematic observation sequence, so findings are incomplete and inconsistently worded.
What to do instead
Use a fixed inspection route (site and grading, structure, roof, exterior, plumbing, electrical, heating/cooling, interior, attic, crawlspace) and for each area record condition, deficiency, and implication. Write findings in the same order every time so nothing is skipped.
Describing a deficiency without stating its significance, location, and recommended action, producing report entries that cannot be acted on or defended.
Candidates write narrative prose that mixes observations and opinions, omit the exact location, and fail to distinguish safety hazards from maintenance items.
What to do instead
Adopt a fixed finding format: location, observed condition, why it matters (safety, function, or durability), and recommended action or further evaluation by a qualified specialist. Separate safety hazards from cosmetic and maintenance items in distinct sections.
Rendering an opinion on concealed conditions or on the remaining life of a system without stating the limits of the visual, non-invasive observation.
Candidates want to be helpful and overstate certainty, then fail questions that test whether the inspector should have disclaimed concealed areas or deferred to a specialist.
What to do instead
For every system, state what was visible, what was not, and whether access was limited. Use deferral language for anything requiring destructive testing, engineering analysis, or specialized evaluation, and never predict remaining service life as fact.
Skipping the documentation of the inspection process itself (date, weather, occupancy status, persons present, tools used, photographs) and reporting only conclusions.
Candidates see documentation as administrative overhead and do not realize that the record of conditions and method is what supports the report if it is later challenged.
What to do instead
Create a standard header captured at every inspection: date and time, weather and recent conditions, occupancy and access status, who was present, and instruments used. Reference photo identifiers in the finding text so the report and the record stay linked.
Mixing code-enforcement conclusions into the residential property report, or mixing inspection observations into a code-compliance determination, instead of keeping each domain's standard and authority separate.
The two domains share vocabulary (egress, occupancy, safety) and candidates cross-apply reasoning from one to the other, citing assembly egress rules in a residential report or citing a property condition standard as if it were enforceable code.
What to do instead
Before writing, name the governing document for the task: a code edition with enforcement authority, or a property condition standard with an observation and reporting scope. Cite only that document, and if a condition raises a question outside it, recommend referral rather than issuing a determination.