Engineering Judgements

Professional Engineering Judgements

EB Life Safety provides documented engineering judgements for fire protection code compliance questions, supporting alternative solutions with technical analysis.

Conditions of Use

The written conclusion should state its applicable area, project phase, assumptions, and expiration triggers so a later design change does not silently extend a narrowly scoped interpretation. Any AHJ conditions should be copied into the affected drawings and inspection checklist rather than left only in meeting notes.

A Defined Code Question

An engineering judgement should answer a specific project question, not act as a general waiver. EB Life Safety identifies the proposed condition, the adopted code and referenced standards, the prescriptive requirement, and the life safety objective that must be maintained. The governing edition and any local amendment should be confirmed with the AHJ before the analysis is finalized.

Analysis and Documentation

Depending on the issue, the technical basis may include comparative calculations, testing information, fire modeling, product listings, egress analysis, or evaluation of an alternative material, design, or method. Documents can reference IBC Section 104.11 or NFPA 101 equivalency concepts where applicable, while explaining assumptions, limitations, and conditions of use. A professional seal is provided only when required and within the engineer's responsible scope.

AHJ Review and Conditions

The engineer can present the rationale, answer reviewer questions, and revise the document when new project information changes the analysis. An engineering judgement does not guarantee approval; the building official or fire official decides whether the proposal meets the adopted requirements. Any acceptance conditions should be carried into drawings, specifications, inspections, and closeout records.

Boundaries of a Responsible Judgement

A defensible judgement is narrow enough to be tested against the actual project. It should identify the building area, occupancy, construction, affected system, proposed condition, and assumptions that limit its use. For example, a conclusion about an opening protective may depend on the listed assembly, wall rating, hardware, clearances, and installation details; it should not be copied to a different assembly without review. A conclusion about egress may depend on occupant load, exit access, travel distance, door operation, discharge, and the approved arrangement. Supporting calculations should show inputs and units, while cited listings, test reports, product data, and drawings should be current and traceable. If information is missing, the document should state what must be verified rather than silently assuming a favorable condition. The engineer can identify a technically supportable option, but the AHJ may require additional analysis, a different documentation format, a restriction, or a formal appeal. The project team should therefore request early feedback when the issue is unusual or likely to affect permit sequencing. Once accepted, the judgement belongs in the project record and should be referenced by the affected plans and specifications. A later change in occupancy, geometry, materials, equipment, or code edition may invalidate the analysis and should trigger a new review. This discipline keeps an engineering judgement useful without turning it into an unsupported blanket approval. The conclusion should also state whether it applies only to a construction document, a product installation, a temporary condition, or a completed building. That distinction prevents a narrowly reasoned interpretation from being reused during construction without checking the changed facts. If the AHJ imposes conditions, those conditions belong in the drawings, specifications, inspection plan, and closeout record, with an identified party responsible for confirming them.

Related Services

• AHJ permit support
• Performance-based design
• Fire and egress modeling

Frequently Asked Questions