30-min call with RobBook a proof-of-concept call
Job 01 · Project management

// Firestopping contractors · Penetration system schedules

Penetration system schedules drafted from the field log, with unmatched openings listed for your project manager.

Your crews walk a floor and log every opening. Someone then has to set each one against the rated wall and floor types and the listed systems on file, and write it up the way that owner's specification wants. A free AI proof of concept drafts that schedule from copies of 20 to 30 schedules you already finished. Your reviewer, the project manager who knows your logs best, checks each draft against the schedule you submitted and whatever came back.

Book a proof-of-concept call30 minutes with Rob
Old schedules
20 to 30
Systems picked by AI
None
Installations ruled on
None

// The one job

From a line in the field log to a line on the schedule

A project's field log says what is in each opening: the floor and room, the barrier, the item passing through, its size, and whatever the installer measured. Your project manager sets those lines against the life safety plans, the rated wall and floor types and the listed systems your company keeps on file, then writes the schedule the specification calls for.

In the test, AI reads copies of those records and drafts the schedule: each penetration's barrier type and rating, its penetrating item and size, its annular space, and the listed system your team named for it or the listings on file whose stated conditions match, shown for your project manager to choose from. Anything with no matching listing goes on its own list for your project manager to resolve with the design team. Nothing is submitted, and the draft chooses no system.

Field penetration logInputs
Location
Barrier type
Item and size
Annular space
ItemMeasuredNote
Made-up log, no real job shown
Compared with
listings on file
Penetration system scheduleDraft
Location
Barrier rating
Listed system
Open items
PenetrationListing on fileQuestion
Made-up schedule, for illustration

// Where it gets hard

A system number is a set of conditions, and a field log rarely states all of them

The number is a sentence in code. UL's published key opens with C, F or W for walls or floors, floors only, or walls only. The next letters name the construction: A and B for concrete floors on either side of 5 inches, C for framed floors, G for cross laminated timber floors, J and K for concrete or masonry walls on either side of 8 inches, L for framed walls, N for composite panel walls. The first digit then names what passes through: 1 metallic pipe, conduit or tubing, 2 nonmetallic, 3 electrical cables, 4 cable tray, 5 insulated pipe, 6 electrical items like busducts, 7 mechanical items like air ducts, 8 a grouping of those, and 0 nothing at all. A series that runs out moves to five digits, as C-AJ-2999 will. Montgomery County, Maryland's permitting guide walks one example, C-AJ-3154, character by character. A log line reading "3 inch pipe, block wall" can't be set against that code until it says what the pipe is made of and whether it is insulated. New York State's master section also accepts designs from Intertek's and FM's directories, so the draft keeps the directory each system came from.

Each owner's schedule has different columns. New York's section asks for product reference numbers, design number, location, the item's material, size, insulation and combustibility, the maximum annular space or opening, wall and floor construction, the hourly rating, and F and T ratings, then says the schedule is for information only and won't be acted on for approval. The University of Maryland, Baltimore wants barrier type with rating, size and type of penetrating material, UL system number and product name, and rejects partial submittals, so every penetration on the project has to arrive in one package. Northwestern University asks for a use matrix of maker and system by condition. The Dormitory Authority of the State of New York's sample form limits T to floors and adds L and W where available. Your reviewer names the format for each old job before the first draft.

F, T, L and W answer different questions. Montgomery County's guide defines F as passage of flame, T as fire and temperature, L as air and smoke leakage and W as water resistance, and says the model codes need no T rating on a floor penetration inside a wall cavity. NIH's specification asks for T only on floors outside wall cavities and rated shaft enclosures. The International Firestop Council warns that in gypsum walls, a listing at one rating doesn't automatically cover another unless it says so. New York notes that its code doesn't require W but a project may want it, and the University of Maryland, Baltimore wants a Class 1 W-rated system at every new and existing floor penetration. The draft shows which rating columns each line has and which the listing on file doesn't address.

Annular space is where logs go thin. Montgomery County calls it the opening around a penetrating item, says its tolerances must be followed, and warns they can change with the rating sought. The Council's inspection video names what else to record: whether a plastic pipe is vented or closed, the type and thickness of any insulation, the largest diameter of a cable bundle, whether a tray is steel or aluminum and how deep its fill runs, and whether a sleeve is present. Some systems allow point contact, it adds, while combustible pipe needs room for material to expand and sprinkler pipe looks to NFPA 13. Owners pile on: the University of Maryland, Baltimore requires black steel sleeves at new floor penetrations, and NIH wants floor openings with annular space over 4 inches in traffic areas to carry the floor load. The draft carries the log's numbers and marks each field it can't find, rather than assuming one.

