A number from its spec section
Each row is numbered by the section that called for it, so 03 30 00 rows sort with Section 03 30 00, and every division in the log shows how many rows it holds.
Submittal log automation that drafts the log from your spec book.
Every submittal on the job starts as a row in the log, and building it by hand means a blank spreadsheet and a spec book of 900 pages. SubPro reads every section, drafts a row for each required item with the page it came from, and flags the rows your PM or PE should look at first.
Stop typing rows out of the spec book
You read sections, copy out requirements, argue about what belongs in the log, and then go hunting for the page again when someone asks why a row is there. At the end of a day of it you've read a few sections, typed a stack of rows, and you've got a feeling something in Division 10 got missed.
When the draft is already done, that day goes to decisions. The automation versus manual page compares the two step by step.
What a drafted row holds
The type and what's owed
Product data, shop drawings, samples, certificates, closeout items and the rest, with a description written from the requirement itself.
Its source
The page in the spec book the row came from, opened with the requirement highlighted.
A status
Draft until your team says otherwise, then on through review to approved. The chips across the top filter the log by status.
The page behind the row
Open a row and press Open source PDF. The spec book opens at that page, the paragraph is highlighted, and its text sits in a band across the top so the reviewer reads it without hunting.
For the concrete mix design row in the sample, that's paragraph B on page 11 of Section 03 30 00: submit the proposed design mix for each class of concrete, with the batching plant, at least 21 days before concrete work starts. The row says what's owed, and the page proves it.
Turn spec sections into draft rows
By hand
- Reading the divisionsA project engineer reads all of it and types rows until the day is gone.
- Knowing where a row came fromYou remember, or you go back through the book.
- Finding the rows that need a callIt depends on who notices and when.
With the draft waiting
- Reading the divisionsSubPro works through each section, finds its submittals article, and drafts a row per required item. A product named in a section with no submittals article still gets a row, marked for a closer look.
- Knowing where a row came fromThe row opens its page, so you confirm the requirement instead of trusting it blind.
- Finding the rows that need a callFlagged rows wait in Needs check. It won't be perfect, and that's what the flags are for.
The drawings fill in the equipment
The spec book says what to submit. The equipment schedules on the drawings say how many, with which tags and at what capacity. SubPro reads those schedules too. When your team approves an equipment row on the Drawings tab, it lands in the log with the tags and the quantity counted from the schedule.
If the make on the drawing doesn't match a manufacturer the spec book names, the row says so and notes a possible RFI, so the question gets asked before the submittal goes out. How SubPro works shows the Drawings tab step by step.
One run, from the PDF to a reviewed log
- The PDF goes inYou load the project manual the way it came from the architect, without retyping anything into a template.
- SubPro reads itSection by section, it finds each submittals article and keeps the page for each item.
- The rows come backOne row for each required item, grouped by division, with the source ready for the reviewer.
- Your PE starts with the flagsThey work through Needs check first, then the rest, and the log exports to Excel or CSV whenever the GC wants a copy.
Submittal log automation FAQ
What is submittal log automation?
It means software reads the spec book and drafts the log so nobody has to type every row by hand. SubPro puts the source page behind the rows and flags the ones that need a decision, so you save the typing and can still stand behind the list.
How does SubPro read the spec book?
Section by section. It finds the submittals article in each one and drafts a log row for each required item, with a reference back to the page it came from. If a section lists products but has no submittals article, each of those products still gets a row, and SubPro marks it so a person confirms what's owed.
How accurate is the automated first pass?
It's a good draft to review, but it's not a guaranteed final log. Some project manuals are written better than others, so the first pass is meant to be checked. The source pages and review flags make that faster, and your team confirms the requirements before handoff.
What happens to the log after it's drafted?
It becomes the record. Each row goes on to its submittal package, its transmittals, the reviewer's response and its closeout items, all in SubPro. The submittal software page follows a row the rest of the way.
Where to go next
Submittal software
What happens after the draft, from the package to closeout, on one record.
Submittal log software
Where the drafted rows land, and how the log is set up for review.
Submittal register automation
Why the register and the log are the same list.
Start your next job from a drafted log.
Send us one project manual on a fit call, and you'll see its drafted rows with their pages. Your team starts at the review.