The firestop submittal package: what the documentation must contain before you start
A coordinator receives a folder of twenty system PDFs with no opening references. Two unusual penetrations await technical responses. The foreman cannot tell which detail belongs to the corridor wall, and the reviewer cannot tell whether the two outstanding conditions are included.
Organize the package around the openings it must resolve. Link each defined condition to its complete proposed system, show unresolved conditions separately, and include the supporting information this project requires. A large folder is not necessarily a complete submission. The useful test is whether the reviewer and installer can find the condition, its technical basis and its current status without guessing.
Build the package around traceable conditions
- Confirm the submission requirements. Read the actual specification, amendments and review route. List the required system information, product data, qualification evidence, proposed judgements and field-record arrangements. Assign missing items to named people. Do not copy another project’s checklist as if it establishes this contract’s requirements.
- Make an opening-condition index. Use a location or type reference that connects to the plans and actual services. Record the assembly, service, opening and other necessary measured or specified information. A typical condition can cover several locations only where the responsible team confirms they actually share the relevant arrangement.
- Connect complete proposed systems. Give each index entry a findable system reference and revision, with the full details and applicable instructions. Explain what condition the proposal addresses. Do not submit a cropped rating table that omits the materials, limitations or configuration needed to assess the proposed installation.
- Separate unresolved conditions. Identify unmatched openings and the evidence sent for technical assessment. Keep supported judgements, their applicable locations and required acceptance together when received. Show outstanding responses as pending. A request number proves that a question exists, not that its proposed answer is accepted.
- Add the required delivery records. Include product and qualification evidence, and the actual labelling, inspection and closeout arrangements where the project requires them. Assign the handoffs before work begins. These records support the submission; they do not turn a mismatched system into a matching one.
- Track the response into field issue. Record the actual review disposition and conditions, reconcile revised entries and return unresolved comments through the agreed route. Issue only the appropriate current information to the crew and retain earlier versions. A submitted package and a released installation have different statuses.
Common mistakes
- Sending system files without a condition or location index.
- Hiding outstanding technical requests in the attachment list.
- Giving the crew a submitted revision as an accepted instruction.
Checklist
The submission package at a glance
- Actual requirement checklist.
- Located condition index.
- Complete system references.
- Visible pending technical decisions.
- Required supporting records.
- Response and controlled field issue.
Check your understanding
The reviewer receives every PDF, but the opening schedule does not identify which one addresses the shaft wall. Is the package findable?
