Esc

↑↓ move↵ openIndex · Pagefind

How to track submittals so long-lead items arrive on time

A submittal log only helps if someone works it every week. Here is how to set submit-by dates from the schedule, what to check each week, how to handle revise-and-resubmit, and how to spot the long-lead item that is about to make the job late, with a worked register snapshot.

Charley Forey6 min readSubmittalsProject managementSchedule
On this page
  1. Step 1: Tie every line to a date the schedule cares about
  2. Step 2: Work back to a submit-by date
  3. Step 3: Put the dates in the subcontracts
  4. Step 4: Review before you forward
  5. Step 5: Work the register every week
  6. Step 6: Handle the return correctly
  7. Step 7: Track delivery until it’s on site
  8. Worked example: a register snapshot on March 2
  9. Common mistakes
  10. How os.construction handles it
  11. FAQ

To track submittals, keep one register with a line for every item the specs require, set each line’s submit-by date by working backward from the date the material must be on site, and review the register every week: sort by submit-by date, check who has the ball in court on each open item, chase anything late, and watch long-lead items most closely. Approved items then need their delivery dates tracked until the material is on site.

Building the register is a one-time job; the submittal register entry covers how to build one from the specs. This post is about the weekly routine that keeps it useful. A register that’s built carefully and then left alone tells you, months later, exactly which item made the job late.

Step 1: Tie every line to a date the schedule cares about

A submittal has no real due date until you know when the material has to be on site. For each line, find the schedule activity it feeds and take its start date, minus any time needed for receiving and staging. That’s the required-on-site date. Items with no date tied to the schedule all look equally urgent, which means none of them are.

Step 2: Work back to a submit-by date

Then subtract, in order:

  1. Lead time: fabrication and delivery after approval. Ask the supplier, not last year’s job.
  2. Design team review: the period in the contract or Division 01.
  3. GC review: the time your own team takes to check it before it goes out.
  4. One resubmittal: time to revise plus time to re-review. Long-lead and complex items are the ones most likely to need it.

submit-by date = required on site − lead time − design review − GC review − resubmittal allowance

Working back from the required-on-site date to the submit-by dateA timeline for an elevator submittal. Reading right to left from the required-on-site date of August 31: 126 days of fabrication and delivery lead time, 14 days of architect review, 7 days of GC review and 21 days of resubmittal allowance, giving a submit-by date of March 16, 168 days earlier.RESUB 21GC 7ARCH 14LEAD TIME 126 DAYSSUBMIT BY MAR 16ON SITE AUG 31168 DAYS BEFORE IT IS NEEDED
Every day an item is submitted late comes out of the resubmittal allowance first. Illustrative.

Step 3: Put the dates in the subcontracts

During buyout, write each sub’s submittal list and submit-by dates into its scope. A date the sub agreed to in the subcontract is far easier to enforce than one they first see in an email in March. This is also the time to confirm lead times with the people actually placing the orders.

Step 4: Review before you forward

Under AIA A201, the contractor reviews and approves submittals before sending them to the architect, and by submitting them represents that it has checked and coordinated them with the contract documents. Check that the submittal is complete, matches the spec section, and fits with adjacent trades before it goes out. A submittal returned for something you could have caught costs the whole resubmittal allowance.

Step 5: Work the register every week

Set a fixed time, usually the day before the OAC meeting, and go through it in this order:

  1. Late to submit. Past the submit-by date and not received. Call the sub.
  2. Overdue in review. Submitted, past the review period, not returned. Check who has the ball in court and chase that person.
  3. Coming due in the next three weeks. Remind the sub now.
  4. Returned but not acted on. A revise-and-resubmit that hasn’t come back.
  5. Approved but not ordered, or ordered without a confirmed delivery date.

Record the dates as they happen: received, sent, returned, action. Those dates are what show later whether a delay sat with the sub, the GC or the reviewer.

Step 6: Handle the return correctly

Reviewers’ action codes vary, but the usual set means:

  • Approved: proceed.
  • Approved as noted: proceed, incorporating the notes, unless the notes ask for a resubmittal.
  • Revise and resubmit: correct and send it again before proceeding. Log it as a new revision of the same item, not a new item, so the register shows how many rounds it took.
  • Rejected: doesn’t meet the requirements; start over.

Send approved submittals to the field and to every trade that needs them, so the people installing the work have the approved version.

Step 7: Track delivery until it’s on site

Keep tracking after approval. Once an item is released, record the confirmed delivery date and compare it with the required-on-site date. A supplier’s date drifting later is the same risk as a late submittal, just a month further along.

