Questions, answered.

A construction submittal is the proof you send for review that what you plan to install matches what the design team specified, before it goes in the wall. It's usually product data, a shop drawing, a physical sample, a certificate or a test report, each one tied to a spec section.

Each section's submittals article in the spec book says what form it wants. Section 08 71 00 Door Hardware asks for product data and a hardware schedule. Section 07 92 00 Joint Sealants asks for product data and color samples. The architect reviews the submittal and sends it back with a stamp action, and that decides whether the item can be released for fabrication.

You go section by section. Open each spec section, find its submittals article and write down every required item with its type, who owes it and the page it's on, one row per requirement. SubPro drafts that first pass from the project manual, so your team is reviewing rows instead of typing them.

The reading is what takes the time. A thick project manual has several hundred requirements in it, and the ones that get missed are usually buried in Part 3 or in a referenced standard. Having the source page on each row is what lets you check the log later. See submittal log automation, or start from the free log template.

The first pass can. SubPro reads the spec book, drafts each log row with its source page and flags the rows that need a decision. Then somebody on your team reviews the log and confirms the rows. SubPro does the typing, and your team still makes the judgment calls.

A drafted log is only worth it if you can check it quickly. That's why each row shows the page it came from, so the reviewer can open it, confirm the requirement and move on. Rows with an or equal clause, an owner selection or a note that can be read two ways get flagged for someone to decide, so SubPro doesn't guess.

Mostly just the word. Register is the Division 01 term for the complete list of submittals the contract requires, tied to the spec book. Log is what most field teams call the working sheet they track status on day to day. Teams that keep both use the register as the source and the log to track.

SubPro builds one list and exports it both ways, the register with the spec pages and the log with status, revision and dates. Whatever your GC calls it, the columns are the same. See submittal register automation.

The submittal is what gets reviewed, like the product data, the shop drawing or the sample. The transmittal is the cover that sends it and records who sent what, for which project and section, and on what date. A transmittal shows it was delivered, but it doesn't say anything about the product inside.

When SubPro builds a submittal package, the transmittal and cover sheet go in front and the product data goes behind them, so the GC gets one numbered PDF. See construction transmittal software.

One submittal package covers one spec requirement. It has a cover sheet with the project, the spec section and the item, a transmittal, and whatever the section asks for, like the product data sheet, the safety data sheet if it's a chemical product, and a shop drawing or sample when the section calls for one.

If a required document is missing, the submittal package says so right on it, so you're not looking at a table of contents that only looks complete. See submittal package software, or compare the manual build.

SubPro is the submittal intelligence system. It reads your spec book and the drawings, lists every product the job calls for before bid day, and after award builds the submittal log and the submittal packages. Each submittal then lives on one record, from the requirement in the spec book through review and revisions to closeout, with the source page on every row.

Trade contractors whose scopes have a lot of submittals, and general contractors who own the log for a whole building. Inside those companies it's the project manager, the project engineer, preconstruction and document control, because they're the ones the spec book lands on the week of award.

The usual scopes are openings and hardware in Division 08, finishes in Division 09, mechanical in Division 23 and electrical in Division 26. If your shop only has a few submittals per job it's not a fit, because a coordinator can list those in an afternoon.

Submittals get carried by hand between too many places: the spec book, the drawings, a spreadsheet, a folder of PDFs and somebody's inbox. Every handoff is a chance to miss a requirement or send an old cut sheet. SubPro does the reading and the assembly, and keeps everything that happens to a submittal on the same record, so nothing has to be carried.

It uses AI for the reading. SubPro goes through the project manual, drafts the rows and answers questions about the spec book. People make the decisions. Each drafted row shows its source page so your team can check the work in the book.

Everything lives in the SubPro app: the submittal log, the submittal packages, the schedule with the date each row has to go out, the review history and the closeout record. When the GC wants a copy, the log exports to Excel or CSV, and each submittal package comes out as one PDF. The output page lists them.

Yes. SubPro reads the equipment schedules on the drawing sheets. When your team approves an equipment row, it goes into the log with its tags and the quantity counted from the schedule, and a make the spec book doesn't name is noted as a possible RFI. How SubPro works walks through it.

Yes. The SubPro chat answers from your spec book and the drafted log, and every answer shows the page it came from. If you ask which sections require samples, or what Section 09 91 13 says about mockups, the answer gives you the page so you can check it yourself.

Ask SubPro, the chat on this website, is a different thing. It answers questions about SubPro and never reads your files. The project chat comes with the work SubPro does on your spec book. See how SubPro works.

From the manufacturers. SubPro keeps a library of the documents manufacturers publish, like cut sheets, product data sheets and safety data sheets, each linked to where it came from. When a drafted row names a product, SubPro pulls the matching documents from that library and your team reviews every match before it goes into a submittal package.

Anyone can search the library for free under Submittal Documents. The documents stay the manufacturers' property, and the rules for that are on the document rights page.

For your side of the work, yes. Every submittal SubPro builds keeps its status, revision history and transmittal record through closeout. SubPro doesn't run the architect's stamping and routing. When the GC requires their own system, the editable Excel and PDF exports go right into it.

So SubPro builds and tracks what your shop owes, and the review above you stays wherever the contract puts it. The submittal software page goes through the whole lifecycle.

SubPro logs the closeout items when it reads the spec book. Owner training, attic stock, warranties and O&M manuals come due against the milestones your team sets, and SubPro builds the closeout binder from what was delivered. The statuses, revisions and transmittals are already on each row, so nobody rebuilds the history from old emails.

No. Nothing goes out without a person. The draft comes to you with its source pages and flags, and someone on your team decides whether to accept, substitute or reject before a submittal goes out. SubPro doesn't stamp anything, doesn't send anything on its own and doesn't decide substitutions.

That's what the flags are for. An or equal clause, an owner selection or a requirement loose enough to read two ways gets marked with the page it came from and waits for a PM.

No. SubPro gets the output ready for you to review and keeps the spec page behind each row where you can see it. Your team still confirms the requirements, who's responsible, substitutions and conformance, and makes the final call on each submittal package.

We read your spec book to do the work on your project, and it's deleted when processing finishes. We never train an AI model on your files. We settle the handling terms, including any NDA or how files get sent, before any real work starts.

The chat on this website is separate and can't take project files at all. The details are on the data handling page and in the privacy policy.

No. The public website and its chat aren't set up for uploading project files. We agree on how your project files get to SubPro before any real work starts.

It's a 15 minute call. We go over the project type, how big the spec book is, timing, how you work now, what output you expect and any data handling needs before we touch any real project files.

Bring the project type, roughly how many pages the spec book is, your trade, the deadline, the tools you use today, and any requirements you have for an NDA, how files get sent or how long they're kept.

Yes. That's what the fit call sample is for. SubPro runs one of your spec books for free, and you look over the log and one finished submittal package from it before deciding. Pilots then start with a few live projects.

Projects with an incomplete project manual, unclear ownership, unusual contract requirements or strict data handling needs may need a closer look before we start.

Per company, by how many projects you run in a year, not per seat. Everyone on the job works from the same record and adding a person doesn't change the price. We send the price in writing after the fit call, before any work starts. The pricing page explains how it's set.

Book a fit call, or open the sample project on the homepage and take the tour of the real app. Either way, have the project type, the size of the spec book, how you work now and your deadline in mind.