The submittal schedule: how to build one that protects the job

By Adam Chandler, founder of Pangea · September 1, 2026

A submittal schedule is the dated plan for getting every submittal the specifications require approved before the work that depends on it has to start. It takes the list of required items and puts four dates on each one: when the subcontractor sends its package, when the general contractor transmits it, when the architect returns it, and when the material has to be released for fabrication. On AIA contracts the general contractor owes the architect one shortly after award, and skipping it has a specific cost — the contractor gives up its right to claim extra time for submittal review.

Most teams treat the submittal schedule as paperwork for the owner. It is better understood as the earliest warning system a project has. A submittal that slips two weeks in October is a conversation. The same slip discovered in February is a crew standing in an empty room.

What does a submittal schedule actually do?

It converts a list into deadlines. The specifications tell you a project needs shop drawings for structural steel, product data for the roofing membrane, samples for the exterior masonry. That list has no dates on it. The submittal schedule is what happens when someone sits down with the construction schedule and asks, for each item, how late it can be approved before it starts pushing the job.

The answer is almost never "a few weeks before we need it." Approval is not the last step before installation; it is the step that lets somebody place an order, and the order starts a fabrication clock the project does not control.

Is a submittal schedule required by contract?

On AIA contracts, yes. Section 3.10.2 of AIA Document A201-2017, the General Conditions of the Contract for Construction, requires the contractor to submit a submittal schedule for the architect's approval promptly after being awarded the contract, and to keep it current afterward. The schedule has to be coordinated with the contractor's construction schedule and has to, in the document's words, "allow the Architect reasonable time to review submittals." The architect's approval cannot be unreasonably delayed or withheld.

The part worth reading twice is the consequence. Under the same section, a contractor who fails to submit a submittal schedule, or who fails to provide submittals in line with the approved one, is not entitled to any increase in contract sum or extension of contract time based on the time review took. In plain terms: no submittal schedule, no delay claim for slow reviews. The document that looks like an administrative chore is the same document that preserves the contractor's leverage if reviews drag.

Section 3.12.5 completes the loop: submittals are provided in accordance with the approved schedule, or, absent one, with reasonable promptness in a sequence that causes no delay. Reasonable promptness is a standard that gets argued about after the fact. Dates on an approved schedule do not.

How is a submittal schedule different from a submittal log?

The schedule is about dates that have not happened yet. The log is about status that has. A schedule says the air handling unit submittal has to be approved by November 3. A submittal log says where that submittal is at this moment: sent October 20, under review, or returned marked revise and resubmit.

They are two views of the same rows, and most teams keep them in one spreadsheet with planned dates beside actual ones. That arrangement is the point: the gap between the two is what tells you whether the job is ahead or behind on procurement.

How do you build a submittal schedule?

Work backward from the installation date, not forward from today. Every date on the schedule is derived from a date on the construction schedule, and the arithmetic runs in reverse: installation, then delivery, then fabrication, then approval, then review, then submission.

Here is that count worked through for a single piece of equipment. The durations below are illustrative placeholders. Real ones come from the contract's review window and the supplier's quoted lead time, and getting those two numbers right is most of the work.

A March installation needs the subcontractor working on its package in late September. That five-month gap is the reason submittal schedules get built in the first few weeks of a job rather than when the work approaches.

Two adjustments make the number honest. First, add a full second cycle for anything likely to come back marked revise and resubmit, because a rejected submittal spends the architect's review window twice plus the subcontractor's rework time in between. Second, check whether the review duration in the specifications is calendar days or working days. Fourteen working days is nearly three calendar weeks, and teams that mix the two units are usually the ones surprised in February.

What columns belong in a submittal schedule?

Enough to answer "what is late, and what does late cost us" without opening another document. These are the columns worth having, and you can build the whole thing in a spreadsheet:

• Submittal number, using the specification section it comes from, so numbering matches the specs rather than the order items were noticed.
• Specification section and paragraph, so anyone can check the requirement against the source.
• Description of the item in words a field superintendent would use, not just the spec title.
• Type: shop drawing, product data, sample, mock-up, certificate, or closeout document. Types carry different review effort.
• Responsible subcontractor or supplier, named as a company and a person.
• Related activity on the construction schedule, with its activity ID if the job runs a CPM schedule. This is the link that makes the rest of the row mean something.
• Installation start date, copied from the construction schedule.
• Quoted lead time, in weeks, with the date the quote was given. Lead times move, and an undated lead time is a guess.
• Required approval date, calculated backward as shown above.
• Planned submission date to the general contractor.
• Planned transmittal date to the architect.
• Review duration allowed, with calendar or working days stated explicitly.
• Actual dates for each of those steps, kept beside the planned ones.
• Current status and stamp action from the most recent review.
• Resubmittal count, because a third pass on the same item is a signal about the item or the reviewer.
• Float in days, meaning required approval date minus projected approval date. Sort by this column and you have your agenda.
• Long-lead flag, so the critical items stay visible when the sheet grows past two hundred rows.

Sorting by float rather than by specification number is the change that makes the sheet useful in a meeting. Spec order tells you where an item lives. Float order tells you what to talk about.

Which submittals should be scheduled first?

Anything with a long fabrication clock or a dependency underneath it. In practice that means switchgear, transformers, generators, elevators, air handling units and chillers, structural steel, curtain wall and glazing, custom millwork, and specialty doors and hardware. These are the items where a two-week submittal slip turns into a six-week delivery slip, because the manufacturer's queue does not hold a place for a project that missed its release date.

Items that gate other trades deserve the same attention even when their own lead time is short; an approved anchor bolt layout is small on the page and blocking underneath it. The preconstruction meeting is the natural place to settle all of this, while the subcontractors who know the real lead times are still in the room.

Why do submittal schedules go stale?

Because they are built once and updated by hand. The schedule is accurate the week it is approved. Then a lead time changes on a subcontractor call, a review window gets renegotiated in an OAC meeting, an item comes back revise and resubmit, and the construction schedule shifts an installation date. Each of those is a change to the submittal schedule, and almost none of them arrive looking like one.

They arrive as sentences in meetings. Somebody says the switchgear lead time went from fourteen weeks to twenty, everyone understands what that means, and whether it reaches the spreadsheet depends on who was in the room and what they wrote down. A schedule that no longer matches what people said out loud is worse than no schedule, because the team still trusts it. The A201 protection depends on this too: the obligation in 3.10.2 is to maintain a current submittal schedule, not to have produced one in month one.

Where Pangea fits

Pangea is an AI notetaker built for architecture, engineering, and land-development firms, and it exists because of the gap described above. It records meetings without a bot joining the call, writes minutes in your firm's own format, and files every meeting, decision, and document to the right project automatically. When a subcontractor says on a Tuesday call that a lead time moved, that sentence is captured, attached to the project, and searchable later with its source cited, rather than living in one person's notebook.

It also answers questions across a project's history. Asking when the switchgear lead time changed, and who said so, returns the answer with the meeting it came from. For teams that keep a submittal schedule in a spreadsheet, that is the difference between updating it from memory and updating it from the record. We will connect the PM software you already run, so approved updates land there with a click rather than being retyped.

It is built for the person who keeps the logs current. If that is your role, the project coordinator page covers it in more detail, and pangeanotes.com has the rest. The trial is 14 days with no credit card.

The short version

Build the submittal schedule in the first weeks of the job, count backward from installation dates rather than forward from today, put the long-lead items in first, and keep a float column you can sort. On AIA contracts, the schedule is not optional and not free to skip: without a current one, slow reviews stop being the architect's problem and become the contractor's.