How to Build a Submittal Log from Specifications

To build a submittal log from specifications, start with Division 01 (usually Section 01 33 00, Submittal Procedures) to learn the rules — review timelines, formats, and copies required. Then go through every technical spec section and read PART 1, where each section lists its required submittals: product data, shop drawings, samples, test reports, and closeout documents. Record each one in a spreadsheet with the CSI section number, submittal description, type, responsible subcontractor, and lead time. Flag long-lead items like switchgear and transformers first, and update the log every time an addendum changes a spec section.

That's the whole process in one paragraph. The rest of this guide covers how to actually do it well — and how long it really takes on a 500+ page spec book.

What Is a Submittal Log and Why Does It Come from the Specs?
Step 1: Read Division 01 First
Step 2: Walk Every Spec Section's PART 1
Step 3: Structure the Log Columns
Step 4: Flag Long-Lead Items Immediately
Step 5: Keep the Log Current Through Addenda
How Long Does This Take on a 500+ Page Spec Book?
How DeadFront Builds the Submittal Log Automatically
FAQs
Bottom Line

What Is a Submittal Log and Why Does It Come from the Specs?

A submittal log (also called a submittal register or submittal schedule) is the master list of every document you're contractually required to submit for approval before you can buy material or build the work: product data, shop drawings, samples, mock-ups, test reports, certifications, and closeout documents.

The reason it comes from the specs — not from memory or a generic template — is simple: the specs are the contract. If Section 26 24 16 requires shop drawings for panelboards and you never submit them, you can't legitimately order panelboards. If Section 03 30 00 requires concrete mix designs 30 days before the first pour and you submit them a week out, you've built a schedule delay into your own project.

Every project's submittal requirements are different. A generic electrical submittal checklist will miss the project-specific items — the seismic certifications, the owner-witnessed factory tests, the extra warranty documentation — and those are exactly the items that hold up approvals.

One more reason to build the log early, ideally during buyout or even before award: the log is where long-lead procurement problems first become visible. More on that in Step 4.

Step 1: Read Division 01 First

Division 01 (General Requirements) sets the rules that apply to every submittal on the project. Before you touch a single technical section, find and read:

01 33 00 — Submittal Procedures. The core section. It defines review turnaround time (commonly 14–21 days per review cycle, sometimes longer for structural items), electronic vs. hard-copy format, numbering conventions, how many resubmittal cycles you get before backcharges, and whether a preliminary submittal schedule is itself a required submittal (it usually is).
01 33 23 — Shop Drawings, Product Data, and Samples (if broken out separately).
01 78 00 / 01 78 23 / 01 78 39 — Closeout Submittals, O&M Data, Record Documents. These are submittals too, and they gate final payment.
01 45 00 — Quality Requirements. Often adds test reports and qualification submittals that aren't repeated in the technical sections.
01 43 00 — Quality Assurance and 01 60 00 — Product Requirements. Look for substitution procedures and "or equal" rules — they determine how much flexibility you have on sourcing.

Write down three numbers from Division 01 before moving on: the review turnaround time, the resubmittal turnaround time, and any required lead time before use (e.g., "submit no fewer than 30 days prior to incorporation"). You'll use these to calculate required submission dates for every line in your log.

If you're rusty on how spec sections are numbered and organized, our CSI MasterFormat complete guide covers the division and section structure this whole process hangs on.

Step 2: Walk Every Spec Section's PART 1

Nearly every technical spec section follows the same three-part format:

PART 1 — GENERAL: scope, references, submittals, quality assurance, delivery/storage, warranty
PART 2 — PRODUCTS: materials and manufacturers
PART 3 — EXECUTION: installation requirements

The submittal requirements live in PART 1, almost always under an article titled "SUBMITTALS" or "ACTION SUBMITTALS / INFORMATIONAL SUBMITTALS" (the two categories matter — action submittals require approval before you proceed; informational submittals are for the record).

The manual process:

Open the table of contents and list every spec section in your scope (for a sub) or the whole book (for a GC).
For each section, go to PART 1 and find the submittals article.
Record every listed item as its own line in the log — don't collapse "product data, shop drawings, and samples" for one section into a single line, because they'll be submitted, tracked, and approved separately.
While you're in PART 1, also check Quality Assurance and Warranty articles. Certifications, installer qualifications, and extended warranties are frequently listed there instead of under Submittals — and they're still required.
Skim PART 2 for named manufacturers and "no substitution" language, and note anything that smells like a long-lead or sole-source item.

Two traps to watch for:

