What we do
Tools
Industries
Department
How we workLet's talk →
Home/Construction Submittal Log
Construction Submittal Log

Construction Submittal Log: What Goes on It and Where to Keep It

A submittal log lists every shop drawing, product data sheet, sample and mock-up the specs require, who owes it, who's reviewing it and when it has to be back. Below are the columns, the dates that actually matter, and the ways a log stops telling the truth halfway through a job.

The short answer

What it is: one row per required submittal, numbered by spec section, tracking it from "owed by the sub" to "approved" and every revision in between.

A spreadsheet is enough on a small job with a handful of subs and one reviewer who answers quickly.

Use the submittals tool in your project platform (Procore, Autodesk Build) when the architect and subs work in it too. Then the reviewer's action updates the log instead of someone copying it in.

Spreadsheet log or the submittals tool in your platform?

Spreadsheet

Fine when the job is small

  • Quick to set up and everyone can open it.
  • Only as current as the last person who updated it.
  • Reviewer replies come by email and have to be typed in by hand.
Procore or Autodesk Build

Better when reviewers work in it

  • Workflows route each item to the next reviewer and track who has it.
  • Procore holds required on-site dates and lead times on the submittal itself.
  • Only helps if the architect and subs actually reply inside it.

If your design team won't work in the platform, you end up with the spreadsheet problem inside expensive software: replies arrive by email and someone keys them in.

Why a submittal log stops matching reality

Returns arrive by email, not in the log

How you'll know: The architect stamped it last Tuesday. The log still says "under review" because the PDF is in the PM's inbox.

Fix: Make one place where returned submittals land, and record the action and date from there the day they arrive.

"Revise and resubmit" treated as done

How you'll know: The row shows a return date, so it looks finished, but nothing was approved and the sub hasn't resubmitted.

Fix: Only an approved or approved-as-noted action closes a row. Anything else puts the ball back with the sub, with a new due date.

Long-lead items logged too late

How you'll know: Switchgear or storefront gets submitted when the sub gets to it, and the delivery date lands after the install date.

Fix: Add long-lead items to the log first, from the spec book, with their submit-by date worked back from the schedule.

The sub's log and the GC's log disagree

How you'll know: Your sub swears it was submitted. Your log says it's still owed.

Fix: One log both sides read from, or a weekly ball-in-court list sent to each sub showing exactly what you think they owe.

Building the log, column by column

These are the fields worth having, in the order you'll fill them in on a new job.

  1. 1

    Spec section and submittal number

    Go through the spec book and list every submittal it calls for, numbered by section, for example 08 71 00-01 for the first door hardware submittal. Numbering by section means anyone can find an item from the spec.

    Watch for: submittals buried in Division 01 or in a general requirements paragraph. They're the ones that never make it onto the log.

  2. 2

    Description, type and responsible sub

    Say what it is ("panelboard shop drawings", not "electrical"), whether it's shop drawings, product data, samples or a mock-up, and which sub owes it.

  3. 3

    Required on site, lead time and submit-by date

    Start from the date the material has to be on site, subtract the fabrication lead time and the review time, and you have the date the sub must submit. Procore can work this back for you when its schedule calculations are turned on.

    Watch for: long-lead items like switchgear, elevators and curtain wall. Their submit-by dates often fall before the sub is even under contract.

  4. 4

    Ball in court and dates sent and returned

    Who has it right now, when it went to them, and when it came back. This is the column people check daily, so it has to be current.

  5. 5

    Action and revision

    Approved, approved as noted, revise and resubmit, or rejected, plus the revision number. A resubmittal keeps the same number with a new revision, so the history stays on one row.

  6. 6

    Closeout

    Mark the final approved revision. That's the set that goes into the closeout package and the O&M manuals.

Questions people ask

Do you provide a submittal log template?

Not a download. The columns above are the template, and they're quick to set up in a spreadsheet or your platform. What we build instead is a submittal log that updates its own status from reviewer replies and the schedule, so nobody has to maintain it by hand.

Can this flag submittals that are about to delay the schedule?

Yes. When each submittal is tied to the schedule activity it holds up, a late return shows up as a risk to that activity weeks ahead, not as a quiet overdue row. If your schedule and log live in different tools, n-frames connects the two.

Is a submittal log the same as a submittal register?

People use the words interchangeably. Some teams call the planned list pulled from the spec book the register, and the record of what's moving through review the log. Either way it's one row per required submittal.

Does Procore have a submittal log built in?

Yes. Procore's Submittals tool keeps the log, routes items through review workflows and tracks ball in court. Autodesk Build has its own submittals tool too. The gaps are usually around them: reviewers who reply by email, and approvals that never reach purchasing.

Is the submittal log quote really free, with no obligation?

Yes. It says what connecting your submittal log would take and what it costs. The decision is yours from there. See our construction automation page for the other jobs we connect on a project.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.