Construction administration
9 min readAll explainers

Submittal log and spec-section compliance — a primer for architects.

A practical submittal-log and spec-section compliance primer for architects: the fields every log needs, the status codes and due-back dates that protect a 14-day review turnaround, and the admin cadence that keeps returned shop drawings reconciled to the master register.

Written by Johnston Admin Management Services LLC · Virginia HQ, U.S. nationwide.
Section 1

Make the submittal log a control document not a list of filenames

A reliable submittal log lets an architect answer three questions without searching across email: what was required, what was received, and what can proceed. That only works when the row carries enough context to connect the contractor's package to the project manual and the review decision back to the returned shop drawing.

Treat these five fields as the minimum on every row: the submittal number, the spec-section reference, the product data sheet or required backup, the status code, and the due-back date. Description, responsible trade, date received, reviewer, revision, date returned, and file links complete the operational trail without turning the register into an unstructured notes column.

The required row

01 · Submittal #

A stable identifier that survives revisions and resubmittals.

02 · Spec section

The project-manual section that governs the submittal.

03 · Product data

The product data sheet, shop drawing, sample, or required backup.

04 · Status code

The exact decision: approved, approved-as-noted, revise-and-resubmit, or rejected.

05 · Due-back date

The date the architect's review is due, calculated from a complete receipt.

Section 2

Make the status code tell the field team what happens next

A status is not a color in a spreadsheet; it is a direction. The architect's response must tell the contractor whether work can proceed, whether comments must be incorporated, or whether the package must come back for another review. Keep the code, the review comments, the reviewer, and the returned date together.

Proceed with a record
Approved means the submitted item satisfies the review. Approved-as-notedmeans it can proceed only with the comments incorporated. Preserve the notes in the returned file so the field team has the same direction the architect saw.
Hold for a new answer
Revise-and-resubmit means the package needs correction before the affected work proceeds. Rejectedmeans it does not satisfy the project requirements and needs a replacement or a documented design decision. Neither should disappear when the next revision arrives.

Keep the prior status visible in the revision history. A current row that says “approved” without showing that the previous submission was “revise-and-resubmit” loses the decision trail that protects the architect when the same detail is questioned later.

Section 3

Keep the queue current before the 14-day clock runs out

The due-back date is the simplest way to turn a contract review period into a working queue. Start the clock when a complete submittal is received, not when an incomplete email first appears. Mark missing product data or drawings as an intake exception, then keep the original receipt and the corrected receipt visible.

A short daily queue check surfaces items due soon, items waiting on the architect, and items waiting on the contractor. A weekly look-ahead protects the next review cycle. If a date changes, record why: an incomplete package, an agreed extension, a resubmittal, or a scope decision. Moving a date without the reason makes the register look current while the project remains exposed.

The cadence that protects turnaround

At intake

Number it, link the spec section, confirm the package is complete, and set the due-back date.

Each morning

Sort by due date and next owner so the 14-day queue is visible before an item becomes late.

On return

Record the status, comments, returned file, and next due-back date for any resubmittal.

Section 4

Use the spec section to stop shop-drawing drift

A shop drawing can be internally consistent and still fail the project manual. The spec-section reference gives the architect the governing checklist: required performance, finish, manufacturer, testing, installation, accessories, and substitution requirements. Without that anchor, review becomes a visual comparison against the last drawing instead of a compliance check against the contract documents.

The reference also keeps revisions connected. When the contractor resubmits a detail, the architect can compare the changed item to the same section and see whether the correction addressed the original comment. That stops a plausible detail from drifting away from the specified assembly over several rounds of shop drawings.

The spec-to-drawing check

Start with the section: identify the paragraph and requirement that governs the product or assembly.

Check the returned drawing: compare materials, dimensions, performance, accessories, and interfaces—not just the geometry on the sheet.

Carry the result forward: link the response and revision to the same submittal number so the next review starts with the contract requirement in view.

Section 5

Let admin support reconcile the register and returned drawings

The master submittal register is only useful if it agrees with what actually came back from review. Admin support can run that reconciliation as a repeatable queue: match each returned shop drawing and product data sheet to its submittal number, confirm the spec section and revision, record the status and review date, and carry any revise-and-resubmit action into the next cycle.

