The Submittal Log Is a Procurement Schedule in Disguise

A submittal log should be built backwards from required-on-site dates, not forwards from spec section numbers. For each item, subtract delivery, fabrication, shop drawing production, two review cycles and subcontractor preparation from the date the material is needed in place. That arithmetic produces the date the submittal must be in the architect's hands. Sorted by that date, the log becomes a procurement schedule with a review process attached.

Why the spec-section log fails

Division 26 sits near the end of the specification. Switchgear has a lead time measured in quarters. A log sorted by section number puts the single most schedule-critical submittal on a project three-quarters of the way down the page, surrounded by items that could be approved the week before installation without consequence.

The failure mode is specific. The project engineer works the log top-down, closing out Division 3 and Division 4 items because they are at the top and they are easy. The electrical subcontractor submits switchgear in week nine instead of week three. The architect takes twenty-two days, returns it revise-and-resubmit over a feeder configuration, and the resubmittal lands in week sixteen. Nobody flags anything, because the log shows the item as "in review," which is a perfectly healthy-looking status.

Then in month eight, the vendor confirms a delivery date that sits four weeks past the electrical room energisation milestone, and the first genuinely urgent conversation about switchgear happens with no remaining options except premium freight, partial shipment or a schedule claim.

The log did not fail because data was missing. Every date was recorded. It failed because the log carried no information about consequence.

Submittal register vs submittal log

The two terms are used interchangeably on most jobs, which costs teams the distinction that actually matters.

	Submittal register	Submittal log
Purpose	Plan	Record
Built	Preconstruction, during buyout	Maintained through construction
Contents	Every required submittal, planned dates, responsible sub, lead time, required-on-site date	Actual transmittal dates, reviewer, revisions, disposition, days in court
Answers	When does this need to move	Where is it and who has it
Derived from	Specifications plus construction schedule	The register, plus actual activity

The register is the forecast; the log is the actual. Teams that only maintain a log can tell you where every submittal is and nothing about whether that is acceptable. Teams that build a register and then track against it can tell you, in week six, that three items are already behind the date they needed to move, which is a schedule conversation with months of runway rather than a delivery conversation with none.

In practice the two should live in the same record, with planned and actual dates side by side on each line. Two documents means two update cycles and a reconciliation nobody has time for.

How to build the submittal schedule

Build it during preconstruction, before the first subcontract is signed, so the dates become scope obligations rather than requests.

1. Extract every required submittal from the specifications. Part 1.3 of each section, plus anything the general conditions require. This is tedious and it is also the only step where completeness is fully within your control.

2. Assign each to a subcontractor and a required-on-site date. The required-on-site date comes from the construction schedule activity that consumes the material. If the schedule has no activity for it, that is a schedule problem the register just surfaced for free.

3. Subtract the procurement chain. Delivery time, fabrication duration, shop drawing production after approval, review duration, and the subcontractor's own preparation time. Confirm fabrication and delivery with the vendor during buyout rather than inheriting a number from the last job.

4. Assume more than one review cycle. Anything engineered, coordinated between trades or governed by performance criteria will come back revise-and-resubmit at least once. Switchgear, elevators, curtain wall, fire alarm, structural steel connections, and anything with a delegated design component. Planning a single cycle treats the normal outcome as an exception.

5. Write the resulting dates into the subcontract. A submittal date that exists only in your log is a preference. A submittal date in the subcontract exhibit is an obligation you can enforce during buyout conversations and, later, in a backcharge discussion.

6. Sort by required submittal date and publish the top twenty. Not the full register, which runs to several hundred lines and gets ignored. Twenty items, reissued weekly, each with the date it has to move.

Long lead item tracking

Long lead items deserve a separate track with different rules, because their float is consumed before anyone sets foot on site.

