Transmittal cover
Every package leads with a cover that names the project, the section, and the item it satisfies.
Submittals automated
Submittals automated, from spec book to finished package.
Not a tracker with empty rows waiting for you to do the real work. SubPro drafts the log from your spec, matches manufacturer literature to every row, and binds each one into a package PDF your reviewer opens, checks, and sends.
The output is a package, not a promise.
What lands in your hands after a run: a transmittal-covered PDF per submittal, built from the log SubPro drafted.
A real assembled package
79 pages of manufacturer documentation, ordered and bound. Nobody merged those PDFs by hand.
The build
Three steps between a spec book and a submittal.
Each step feeds the next, and each one leaves a trail you can audit.
Spec to rows
SubPro reads the divisions and drafts the log: one row per required submittal, each citing the spec page it came from.
Rows to documents
Each row is matched against a library of manufacturer literature: data sheets, safety data sheets, installation instructions.
Documents to package
Matched documents stack behind a transmittal cover and bind into one PDF per submittal, ready for review.
What automated means here
The grind is automated. The judgment is not.
On most jobs the submittal process is a coordinator, a spec book, and several weeks of copying requirements into a spreadsheet and hunting cut sheets on manufacturer websites. None of that work requires judgment. All of it punishes a lapse in attention, usually three months later when the missing sheen schedule turns up at closeout.
SubPro takes exactly that slice: the reading, the transcribing, the hunting, the merging. What it refuses to take is the decision. Every drafted row shows the spec page it came from, every matched document names its manufacturer and product, and every package waits for a person to look before anything leaves. Your reviewer stops being a document mover and goes back to being a reviewer.
That boundary is the design, not a limitation. A submittal is a contractual representation to the design team. Software that fires those off unread is not automation, it is liability at scale.
Worked example
Section 08 71 00, door hardware, start to finish.
Door hardware is a submittal-heavy section with real consequences for getting it wrong. Here is the automated pass.
Log rows drafted
Product data, hardware schedule, keying schedule, and warranty rows appear on the log, each citing its paragraph in 08 71 00.
Literature matched
Data sheets for the specified hinges, closers, and exit devices attach to their rows from the manufacturer library.
Decisions flagged
The keying schedule is flagged as an owner decision. No software should guess who gets a master key.
Packages bound
Each row's documents bind behind a cover into a PDF, previewed before anything moves toward the architect.
Submittals automated FAQ
What does submittals automated actually mean?
It means the assembly work is done by software and the judgment stays with people. SubPro reads the spec book, drafts the log, matches manufacturer literature to each row, and binds the result into package PDFs. Your team reviews, decides, and sends.
Does SubPro send the submittal for me?
No. SubPro builds the package and hands it to your team. A person reviews every package before it goes to the architect, because approval is a decision, not a file operation.
Where do the product documents come from?
From a maintained library of manufacturer product literature: data sheets, safety data sheets, and installation instructions, matched to the products the spec names. You can browse it yourself in the manufacturer library.
What happens when no document matches a row?
The row says so. SubPro flags the gap for a person to fill instead of padding the package to look complete. An honest hole beats a confident blank page.
Start with the log
The packages begin as rows.
Everything on this page starts from a drafted log. The Log Build produces one from your spec book.
Related SubPro pages
Go deeper on any step.
Each stage of the automated build has its own page with screenshots and specifics.
Submittal package software
How the package itself gets assembled behind its cover.
Submittal review software
The review pass: source checks, flags, and the human sign-off.
Submittal handoff output
The complete file inventory a finished run delivers.