Construction professional working on Firestopping Inspection Records: A Practical QA/QC Checklist for Building Projects

Firestopping Inspection Records: QA/QC Checklist

This practical checklist helps QA/QC engineers, MEP coordinators, and site inspectors review firestopping inspection records. It focuses on traceability: connecting each penetration to its approved firestop system, observed installation, inspection result, and any corrective action. It is not a design guide or universal installation procedure. The contract, approved drawings and submittals, applicable authority requirements, manufacturer information, and project inspection and test plan govern the requirements for each installation.

A general note such as “firestopping complete” does not identify which opening was inspected or what evidence supports the result. A useful record lets another reviewer locate the opening, identify the reference used for the check, understand what was observed, and follow unresolved items through their disposition. The checklist below is a record-review aid, not a substitute for project-specific acceptance criteria.

Set the record boundary

Before reviewing entries, establish the area and work they cover. Identify the building, floor or zone, room or grid reference where available, work package, inspection date, and the organisations or roles responsible for installation and review. Use the project’s location conventions so someone else can find a penetration without relying on the original inspector’s memory.

Clarify what each record is meant to establish. An inspection log may document observed installation and outstanding actions; it should not imply design approval, product approval, or final acceptance unless the assigned reviewer has that authority and the governing documents provide for it. Keep installation, inspection, deficiency resolution, and project acceptance distinct.

Confirm which controlled records are in scope for the review, such as the inspection form, penetration schedule, marked-up drawing, approved submittal, photographs, and corrective-action record. This is general workflow guidance: the project’s document-control process determines which records are required and how they are maintained.

Identify each penetration and its system reference

Each inspected penetration needs a unique reference, or another controlled identifier already established by the project. Check that its location description distinguishes it from nearby openings. Depending on project conventions, location details may include building, level, room, grid, wall or floor reference, and a drawing or schedule reference. If a location changes or a drawing is revised, preserve the link to the applicable record rather than silently reusing an ambiguous description.

For the opening, record the information required by approved project documents to identify the condition being inspected. This may include the service or services passing through, the barrier or assembly reference, and a description of the penetration. Do not infer a required rating, dimension, or other design property from appearance or from a generic checklist. Use the approved drawing, schedule, submittal, or other governing project evidence.

Link the penetration to the approved firestop system reference for that condition. Record the product or system identification as it appears in the approved submittal or project schedule, with the document title or identifier and revision where available. The record should allow comparison of the observed work with the project-approved reference. If that reference is missing, unclear, or appears not to match the observed condition, record the discrepancy for resolution; do not choose a substitute system by guesswork.

Capture observed installation evidence

The inspection entry should describe what was actually observed, not merely repeat the planned work description. Record the inspection date, inspector or responsible role, inspection stage, and result. State whether the work was accessible for review and identify any portion that could not be seen. If work is concealed before inspection, follow the project’s defined inspection and documentation process; this article does not establish a universal hold point or concealment rule.

Use photographs or other project-approved evidence where they help identify the location and show the observed installation. Link each image to the penetration reference and label it so a later reviewer can tell which opening it depicts. A photograph without a location or system reference may be difficult to verify. Images support the record but do not independently establish compliance with an approved system or acceptance criteria.

Describe observed features using the checks and terminology in the approved project documents and applicable manufacturer information. Do not add generic dimensions, material details, or pass/fail limits that are not in those sources. If the inspection compares the work with a drawing, submittal, or installation instruction, cite the specific document and revision used. This ties the observation to its stated basis instead of an unstated assumption.

When reviewing a record, check whether it distinguishes observed facts from information copied from a schedule or plan. For example, a scheduled system reference identifies the planned basis for review; it does not by itself document what the inspector observed at the opening. Record any unavailable evidence or mismatch explicitly and route it through the project process.

Make each inspection result reviewable

For each check, identify the criterion or source applied, the observation, the result, and who recorded or reviewed it. A clear entry can identify the approved system reference, state that the observed installation was compared with it, and record either the observed match or the specific discrepancy. If the project form uses status codes, follow the project’s definitions; a code such as “accepted” does not necessarily carry the same authority on every project.

Keep “not inspected,” “not accessible,” “incomplete,” and “not applicable” distinct from a satisfactory result. Explain why a check could not be completed and identify the next action or responsible owner where the project process requires it. An empty field or ambiguous mark should not be left to imply approval.

The inspection record is part of quality documentation, but it does not replace the governing acceptance process. The responsible project reviewer must determine whether the evidence and disposition meet contract and approved project requirements. Jurisdictional requirements vary; confirm the applicable authority requirements for the project rather than inferring them from this general checklist.

