Grounded review prep
Move through the spec book faster while the exact page stays close enough for a reviewer to check the work.
AI submittal software that keeps construction review in the loop.
Anyone can generate a log. A reviewer asks where each row came from. SubPro keeps source checks and human review in the workflow: every drafted row carries its spec page, open questions are flagged, and nothing goes out until a person says so.
Inspect the output before you trust it
Built to be inspected
Rows, flags, and submittal packages sit in the open before your team sends anything onward.
Data handling first
Pilots confirm scope and handling terms before real work begins. The public site chat takes no files.
Split the reading from the deciding
The useful version of this software is narrow on purpose. SubPro reads the specification sections and drafts the first-pass rows with the source page attached to each one. It is not asked to approve a submittal, judge a substitution, or decide conformance. Those are human calls, and they stay human.
That boundary is what makes the output trustworthy. Because every row keeps its source reference, a reviewer confirms the basis in a click, and the flags point at the rows that most need a look. Perfect extraction is not promised. A fast, checkable first pass is.
Walk one lighting section through review
SubPro drafts the rows
Section 26 51 00 Interior Lighting: product data for luminaires, drivers, and controls becomes draft rows, each linked to the page it came from.
SubPro flags the questions
Where a fixture allows an equal or a substitution, the row is flagged for a decision rather than assumed.
The reviewer confirms
A PE or PM opens the source page, confirms the requirement, and corrects anything the draft got wrong.
The team approves the handoff
Only after that review do the 26 51 00 rows move into the export. Nothing approves itself.
Compare manual prep, a general chatbot, and SubPro
| The work | Manual prep | General chatbot | SubPro |
|---|---|---|---|
| Reading the spec book | Weeks of page-turning, section by section | Reads what you paste, loses the page numbers | Reads every division and keeps the page behind each row |
| Evidence behind a row | Whatever the coordinator remembered to note | Prose, not citations | One click from any row to its page |
| Rows the tool was unsure about | Invisible until a reviewer catches them | Stated as flatly as everything else | Flagged for a person, never assumed |
| Supporting documents | Hunted down one manufacturer site at a time | Links that may not resolve | Matched from a maintained library |
| The final call | Human | Unclear | Human, every time, by design |
Back every draft with real documents
More than 11,000 documents
Product data, safety data sheets, and installation guides, collected from manufacturer sources and searchable in the document library.
More than 800 manufacturers
Indexed with their divisions and products in the manufacturer library, so a drafted row points at real paperwork.
Provenance on record
Library entries keep their source, and takedown requests are honored through the published document rights process.
Source checks and review FAQ
How does SubPro draft the rows?
It reads the project manual section by section, finds each submittals article, and drafts a row per required item with the source page attached. The reading is fast. The final call is not delegated: review flags and a person's approval stay in the workflow.
Can the software produce final submittals without review?
No. SubPro prepares review-ready output, not finished submittals. Your team verifies requirements, ownership, substitutions, conformance, and the final submittal package decisions. Perfect extraction is not promised, which is why the page behind every row stays visible.
Is my project data used for training?
No. The project manual is processed for the job, then deleted, and is never used for training. Data handling terms are confirmed before any real project work begins.
Does SubPro accept public website file uploads?
No. Project PDFs and files cannot be sent through the public website chat. Real project work happens after a pilot fit call where data handling is confirmed in writing.
Related reading
Submittal log automation
The drafting engine: spec sections in, cited log rows out.
Submittal register automation
Registers where every row keeps its page number.
Submittals automated
The whole build, from spec book to bound submittal package PDFs.
See the evidence on your own rows.
One project manual, one drafted log, and a citation to click on every row. The Log Build ships either the drafted log with its flags or every row read by a person first.