30-min call with RobBook a proof-of-concept call
Through-penetrations and joints

// For firestopping contractors

AI for firestopping contractors, tested on penetration logs you already closed out.

For specialty subcontractors who seal through-penetrations and joints in hospitals, schools, data centers and offices. Two jobs make a fair first test: the penetration system schedule built from a field log, and the firestop inspection record your closeout package needs. Either one runs as a free AI proof of concept on copies of 20 to 30 schedules or closeouts you've finished. Your reviewer, whoever on your staff knows that work best, holds each draft against what your team turned in.

Book a proof-of-concept call30 minutes with Rob
Firestop proof of conceptSettled up front
First job
Penetration system schedules, or firestop inspection records
You send
20 to 30 finished schedules or closeouts, copied after an NDA
Stays out
Firestop management applications, job cost systems and live records
Never
Picks a listed system, rules on an installation or signs an inspection
Reviewer
Named by the owner, often a senior project manager
Left out
Certified payroll
Price
A range first, a fixed price before signing

// Jobs we would test

From the field log to the closeout binder

Schedule or records first
Two more, later

// Why these two first

A firestop gets judged on paper, and your finished jobs hold that paper

The paperwork starts before the sealant. Montgomery County, Maryland's permitting guide wants system numbers, details and the maker's installation recommendations on the plan submittals and in front of field inspectors. County inspectors then have to see each firestop before it gets covered, unless something else is approved. Every schedule your project managers finished already answers that question for a real job, which is what makes a test on old work fair.

Your records get audited too. FM 4991 approval means passing an audit of your quality system and record keeping, then a job site audit of how you select systems and how design requirements reach the field, with at least two randomly selected items opened up. UL's Qualified Firestop Contractor Program requires a designated responsible individual on staff and audits the firm again every year. Owners write those programs in: the University of Maryland, Baltimore and Northwestern University both name them in their installer qualifications.

Hospitals bring inspector rules of their own. California's hospital construction regulator, in Policy Intent Notice 67, revised in May 2021, calls for special inspection of fire-resistant penetrations and joints by an approved agency under ASTM E2174 and E2393. The people doing it need a current Firestopping Credential of Learning Achievement from the International Code Council. The notice says the UL and FM firestop exams focus on design and selection and don't address qualifying inspectors, so the inspector's name and credential belong in the record beside the result.

Cities draw the line in different places. A building division bulletin from Bend, Oregon, requires special inspection in Risk Category III and IV buildings and in separated mixed occupancies. Its building official adds structures built with alternate materials or methods, on the reasoning that listed systems carry manufacturer instructions the code itself doesn't contain. What has to be inspected in one city may not be in the next, so your reviewer names the jurisdiction on each old job in the sample.

Owners add rules no code has. The University of Kentucky's standard, revised in February 2026 for its healthcare and education campuses, requires all firestopping to be red, bars it from non-rated work, and wants a listed cable pathway system wherever cable tray crosses a rated wall. The International Firestop Council cautions that color and a logo on the tube say very little, since not every listed sealant is red. NIH's specification requires re-enterable products for data and communication cabling so cables can move without disturbing the firestop, which means what sits in a data center opening can change after your crew leaves.

People keep every judgment call. The test stays away from any firestop management application, job cost system or live record. It never picks a listed system, never decides that an installation meets a listing and never signs an inspection. Your project manager, with the design team and the authority having jurisdiction, decides every system, and a qualified inspector signs every inspection. Rules named here are general information, not legal, code or engineering advice.

// How the test runs

One job, one reviewer, then a decision

  1. Step 01

    Pick the job and the person

    Your owner names the reviewer, often a senior project manager for schedules or whoever assembles closeouts for records. Success criteria go in writing, you get a price range for running it live, and the NDA is signed before a single log moves.

  2. Step 02

    Send jobs you already turned over

    Send 20 to 30 finished schedules with the field logs, rated wall and floor types and listings behind them, or 20 to 30 closeouts with installers' logs and inspector's reports. Our shorthand for it is the sandbox: a free AI proof of concept that only ever sees finished firestop work. Where an owner forbids copies, we rebuild look-alike logs with your reviewer.

  3. Step 03

    Live for about 30 days, after a yes

    The same job runs on new logs or new closeouts for about 30 days, and a person approves each schedule or record before it goes anywhere. A next job gets a price of its own, with monthly support once a job is live.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

Rob sets the range on the call, from how many penetrations a typical project logs and how many schedule and closeout formats your owners ask for.

// Questions

Questions firestopping contractors ask first

Does this connect to our firestop management application?
No. The test reads PDFs and exports of logs, schedules and inspector's reports. Nothing signs in to a firestop management application, a job cost system or an owner's portal, and no live record is touched.
Will the AI choose the listed system for a penetration?
No. It compares what your field log says with the systems you have on file and shows which line up and which don't. Your project manager, with the design team and the authority having jurisdiction, decides every system, and nothing on this page is code, legal or engineering advice.
We hold FM 4991 approval or UL's contractor qualification. Does this touch that program?
No. The test runs outside your management system on copies of finished work, and nothing from it enters your project records. If the job goes live, your designated responsible individual decides how drafts fit your written procedures.
Do joints and perimeter fire containment count, or only penetrations?
Penetrations come first because each one has its own item, size and annular space. Joint systems and perimeter conditions can be in the sample if your logs carry them together, and your reviewer writes separate success criteria for those lines.
Hospital owners restrict photos and drawings. Can we still run it?
Yes. Whatever a hospital won't release stays out of the sample: crop or pull those files before anything is copied. If an owner refuses copies altogether, we build look-alike logs with your reviewer and test on those.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Bring one finished schedule and the log behind it.

Thirty minutes with Rob on your company, your role, the job you'd test first and about how many penetrations a typical project logs. Logs, drawings and reports stay with you until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.