Submittal log software that gives your team a first draft to review.

SubPro reads the project manual and drafts the log for you. The rows show the spec page they came from, the ones that need a decision come flagged, and the whole log exports to an Excel file you can edit.

Book a fit call Compare the automation workflow

A gypsum board product data row opened on the SubPro Review page: its history from draft to submitted under transmittal T-5 and under review, the open cycle, and the Respond menu with Approve, Approve as Noted, Revise and Resubmit, Reject, Not Reviewed and Acknowledge Receipt

The row that never made it into the log

A log can look complete. The columns are neat, the section numbers look right and there are plenty of rows. Then five months in, the GC asks for the firestopping product data and there's no row for it, because the requirement was on page 412 and nobody typed it in.

When a log built by hand is missing something, nothing tells you. You can't see a row that isn't there. Submittal log software is worth having if it lets you check each row and find the gaps early, while they're still easy to fix.

A thick spiral bound project manual open deep into its pages on a field office plan table, a finger resting on one dense paragraph, a printed spreadsheet log beside it with one row circled in red — A thick project manual open on a plan table next to a printed log with one row circled in red.

Start with the rows already drafted

Rows drafted from the spec book

The requirements come grouped by section, so your team reviews a list and doesn't have to build one.

The source page on the row

When someone asks why a row is there, you open the page attached to it. You don't have to go hunting through the manual again.

An editable handoff

Clean it up and export it to Excel, and your tracker starts out with rows in it.

Work in the spreadsheet you already use

Column	What it holds
Number	The submittal number, so everybody on the phone is talking about the same item.
Section and title	Like Section 08 71 00 Door Hardware, so anyone can tell which trade it belongs to.
Type	Product data, shop drawings, samples or test reports. Each one gets handled differently.
Responsible party	Who's responsible for getting it in.
Source page	The page in the project manual that created the row, on each row SubPro could tie to a page. Rows it could not tie to one carry a no page reference flag.
Status and notes	Where the row is and what was decided about it.

Check the draft row by row

SubPro puts a link on each drafted row to the page it was read from. If a row looks off, you open that page and check it.

In a log typed by hand, a wrong row can sit there until it causes a problem in the field. With the page on the row, your reviewer catches it at the desk. Rows SubPro wasn't sure about come flagged for a person.

A plan table seen from standing height, a thick specification volume open with one paragraph highlighted, a printed log beside it with a pencil resting between the two, a hard hat and coffee at the far edge — An open project manual with one paragraph highlighted and a printed log beside it, a pencil between them.

What door hardware looks like as drafted rows

Section 08 71 00 Door Hardware is a long one, with hinges, closers and keying language, and it has one of the longest submittals lists in the book. It's where logs typed by hand start missing rows.

A row for the hardware schedule, tagged 08 71 00 with the page behind it.
Separate product data rows for hinges, closers, locksets and exit devices, so each one gets reviewed on its own.
The keying schedule row flagged as an owner decision, because the owner sets the keying plan.
All of it in the XLSX with every other section, ready to sort and hand off.

One log from kickoff to closeout

A lot of submittal logs get built at kickoff and then fall behind while the revisions pile up in somebody's inbox. In SubPro the status changes on the row as it gets reviewed, sent, returned and revised, so the log keeps up with the work.

A long printed submittal log pinned to a jobsite trailer wall in several sheets, dense with handwritten marks and highlighter, a nearly finished building through the window beside it — A printed submittal log pinned to a trailer wall, covered in handwritten marks and highlighter.

For whoever owns the log

Specialty contractors

You get the rows for your scope without pulling someone off estimating to type them.

Project engineers

You review a draft with the pages on it and spend the time you get back on coordination.

Document controllers

The source pages and statuses are already on the rows, so you're not stuck formatting the log.

PMs inheriting a job

Run the project manual through SubPro and compare the draft against whatever log the last team left you.

The boilerplate sections get read too

Section 23 05 29 Hangers and Supports for HVAC Piping and Equipment reads like boilerplate, so it gets skimmed, and then a seismic bracing requirement comes up at inspection with no submittal behind it. The draft has rows for hanger types, channel framing and attachment hardware, it keeps the bracing row that a quick skim would miss, and it flags the support layout drawings for coordination.

A mechanical corridor under construction, pipes hung on clevis hangers from threaded rod along the wall, an inspector in a yellow hard hat shining a flashlight down the run — Pipes on clevis hangers in a mechanical corridor, an inspector checking the run with a flashlight.

Two things we hear a lot

"Our Excel log works fine."

It probably does on smaller jobs. It gets harder on a big building with three addenda, because the more pages there are, the easier it is to miss something when you're typing it by hand.

"We tried extraction once. It made things up."

That's fair, and you should be suspicious of anything you can't check. Here you click the page on the row and read the paragraph, and you'll see right away if the row is wrong. The spec book you upload is deleted when processing finishes. The data handling page has the details.

Submittal log software FAQ

What should submittal log software actually do?

It should find the submittal requirements in the project manual, keep the source page on the row, flag the rows that need a decision and keep the status and history up to date after kickoff.

What does the exported submittal log look like?

It's an XLSX you can edit, with one row per requirement. Each row has the section, the submittal type, the responsible party, the source page where SubPro could tie the row to one, the review status and notes. You can sort it, filter it and paste it into whatever tracker your GC uses.

Can I edit the draft SubPro produces?

Yes. The draft is just where you start. Your team edits rows, adds or removes requirements, and the final log is yours.

What happens when an addendum lands?

The rows it touches update as revisions, and what they said before stays in the row's history. So you can look up what changed, when it changed and what the log said before.

Check a draft built from your own project manual.

Send us one project manual. Read the rows, click through to a few pages and see if the draft holds up on your own job.

Book a fit call

Submittal log software that gives your team a first draft to review.

The row that never made it into the log