SubPro
Example project Sample spec set
Get started
Submittal log software

Submittal log software for the first draft your team can review.

SubPro turns a project spec book into a first draft your team can check: every row cites its spec page, the rows that need a decision are flagged, and it all exports as an editable Excel file.

Review a real spec Compare automation workflow

See the review surface.

The first pass shows up as draft rows with their matched documents and clear next actions, ready to inspect before export.

SubPro populated draft submittal log rows
Practical log view

Rows are arranged so the team can review requirements, responsible sections, and status without starting from a blank spreadsheet.

SubPro draft rows with package matches visible
Package context included

Available supporting document matches appear beside the row, making package review part of the same workflow.

Reviewable output

Start with a log, not a blank sheet.

The first draft is where the day usually disappears: rows, page numbers, responsible sections, and the nagging sense that Division 07 hid something nasty. SubPro builds a practical first pass that shows what the spec requires, where it came from, and which rows deserve a closer look before handoff.

Spec-driven rows

The requirements arrive as a working draft, grouped by section, so your team reviews a list instead of building one.

Source page on every row

When someone asks why a row is there, the answer is the spec page attached to it, not another hunt through the manual.

Exportable handoff

Review it, clean it up, and export it to Excel. Your tracker gets a finished starting set instead of an empty register.

The XLSX handoff

A spreadsheet your team can actually work in.

The value of submittal log software is not a pretty dashboard. It is what you can hand the next person. SubPro exports a standard editable XLSX log with one row per submittal requirement, each carrying its CSI section, submittal type, responsible party, the source specification page, review status, and notes.

Because it is an ordinary spreadsheet and not a locked format, your team can sort it by section, filter to one trade, add or delete rows, and paste it straight into whatever tracker you already run. The draft removes the blank-sheet grind. Your team keeps full control of the final log.

Every row keeps its source page reference, so when a reviewer questions a line, the answer is one click away instead of a hunt back through the manual. That is the difference between a list you trust and a list you re-check by hand.

Worked example

One section as reviewable rows.

Take Section 08 71 00 Door Hardware, a section that carries a long submittals list. Here is how it lands in the draft log.

Hardware schedule

A row for the required hardware schedule submittal, tagged with the 08 71 00 section and the spec page behind it.

Product data

Separate rows for the specified hinges, closers, locksets, and exit devices, so each product line can be reviewed on its own.

Keying schedule

A row flagged as an owner decision, because keying is coordinated with the owner rather than picked from a catalog.

Ready to export

All the 08 71 00 rows drop into the editable XLSX alongside every other section, ready to sort, filter, and hand off.

Submittal log software FAQ

What should submittal log software do before tracking starts?

It should identify submittal requirements from the specifications, keep source page context close, flag items that need review, and prepare an editable log for handoff, so the tracker starts from a real draft instead of a blank sheet.

What does the exported submittal log look like?

An editable XLSX log with a row per requirement, carrying the CSI section, submittal type, responsible party, source specification page, review status, and notes. Being a standard spreadsheet, your team can sort, filter, and paste it into an existing tracker.

Can I edit the draft SubPro produces?

Yes. The draft is a starting point, not a locked output. Your team edits rows, adds or removes requirements, and owns the final log. SubPro removes the blank-sheet grind, it does not make the decisions.

Does SubPro replace the project team's review?

No. SubPro prepares a reviewable starting point. The project team still verifies requirements, responsibility, substitutions, and final package decisions before anything moves forward.

Related SubPro pages

From the draft log to the register, the AI behind it, and the files you get at the end.