Project delivery

What is a submittal log in construction?

A submittal log is the running list of every submittal a project requires, with its spec section, who is responsible, where it sits in review, and the date it must come back to keep the schedule.

Two construction professionals compare an aluminum frame sample with shop drawings in a site office.
Check the proposed sample and coordinated drawings before releasing fabrication. AI-generated illustration.

A submittal log (sometimes called a submittal register) is the GC's master tracker for every submittal on the job. Each line is one package: a spec section, a description, the sub or supplier who owes it, the dates it went out and came back, and the review result. A good log answers one question fast: what is holding up procurement right now?

The log usually starts at buyout. The project engineer reads every spec section, lists each required item, and assigns it to the sub who bought that scope. On a mid-size commercial job, that first pass can produce a few hundred lines.

Columns most logs include

Typical submittal log columns
ColumnWhy it matters
Submittal number and revisionKeeps resubmittals tied to the original
Spec section and descriptionShows exactly which requirement it answers
Responsible sub or supplierTells you who to chase
Required by dateBack-calculated from the install date and lead time
Date sent to reviewerStarts the review clock
Date returned and actionApproved, approved as noted, revise and resubmit, rejected
Lead time after approvalShows when material will actually arrive
Ball in courtWho has it today: sub, GC, architect, or engineer

How the log works week to week

Say a GC is building a $6 million school addition and the storefront sub says its aluminum takes 10 weeks to fabricate after approval. The framed openings are scheduled to be ready on week 22. Working backward, the material has to be ordered by week 12, so the approved shop drawings must be back by week 11. With a two-week review window and one likely resubmittal, the sub needs to send the first package by week 7.

That required-by date goes in the log. Every Monday the project engineer sorts the log by that column and looks at anything within two weeks of it that is not yet approved. Those lines go on the agenda for the weekly meeting and onto the three-week look-ahead. Lines that are late get a note explaining whose court the ball is in, which becomes important if the delay later turns into a claim.

  • Sort by required-by date, not by spec section, when you review it.
  • Track resubmittals as revisions of the same number so the full history stays together.
  • Record review time per reviewer. If the architect is averaging three weeks, raise it early.
  • Keep informational items (warranties, O&M data) on the log too, so closeout does not stall later.

Common submittal log mistakes

  1. Building the log from memory instead of from the spec. Missed sections show up as surprises during inspections.
  2. Logging dates sent but not dates returned, so nobody can prove how long review took.
  3. Keeping a separate log per sub, which hides conflicts between trades.
  4. Letting the log go stale. A log updated once a month is history, not a tool.

Related terms

The submittal log is the companion to the RFI log and the drawing log, and it feeds the submittal schedule. Start with the free submittal log template. Smart Business Automator keeps the log in one shared place and flags items approaching their required-by date; see RFI and submittal tracking automation.

Frequently asked questions

Who keeps the submittal log?

Usually the general contractor's project engineer or project manager. Subs often keep their own lists, but the GC's log is the one used in meetings and disputes.

What is the difference between a submittal log and a submittal schedule?

The schedule plans when each submittal should be sent and returned. The log records what actually happened. Many teams keep both in one sheet.

Should the architect see the submittal log?

Yes. Sharing it at each meeting shows the design team what is waiting on them and when it is needed, which tends to shorten review times.

How long should the log be kept after the job?

Keep it with the project records. It is often the best evidence of who caused a procurement delay if a claim comes up later.

Written and edited by

Maurice Francois writes and edits construction operations guides for Smart Business Automator. More from Maurice on the Scaling Legends podcast.

Get a free assessment