Gather the product data
Painting is heavy on data sheets. For each specified coating system, the manufacturer's data sheet is pulled from the catalog and set behind the cover for that row.
A log row says a submittal is owed. The package is what actually satisfies it. SubPro stacks the product data behind a cover sheet, one submittal package per row.
Painting is heavy on data sheets. For each specified coating system, the manufacturer's data sheet is pulled from the catalog and set behind the cover for that row.
The SDS for each product rides in the same PDF where the catalog has it. The conformance evidence the section asks for travels with the product data.
The color and sample row is an owner or architect decision. It is flagged as one and left open, instead of guessed at and buried in the PDF.
The assembled 09 91 00 PDF opens for a read-through: cover, data sheets, safety sheets, in order. A reviewer checks it before the transmittal goes anywhere.
Anyone who has built submittals by hand knows the loop. Find the product page on the manufacturer's site, download the SDS, chase the warranty letter, format a cover, merge the PDFs, fix the page order. Then the next item. An afternoon per submittal, hundreds of items per job, done by the most careful person in the office.
SubPro runs that loop for you. For each log row it pulls the matching manufacturer documents from its catalog of product literature. It sets them behind a cover sheet that already knows the project, section, and item, and binds the result into one PDF. Assembly stops being an afternoon and becomes a selection: this product, yes; this substitution, decide.
When the catalog has no match for a row, the row says so. A person supplies the document, the submittal package closes, and nothing leaves looking complete when it is not. What a package contains depends on the product and the project. SubPro assembles what it can find and flags what it cannot.
Package assembly needs rows to assemble against. A Log Build drafts them from your project manual, each row citing its page.
It turns a log row into a file the GC can open. The product data the spec section calls for is stacked behind a cover sheet and bound into one PDF per submittal.
Take Section 09 91 13 Interior Painting. The section calls for product data on every coating. That submittal package is the manufacturer's data sheet for the specified paint, its safety data sheet, and the sheen and color documentation. A cover sheet names the project, the section, and the item.
SubPro places the product pages behind a cover sheet tied to the log row, in reading order. The reviewer sees the requirement and its evidence together and previews the PDF before it goes to the GC.
No. What a submittal package contains depends on the product and the project documents. SubPro assembles what the catalog holds and keeps a missing or unclear document visible for review instead of hiding the gap inside a finished-looking PDF.
The full inventory of files a run delivers, PDF and XLSX, and how each one is named.
Putting the cover on it: how the transmittal is written from the package it fronts.
The hub that ties the submittal package back to the log and the closeout record.
Book one fit call and send one of your project manuals. You open a finished submittal package from your own job before committing to a pilot.