Submittals referenced by cross-reference. A section might say "comply with Section 01 33 00" and list nothing locally, or it might reference test standards that carry their own reporting requirements. Read the referenced section.
Non-standard requirements buried mid-paragraph. The dangerous items are the ones that deviate from what your crews and vendors do by default. We've seen a contractor miss a spec requiring conduit labeling every 30 feet — standard practice is labeling at starts and terminations only — across more than a million feet of conduit in a data center. That single buried sentence cost over $600k and weeks of schedule. The submittal walk-through is often your best chance to catch these, because it forces you to actually read PART 1 of every section.

Step 3: Structure the Log Columns

Here's a column structure you can copy straight into Excel or Google Sheets. It works for GCs and subs; delete what you don't need rather than starting thinner and adding columns mid-project.

#	Column	What Goes in It
1	Submittal No.	Your numbering per Division 01 (commonly `SectionNumber-SequenceNumber`, e.g., 26 24 16-001)
2	Spec Section	Six-digit CSI section number (26 24 16)
3	Section Title	Panelboards
4	Submittal Description	Exactly what the spec asks for ("Shop drawings showing bus arrangement, dimensions, and ratings")
5	Type	Product Data / Shop Drawings / Samples / Test Report / Certification / Closeout / O&M
6	Action or Informational	Per the spec's own categorization
7	Spec Paragraph	Where the requirement lives (1.05.B.2) — saves arguments later
8	Responsible Party	Sub or vendor who produces it
9	Lead Time (weeks)	Fabrication/delivery time after approval
10	Long-Lead Flag	Y/N — sorts your procurement priorities
11	Required On-Site Date	From the construction schedule
12	Submit-By Date	On-site date minus lead time minus review cycle(s) minus float
13	Date Submitted	Actual
14	Date Returned	Actual
15	Review Result	Approved / Approved as Noted / Revise & Resubmit / Rejected
16	Resubmittal No.	Track cycles — Division 01 often limits them
17	Status	Not Started / In Prep / Submitted / Returned / Closed
18	Notes	Substitution requests, addendum changes, RFI references

The column that separates a useful log from a filing exercise is #12, Submit-By Date. Work backwards: if switchgear must be on site March 1, lead time is 20 weeks after approval, and the engineer gets 21 days per review — you need to submit by late September of the year before, and that assumes first-pass approval. Put a real date in that column for every line and sort by it. That sorted list is your procurement plan.

Step 4: Flag Long-Lead Items Immediately

Some equipment takes so long to fabricate that the submittal has to move before almost anything else on the project. Typical offenders and rough current lead-time ranges:

Transformers and switchgear — routinely 12–24 weeks after approved submittals, and large or custom gear can run far longer
Custom air handlers and packaged HVAC equipment — often 12–20+ weeks
Structural steel — detailing, approval, and fabrication commonly stack up to 12–16+ weeks
Generators, elevators, custom lighting, long-run cable and bus duct — frequently in the same range

Lead times move with the market, so treat every number above as a prompt to call your vendor, not a fact to plan around. The point is the order-of-operations logic: the review clock and the fabrication clock only start after you submit, so long-lead submittals go first — regardless of when the work happens in the schedule. Electrical gear that installs in month 10 may need its submittal in month 1.

A practical habit: the day you finish the log, sort by the Long-Lead flag and get those submittals into preparation before mobilization paperwork, before the schedule of values, before anything that isn't contractually urgent. A rejected switchgear submittal in week 2 is an inconvenience. The same rejection in month 4 is a delay claim.

Step 5: Keep the Log Current Through Addenda

During bid and after award, addenda and revised spec sections will change your submittal requirements — new sections appear, submittal articles get rewritten, products get swapped. A log built from the original bid set quietly goes stale.

The manual discipline:

When an addendum drops, read the narrative and re-check every reissued spec section's PART 1, even if the addendum summary doesn't mention submittals. Addenda summaries are frequently incomplete about what actually changed inside a reissued section.
Diff the reissued section against the old one. Line-by-line, side by side. Tedious, but the alternative is pricing and submitting against a dead version.
Update affected log lines and note the addendum number in the Notes column so there's a paper trail.
Re-run the submit-by math for anything whose lead time or product changed.

This is the step that fails most often in practice — not because people don't know to do it, but because addendum three lands 48 hours before bid and nobody has time to re-read 40 reissued pages. (It's also the step software helps with most; DeadFront's Spec Diff shows exactly what was added, removed, or modified between versions so you're not eyeballing two PDFs at 9 p.m.)

How Long Does This Take on a 500+ Page Spec Book?

Honest numbers, assuming you're building the log properly — reading PART 1 of every section, not skimming a table of contents:

Task	Time
Division 01 review and rule capture	1–2 hours
PART 1 walk-through, ~50–80 technical sections at 5–10 min each	5–12 hours
Building the spreadsheet, numbering, dates, lead-time calls	2–4 hours
Per addendum with reissued sections	1–3 hours each

Call it a full working day to two days for a 500-page book, and more for the 1,000+ page public-works sets where Division 01 alone can run 100 pages. That's why the log so often gets built from a recycled template, late, or not at all — and why missed submittals remain one of the most common self-inflicted schedule hits in the field.

If you're doing it manually, the best corner to cut is not the reading — it's the transcription. Read every PART 1, but dictate lines into the spreadsheet or use split screens rather than flipping between windows. The reading is where the value (and the risk) is.

How DeadFront Builds the Submittal Log Automatically

DeadFront.AI does the walk-through described above as part of analyzing your bid documents. Upload the spec book (200–1,000+ pages, scanned PDFs included — image-only docs are run through AI vision OCR automatically) and it extracts every submittal requirement into a structured log with:

CSI section number and title for every line
Submittal type (product data, shop drawings, samples, test reports, closeout)
Long-lead flags so procurement priorities surface immediately
One-click Excel (xlsx) export — the output drops into the column structure above, ready for dates and status tracking

Every extracted item links back to a citation that highlights the exact text in the source PDF, so you can verify any line against the spec in one click instead of trusting a black box. And because the same analysis risk-scores the whole book, the non-standard requirements — the conduit-labeling-every-30-feet class of item — show up in the high-risk list with rationale, not buried in paragraph 1.05.B.2. When addenda arrive, Spec Diff shows exactly what changed between versions so updating the log takes minutes instead of an evening.

A typical 1,000-page spec book surfaces 15–40 non-standard requirements, with 2–5 needing immediate RFI or change-order attention. The submittal log is one output of that same pass — you get the log, the bid brief, and the risk-scored extraction from a single upload.

You can poke at a live example in the interactive demo, no signup required.

FAQs

What's the difference between a submittal log and a submittal schedule?

In practice the terms are used interchangeably. Strictly, the log is the tracking register (what's required, submitted, returned), while the schedule adds dates tied to the construction schedule. Division 01 often requires you to submit a "schedule of submittals" early in the project — the column structure above satisfies both if you fill in the date columns.

Where exactly in a spec section are submittal requirements listed?

In PART 1 — GENERAL, usually in an article titled "SUBMITTALS," "ACTION SUBMITTALS," or "INFORMATIONAL SUBMITTALS." But also check the Quality Assurance and Warranty articles in PART 1, which frequently require certifications and warranty documents that function as submittals, and Division 01 Section 01 33 00 for the procedural rules that apply project-wide.

Should subcontractors build their own submittal log or rely on the GC's?

Build your own for your scope. The GC's log tells you what they'll track; your own log — built from PART 1 of your sections — is how you catch requirements the GC's template missed and how you defend yourself when there's a dispute about what was required. It also drives your own procurement dates, which the GC's log won't manage for you.

How early should long-lead submittals go in?

As early as contractually possible — often within days of notice to proceed, and some contractors prepare them at-risk during the award gap. Work backwards from the required on-site date: subtract fabrication lead time, then subtract one review cycle (add a second if the item is complex or the engineer is known to mark things up), then subtract shipping and float. For 20-week gear with 21-day reviews, "early" usually means month one.

Do closeout submittals belong in the same log?

Yes. O&M manuals, warranties, as-builts, and training documentation (Division 01 Sections 01 78 00 and related) gate retainage and final payment. Putting them in the log from day one means you collect them as work completes instead of chasing vendors a year later.

Can AI really extract submittal requirements accurately from a spec book?

The honest answer: verify anything you'd bet money on — which is why DeadFront links every extracted item to a highlighted citation in the source PDF. One utility-sector electrical contractor ran 30+ public-works bids through the platform in six months, roughly 10,000 extracted items, with a workflow of upload the bid set, read the brief and high-risk list, done in minutes. The citations are what make that workflow trustworthy: checking a flagged item takes one click, not a page hunt.

Bottom Line

Building a submittal log from specifications is a five-step job: learn the rules in Division 01, walk PART 1 of every technical section, structure the log with real submit-by dates, flag long-lead equipment first, and re-verify against every addendum. Done properly it costs a day or two per spec book — and it's one of the highest-leverage days on the project, because a missed submittal becomes a missed delivery becomes a delay you paid for.

If you'd rather get the log — plus the risk-scored extraction and bid brief — from a single upload with an xlsx export at the end, book a 15-minute demo, try the interactive demo, or see pricing. Pro runs $1,000/month with unlimited users, up to 25 active projects, and a 30-day risk-free pilot.