Helonic

How to build and manage a construction submittal log

Helonic is an AI construction drawing analysis platform for teams researching submittal log guide during drawing review. A submittal log is your master record of every item that must be submitted for review and approval before construction proceeds. Done right, it prevents schedule delays and procurement surprises.

What belongs in a submittal log?

Your submittal log is a spreadsheet (or Procore/Autodesk sheet) that tracks every item requiring approval. At a minimum, each entry should include:

  • CSI Spec Section Number (e.g., 03 30 00 Concrete), makes it easy to cross-reference specifications
  • Item Description (e.g., "Ready-Mix Concrete, 4000 PSI"), specific enough that everyone knows what's being submitted
  • Submittal Type: Shop Drawing, Product Data, Sample, or Certification
  • Responsible Party (e.g., concrete contractor, equipment supplier), who owns submitting this
  • Due Date, when it must be submitted to stay on schedule
  • Submission Date, when it was actually submitted
  • Reviewer (Architect, Engineer, GC), who reviews it
  • Status (Not Yet Submitted, Submitted, Pending Review, Approved, Rejected, Resubmit Required)
  • Approved Date, when final approval was issued
  • Notes, conditions of approval, or reasons for rejection

What types of submittals should you track?

Know the difference between product data, shop drawings, and samples so you prepare the right document.

Shop Drawings

Contractor-prepared drawings showing how the work will be built. Examples: structural steel connection details, curtain wall assemblies, MEP coordination layouts, cabinetry elevations, custom millwork.

Shop drawings are NOT approved drawings, architect's approval means the design intent is met, but doesn't transfer responsibility from the contractor for means, methods, or constructability.

Product Data

Manufacturer's technical information. Examples: concrete mix designs, mechanical equipment spec sheets, electrical panel schedules, window performance ratings, roofing material certifications.

Usually supplied by the vendor/distributor, but the general contractor compiles and submits them to prove compliance with the specifications.

Samples

Physical or digital samples of finishes, colors, and materials. Examples: paint color chips, window frame samples, tile samples, brick samples, carpet swatches.

Samples must be submitted before purchasing in bulk. Approval confirms the owner and architect accept the aesthetic and quality.

Certifications

Third-party test reports and compliance documentation. Examples: fire-rated assemblies, roof wind ratings, concrete lab reports, welder certifications, equipment commissioning reports.

These prove compliance with code and specification requirements. Usually submitted toward the end of the project.

How do you build a submittal log from the specifications?

Do not guess what needs to be submitted; go through the spec book division by division.

1

Start with Division 01 (General Requirements)

The project specifications usually include a submittal schedule in Division 01. This is your gold standard list. Copy every item listed.

2

Read Each Spec Section Carefully

Many specs have submission requirements embedded in the text, not just in a master schedule. Example: "Concrete contractor shall submit mix design and slump test results before placing concrete." Add this to your log.

3

Note Any Conditional Submittals

Some submittals are conditional: "If metal stud framing is used, submit stud schedule; if wood framing, submit lumber certifications." Mark these clearly so you know whether to expect them.

4

Check the Contract

Some submittal requirements live in the contract, not the specs. Read the Special Conditions and Exhibit A for any requirements called out by the owner or lender.

How should you set submittal due dates?

This is where submittal logs prevent disasters. A late submittal can delay procurement, which delays installation, which delays the whole project.

Work backward from the date work must be installed:

Example: Structural steel must be installed on May 1st

  • • Fabrication time: 6 weeks → Steel mill delivery needed by March 20
  • • Procurement time: 2 weeks → Purchase order needed by March 6
  • • Review/approval time: 1 week → Drawings submitted by Feb 27
  • • Due date in submittal log: Feb 20 (buffer for one rejection/resubmit)

Always build in a buffer. Most submittals get at least one round of comments. If your due date is March 1 and you expect a 1-week review cycle plus resubmit time, the actual submission date should be Feb 15 to May 1st installation happens on time.

How does the submittal review cycle work?

Every submittal goes through a review workflow that you should track from submit to return.

1

Submit

GC (or subcontractor) submits to the architect/engineer. Record submission date in your log. Status: "Submitted"

2

Pending Review

Architect reviews. Expected turnaround is 3–7 business days, depending on complexity. Status: "Pending Review"

3

Review Response (Three Possible Outcomes)

  • Approved: As submitted. You're clear to proceed. Status: "Approved"
  • Approved with Comments: Approved, but must incorporate changes or notes on next phase. Status: "Approved" (note conditions in Notes field)
  • Rejected/Resubmit Required: Does not comply. Must revise and resubmit. Status: "Resubmit Required"
4

Resubmit (if necessary)

Create a new line item in your log for the resubmittal. It's a separate submission with its own dates. This matters for payment and claims, contractors are often not paid for work until submittals are approved.

How do you track open and aging submittals?

Once you have entries, the critical skill is aging. Add a formula column in your spreadsheet: Days Pending = TODAY() - Submission Date

