Fire Protection Engineer Notes on iPhone: Code Research, Inspection Findings & Hydraulic Calculation Records

Fire protection engineering combines code interpretation, hydraulic analysis, and field observation across buildings where the stakes — life safety — leave no tolerance for documentation gaps. A sprinkler system deficiency that isn't documented thoroughly isn't actionable. A code interpretation reached after hours of research isn't useful if you can't retrieve it six months later. Nemos gives fire protection engineers a structured place to capture both field observations and technical research.

Why Fire Protection Engineers Need Structured Notes

Fire protection projects involve multiple overlapping systems — suppression, detection, alarm, egress — across buildings with decades of construction history and code revision. The engineer who did the original design may be gone. The record drawings may not reflect as-built conditions.

Field observation is how you reconstruct what's actually there. Structured note-taking is how you make those observations actionable for design, compliance documentation, and expert reporting.

What to Capture in Nemos

Code Research Notes Fire protection codes — NFPA 13, NFPA 72, IBC, local amendments — are frequently revised, and jurisdiction-specific amendments add another layer. When you've worked through a code question, document: - Code edition and section reference - Your interpretation and the reasoning - Any relevant Annex material or TIA - Applicable jurisdiction amendment - Whether AHJ (Authority Having Jurisdiction) confirmed the interpretation

This avoids re-researching the same code question on the next project and creates a reference you can cite in reports.

Sprinkler System Inspection Observations When inspecting an existing system: - System type (wet, dry, pre-action, deluge) - Sprinkler head types and K-factors observed - Coverage pattern and spacing measurements (spot-check) - Control valve status and location - Backflow preventer condition - Any physical damage, corrosion, or obstruction - Deficiency description with location reference

Deficiencies need location-specific documentation to be correctable. "Sprinklers obstructed by storage" is insufficient. "Aisle 14, bays 6–9, obstructed by pallet storage within 18 inches of deflectors" is actionable.

Hydraulic Calculation Input Notes Before running hydraulic calculations: - Design area selection rationale - Remote area location and justification - Hazard classification applied and code basis - Pipe schedule or hydraulically designed - Water supply test data used (date, location, static, residual, flow)

These input notes document the engineering basis for the calculation — essential for peer review and record sets.

Life Safety System Findings For egress, emergency lighting, and fire alarm assessments: - Occupant load calculations by room and floor - Exit capacity observations - Travel distance measurements (approximate, flagged for survey confirmation) - Emergency lighting coverage gaps - Fire alarm device coverage observations - Any ADA life safety conflicts noted

Pre-Construction Meeting Notes Capture key agreements and clarifications from contractor coordination: - Contractor name and project contact - Items agreed regarding phasing of system installation - Coordination with other trades (ceiling, HVAC, structural penetrations) - Special inspection requirements - AHJ submittal requirements confirmed

Building a Code Reference Library

Accumulate a note per code topic you encounter repeatedly: occupancy classification, hazard classification, sprinkler exemptions, alarm initiation thresholds, egress width requirements. Each note stores your current working interpretation with code section citations. This library becomes a rapid reference that eliminates re-reading the same sections repeatedly.

FAQ

Can I use Nemos offline during field inspections in buildings with poor signal? Yes. Nemos works fully offline. Notes sync to iCloud when you're back in range.

How do I handle photos of deficiencies? Attach photos directly to the inspection note with a caption describing location. Photo documentation of deficiencies is critical for insurance, litigation, and corrective action verification.

What about NFPA 25 inspection records — does Nemos replace those? No. NFPA 25 requires formal inspection forms with specific data fields. Nemos supplements formal records with contextual field observations. Keep formal records in your inspection management system.

How do I organize notes across large campuses with many buildings? Use a consistent title convention: campus name, building identifier, inspection date. Tags by system type (sprinkler, alarm, egress) add a second search axis.

Can I capture voice notes during inspections? Yes. Voice memos attached to notes are useful when your hands are occupied. Transcribe key findings to text for searchability after the inspection.

Why not just use the inspection report template? Report templates capture structured fields. Nemos captures the observations that don't fit in fields — engineering judgment, code interpretation reasoning, and contextual details that inform the final report.

Related Reading

• /blog/safety-officer-notes-iphone — regulatory compliance documentation and safety observation records
• /blog/structural-engineer-notes-iphone — building condition assessment and code review documentation
• /blog/quality-control-inspector-notes-iphone — systematic inspection documentation patterns
• /blog/acoustic-engineer-notes-iphone — engineering field observation and measurement documentation

Sources

• Fire protection code references: NFPA 13 (2022 edition), NFPA 72 (2022 edition), IBC (2021 edition)
• Inspection documentation requirements: NFPA 25 (2023 edition) — Standard for the Inspection, Testing, and Maintenance of Water-Based Fire Protection Systems

Download Nemos free on the App Store.