The submittal schedule (AIA term) or schedule of submittals (EJCDC term) is the calendar that protects your procurement chain, and gaps in it can result in long-lead procurement risk. CSI defines the schedule of submittals as the list of required contract submittals, when the contractor will deliver them to the design professional, and the duration allowed for review.
Construction teams can protect that schedule by building it backward from installation dates. This guide walks through that back-scheduling process, shows why a single missed long-lead window can trigger unrecoverable slip across the entire project, and explains how agentic AI is reshaping the way teams execute the workflow.
Who owns the submittal schedule and what AIA A201 requires
The contractor owns the submittal schedule, and the AIA A201 contract makes producing one a contractual obligation with real teeth. Under A201–2017 § 3.10.2, the contractor must submit a submittal schedule for the architect's approval "promptly after being awarded the Contract and thereafter as necessary to maintain a current submittal schedule." The schedule has to be coordinated with the construction schedule and allow the architect reasonable time to review.
The penalty for skipping it
A201 § 3.10.2 limits the penalty but makes it serious. If the contractor fails to submit a schedule or fails to provide submittals in accordance with the approved one, the contractor "shall not be entitled to any increase in Contract Sum or extension of Contract Time based on the time required for review of submittals."
So if you skip the schedule or miss its dates, you eat any delay costs tied to submittal review yourself, with no recourse to the owner for more money or more time.
When it's due and who else participates
The schedule is due early, before the procurement clock has burned. Spec procedures commonly require the initial schedule within roughly 30 days of Notice to Proceed. That schedule covers the first 90 days of submittals plus anything required early for long-lead manufacture.
The architect reviews and approves. The construction manager determines long-lead items during preconstruction, and subcontractors feed the dates. CMAA places long-lead item determination in the procurement and pre-construction phase.
The absence of a submittal schedule usually signals that the contractor has not planned the sequence of submittals, which is a serious flaw in the work plan.
Building a submittal schedule from the spec book
You build a construction submittal schedule by walking the spec book section by section, then back-scheduling every long-lead item from its installation date.
The submittal log captures what needs to happen and where things stand. The schedule captures when each step must occur to protect the install date.
Start with Division 01, then walk every technical division
Read the project's Division 01 first because it sets the review-period math that applies across the trade sections. On projects whose Division 01 includes Section 01 33 00, that section establishes the submittal procedures and project-wide review-period assumptions. The review period you find there, whether 14 days or 15 business days, is the baseline for the job.
Then walk the technical divisions, 02 through 49. Every spec section with a "Submittals" paragraph generates required items. Do not stop at headline trades. Supporting divisions can carry items that surface late if teams miss them (e.g., specialty coatings, acoustic treatments, access control, elevator finishes).
Identify the long-lead items
Flag every item whose procurement duration could affect installation, because those items drive the front end of your schedule. Start with divisions and systems that control downstream work, such as MEP equipment, structural steel, custom glazing, and conveying equipment.
For complex engineered equipment, the full procurement cycle can stretch across many sequential steps, including purchase requisition, bidding, purchase order issuance, vendor drawing approval, fabrication, inspection, assembly, packing, transport, and delivery.
Because each of those steps carries its own duration, and because current lead times vary by product configuration and market, the total cycle time is rarely something you can estimate from memory. That makes current supplier and subcontractor input non-negotiable before the team locks the schedule.
Back-schedule from the installation date
Set each submittal due date by working backward from when the material has to be on site. Start with the installation date from the master schedule, then subtract procurement lead time, design-team review, GC coordination review, and preparation time. What's left is the latest possible date the submittal can go out.
Take structural steel as an example. With a 14-week fabrication lead time and erection scheduled for week 20, the team needs design-team approval no later than week six. Once you back out the additional review and coordination time on top of that, shop drawing preparation may need to start immediately after award, leaving essentially no buffer between contract award and the first deliverable.
Logic-link procurement to the CPM
Back-scheduled dates only protect the project if they live inside the schedule everyone is already tracking. That schedule is the CPM (Critical Path Method) schedule, the master project timeline that maps every activity, its duration, and its dependencies to identify the longest sequence of tasks driving project completion. If a submittal isn't represented there, a slip on that submittal won't show up as a slip on the project.
So the next step is to connect each submittal-to-delivery chain as predecessor activities in the CPM. The full chain runs prepare shop drawings → review and approve → fabrication → delivery → install, and each node needs to live as a sequenced activity in the CPM.
That linkage is what makes the schedule self-reporting. When an approval date slips, the downstream construction activities shift automatically and the impact is visible immediately. Without it, teams cannot trace a missed delivery date to its schedule impact until after the delay happens.
Guidance from Navigant Construction Forum flags submittal review omissions as a scheduling failure mode for exactly this reason. When teams do not show review time before construction activity begins, the delay surfaces on the jobsite instead of on the schedule.
Why missed long-lead windows cause unrecoverable slip
A missed long-lead submittal window can become unrecoverable because the procurement chain is sequential. The hard sequence, prepare → review → approve → PO → fabricate → deliver → install, has little give once float runs out or the team loses a manufacturer production slot.
That is why review cycles matter. FMI's study of stressed projects found 33% had a poor-performing submittal process that could not keep pace with the schedule, with first-cycle approvals at only 25–50%.
Then float runs out. CMAA defines total float as the time an activity can slip without moving project completion. One resubmission cycle can consume all available float on a near-critical procurement activity. Once float hits zero, the activity can become part of the path that directly determines completion. The cascade is not contained to one trade. A rejected structural steel submittal can push downstream work, from mechanical rough-in to drywall and finishes, all the way to occupancy. By the time everyone aligns on the problem, expedited shipping is expensive or unavailable and the team may already have lost the available recovery window.
The package itself can create that extra cycle. A missing cover page, unordered supporting material, or inconsistent submittal structure can turn an on-time schedule date into a rejected submission. Datagrid's Submittal-Builder Agent connects to all of your systems and assembles complete, properly formatted submittal packages from cover page to final PDF.
Where manual submittal schedule building breaks down
Even teams that know how to build a submittal schedule the right way run into the same handful of failure points when they do it by hand. Most of them come down to incomplete information, broken sequencing, or starting too late to recover.
Here is where manual scheduling tends to break down:
The spec-book pull is incomplete. Manually reviewing a large register leaves room for omissions, and a missed submittal often surfaces late, after the procurement window has already closed.
Lead times are guessed or stale. Teams rely on memory or older assumptions, then get surprised when supplier-confirmed dates no longer match what the schedule was built around.
The schedule is not sequenced against the CPM. Teams build the log first and try to slot it into the project schedule as an afterthought. When submittal milestones live in a separate tracker, a slipped approval date stays buried there instead of surfacing as a schedule risk.
The list starts too late. The schedule should be drafted promptly after award, before the first long-lead procurement decisions face hard constraints. Teams that wait for the kickoff meeting have already burned their buffer on anything with an extended lead time.
Each of these failure points compounds the others. An incomplete pull feeds stale lead times into a tracker that isn't linked to the CPM, and by the time anyone notices, the recovery window is gone.
How agentic AI changes submittal scheduling
Agentic AI shifts the operating model from systems that read project files and wait for instructions to AI agents that reason through them and act. For submittal scheduling, that means the work around the schedule (pulling requirements, checking packages against specs, assembling submissions) no longer has to happen entirely by hand.
ENR reports that construction is approaching agentic AI use cases that automate repetitive workflows, including reviewing project files. The schedule itself still needs human sequencing, current supplier input, and CPM logic. What changes is the speed and reliability of everything that feeds into it.
Datagrid's AI agents can review material submittals against project specifications, identify non-compliant items, and track approval status across connected project files including contracts, specifications, submittals, RFIs, change orders, and compliance records. When the schedule says a formal submittal is due, the Submittal-Builder Agent assembles the package itself, so the submission has a consistent structure before it reaches owner or design-team review.
Where Datagrid's agents fit into the workflow
At a high level, Datagrid's agentic AI approach covers three parts of the spec-to-submittal workflow:
Find requirements faster. Agents search across specifications, drawings, RFIs, and submittals to surface what's required, grounded in actual project records.
Catch gaps before review cycles. Agents compare submittals against specs to flag compliance issues before they trigger a rejection.
Assemble the package. Agents build complete, properly formatted submittal packages from cover page to final PDF, enforcing consistency every time.
The net effect is earlier visibility and fewer surprises. Teams can see what's required and check what's been prepared before a submission goes out, while the kickoff buffer still protects long-lead items.
Protect the schedule before the schedule breaks the project
The submittal schedule is the difference between identifying a long-lead steel package early and discovering it after the approval window has tightened. You know how to build one. Can your team read every spec section and keep every lead time current on every project? Can it package every formal submittal cleanly and link it all to the CPM, by hand, every time?
See how the Submittal-Builder Agent parses the spec book, flags long-lead items, and surfaces schedule conflicts before they cost you a production slot.
