Set up a firestop documentation and as-built labeling chain for a new construction project
domain: fcia.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Require the firestop installer to submit product data and the specific UL/Intertek listed system numbers (or EJ) for every distinct penetration or joint condition before installation.
Have the installer label or log each firestop location with the system number, installation date, and installer/DRI of record.
Compile as-built firestop documentation into the project closeout/O&M package, keyed to drawings or a numbered location log so a future facilities manager can locate each firestop.
Cross-reference the installed log against the special-inspection reports (ASTM E2174/E2393) to confirm every documented location was actually inspected and accepted.
Hand off the completed documentation set to the owner as the baseline for the building's ongoing barrier-management program.
Known gotchas
There is no single uniform national labeling format mandated in every jurisdiction — confirm what the local AHJ, owner spec, or accreditation program (FM 4991/UL QFCP) actually requires before assuming a standard format exists.
Documentation created only for permit closeout often gets orphaned from facilities management — explicitly hand it off to the owner's O&M records, not just the general contractor's closeout binder.
A system number recorded without the matching product data sheet is not sufficient for later verification — capture both together.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?