SubPro
Method Spec book to handoff
Get started
The method

How SubPro builds a submittal pass.

From spec-book ingest to editable handoff, here is the actual method: draft the log, assemble packages, keep source context and review flags visible, then release the handoff and delete the processing data. Nothing about it asks your team to trust a black box.

Talk through your workflow Read the data-handling summary
Five steps

Spec book in, reviewable handoff out.

The same five steps run on every project. Each one keeps the source context attached so the team can check the work.

1. Ingest the spec book

The project specifications are read section by section, processed for the job under a process-and-release workflow.

2. Draft the log

Each required submittal becomes a row with its CSI section, type, responsible party, and a reference back to the source page.

3. Assemble packages

Where product data is available, SubPro assembles the supporting evidence for each package behind a cover.

4. Flag for review

Rows that need a human decision are flagged and kept visible with their source context, so nothing important hides in the list.

5. Release the handoff

The reviewed log and packages export as editable XLSX and PDF to your approved location, and the processing data is deleted.

Why it is built this way

Every row can be traced, and nothing is kept.

Two design choices run through the whole method. First, every draft row carries the specification page it came from, so a reviewer can confirm the basis instead of trusting a list. That is what turns a first pass into something a PE will actually sign off on. Second, SubPro does not hold onto your documents. The workflow is process-and-release: prepare the log, assemble the packages, review the evidence, release the handoff to your approved location, and delete the submitted processing data.

Output lands in your local project folder or an approved handoff location, alongside an audit log of what was produced. SubPro is not a cloud document repository, and your specifications are never used for AI training or model improvement. Data-handling requirements are confirmed before any real project files are used.

How SubPro works FAQ

Does SubPro keep my spec PDFs after the job?

No. The workflow is process-and-release: SubPro prepares the log and packages, releases the handoff to your approved location, and deletes the submitted processing data. It is not a document repository.

How can a reviewer trust the draft?

Every row keeps a reference to the source specification page, so a reviewer can open the page and confirm the requirement rather than accept the row on faith. Rows needing a decision are flagged.

What files come out at the end?

An editable XLSX submittal log and schedule, plus PDF package support where evidence is available, delivered to your approved location with an audit log. See submittal handoff output.

Is human review still required?

Yes. SubPro drafts and organizes; your team confirms requirements, decides substitutions, and owns the final log. SubPro does not promise perfect extraction.

Related SubPro pages

The method above maps to these pages.