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 rows. Here is what that costs, and what changes when the first pass arrives drafted.

Book a fit call See how the first pass is drafted

SubPro reading a 442-page project manual, the submittal list still empty while the first pass runs

Compare the two weeks side by side

What a project engineer or coordinator does when the log starts from nothing, against what the same person does when the draft arrives first.

By hand

Read every sectionWork through each spec section, find the submittals article, and interpret it. Skip a paragraph and you skip a submittal.
Type each rowEnter the requirement into the spreadsheet. Months later, reopen the PDF when someone asks why the row exists, because the page was never captured.
Discover the gaps lateAdd rows after material is on order, and rebuild the picture every time a new reviewer picks the log up.

First pass drafted

The reading is doneSubPro works through the sections and drafts a row for each required item. The source page is attached, so nothing floats without evidence.
The team reviews rowsThe engineer inspects a draft instead of building one, confirms requirements, and decides substitutions, with flags pointing at what needs a look.
The handoff carries its sourcesThe reviewed log exports as XLSX with spec-page references intact, ready for whatever tracking the GC requires.

A project engineer's desk late at night: a tabbed project manual open under a lamp with a highlighter in the gutter, hands on a keyboard, an empty spreadsheet on the monitor, two coffee cups — By hand, the week looks like this: one person, one highlighter, and a spreadsheet that fills at forty rows a day.

See what the first pass produces

The SubPro submittal log for a sample project after the first pass: 82 draft rows listing spec section, submittal type, description, product, and status, starting with Division 01 — Eighty-two rows drafted from one project manual before anyone on the team typed a line. Each row carries its section, type, description, and a Draft status waiting for review.

Count the hours, not the adjectives

Do the math on a mid-size commercial job: an 850-page project manual holding 60 to 80 spec sections. The figures below are from that job.

Step	By hand	First pass drafted
Read each section and find the submittals article	20 to 40 minutes per section	Machine time you do not sit through
Type the rows	A 40-hour week before anyone reviews a requirement	None
Capture the source page	Rarely, and never consistently	On every row
Review and decide	After the week is gone	2 to 4 hours, starting the day the draft lands
Answer what changed in March	Nobody recorded it	Revision history on the row

A field office in morning light: a printed log of many rows flat on a plan table, a red pen marking one row, the tabbed project manual closed to the side, a mug of coffee — Drafted first, the same week starts on a Tuesday morning with a red pen. The reading is done. The deciding is not.

Keep the judgment where it is

Building the log by hand depends on one person not missing anything across hundreds of pages. Drafting the first pass moves the reading to software and leaves the reviewing and deciding with the team. Neither approach removes a person from the loop. They differ in how much of the week burns before the judgment starts.

SubPro does not promise a perfect extraction. That is the reason the spec page and the review flags sit on every row. A reviewer verifies a row against the source instead of taking it on faith. Requirements, substitutions, conformance, and the final log stay with your team.

The hand-built log has a second cost that surfaces months later: it has no memory. Nobody recorded who changed a row, which revision went to the architect, or what was outstanding when the phase closed. SubPro keeps that history on every submittal without anyone maintaining it, which matters when closeout asks what happened in March. If the GC runs approvals on their own system, the editable exports carry that record into it. The lifecycle page covers the handoff.

A drafted submittal row opened in SubPro, showing the spec page it cites, its review flags, and the product data matched to it

Submittal log automation

The automated first pass, step by step, with the screens it produces.

Submittal software

Everything SubPro does once the first pass is drafted, through closeout.

Submittal answers

Short answers to the questions this comparison tends to raise.

Manual vs automated FAQ

Is it worth automating the submittal log?

The first pass through a project manual is slow, repetitive, and easy to get wrong, which is the kind of work worth handing to software. Drafting the log that way frees the team to review and decide instead of transcribe. The judgment still belongs to a person.

What are the risks of building a submittal log by hand?

A missed requirement. A submittals article buried deep in a section is easy to skip. A skipped row becomes a submittal nobody chased until the material was late. Hand-built logs also lose the source page, so rows are hard to verify later.

Does automating the submittal log remove human review?

No. Software handles the reading and drafting. A person still reviews the rows, confirms requirements, handles substitutions, and owns the final log. SubPro keeps the spec page and the flags on every row so that review goes quickly.

Where does SubPro fit against a tracking tool?

SubPro builds the log and keeps the record: status, revisions, and what went out, item by item. If the GC runs approvals on their own system, the editable exports carry your record into it instead of starting over. The lifecycle page covers that handoff.

Send us one spec book.

Time the two approaches on your own project manual. You get the drafted log back with its citations and decide from there.

Book a fit call Build my log instead