SubPro Book a fit call

Submittal software for contractors who need a reviewable first handoff.

SubPro reads the spec book, drafts the cited log, and gathers the package evidence behind each row. What lands on the reviewer's desk is checkable on arrival.

Book a fit call See the work
The cited pageSection 033001, page 138 of 442
The project manual open in SubPro at page 138 of 442, Section 033001 Cast-in-Place Concrete, with the submittals paragraph highlighted and quoted above the page as the source text for one row

Cut the week between award and first submittal

On a commercial job the project manual runs hundreds of pages across dozens of sections. Someone reads it line by line and types rows. Call it 30 pages an hour and 40 rows a day between phone calls. An 850-page manual with 500 requirements is a week of one person's full attention.

One skipped paragraph on page 214 becomes a missed submittal that surfaces after the material is on order. SubPro takes the reading, the drafting, and the evidence gathering. The judgment stays with your team.

Two tabbed project manual binders open on a pickup tailgate beside a radio and a hi-vis vest, a dozer grading the pad behind them at dusk
The project manual shows up as two binders on a tailgate. The first week of the job is somebody reading them.

See what changes on your job

The week, returned

The arithmetic of hand-building against reviewing a draft, run honestly.

Follow one workflow from spec book to handoff

  1. Reads the spec bookDrafts the first log rows from every section, page numbers attached. Detail on submittal log automation.
  2. Builds a reviewable logYour team edits the cited draft, then exports it to XLSX. Detail on submittal log software.
  3. Keeps review in the loopFlags and page references stay on each row for the PE or PM. Detail on submittal review software.
  4. Assembles the submittal packageProduct data stacks behind a cover sheet instead of a bare list. Detail on submittal package software.
  5. Hands it off cleanEditable logs, schedules, and PDF submittal packages with a transmittal. Detail on construction transmittal software.
  6. Shows what shipsWhich files you receive and how each is structured. Detail on the submittal handoff output.

Run one section start to finish

Take Section 07 92 00 Joint Sealants. It appears on almost every commercial job and hides more obligations than its page count suggests.

  1. Read the section: product data for each sealant, color samples, applicator qualifications, safety data sheets.
  2. Draft the rows, each with its section number, its type, and the page it came from.
  3. Flag the color sample row as a call the team owns, since the architect selects from the manufacturer's range.
  4. Attach the sealant product data and safety data sheets the library holds.
  5. Export the 07 92 00 rows into the XLSX log beside every other section, PDF submittal packages ready.
Product data, matchedWhat the library found for each row
Drafted Section 03 30 01 rows in SubPro, each with its submittal type, the matched manufacturers and products, a Draft status, and a Create Submittal button

Treat sitework the same way

Section 32 31 13 Chain Link Fences and Gates gets ignored until the owner asks about fabric gauge in writing. The draft carries product data for fabric, framework, and gates, plus shop drawings for gate hardware. The galvanizing certificate rides in a reference standard, not the submittals list, so its row arrives flagged.

A construction field office at night: a workstation on a plan table beside an open steel case of tabbed bid folders and rolled drawings, a hard hat and vest on the wall
Section 32 31 13 gets read at night, after the phone stops. A draft that read the whole manual already has it logged.

Keep the whole job on one screen

The log, the evidence, the sent record, and the spec book usually live in four places. In SubPro a project is one screen: rows, statuses, flagged decisions, matched documents, and the source page behind each. Checking the work is a glance.

All projectsDraft, review, and approved counts per job
The SubPro projects screen listing ten sample projects with draft, review, and approved counts for each

Judge it on your own spec book

No staged demo on a groomed sample. A short fit call, then a sample build on one of your real project manuals.

  • The drafted log, grouped by division, every row cited.
  • The assembled submittal packages for the rows the library could match.
  • The flagged rows, with the page behind each one.
One finished submittal packageTransmittal cover first, product data behind it
A generated submittal transmittal cover for Section 10 28 14 Electric Hand Dryers, with the manufacturer's product pages queued behind it in the thumbnail rail

Push on the hard questions

On accuracy

Software that reads a project manual will sometimes read one wrong. So rows cite pages, uncertain rows arrive flagged, and a person reviews before it becomes the log.

On the tools you already run

Most construction software manages submittals somebody already made. Making them is the product here, and the exports feed whatever portal the GC mandates.

On the spec book itself

It is read for your job, then deleted, with no training use. The data handling page spells out the mechanics.

Stay on the job after the log is built

Building the log used to be where tools like this clocked out. Here each submittal keeps its review status, its revision stack, and every dated transmittal through the closeout binder, and your copy stays home even when a GC requires a portal.

One row, expandedApprove, reject, edit, or open the source PDF
A submittal row expanded in SubPro showing its type, manufacturers, products, source page, and the approve, reject, edit, and open source PDF controls

Submittal software FAQ

What is submittal software?

Software that manages the submittals a project manual requires. SubPro reads the spec book, drafts a cited log, gathers product data where the library has it, and keeps status, revisions, and transmittal history on every item to closeout.

How is SubPro different from a submittal tracking tool?

A tracker manages submittals somebody else made. SubPro makes them, then tracks its own work. Teams under a GC mandate still export into the required portal, and they arrive with the work already done.

Does SubPro submit or approve submittals automatically?

No. It prepares a reviewable first pass with spec-page references and review flags. A person on your team reads the draft and decides what is ready before anything is submitted. The review stays human.

How do you evaluate submittal software?

Hand it a real project manual and read what comes back. Count the rows against the sections you know are in there, click from a row to its cited page, and check what it did with a substitution.

Send us one spec book.

One fit call, one real project manual, and a drafted log with a finished submittal package to judge before any decision.

Book a fit call Build my log instead