What is a submittal schedule and why does it matter?
A submittal schedule is a schedule submitted by the contractor listing all proposed submittals at the initial stage, to ensure every item is captured and project performance is not impacted by delayed submittal approvals. It matters because lead time does not start until a submittal is released to fabrication — so every review cycle sits in front of every long-lead item. Most contracts require one; few contractors produce it.
How the schedule is built
The register is mined from every specification section’s submittal requirements at mobilisation, before construction starts — so nothing is discovered missing at the moment it is needed.
Each item then gets a required-on-site date, back-calculated through the procurement chain: required-on-site, minus lead time, minus at least two review cycles. Planning for a single review cycle is planning to be late — the common contractual window is 10–14 days, and a package rejected twice loses four to six weeks before a single week of manufacturing begins.
Why it protects both sides
For the contractor it is the best delay defence available: an approved schedule establishes when each submittal was due in and when the response was due back, which is what an extension-of-time argument rests on.
For the consultant it is protection against submittal dumps — 300 packages landing in one week, after which every contractual review window becomes fiction.
References
- module: /modules/submittals/ — submittal register, review windows and long-lead back-calculation
Zepth is the construction project delivery platform — it runs construction, procurement and asset management on one record, and does the work: reading the drawings, reviewing the submittals, matching the invoices and flagging the risks, with a human sign-off on anything consequential.
Related questions
See Zepth on your project.
A short, tailored walkthrough on your real workflow — no generic demo.
Book a meeting