Worked example: a register snapshot on March 2

Illustrative numbersA made-up register. Every line uses 7 days of GC review, 14 days of architect review and 21 days for one resubmittal (42 days in total), all calendar days.
Spec section Item Required on site Lead time Submit-by Status on March 2
08 11 13 Hollow metal frames Jun 1 56 days Feb 23 Submitted Feb 20; with architect
07 54 23 TPO roofing product data May 4 21 days Mar 2 Not received; due today
14 24 00 Hydraulic elevator Aug 31 126 days Mar 16 Not received; sub now says Mar 30
26 24 16 Panelboards Jul 13 70 days Mar 23 Submitted Feb 5; returned revise and resubmit Feb 26
09 91 23 Interior paint samples Aug 3 14 days Jun 8 Not due

Each submit-by date is the on-site date minus the lead time and the 42 days. The frames, for example: June 1 minus 56 days is April 6, minus 42 days is February 23.

The line that matters is the elevator. If it arrives March 30, two weeks late:

  • GC review to April 6, architect review to April 20, approved first time.
  • April 20 plus 126 days of lead time is August 24. It arrives a week before it’s needed.
  • If the architect returns it revise and resubmit, add 21 days: September 14, two weeks after it’s needed.

So the late submission has used up most of the resubmittal allowance before anyone has looked at the submittal. That’s worth raising now: call the sub, ask what’s holding it, offer a pre-submittal review with the architect if the issue is technical, and put it on the OAC agenda. The panelboards, by contrast, look worse on paper (already returned once) but were submitted more than six weeks early. Revised by March 5 and re-reviewed by March 19, they arrive around May 28, well ahead of July 13.

The paint samples are fine. Sorting by submit-by date rather than by spec section is what shows the elevator as the item to chase this week.

Common mistakes

  • Building the register and then not working it. It goes stale within weeks.
  • No required-on-site dates. Everything looks equally urgent.
  • Overwriting a line on resubmittal. You lose the count of rounds and the review history.
  • Not recording review time. Reviewer delay is invisible when you need to show it.
  • Ordering before approval without written agreement from the owner.
  • Forgetting closeout submittals such as warranties, O&M data and attic stock until the end.

The free submittal log CSV has these columns with submit-by and late-flag formulas built in.

How os.construction handles it

The Submittals tool lists each item with number, revision, spec section, type, status, ball in court and due date. Create from Spec Sections generates a draft submittal for each section you pick. Each submittal records submit-by and due dates plus delivery tracking (lead time, required on-site date, confirmed and actual delivery), and an ordered approval workflow shows each step’s due date and response. The log opens with the weekly queues from this routine: overdue in review and waiting for resubmittal, plus a procurement follow-up for approved items: procurement at risk (passed targets or late forecasts), release due in the next 14 days, and partly entered delivery plans. The release target is the required-on-site date minus the lead time, and approval alone doesn’t count as ordered or received. From an approved revision a buyer can prepare a purchase request that a different person approves before it becomes a draft purchase order. The submittals walkthrough follows one through revise and resubmit to approval, and construction submittal software covers what to look for in any submittal tool.

FAQ

How do you track submittals in construction?

Keep one submittal register with a line for every item the specs require. Give each line a required-on-site date from the schedule, a lead time and a submit-by date worked backward from those. Every week, sort by submit-by date, check who has the ball in court on each open item, and chase anything late to submit or overdue in review.

How do you calculate a submittal's submit-by date?

Start from the date the material must be on site and subtract the fabrication and delivery lead time, the contract review periods for the GC and the design team, and an allowance for one resubmittal. Illustrative: on site August 31, 126 days of lead time, 7 days GC review, 14 days architect review and 21 days for a resubmittal gives a submit-by date of March 16.

What does approved as noted mean on a submittal?

The reviewer accepts the submittal subject to the notes or corrections marked on it. The contractor can usually proceed with fabrication incorporating the notes, without resubmitting, unless the notes say to resubmit. Revise and resubmit means the submittal has to be corrected and reviewed again before work proceeds.

Who is responsible for tracking submittals?

Usually the general contractor's project engineer or project manager keeps the register, and each subcontractor is responsible for preparing and delivering its own submittals on time. Under AIA A201 the contractor reviews and approves submittals before sending them to the architect.

Should material be ordered before the submittal is approved?

Generally no. Releasing fabrication before approval means paying for changes if the reviewer marks it up. Where the schedule truly forces it, get the owner's agreement in writing and understand the risk.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file