Skip to content

Fireproofing

Close out fireproofing: reconcile locations, reports, repairs and open evidence

By Review.LivePublished 3 min readHow we write

A hotel owner's representative asks which finish protects the lobby columns and what a future tenant should do before adding signs. The coordinator must reconcile months of coating, repairs and reports into useful records.

A thick black ring binder packed with bound documents lies on a wooden desk.
Photo: Kelly Sikkema on Unsplash

Reconcile the current protected scope with its requirements, recorded work, review evidence and maintenance information. A closeout package should let the reader trace a location and see what remains unresolved. A voluntary contractor quality-management program includes design requirements, field quality and records; its existence does not establish that this project's evidence is complete or that every member has been tested.

Carry the finding through to its evidence

  1. Start with the final scope index. Identify protected members or defined areas against current drawings and reviewed changes. Include different systems and scope boundaries clearly. Compare the installer and project records for missing or duplicated locations. Do not infer a complete protected scope from the number of pages in the report folder.
  2. Link each location to its requirement and system. Provide the relevant design or approval reference and actual product information, with primer or topcoat records where applicable. Keep superseded documents distinguishable. A generic product brochure should not be presented as the design covering every member or as evidence of what was installed.
  3. Reconcile application and review evidence. Index the recorded work, agency reports, technical reviews and required acceptance documents by their actual scope. Distinguish sampled locations from broader declarations and preserve their limitations. Ask the responsible reviewers to resolve gaps; do not write an unqualified whole-building pass from a collection of selected results.
  4. Carry every recorded disturbance through its response. Link findings, directed repairs, required follow-up and applicable closure decisions to the original location. Keep unresolved items visible with a responsible party and required next evidence. A patch photograph or paid repair invoice may document part of the chain without completing its technical acceptance.
  5. Prepare useful owner information. Identify the actual installed coating and finish and provide the required maintenance, repair and alteration instructions. Give a route for future technical questions. Do not approve tenant sign attachments from the closeout desk; their proposed construction and disturbance to protection need the applicable review.
  6. Issue a reviewed package with explicit limits. Have the assigned parties confirm their contributions and required sign-offs through the project process. Test whether a reader can find a selected location and follow its evidence. Record open scope or missing material honestly instead of using a polished cover page to imply that unresolved technical work is complete.

Common mistakes

  • Treating selected test results as every-member proof.
  • Closing a repair from its invoice or photograph alone.
  • Using handover to approve a future attachment.

Checklist

Reconcile six closeout links

  • Final protected scope and current changes.
  • Location-specific system and design references.
  • Application, reports and actual scope limitations.
  • Disturbances, repairs and closure decisions.
  • Installed finish and maintenance information.
  • Required sign-offs and honest open evidence.

Check your understanding

Does a complete-looking binder prove that every protected member has been tested and accepted?

Show the answer
No. Check what the records and actual declarations cover, reconcile the required scope and preserve gaps. Sampled reports, repair evidence and acceptance decisions each have their own limits.

Sources

  1. UL Solutions Qualified Contractor Program — voluntary quality management and recordsUL Solutions · Voluntary contractor program example; not a project's complete acceptance or Canadian regulatory process · accessed