Submittal log automation
How the first pass gets drafted, step by step, with screenshots.
Building a submittal log by hand vs automating the first pass.
Most teams still build the first log by reading the project manual and typing the rows in one at a time. Here's what that costs you, and what changes when the first pass shows up already drafted.
The two ways, side by side
What a project engineer or coordinator does when the log starts from a blank sheet, and what the same person does when the draft is already there.
By hand
- Read every sectionYou go through each spec section, find the submittals article and work out what it's asking for. If you skip a paragraph, you skip a submittal.
- Type each rowYou type each requirement into the spreadsheet. Months later somebody asks why a row is there and you're back in the PDF looking for it, because nobody wrote down the page.
- Find the gaps lateRows get added after material is already on order, and every time a new reviewer picks up the log they have to figure it all out again.
First pass drafted
- The reading is doneSubPro goes through the sections and drafts a row for each required item, with the source page attached when it can tie the row to one.
- The team reviews rowsThe engineer goes through a draft instead of building one from scratch, confirms the requirements and decides on substitutions, and the flags point at what needs a look.
- The handoff keeps its pagesOnce it's reviewed, the log exports as XLSX with the spec page on every row that has one, ready for whatever tracking the GC wants.
What the first pass looks like
This is Division 07 of the sample project, which is a small elementary school addition. There are twenty two rows: insulation certificates, the air barrier warranty and its field reports, roofing samples and shop drawings, and then the sealant section with its product data, color samples and test reports. Every row shows the section number, the submittal type and the page in the book. Two of the rows already show the architect's answer, because the sample job is under way and the log keeps track of that.
Step by step on one job
Say it's a medium sized commercial job with a project manual of several hundred pages and dozens of sections. Here's how each step gets done both ways.
| Step | By hand | First pass drafted |
|---|---|---|
| Read each section and find the submittals article | One person reading every section, one after another | SubPro does it, and you don't have to sit through it |
| Type the rows | Every row typed in before anyone reviews a requirement | None |
| Capture the source page | Hardly ever, and not the same way twice | On every row it can tie to a page |
| Review and decide | After all the typing is done | Starts as soon as the draft is in |
| Answer what changed in March | Nobody wrote it down | Revision history on the row |
Your team still makes the calls
When you build the log by hand, it all depends on one person not missing anything across hundreds of pages. When the first pass is drafted, software does the reading and your team still does the reviewing and deciding. There's a person in the loop either way. With a draft, that person just gets to the decisions sooner.
SubPro won't catch everything, and we don't promise a perfect extraction. That's why the rows carry the spec page and the review flags, so a reviewer can check a row against the source and doesn't have to take it on faith. Requirements, substitutions, conformance and the final log stay with your team.
A log built by hand costs you something else months later, because it doesn't remember anything. Nobody wrote down who changed a row, which revision went to the architect or what was still open when the phase closed. SubPro keeps that history on every submittal without anybody having to keep it up, and that matters at closeout when somebody asks what happened in March. If the GC runs approvals on their own platform, the editable exports carry that history into it and that platform stays the record. The lifecycle page covers the handoff.
More on the drafted log
Submittal software
What SubPro does after the first pass, all the way through closeout.
Submittal questions, answered
Short answers to the questions people usually have after reading this.
Manual vs automated FAQ
Is it worth automating the submittal log?
The first pass through a project manual is slow and it's easy to get wrong, and that's the kind of work worth handing to software. When the log gets drafted that way, your team spends its time reviewing and deciding instead of typing. A person still makes the calls.
What are the risks of building a submittal log by hand?
The big one is a missed requirement. A submittals article buried deep in a section is easy to skip, and a skipped row turns into a submittal nobody chased until the material was late. Logs typed by hand also lose the source page, so it's hard to check the rows later.
Does automating the submittal log remove human review?
No. Software does the reading and the drafting. A person still reviews the rows, confirms the requirements, handles substitutions and owns the final log. SubPro keeps the spec page and the flags on the rows so the review goes faster.
Where does SubPro fit against a tracking tool?
SubPro drafts the log and tracks the status, the revisions and what went out, item by item. If the GC runs approvals on their own platform, the editable exports load that history into it and their platform stays the record for the job. The lifecycle page covers that handoff.
Try it on one of your own project manuals.
Run one of your project manuals through SubPro and you'll get the log back with its pages cited. Then you can decide for yourself.