The open list is the point of the job. Montgomery County's guide says a modification to a tested system voids its rating. Where nothing listed fits, Northwestern wants the modified illustration approved by the maker's fire-protection engineer as an engineering judgment, with the authorities having jurisdiction approving before submittal, and the Council's 2025 pocket guide says plan submittals should always show which details rest on judgments. The draft never writes one. It lists the penetration, the barrier, the item and what the listings on file don't cover. Your reviewer will look for a listing matched to the wrong barrier, a size or annular space outside what a listing states, a missing field passed over in silence, and any line that reads like a ruling. Rules here are summarized for context only and are not legal, code or engineering advice.

// What you send

Schedules your project managers already finished

Copies only
Listings as you kept them
01

20 to 30 finished schedules

From hospitals, schools, data centers or offices, each with its field log. Include one that came back for resubmittal, one renovation, and one with an engineering judgment in it.

02

The rated wall and floor types

Life safety plans, partition and floor assembly types, the firestopping section of each spec book and any addenda, as issued for those jobs.

03

The listings you had on file

Prints of the system details your team used at the time, from whichever directories those jobs called for, plus maker letters and judgments.

04

Copies, once the NDA is signed

Nobody from Massmarket opens your firestop application or job cost system. Logs an owner won't release become look-alikes, built with your reviewer.

// Before it starts

On paper before a log is copied

The owner signs off on each of these in writing first.

Schedule test termsOwner signs off
Your reviewer
Named by the owner, usually a senior project manager
Success criteria
In writing: fields carried, listings matched, unmatched lines raised
Schedule format
The columns each old job's specification asked for
Listing source
The directory prints your team kept for that job
Who decides
Your project manager, with the design team and authority having jurisdiction
Price
A range for running it live, before day one
NDA
Signed before any log moves

// How it's judged

The schedule you submitted next to each draft

Penetration by penetration
Field by field
Across the same 20 to 30 schedulesSchedule you submittedThe AI draft
Barrier type and hourly rating on each lineFilled from your schedulesFilled from your schedules
Penetrating item, material and sizeFilled from your schedulesFilled from your schedules
Annular space or opening size as loggedFilled from your schedulesFilled from your schedules
Listed system number and its directoryFilled from your schedulesFilled from your schedules
F, T, L and W columns where the owner askedFilled from your schedulesFilled from your schedules
Penetrations with no matching listing, held for a personFilled from your schedulesFilled from your schedules
Questions the design team or reviewer raised on the originalFilled from your schedulesFilled from your schedules
Nothing filled in yet. Each cell waits for your own schedules to run.Your project manager marks each row and makes the call.

// After a yes

About 30 days on new field logs

With your reviewer's yes, new logs get the same draft schedule for about 30 days.

Your project manager reviews every line and decides every system before anything is submitted, and unmatched penetrations still go to the design team and the authority having jurisdiction.

Drafts stay side by side with what you would have sent. Any next job carries a separate price.

// Possible next jobs

After schedules, if you want more

Ranked, not promised
One price at a time
  1. 01

    Firestop inspection records

    Installers' logs and the inspector's reports pulled into one closeout draft, with locations that have no record listed.

    Next
  2. 02

    Engineering judgment request packets

    Each unmatched condition written up with its barrier, item, opening size and photos for your project manager to send on.

    Then
  3. 03

    Firestop bid scope letters

    Rated barrier counts and owner requirements read out of a spec book into a draft scope for your estimator.

    After that

// One hard limit

The draft never picks a listed system.

It works on copies of schedules you already finished. It never touches a firestop management application, job cost system or live record, never picks a listed system, never decides that an installation meets a listing, and never signs an inspection or contacts a designer, inspector or maker. Your project manager, with the design team and authority having jurisdiction, decides every system, and a qualified inspector signs every inspection. Nothing on this page is legal, code or engineering advice. Certified payroll is out of scope.

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 formats your owners ask for.

// Questions

Penetration schedule questions

Does the AI pick the listed system?
No. It carries the system your team named, or shows the listings on file whose stated conditions match the log, and your project manager chooses. Whether a system is right for a location rests with your project manager, the design team and the authority having jurisdiction.
What happens when the log has no annular space?
The field stays blank and the line goes on the open list with its location and item. The draft doesn't estimate a measurement from a drawing or a photo, so your crew or project manager fills it in.
We use several makers' systems. Is that a problem?
Put them all in the sample. The draft keeps the maker and directory with each system, and if an owner's specification limits a job to one maker, your reviewer can add that to the success criteria.
Does it search a live listing directory?
No. It reads the prints and files your team kept for those jobs, so each draft is compared with what your project manager had at the time. If a listing has changed since, that sits outside this test.
Can it handle renovations with existing penetrations?
If your logs record them, yes. Existing openings stay separate from new ones in the draft, and any line missing its barrier or item goes on the open list for your project manager.
Rob Eason

Rob Eason, founder

// Book a proof of concept call

Start with a schedule that came back for resubmittal.

A half-hour call with Rob about your company, your role, the owners you work for and about how many penetrations a typical project logs. Field logs, drawings and listings stay in your office 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.