Project Planning, Documentation, and Applicable Codes and Standards
This domain covers the work that happens before fieldwork: defining scope, identifying the governing code edition, assembling documents, and planning tests so results are defensible. Questions often place a contract, a code book, and an authority having jurisdiction (AHJ) requirement in tension.
Core rules and concepts
- The enforceable edition is the one adopted by the AHJ, not automatically the newest edition or an edition named in an old contract.
- Assemble the contract scope, approved plans, as-built drawings, hydraulic calculations, manufacturer instructions, prior inspection reports, permits, and the record of completion.
- NFPA 25 is the baseline for inspection, testing, and maintenance of water-based systems; NFPA 72 governs detection and alarm records.
- The inspection plan should sequence notifications, impairment control, testing, restoration, and documentation.
- Scope changes need written authorization; informal additions can change liability and code compliance.
Worked example
A contract references NFPA 25-2017, but the AHJ has adopted NFPA 25-2020 and the sprinkler system was modified last year. The correct approach is to confirm the adopted edition with the AHJ in writing, apply the current requirements to this inspection, and document the contract conflict for the owner. Following the older contract without review is wrong; silently applying the newer edition without recording the discrepancy is also weak documentation. The report should state the basis of inspection and any limitation.
Traps that cost marks
- Assuming the newest code is automatically enforceable.
- Using a generic checklist that omits system-specific devices.
- Skipping AHJ notification before tests that discharge water.
- Failing to record pre-existing deficiencies at the start, then being blamed for them later.