The contractor’s formal evidence of how it intends to comply with the design — and the review cycle that quietly controls the critical path.
Last updated
Zepth Core module
10–14 days
the common contractual review window per submittal cycle
Common specification convention
Case law is inconsistent: one tribunal found 10–12 weeks reasonable, another found more than 14 days unreasonable. The contract and the approved submittal schedule decide it.
4–6 weeks
lost by a package rejected twice — before a single week of manufacturing begins
Two review cycles at the contractual window
2–3 weeks
added by each rejection cycle before fabrication can start
Industry convention
A submittal is the contractor’s formal evidence of how it intends to comply with the design: shop drawings, product data, samples, mock-ups. The consultant reviews and returns each one with a response code, and nothing gets fabricated, ordered or installed until that cycle completes. Which is why submittals — not concrete — quietly control the critical path.
Zepth keeps the register, the submittal schedule and the review workflow in one place. Every submittal carries its spec reference, response history, current code and — critically — its downstream procurement linkage, so the team sees “this approval is now blocking the chiller delivery” while it is still a two-day problem.
Every long-lead item on a project sits behind a submittal. The procurement chain runs: submit → review → approve → release to fabrication → lead time → ship → install. Lead time doesn’t start until release — so every day in the review cycle sits in front of the switchgear, the curtain wall, the chillers, the lifts.
A submittal package rejected twice loses four to six weeks before a single week of manufacturing begins. Miss the required-on-site date on one critical item and the path slips; because a late submittal is usually contractor-caused, the extension of time is usually denied.
Review windows are contractual: 10–14 days is the common specification, but the case law is famously inconsistent — one tribunal found 10–12 weeks reasonable, another found more than 14 days unreasonable. What decides it is the contract language and the approved submittal schedule, which is exactly why both deserve more attention than they usually get.
The response codes carry legal weight. “Approved / No Exceptions Taken”, “Approved as Noted”, “Revise and Resubmit”, “Rejected” — or the A/B/C/D letter codes used on government and GCC projects. Each has consequences: fabricating off “Approved as Noted” without confirming the notes is a classic dispute; “Revise and Resubmit” stops the procurement clock entirely.
Review is not approval — but liability is real. Under AIA A201 the consultant reviews only for conformance with design intent; dimensions, quantities, coordination and means-and-methods remain the contractor’s responsibility, and approval doesn’t excuse deviations unless they were specifically flagged in writing. The limits of that protection were written in the hardest way possible: the 1981 Hyatt Regency walkway collapse, which killed 114 people, turned on a fabricator’s connection redesign shown on shop drawings that the engineer of record reviewed without re-analysis. The doctrine since: stamp language reduces designer exposure; it does not eliminate it, especially where a shop drawing contains a design change.
The submittal log is built from the specification. A proper register is mined from every spec section’s submittal requirements before construction starts, and linked to the construction schedule. Most contracts require a submittal schedule; few contractors produce one — yet it is the contractor’s best delay defence and the consultant’s protection against submittal dumps.
Substitutions are not submittals. “Or-equal” and substitution requests follow their own procedure, with the burden of proof on the contractor. Sneaking a substitution through as a routine submittal is a reliable way to create a dispute.
No register, and items are discovered missing at the moment they are needed. No schedule, and the consultant receives 300 submittals in one week — every review window becomes fiction. No long-lead linkage, and an approval that was “only” two weeks late surfaces three months later as a missed delivery. No deviation flagging, and non-conforming work gets installed with an approval stamp on it, followed by a fight about who pays for the rework.
Industry sources commonly cite roughly a third of submittals rejected on first review — each rejection cycle adding two to three weeks or more before fabrication can begin. Treat that figure as a directional signal rather than a benchmark: no rigorous public study of first-pass rejection rates exists.
Long-lead items stop being a surprise — every submittal is linked to what it is blocking, so a two-day problem is visible as a two-day problem.
The review clock is enforced — routing follows your actual approval chain, and the contractual window is tracked rather than hoped for.
Fewer rejection cycles — deviations, missing certifications and non-conforming products are caught in the first pass, not the second.
A defensible record — the full response history stands ready for any dispute about who took how long.
Build the submittal register from the specification sections, with required-on-site dates back-calculated through lead time and review cycles.
A/B/C/D letter codes or US stamp language — configured to your contract and applied consistently, with the consequences of each code made explicit.
Every submittal is linked to the long-lead item it releases, so a delayed approval surfaces as a threatened delivery date.
Full version history against prior review comments, so a resubmittal can be checked against what was actually asked for.
Routing to the responsible reviewer and specialist consultants, with the contractual window tracked and overdue reviews escalated.
Mined from the spec sections at mobilisation. Every item gets a required-on-site date, back-calculated through lead time plus at least two review cycles.
The GC reviews and stamps before submitting. Consultants return unstamped submittals without action.
Within the contractual window, with specialist sub-routing where needed. Delegated-design items — steel connections, curtain wall — are reviewed for design criteria only.
A/B — proceed, incorporating the notes. C — revise and resubmit, and the clock restarts. D or rejected — back to the start.
Lead time finally begins. Long-lead items are tracked against the register and the required-on-site dates.
The AI checks each submittal against the specification section, the drawings and the contract — flagging deviations, missing certifications and non-conforming products, with citations and a confidence score. The consultant’s engineer reviews the findings and makes the call.
The specific failure mode behind the Hyatt doctrine — a deviation buried in a shop drawing that nobody flagged — is what machine reading is best at surfacing for human attention.
Builds the submittal register from the specification automatically, links long-lead items to schedule dates, and flags the packages whose review delay now threatens the critical path.
On resubmittals, the AI diffs against the previous version and the prior review comments — showing the reviewer exactly what changed, and whether every comment was addressed.
The engineer’s judgment stays in charge; the AI removes the latency and the blind spots.
A live submittal register with response codes, review ageing against the contractual window, resubmission counts, and long-lead items tracked against their required-on-site dates — exportable for the consultant, the client, and any dispute about who took how long.
A submittal is the contractor proposing evidence of compliance — “here’s what we intend to install”. An RFI is a question about the documents — “what did you mean here?”. Different workflows, different legal weight.
Read the full answerGenerally yes, provided you incorporate the reviewer’s notes — but confirm scope-affecting notes before proceeding, and check whether your spec requires a record resubmittal showing the notes incorporated. It is the most dispute-prone code precisely because it is half-approval.
Letter codes used on government and many GCC projects: A approved; B approved with comments, no resubmission; C approved with comments, resubmission required; D/E returned or disapproved. Private US work typically uses stamp language instead (“No Exceptions Taken”, and so on). Same logic, different labels.
No. Review is for conformance with design intent only — dimensions, quantities, coordination and means-and-methods stay with the contractor, and approval doesn’t excuse deviations that were not specifically flagged.
Read the full answer10–14 days per cycle is the common contractual window. Whether longer is “unreasonable” depends on the contract and the approved submittal schedule — tribunals have gone both ways.
Lead time starts only at release to fabrication, so submittal cycles sit in front of every long-lead item. Back-calculate: required-on-site date, minus lead time, minus at least two review cycles, equals when the submittal must go in.
Read the full answerRelated answers
Terms defined here
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.
A short, tailored walkthrough on your real workflow — no generic demo.