Record deficiencies and follow them to disposition

When an observation does not meet a stated project criterion, link it to a deficiency, nonconformance, or other project-controlled action record. Include the penetration reference, concise description of the observed condition, applicable criterion or source, assigned person or organisation, and status. Add dates, priority, or target completion information only as required by the project process.

Keep the original finding visible when corrective work is recorded. Add the action taken, any required reinspection evidence, the name or role of the reviewer, and the resulting disposition. A closed item should let another reviewer understand what changed and how closure was established. Do not close a deficiency solely because corrective work was reported if the project requires inspection or other verification.

If the approved system reference or governing documents are unclear or conflicting, record the issue and refer it to the responsible design or project authority. Do not resolve a design question by changing the inspection criterion. The project’s authorised parties determine how the issue is answered and documented.

Build a practical inspection record set

A project may use a spreadsheet, inspection form, digital quality platform, drawing register, or combination of records. Whatever the format, maintain a reliable link among location, penetration identifier, approved firestop system, inspection evidence, result, and corrective-action record. Use consistent identifiers across forms and photographs, and control revisions so current information can be distinguished from superseded entries.

As a review aid, check whether each entry contains the following information where applicable and required by the project:

  • Unique penetration reference and location information sufficient to find the opening.
  • Relevant drawing, schedule, or other location reference, including revision where recorded.
  • Description of the penetration and observed services or condition, as required by the project form.
  • Approved firestop system or product reference linked to its controlled project document.
  • Inspection date, stage, inspector or responsible role, and access limitations.
  • Observed installation evidence, including linked photographs where used.
  • Inspection result tied to the applicable project criterion or source document.
  • Deficiency reference, assigned owner, corrective-action evidence, reinspection, and disposition where applicable.

This list is not a mandatory universal data schema. The project’s approved forms and document-control process govern required fields. If a field does not apply, use the project’s convention for recording that fact rather than leaving a value that could be mistaken for an omission.

Review completeness before close-out

Before compiling records for handover, compare inspected locations against the relevant penetration schedule, drawings, or other controlled scope record. Resolve duplicate identifiers, unexplained gaps, and entries that cannot be matched to a location. Confirm that each recorded system reference points to the intended approved document and that revisions have not been mixed without explanation.

Review open and closed deficiencies separately. For open items, show current status and responsible owner according to the project process. For closed items, verify that required corrective-action and inspection evidence is linked. A complete-looking register is not proof that every installation has been accepted; the authorised reviewer makes that determination under project requirements.

When records are incomplete, identify the missing information, the party responsible for providing or reviewing it, and the means of resolution. Preserve an audit trail when entries are corrected or supplemented. Do not overwrite prior observations in a way that conceals what was first recorded or how the issue was resolved.

Reviewer’s checklist

  • Can a reader locate each recorded penetration using project location references?
  • Is each penetration linked to the relevant approved firestop system reference and controlled document?
  • Does the entry distinguish observed installation evidence from planned or assumed work?
  • Are the inspection result and its basis identifiable, without unsupported generic acceptance limits?
  • Are photographs or other evidence labelled and linked to the correct penetration, where used?
  • Are inaccessible, incomplete, or uninspected conditions clearly distinguished from satisfactory results?
  • Can each deficiency be traced through assigned action, verification, and recorded disposition?
  • Are unresolved system-selection or document conflicts referred to the responsible project authority?
  • Do the records follow project document-control and close-out requirements?

Related EngineersBlog reading

Research and scope notes

The linked EngineersBlog pages provide related reading context, not technical proof for firestopping requirements. The available research does not establish a jurisdiction, firestop system, installation criterion, or project acceptance threshold for a particular building. Confirm those matters in governing project documents, approved submittals, applicable manufacturer information, and authority requirements. This article addresses record structure and traceability only.

For general guidance on people-first informational content, see Google Search Central: Creating Helpful, Reliable, People-First Content. This editorial source does not define engineering acceptance criteria.

Conclusion

Firestopping inspection records are useful when each penetration can be followed from its location and approved system reference to observed installation, inspection result, and any deficiency disposition. Keep those links explicit, preserve document revisions, and distinguish unresolved or inaccessible work from accepted results. The applicable contract, approved project documents, jurisdiction, and authorised reviewers—not a generic checklist—determine requirements for a particular installation.

Terminology note: For search and record clarity, this article uses the project’s own definitions and evidence for the following topic terms: sealing. These labels do not create project-specific acceptance criteria.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top