The result is an exceptions list for the architect, not a second inbox. It calls out a returned file with no register row, a register row with no returned file, a status that does not match the review comments, a changed revision that was closed instead of carried forward, or a due-back date with no owner. The architect keeps the design decision; the admin cadence keeps the record complete. See our construction administration support for architects for the broader workflow.

Reconcile these six points
  • Submittal number and revision match the returned file.
  • Spec-section reference matches the project-manual requirement.
  • Product data sheet or shop drawing is present and linked.
  • Status code matches the review comments and stamp.
  • Review date and next due-back date are current.
  • Open revise-and-resubmit items remain visible in the master register.
FAQ

Frequently asked questions.

What fields belong in an architect’s submittal log?

At minimum, each row should identify the submittal number, the project manual spec-section reference, the product data sheet or other required backup, the status code, and the due-back date. Add the description, responsible contractor or trade, date received, date returned, reviewer, and returned-shop-drawing link when those fields support your project workflow. The point is to make each submittal traceable from the specification requirement to the architect’s response and back to the master register.

What do approved, approved-as-noted, revise-and-resubmit, and rejected mean?

Approved means the submitted product or document can proceed as reviewed. Approved-as-noted means it can proceed only with the review comments incorporated. Revise-and-resubmit means the submittal needs a corrected submission before the affected work should proceed. Rejected means it does not satisfy the project requirements and needs a replacement or a documented design decision. Keep the exact status code, review comments, and return date together so the field team cannot mistake a conditional response for an unconditional approval.

How does a due-back date protect the 14-day review turnaround?

Set the due-back date when the submittal is logged, based on the contract review period and the date a complete package was received. A visible due-back date turns the 14-day review turnaround into a queue the architect can manage: items due this week rise to the top, incomplete packages can be returned for missing information, and an approaching deadline is visible before it becomes an escalation. The date should be updated only with a traceable reason, not silently moved to make an overdue item look current.

Why should every submittal point to a spec-section reference?

The spec-section reference anchors the product data sheet and shop drawing to the project manual requirement that governs it. It lets the reviewer check the right performance criteria, finish, manufacturer, testing, and installation language instead of reviewing a drawing in isolation. That link prevents shop-drawing drift: a detail can look reasonable while quietly departing from the section that controls the specified assembly, approved substitutions, or required accessories.

How often should an architect update the submittal log?

Update it at intake, after the completeness check, when the review is assigned, when the response is returned, and whenever a resubmittal or clarification changes the next action. A daily short queue review plus a weekly reconciliation is usually enough to protect the 14-day turnaround without making the log a second inbox. The current register should always show what is waiting on the contractor, what is waiting on the architect, and what has been returned to the field.

What does admin support reconcile against returned shop drawings?

Admin support reconciles the master submittal register to the shop drawings and product data sheets returned by the architect: submittal number, spec section, revision, status code, review date, comments, and the next due-back date. The reviewer also checks that every returned drawing has a matching register row, every register row has the correct returned file, and a revise-and-resubmit item is carried forward rather than closed. Any mismatch becomes an exception for the architect or project manager to resolve.

TL;DR

The six-field version.

  • Make submittal number, spec-section reference, product data sheet, status code, and due-back date mandatory fields—not optional notes.
  • Use approved, approved-as-noted, revise-and-resubmit, and rejected consistently so the field team knows what can proceed.
  • Keep the queue current at intake, return, and resubmittal points so the 14-day review turnaround is visible before a deadline is missed.
  • Tie every shop drawing to the project manual section that governs it; that reference is the control against drawing drift.
  • Reconcile the master register to returned files and carry open revisions forward instead of closing the paper trail early.
Who this helps

For architects.

Keep submittals tied to the project manual, current specs, and decision trail so the architect can see what needs attention next.

Explore support for architects
Send the register and the review starts

Keep every submittal on the architect's radar.

Send the project manual, master register, and returned shop drawings. We'll keep the fields current, protect the 14-day review queue, and reconcile the files at $45/hour, billed to the exact minute.

Spec-linked · status-controlled · Clockify-tracked
Read next
Architects

The construction administration handoff checklist.

Start the CA package with the logs, spec set, distribution record, and inbox cadence the project needs after CDs are issued.

Services

Construction administration support for architects.

Keep the submittal, RFI, and ASI queues moving while architectural decisions stay with the architect.