SubPro is the submittal intelligence system.

SubPro streamlines the submittal process from bid to closeout.

See it run on your spec book How it works

Just need a submittal log? Build my log puts the submittal log in your inbox before you can finish section 01.

47444E Manual.pdf Page 138 of 442

Section 033001, Cast-in-Place Concrete

1.03 SUBMITTALS

A. Submittals Package: Submit product data for design mix(es) and materials for concrete specified below at the same time as a package.

B. Submit an Environmental Product Declaration (EPD) from the manufacturer for concrete within this specification section, if available.

138

Submittal log, Tower 28 Rev28 Draft 490 rows

Section	Type	Description	Cites	Status
02 33 13	Other	Subsurface investigation report	p. 96	Draft
03 30 01	Product data	Concrete design mixes and batching plant	p. 138	Draft
03 30 01	Shop drawings	Placing drawings, bar reinforcement	p. 138	Draft

Every row cites its page The page number sits beside each requirement. Review starts at the source.

Your team reviews before delivery Anything that needs further review gets flagged for your call.

We are privacy first Unlike other companies, we keep your data private. Project files are deleted after processing.

The week you already know.

It's Thursday. The bid is due tomorrow at two, and your estimator is 300 pages into a 900-page project manual, pulling out every product it names, because the number is only as good as the list of materials the architect specifies. After award the same book lands on a project engineer, who types each required submittal into a spreadsheet and then goes hunting for the product data behind every one of them.

At closeout, somebody opens a binder and starts the hunt again. This is the reason SubPro exists.

What a submittal intelligence system does

Read the full method

Step 1

Reads the spec book and lists every product

Know every specified product prior to bid. SubPro reads the spec book front to back and puts each specified product on its own row with the page it came from, so the estimate starts from a list rather than a skim.

The project manual open in SubPro at page 265 of 850, Section 07 92 00 Joint Sealants, the installer qualifications requirement highlighted on the page and quoted in the bar above it

Step 2

Turns the list into the submittal log

After award, the same rows become the log: section, type, description, page. Divisions group themselves. Nothing gets typed twice.

The drafted submittal log for The Bridge grouped by CSI division, Division 07 Thermal and Moisture Protection expanded to its 48 rows, each with spec section, type, description and Draft status

Step 3

Builds each submittal package

Product data from the manufacturer database stacks behind your transmittal sheet. One submittal package per row, ready to review and send straight from the app.

A completed submittal cover sheet for Section 09 91 13 Exterior Painting, listing the manufacturer and product

Step 4

Flags what needs eyes on it, tracks the rest to closeout

Unclear language, no material specified, items that need further attention get flagged at the start of the project.

The Cedar Park Renovation log filtered to rows that need a check, flag chips reading Possible duplicate and Learned pattern beside the rows a person has to rule on

See the work first.

Real screens from sample projects, run end to end. Judge the output before you judge us.

See everything that ships

The T2232-01 project manual open at page 348, Section 12 24 13 Roller Window Shades, the maintenance data requirement highlighted and quoted above the page — **The requirement, on its page**Open any row and the spec page opens with it, the requirement highlighted.

Row 07 11 13-078 for bituminous dampproofing opened in SubPro, four manufacturers listed against it with the matched product and source page 255 — **Product data, matched**Manufacturer documents from the library, matched to the row and ready to stack behind the cover sheet.

A finished five-page submittal package for roller window shades open in the PDF viewer, the transmittal cover on page one and the manufacturer's pages in the thumbnail rail — **The finished submittal package**Cover sheet, transmittal, and product data in one PDF, named and numbered.

How your submittal workflow changes

The manual week

Read and search the spec book manuallyOnce at bid time for the products, once after award for the submittals. Several evenings each. One missed row surfaces months later, usually from the architect.
Track down every cut sheetManufacturer sites, shared drives, merged PDFs, corrected page order. Repeated for every item on the log.
Rebuild the record at closeoutO&Ms and warranties become a second project, assembled under deadline at the end of the job.

With SubPro

A cited list, then a cited logThe product list prior to bid day and the log the week of award, the source page on every row, so your team starts at review.
Submittal packages arrive assembledMatched product data, SDS sheets, manufacturer shop drawings, warranties, O&M manuals behind a cover sheet on your transmittal sheet. Gaps are flagged so you can see them.
Closeout builds as the job runsStatuses, revisions, and transmittals accumulate row by row and are ready at turnover.

From the founder

I spent twenty years running construction projects, and on every one of them the submittal process was the part I dreaded. I have sat on jobs where it took months. Not because the work was hard, but because it never ended: search the spec book, find the products, build the submittal packages one at a time, chase every one, then do most of it again at closeout.

I kept waiting for somebody to fix it. Nobody did. So I built the system I wanted on those jobs, and I built it to show its work, because I would not have trusted a black box either.

If you run submittals, I would like to show it to you on one of your spec books.

John Devitt, founder Connect with John on LinkedIn

What SubPro does not do

The limits, stated plainly, so the fit call can be short.

It does not replace your team's review

SubPro drafts and organizes. Your team confirms each requirement, decides substitutions, and owns the final log. Flagged rows exist to be read by a person, and they are.

It does not promise a perfect extraction

Spec books contradict themselves, and some requirements hide in a note. That is why every row carries its page: a reviewer can confirm any row against the source in seconds.

It does not keep your documents

Your spec book arrives, the deliverables leave, and the working copies are wiped. Nothing you send trains a model. The full policy is on the data handling page.

It does not change what the GC receives

The output is the same product data, cover sheet, and transmittal you send today, as PDF and Excel files that drop into any project platform. Nothing about your process has to change.

It does not publish a price list

Price depends on how many projects you run, so we quote per company. The pricing page explains what drives the quote and what every subscription includes.

Who it is built for

A fit

Trade contractors and general contractors with spec-heavy scopes: doors and hardware, finishes, HVAC, electrical, plumbing, and any contractor that is over giving weeks away to submittals.
Teams whose PM would rather review submittals than transcribe the project manual.
Shops running several projects a year that want the product list before bid day and the submittal packages started the week of award.

Not a fit

Scopes with a handful of submittals that a coordinator can list in an afternoon.
Teams looking for a tracking dashboard rather than the drafted work itself.
Anyone who finds joy in manually building submittal logs and chasing down each submittal document.

Send us one spec book.

One fit call and one of your real spec books. You will see the product list, the drafted log, and a finished submittal package before you decide anything.

Book a fit call Build my log instead