A draft that shows its sources
The rows come straight out of the project manual with the page they came from, so a reviewer can see why each one is there before the register moves on.
A register only helps if your team can see where the rows came from. SubPro drafts the first pass from the project manual, puts the spec page on each row it can tie to one, flags the rest, and exports a register your team can go through.
The rows come straight out of the project manual with the page they came from, so a reviewer can see why each one is there before the register moves on.
Anything that needs clarifying or a decision from the PM is marked, so nobody calls the register complete with it still open.
When you're done checking the rows, the register exports to a spreadsheet and feeds the schedule.
| Submittal register | Submittal log | |
|---|---|---|
| What it is | The list of submittals the project manual calls for, one row each. | The same list. Field teams usually call it the log. |
| When it is built | When the spec book is read, before anything is tracked. | The same rows, updated as they go out and come back. |
| What goes wrong | A requirement skipped here never gets tracked. | Statuses fall behind when keeping them current is somebody's side job. |
| What SubPro builds | The drafted rows, with the page behind every row SubPro could tie to one. | The same rows, carried forward with status and history. |
Section 05 12 00 Structural Steel gets a row for the shop drawings, with the section and the page that calls for them.
A row for the mill test certificates, with its page attached, so a reviewer doesn't have to go hunting through the book to confirm it.
Rows for welder qualifications and welding procedures, flagged where somebody needs to decide or clarify something.
The 05 12 00 rows come with their pages attached, so the team can back them up in coordination meetings.
Once a reviewer finds one row that turns out to be somebody's guess, they stop trusting the rest. That's why SubPro puts the page on the row. If a row looks wrong, you open the page and check it, and if SubPro couldn't tie a row to a page, the row is flagged so you know.
The reading is the risky part. If somebody skips a requirement when they read the book, no amount of tracking later is going to find it.
It means software reads the project manual and drafts the register for you, so your team reviews rows instead of typing them. SubPro keeps the source page behind the rows and hands you a file you can edit.
For most teams they're the same thing, the list of submittals the project manual asks for with a row apiece, and we use the words that way too. The one extra at SubPro is the section register that comes with every log. It lists the sections that call for submittals and the count for each one.
Because your team has to be able to check it. With the source page behind a row, a reviewer can see why the requirement is on the list and catch what's missing, and doesn't have to take the list on faith.
No. It's a starting point for your team to review. They check the scope, substitutions, responsible parties, dates and final requirements before it goes into tracking.
Every log SubPro drafts arrives with a section register beside it. It shows which sections call for submittals and how many are in each one.
How SubPro reads the book and fills in the register to begin with.
Where the register goes after that: status, history and closeout, kept in one place.
What the exported files look like when you open them.
Send us a project manual and you'll get the register back with the pages on it. Open the rows, check them against the book and decide from there.