Flag any item where the procurement chain exceeds the available duration by more than a short margin. Typically: switchgear and distribution equipment, generators, elevators and escalators, curtain wall and unitised facade, chillers and major air handling units, custom structural steel, specialty doors and hardware packages, and anything imported.

For those items, do three things the standard log does not do.

Track the vendor's order date separately from the approval date. Approval is not the milestone that matters; the purchase order release is. An approved submittal sitting unpurchased for three weeks because of a credit hold burns the same float as a late approval and appears nowhere in a conventional log.

Hold a procurement review during buyout, with the subcontractor and the vendor, that confirms current fabrication lead times. Lead times quoted at bid and lead times at purchase order release are different numbers.

Escalate at the planned date, not the required date. If the item needed to be submitted by 14 March and it is 14 March, that is the escalation trigger. Waiting until the required-on-site date is at risk means waiting until the remedy costs money.

Delays on these items rarely arrive alone, and the same discipline that catches them early also reduces the downstream change orders they produce. The connection between slow approvals and schedule exposure is covered in more depth in our guide to preventing RFI and submittal delays.

Ball-in-court tracking

"In review" is not a status. It is the absence of one.

Ball-in-court tracking records a single party holding each submittal and the number of days they have held it. The field has to be singular. A submittal held jointly by the architect and the structural engineer is held by nobody, and will sit for a month while each waits on the other.

Four values cover most projects: subcontractor preparing, contractor reviewing, design team reviewing, and closed. A days-in-court counter runs against each, reset at every handoff, and compared to the contractual review duration in the general conditions.

What this changes is the weekly conversation. Instead of "where are we on submittals," the OAC meeting gets a list: six items with the design team past the fourteen-day review period, longest at twenty-two days, two of them long lead. That is a specific, dated, attributable record. If it later supports a time extension request, the days-in-court history is the evidence, and it is far stronger evidence than an email thread reconstructed after the fact. The broader case for keeping that record defensible is covered in our piece on audit trails in construction administration.

Ball-in-court also exposes your own delay. GCs lose real days in contractor review, particularly where a submittal needs coordination across three trades before it goes out. Tracking it honestly is the only way to find out whether the bottleneck is actually the architect.

Who owns the submittal log

The general contractor owns it. The contractor is responsible for procurement and for demonstrating compliance with the specification, and the log is the instrument of both.

The architect owns review and disposition, and almost always keeps their own tracking. That is fine until two logs disagree about whether a revision was received, at which point a dispute about facts replaces a dispute about substance.

Resolve it in the general conditions and at the first OAC meeting: one log is authoritative, it is the contractor's, the design team transacts in it, and disposition recorded there is the record of record. Owner's reps on larger programs will often want visibility into the same register rather than a weekly export, which is reasonable and should be granted. What owners should be asking at an OAC meeting includes exactly these questions about long lead approvals.

The administrative cost of running this well

The register above is more work than a spec-sorted list. The arithmetic is per-item, the dates change when the schedule changes, and ball-in-court only works if handoffs are logged as they happen rather than reconstructed on Thursday afternoon.

That work is where the method usually dies. A project engineer maintaining a submittal register in a spreadsheet, a schedule in separate software and correspondence in email spends several hours a week keeping three versions of the same truth aligned. Those hours are margin.

The argument for running submittals in the same system as the schedule, the subcontracts and the correspondence is that the maintenance disappears into the transaction. When the required-on-site date shifts because a schedule activity moved, the planned submittal date moves with it. When the architect returns a submittal, the days-in-court counter stops because the action was taken in the system rather than reported into it afterwards. This is what INGENIOUS.BUILD is built to do: hold submittals, commitments, schedule and the correspondence record as one connected set rather than four exports that have to be reconciled.

The test of a submittal log is narrow. On any Tuesday, can the project team name the three items most likely to miss their fabrication window, say who is holding each one and for how long, and show when it was escalated. A log sorted by spec section cannot answer that. A register built backwards from the schedule answers it without anyone having to go and look.