Confirm the governing sprinkler design basis and review authority before checking the documents. Map the supplied plans to hydraulic nodes, product data, ceiling conditions, and system interfaces. Record missing or inconsistent inputs for the qualified designer; a completed checklist does not approve the sprinkler design.
Establish the system, edition, and jurisdiction
Record whether the submitted basis is NFPA 13, NFPA 13R, NFPA 13D, or another applicable standard, together with its adopted edition and local amendments. Do not transfer criteria between system standards. Identify new installation, alteration, relocation, demolition, and retained work so the limits of the review are explicit.
Long Beach’s PRC-05F sprinkler and standpipe checklist, revised March 3, 2026, explicitly references NFPA 13, 2025 edition, and local amendments. It also separates underground fire-service requirements. This is a Long Beach document example, not evidence that the same edition or permit boundary applies elsewhere.
Obtain the current requirements directly from the project’s authority having jurisdiction and record the designer’s basis. If the cover sheet and specification cite different editions, resolve that discrepancy before using either to judge details. Keep fire alarm, fire pump, standpipe, and underground-service interfaces identified even when their detailed reviews belong to separate packages.
Twelve sprinkler document checks
Gather the sprinkler layout, riser, calculation report, water-supply record, component data, architectural room and ceiling plans, and structural information. Use the table to connect those inputs. The CSV adds blank criteria, evidence, decision, and closure fields so the specialist can record what was actually reviewed.
| Review area | Sources to compare | Question to resolve |
|---|---|---|
| Governing basis | Cover sheet, project code analysis, authority requirements | Are the system standard, adopted edition, local amendments, and review authority explicitly recorded? |
| Work boundary | Existing/proposed plans, demolition scope, system description | Does the package identify new, relocated, retained, and removed portions and the systems they belong to? |
| Space use | Room-use plan, storage description, hazard design notes | Do actual intended uses match the assumptions the qualified designer used for protection criteria? |
| Water supply input | Flow-test record, supply diagram, calculation input | Can the supply source, test location/date, elevations, and selected design input be reconciled? |
| Calculation map | Hydraulic node labels, calculation report, pipe plan | Do referenced nodes, pipe segments, elevations, and design areas resolve to the submitted layout? |
| Sprinkler selection | Legend, layout symbols, product data | Can each symbol be traced to the intended sprinkler model and its applicable listing information? |
| Ceiling geometry | Ceiling plan, sections, beam/soffit information | Is the geometry around sprinklers represented sufficiently for the specialist to assess placement and obstructions? |
| Pipe/support arrangement | Pipe plan, hanger/bracing details, receiving structure | Are support references and attachment responsibilities clear for the actual structural condition? |
| Riser devices | Riser diagram, equipment layout, valve/test/drain references | Do the devices shown on the diagram have consistent locations and accessible service references? |
| System interfaces | Underground service, alarm interface, pump/standpipe scope | Are connection points and separately reviewed systems identified with a responsible party? |
| Unprotected areas | Scope notes, ceiling/room plans, designer justification | Is each stated omission supported by a recorded applicability decision rather than a missing symbol? |
| Revised design | Accepted response, revised layout, calculations and data sheets | Has the designer assessed whether the change affects calculations, selections, or other protection areas? |
Use an explicit pending status for an unavailable flow test, unresolved hazard basis, or incomplete ceiling information. A missing input must remain visible even if other rows can be completed.
Connect the calculation map to the drawing
Choose a referenced design area in the calculation report and locate it on the plan. Match node identifiers, pipe segments, and elevation descriptions. Confirm the report and layout belong to the same design issue. This trace helps identify when a revised layout is still paired with earlier calculation references.
Record the supply test location and date, the stated reference elevation, and the input selected for design. Ask the qualified designer to explain any transformation or allowance between the test and the calculation. A reviewer should not silently substitute a more convenient supply value or infer that a test is representative merely because it is attached.
Compare room use and storage descriptions with the basis used by the designer. An architectural room name alone may not describe the contents or storage arrangement needed for protection design. Keep that information request separate from the drawing-reference question so the owner and designer can answer their respective parts.
Worked example: a ceiling revision is missing
Hypothetical example. The architectural reflected ceiling plan adds a deep soffit across a room. The sprinkler layout still references the earlier flat-ceiling background, and the submitted section does not show the soffit. This is evidence of an unresolved geometry input, not proof of an obstruction violation.
The current ceiling plan adds a soffit through the area served by the illustrated sprinkler branch. The sprinkler background and section show the earlier ceiling. Please review placement against the revised geometry and identify any layout, product, or calculation changes required.
Assign the technical decision to the qualified sprinkler designer and involve the architect for ceiling dimensions. Backcheck the updated background, relevant sections, sprinkler arrangement, and any affected calculations or data sheets. Record the designer’s conclusion even if the final decision is that no sprinkler relocation is needed.
Keep approval and document closure distinct
A coordinated package may still need technical review, authority approval, installation inspection, and acceptance testing. This worksheet tracks document questions and their resolution. It does not establish sprinkler spacing, hydraulic adequacy, hazard classification, or compliance with a product listing.
When a change affects pipe routing or supports, include the receiving structural condition and attachment responsibility in the backcheck. When it changes a room use, revisit the documented design basis. The structural checklist and MEP coordination checklist help organize those interfaces.
Use AI for source-linked sprinkler document questions
Groundbook reviews supplied PDFs and uploaded project references to return potential findings with source links. It can help a team investigate inconsistent backgrounds, references, and descriptions. Supply the applicable code and reference material needed for the review; do not assume every edition is already available.
Read about reviewing supplied code references or start with a defined document scope. Final sprinkler design and approval decisions remain with the responsible professionals and authority.