SubPro FAQs

SubPro is the submittal intelligence system. It reads your spec book, lists every specified product on bid day, builds the submittal log and each submittal package after award, sends and tracks them, and shows the page every row came from. The output arrives as files your team can edit.

Trade contractors and general contractors with spec-heavy commercial scopes. The people who use it day to day are project managers, project engineers, preconstruction staff, and document control.

The whole chain, starting with the first pass. Reading the spec book at bid time for the products, reading it again after award for the submittals, transcribing rows, finding the source page again: that is coordinator time a spreadsheet never gives back. SubPro does that work and hands your team a log to inspect before tracking starts.

PDF submittal packages, the submittal log in Excel, and the submittal schedule in Excel, with a submit-by date on every row and a warning before any of them is late. Chat answers questions from the spec book and the drafted log. Every row keeps its source page and its review flags.

Yes. Chat reads the spec book and the drafted log, and each answer names the page it came from, so a reviewer goes straight to the source.

It builds the log and the submittal packages, and it tracks them too. Each submittal carries a status, its revision history, and a record of what was transmitted and when. If the GC mandates its own system, the editable exports feed it.

Statuses, revisions, and transmittals are recorded as the work happens. At turnover the closeout record already exists. Nobody rebuilds it from old emails.

No. SubPro prepares reviewable output and keeps the spec page behind every row in view. Your team still confirms requirements, responsibility, substitutions, conformance, and the final call on each submittal package.

Teams use the terms differently. In SubPro, both mean the structured list of required submittals that your team reviews, cleans up, assigns, and exports for handoff.

A 15-minute call that checks project type, spec book size, timing, current workflow, expected output, and data-handling needs before any production file work begins.

Yes. Every pilot starts with one spec book, so both sides can judge the output, the timing, and the fit before anything scales up.

The project type, an approximate page count for the spec book, your trade focus, the target deadline, the tools you use today, and any NDA, transfer method, or file retention requirements.

Projects with incomplete project specifications and project manuals, unclear ownership, unusual contract requirements, or strict data-handling needs may need additional review before SubPro work begins.

For the reading. SubPro works through the project manual, drafts the rows, and answers questions about the spec book. People make the calls. Every drafted row cites its source page so your team checks the work instead of trusting it.

No. The spec book is read to build your deliverables, deleted when the job closes, and kept out of AI training entirely.

No. The public website and its chat are not a production file-upload portal. How project files reach SubPro is confirmed before real work begins.

No. SubPro prepares review-ready output. Contractors still verify requirements, ownership, substitutions, conformance, package decisions, and their professional review obligations.

SubPro hands off PDF submittal packages plus the submittal schedule and the submittal log in Excel, all editable. Exact deliverables are confirmed before work begins.

Yes. The handoff is editable Excel files and PDFs, so whatever your team uses for tracking and approvals picks up where SubPro leaves off. Nothing to rip out.

From a library of manufacturer product documents that SubPro maintains: cut sheets, product data, and safety data sheets. Submittal packages assemble from the matching documents, your team reviews each match, and the same library is free to search under Submittal Documents.

No. SubPro quotes per shop after seeing a project manual. Scope, timing, deliverables, data handling, and fees are confirmed in writing before work begins. The pricing page explains what drives a quote.

No. Send one spec book through Build my log and a drafted log comes back for your team to review. Start with the output and decide from there.

Book a fit call, or send one spec book through Build my log and judge the drafted output directly. Either way, bring the project type, spec book size, current workflow, deadline, and file-handling expectations.