Use this to hold your architect and subs accountable:

  • Submittals over 7 days pending: Follow up with architect
  • Submittals over 14 days pending: Email the A/E project manager and escalate
  • Submittals that miss the due date: Alert project manager immediately. Impact on schedule?

Many schedule delays originate from slow review cycles. Your submittal log is your evidence that you pushed back and tracked delays.

What happens when submittals are late?

A single missed submittal cascades into late procurement and delayed installation.

Scenario

Structural steel shop drawings are due Feb 20. Contractor doesn't submit until March 1. Architect takes 1 week to review (now March 8). One revision required. Resubmit by March 15. Architect approves March 22. Purchase order placed March 25. Mill quote was 6-week lead time. Steel now arrives in early May instead of late March. Framing schedule slips 6 weeks. Drywall schedule slips 6 weeks. Mechanical, electrical, paint all slip. Project completion moves from November to December. That submittal cost you one month.

This is why contractors track submittals religiously and why late subs get heated phone calls.

Submittal log template: what columns should it have?

A working submittal log template needs 13 columns: submittal number, spec section, description, type, sub or supplier, the four review dates, the A/E action code, resubmittal number, status, and lead time with a required on site date. The dates are what let you prove where a package sat and for how long.

Download the submittal log template (CSV, opens in Excel or Google Sheets). It has the header row below and one filled example line you can overwrite.

FieldWhat to enterExample
Submittal #Unique number, usually the spec section plus a sequence08 41 13-001
Spec sectionCSI MasterFormat number and title that requires the submittal08 41 13 Aluminum-Framed Entrances and Storefronts
DescriptionWhat is in the package, specific enough to tell two packages apartStorefront shop drawings, Levels 1 and 2
TypeShop drawing, product data, sample, certification, or closeoutShop drawing
Sub / supplierCompany responsible for preparing the packageSummit Glazing Co.
Date received from subDate the GC received the package11/02/2026
Date sent to A/EDate the GC forwarded it after its own review11/04/2026
Required return dateDate sent plus the review period in the contract11/18/2026
A/E action codeThe reviewer's stamp, as writtenRevise and Resubmit
Date returnedDate the reviewed package came back11/17/2026
Resubmittal #Revision suffix when the package goes back in08 41 13-001.1
StatusOpen, With A/E, Returned, Resubmit Required, or ClosedResubmit Required
Lead time / required on siteFabrication and delivery time, and the date material must be on site10 weeks / 03/15/2027

Here is what three lines look like on a mid-rise office job. The storefront package came back marked Revise and Resubmit, so it gets a resubmittal number and stays open until the .1 package is returned.

Submittal #Spec sectionDescriptionTypeSub / supplierRec'd from subSent to A/ERequired returnA/E actionReturnedResub #StatusLead time / on site
03 30 00-00103 30 00Concrete mix designs, 4,000 psiProduct dataRidgeline Concrete10/06/202610/07/202610/21/2026No Exceptions Taken10/16/2026Closed2 weeks / 11/09/2026
05 12 00-00205 12 00Structural steel shop drawings, Level 2 framingShop drawingKeystone Steel10/20/202610/22/202611/05/2026Make Corrections Noted11/04/2026Closed8 weeks / 01/11/2027
08 41 13-00108 41 13Storefront shop drawings, Levels 1 and 2Shop drawingSummit Glazing Co.11/02/202611/04/202611/18/2026Revise and Resubmit11/17/202608 41 13-001.1Resubmit Required10 weeks / 03/15/2027

Set the required return date from the review period in your contract, not from habit. If the spec gives the architect 10 working days, the storefront line above is due back November 18. Sort by required on site date minus lead time to see which open packages are about to hold up procurement.

If your project runs submittals in Procore or Autodesk Construction Cloud, those tools carry most of these fields natively, and the spreadsheet is better used for a pre-bid list or a sub's own tracking. Our guide to construction submittal types covers what goes in the Type column, and Helonic submittal review checks returned packages against the drawings and specs.

What submittal-log mistakes should you avoid?

Avoid missing spec items, no due dates, and logs that never age open submittals.

  • Forgetting to read Division 01. Submittals are often hidden in the general requirements section. Don't skip this.
  • Not factoring in review time. Due dates should account for review and one round of revisions. If you need approval by March 1, start the submission by Feb 10.
  • Losing track of resubmittals. Each revision is a separate submittal with its own timeline. Don't treat it as complete until final approval.
  • Submitting incomplete documents. Architects reject submittals that are missing signatures, certifications, or required attachments. Check the spec before submitting.
  • Not following up on aging submittals. If it's pending review for more than a week, send a polite reminder to the architect. Many projects slip because nobody follows up.
  • Ignoring conditional submittals. If the spec says "if X material is selected," make sure you track whether X was selected, and whether the submittal is still required.

Stop missing submittal deadlines

Late submittals cascade into schedule delays. Helonic helps you identify what needs to be submitted by analyzing your drawings and specifications, so you can build your log faster and catch issues early.