SubPro Book a fit call

Submittals automated, from spec book to finished package.

Not a tracker with empty rows. SubPro drafts the log from the project manual, matches manufacturer literature to each row, binds one PDF per submittal, and keeps the record through closeout.

Book a fit call Read the full method
Inside one bound PDFCover sheet first, manufacturer pages behind it
Manufacturer product data pages stacked behind a submittal cover sheet in the assembled PDF

Look at a package nobody assembled by hand

A hand holding a thick clear-covered submittal package by its edge, the weight bending it, an open box trailer stacked with more of them out of focus behind
Seventy-nine pages has a weight to it. Nobody merged those PDFs by hand.
A site office at night with a wall clock, a desk lamp over a laptop and a row of binders, one person silhouetted at the dark window with a mug
The old way to get seventy-nine pages behind one cover was a night like this one.

Follow one job from award to closeout

  1. Award: the manual becomes rowsThe week of award, SubPro reads the divisions in your scope and drafts the log. One row per required submittal, each citing the page it came from. Nobody types.
  2. Build: rows become bound PDFsEach row is matched against the manufacturer library. The data sheets, safety data sheets, and installation instructions stack behind a cover and bind into one PDF per submittal.
  3. Review: flags wait for a personAn or equal, an owner selection, a row with no matching document. Each is flagged with the page behind it, and your reviewer clears it before the transmittal is written.
  4. Closeout: the record is builtEvery send date, stamp action, and resubmittal lands on the row it belongs to. Turnover opens on a record, not on a reconstruction from email.

Run Section 08 71 00 start to finish

Door hardware is submittal-heavy, and the cost of a wrong hardware set shows up at the frame. Here is the automated pass on one section, and where it stops.

Row drafted Drafted from Matched from the library Who decides
Product data, hinges, closers, exit devices The product data paragraph in Section 08 71 00, cited by page Data sheets for the specified hinges, closers, and exit devices Your reviewer confirms the match and marks the row ready
Hardware schedule The schedule requirement in the same section Nothing to match. The schedule is yours to produce Your team attaches it; the row stays open until then
Keying schedule The keying paragraph, cited by page Not matched on purpose Flagged as an owner decision. Nobody guesses who holds a master key
Warranty The warranty paragraph, cited by page The manufacturer's warranty document where the library holds it Your reviewer checks the term against the section and binds it
A commercial steel door slab laid across sawhorses in an unfinished corridor, an installer's hands fitting a mortise lockset, a door closer and stainless hinges laid out beside it
Section 08 71 00 on the bench: lockset, closer, hinges. The library already holds the cut sheet for each.
A clear tray of brass key cylinders and keys on a job box in an unfinished corridor, a clipboard hanging on the door frame beside it, door openings running down the hall
The keying schedule is the one door hardware row that stays flagged. Someone has to decide who gets which key.

Automate the grind, not the judgment

On most jobs the submittal process is a coordinator, a project manual, and several weeks of copying requirements into a spreadsheet. Then come the weeks of hunting cut sheets on manufacturer websites. None of that work needs 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 does not take is the decision. Every drafted row shows the page it came from, and every matched document names its manufacturer and product. Every PDF waits for a person to read it before anything leaves. Your reviewer stops moving documents and goes back to reviewing.

That boundary is the design. A submittal is a representation to the design team under the contract. Software that sends those unread is not saving anyone time; it is moving the risk to the day the architect reads it. If you want the first step on your own document, a Log Build drafts the rows from your project manual.

A project manager's hand signing the bottom of a printed sheet on a plan table, a white hard hat and a phone beside it, a hi-vis vest over the chair by the window
The grind is automated. The signature is not.

Submittals automated FAQ

What does submittals automated actually mean?

The assembly is done by software and the judgment stays with people. SubPro reads the project manual, drafts the log, matches manufacturer literature to each row, and binds one PDF per submittal. Your team reviews, decides, and sends.

Does SubPro send the submittal for me?

No. SubPro builds the submittal package and hands it to your team. A person reads every one before it goes to the architect, because a submittal is a representation to the design team, not a file operation.

Where do the product documents come from?

From a maintained library of manufacturer literature: data sheets, safety data sheets, and installation instructions, matched to the products the spec section 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 submittal package to look complete. A visible gap is worth more than a page that only looks finished.

Send us one spec book.

Everything on this page starts from a drafted log. Send one project manual and watch the first section go from rows to a bound PDF.

Book a fit call Build my log instead