Skip to content

Fireproofing

Who reviews fireproofing: name the checks, reports and acceptance responsibilities

By Review.LivePublished 3 min readHow we write

A warehouse superintendent expects the building inspector to check all fireproofing. The specification also names agency testing and a technical review, so the team needs the actual responsibilities before starting.

Four people review construction plans together beside a rural work area.
Photo: U.S. Fish and Wildlife Service Southeast Region on Wikimedia Commons · Site meeting at Ochlawaha Bog (5413347466) · CC BY 2.0 · Cropped, resized, colour adjusted and sharpened.

Read the project's requirements and name who performs each check, produces each record and makes each applicable acceptance decision. Do not assume one visit covers all those roles. A public US guide specification distinguishes independent testing from manufacturer inspection and certifications; it is an example of separate functions, not the required review chain for every Canadian project.

Connect the requirement to a named record

  1. Gather the actual review requirements. Read the current specification, approved protection information, contract assignments and applicable authority requirements with the responsible project team. List unresolved references. Ask which checks apply to each system rather than importing a sprayed-material testing arrangement into an intumescent coating package.
  2. Separate the functions on the sheet. Give installer application checks, agency measurements or tests, technical review and authority involvement their own rows where required. Record each row's scope and deliverable. A manufacturer's visit, a crew check and an agency report should be labelled accurately instead of all appearing as 'inspection complete'.
  3. Name the responsible organizations and contacts. Confirm appointments and required qualifications through the actual project process. Record who arranges attendance and who receives findings. Do not assume that a person paying an invoice is the technical reviewer or that a familiar agency is appointed to perform this project's required work.
  4. Confirm who decides the next activity. Ask how each report or review becomes an applicable acceptance or release decision and what its scope covers. Identify unresolved findings and required follow-up. A coordinator can track the evidence without claiming authority to change acceptance criteria or release a concealed area independently.
  5. Arrange the information reviewers need. Agree the current documents, location records, preparation or application evidence, notices and access arrangements. Tie them to the relevant stages. A named reviewer without an agreed visit purpose can arrive after the required condition has been hidden or before the scope is ready.
  6. Keep responsibilities current through changes. Update the sheet when products, areas, reviewers or sequences change. Circulate it to the affected parties and retain the previous decisions. Use the same references for deficiency follow-up so a repair is not left waiting because the original testing and acceptance duties were never assigned.

Common mistakes

  • Treating every visit as the same inspection.
  • Assuming the payer decides technical acceptance.
  • Naming an agency without confirming its appointed scope.

Checklist

Name the review chain

  • Current system and review requirements.
  • Separate checks and deliverables.
  • Appointed organizations and contacts.
  • Actual acceptance and release responsibilities.
  • Notice, documents and access arranged.
  • Changes and follow-up assignments recorded.

Check your understanding

Can the superintendent rely on a building-inspector visit to replace an agency test named in the specification?

Show the answer
First confirm the actual required functions and authority process. Do not assume one role replaces another; arrange the specified evidence and its applicable acceptance route.

Sources

  1. UFGS 07 81 00 — selected pre-installation and execution provisionsUSACE / NAVFAC / AFCEC · United States; editable guide specification, not a Canadian requirement · accessed