Submittal automation for construction teams

Most submittal tools build you a list. We build the submittals.

SubPro turns your spec book into a review-ready submittal log, assembles supporting documentation where available, and keeps the handoff clean for the tools you already use.

Ask questions across the full spec book or the generated log, review the flags, then export an editable package set with human review still in the loop.

40 hoursmanual log and package assembly basis

2 to 4 hoursSubPro assisted review target

Pilots openfit calls available now

Actual timing depends on spec quality, project scope, available package matches, and your team's review process.

Book a pilot fit call See how it works

Submittal Log + Package Assembly Sample

1. Ingest 2. Extract 3. Review 4. Export

Try: Which rows need review before export?

CSI Section	Submittal	Requirement	Ref.	Review
03 30 00	Concrete Mix Design	Submit concrete mix designs with compressive strength, slump, and admixture data.	2.3.A	Ready
04 20 00	Masonry Units	Submit masonry unit product data, dimensions, colors, and samples.	2.2.A	Check
07 20 00	Thermal Insulation	Submit insulation product data with R-value, thickness, and attachment method.	2.4.A	Ready
08 41 13	Aluminum Storefront System	Submit storefront shop drawings, anchorage details, and finish data.	2.3.A	Flagged
09 90 00	Coating System	Submit coating system product data, surface preparation, and application requirements.	2.1.B	Check
26 05 00	Panelboards	Submit panelboard schedules, product data, and short-circuit ratings.	2.5.A	Review

203 sample rows surfaced 19 sample rows flagged Export XLSX register / Sample handoff Book a pilot fit call

Synthetic sample. Real output depends on the source documents, available package matches, and your team's review. Flagged rows point your team to items that need a decision before handoff.

How it works

One spec book becomes a reviewable log, assembled packages, chat context, and a clean export path.

Turn one spec book into a reviewable submittal log with source references.
Automatically assemble supporting documentation where matches are available.
Chat with the full spec book or the generated submittal log, then export clean to Excel or your internal handoff.

1. Spec bookDrop in your spec bookStart with the project documents your team already has

2. Build log

03 30 00 Concrete

07 92 00 Sealants

08 41 13 Entrances

3. Assemble packages

Product data

SDS

Shop drawings

4. Review flags

Concrete Mix Design High

Coating System Med

Panelboards Low

5. Chat with spec + log

Ask the full spec book

Ask the submittal log

Find buried requirements

6. Export cleanSubmittal Log.xlsxReady for Excel or internal handoff

Sample output

The output stays inspectable, source-linked, and ready for review.

Download example Excel log

!Requirement risk

Vague spec language, missing deliverables, and rows that need a PM or PE call stay flagged.

?Source proof

Every row keeps source page context so the package is easier to verify before handoff.

↔Package matching

Product data, SDS, and shop drawing matches stay visible with anything uncertain marked for review.

◷XLSX handoff

The output stays editable so the team can clean it before Excel or its internal process.

Why SubPro

What makes SubPro different

Most tools stop at the list. SubPro is built for the work that comes next: assembled documentation, source proof, chat context, and handoff.

We assemble, not just list.

Competitors generate the submittal list; your team still hunts down the documents. SubPro pairs the log with available supporting documentation so the handoff starts closer to review.

Show your work.

Every line traces back to source context and keeps review flags visible, so your team can verify quickly instead of blind-trust.

Chat with your spec book and log.

Ask the full spec book for buried requirements or ask the submittal log about rows, flags, references, and package context.

Complements your stack.

Hands off to Excel, email, or your internal workflow. SubPro is not another platform to adopt.

Document control

Built for project documents that need control.

SubPro does not store your spec PDFs as another document repository. The workflow is process-and-release: prepare the log, assemble packages, review the evidence, and release the handoff.
Output stays in your local project folder or approved handoff location.
Data-handling requirements are confirmed before real project work.

Local Project Folder

Specs / Project Specifications.pdf

SubPro Output / Submittal Log.xlsx

Audit Log.json

✓

Process-and-release workflow confirmed before real project work.

Pilots open

Pilots are currently open.

SubPro is speaking with construction teams that want to turn spec-heavy submittal work into a cleaner, source-linked workflow. Reach out to schedule a call and talk through fit.

Current availability Pilots open

Reach out to schedule a call. We will talk through your workflow, spec volume, data-handling needs, and whether SubPro is a fit.

Best next step Schedule a call

Bring a spec-heavy workflow you want to improve. We can discuss the right sample, review process, and handoff expectations before project files are used.

How to reach us Book or email

Book a pilot fit call or email pilots@sub-pro-ai.com. We will help you decide whether SubPro is a practical fit for the workflow.

Get started

Schedule a pilot fit call, then decide whether SubPro is a fit.

Pilots are currently open. Reach out to schedule a call; we will talk through your specs, workflow, data handling, and the right next step.

Commercial contractors

Build a cleaner log and assembled packages before the project team imports or manages them downstream.

Specialty contractors

Turn PDF spec review into package-ready submittals with clear review flags.

PMs and PEs

Cut document hunting, keep source and context notes, and review flagged rows before handoff.

Document controllers

Export an editable XLSX register and package set when the team needs it.

Book a 15-minute fit call

FAQ

Frequently asked questions

Answers for the pilot fit call. SubPro stays focused on building the log, assembling packages, making the spec book and log easier to query, and handing off to your existing workflow.

How is this different from other submittal tools?

They help generate lists, route documents, or manage workflow. SubPro focuses on the handoff your team needs before downstream tools: a reviewable log, supporting documentation where available, clear flags, and a clean export.

What do I see before a pilot?

The first step is a fit call and sample build on one of your real specs: a reviewable submittal log, assembled packages where matches are available, review flags, spec-book chat context, submittal-log chat context, and a short review call. Pilot specs may range from roughly 200 to 1,500+ pages.

What about my data?

We confirm data-handling requirements before real project files are used. Synthetic or anonymized material can be used first, and the workflow remains process-and-release rather than another document repository.

Is my spec book and project data safe with SubPro?

All user data, including spec books, is used only to build your SubPro output, then released and deleted after processing. SubPro does not retain user data, and user data is never used for AI training or any other use. Data is sent over encrypted HTTPS/TLS connections, and a mutual NDA is available before you send project files.

Are pilots currently open?

Pilots are currently open. Reach out to schedule a call so we can talk through your workflow, spec volume, data-handling needs, and next step.

How long does a spec take?

For current-scale specs, expect about 2 to 5 minutes of automated processing per spec, with total turnaround typically 2 to 4 hours including your team's review. Timing varies with spec book PDF size, spec quality, available package matches, and review depth.

How do review flags work?

Rows that need a decision stay visible with source context, so your team can check the exact requirement before package handoff.

Who reviews the output?

Your team does. SubPro prepares the log and packages; it does not remove PM, PE, or document-control review.

What is the handoff format?

The handoff centers on an editable XLSX register and assembled package files so the output can fit existing review and import workflows.