Material Submittal Approval

Definition

Material submittal approval is the contractual process by which a contractor proposes the actual products, systems and finishes it intends to install, and the designer or engineer confirms they satisfy the specification before anything is ordered. A submittal package normally contains manufacturer data sheets, test certificates, compliance statements against the specification clause, samples where required, and — for engineered items — shop drawings. The approval status returned is rarely a simple yes: "approved", "approved as noted", "revise and resubmit" and "rejected" each carry different consequences for procurement.

Why It Matters

On most building projects the submittal register, not the construction programme, is the true early-warning system. Every long-lead item — switchgear, lifts, curtain wall, chillers, specialist valves — has a manufacturing lead time that only starts counting from the day the order is released, and the order cannot be released until the submittal is approved. A four-week review cycle on a sixteen-week lead item quietly becomes a twenty-week gap. Because that gap sits in procurement rather than on site, it is invisible in a baseline schedule that only shows installation activities, which is exactly why it surprises people.

How the Loop Actually Works

1. Register first. Extract every specification section requiring a submittal into a register with responsible party, target submission date, review duration and required-on-site date.
2. Work backwards from installation. Required on site minus delivery lead time minus fabrication minus approval duration equals the submission deadline. That date, not the installation date, is what you drive.
3. Submit complete. Partial packages are the leading cause of "revise and resubmit" — and a resubmission usually restarts the full review clock, not the remainder of it.
4. Track review time contractually. Most contracts give the designer a fixed period (commonly 14 days). Log receipt dates and returns; the record matters later.
5. Close the loop to procurement. Approval means nothing until the purchase order is released; someone must own that handover explicitly.
6. Link to the schedule. Long-lead submittals belong in the programme as real activities with logic into the installation work.

Real-World Example

On a mid-rise hospital fit-out, the medical gas manifold submittal was returned "revise and resubmit" because a single valve model in a twelve-page package was superseded. The subcontractor corrected the page in two days, but the resubmission entered the back of the designer's queue and took another fourteen. The order released five weeks after the planned date, and the manufacturer's slot had gone: a further six-week wait. The installation activity had thirty days of float, so nobody noticed until the float was gone — and by then the commissioning window was compressed into the client's move-in period. The recovery cost, mostly premium-time commissioning, was roughly forty thousand pounds. The root cause was not the valve model; it was that nobody was tracking submittals as schedule activities.

Practical Lessons Learned

• Resubmission is the expensive event. One right-first-time package beats three quick ones — the queue, not the review, is what costs you weeks.
• "Approved as noted" is not permission to ignore the notes. Comments carry contractual weight; installing to the original submission invites a rejection at inspection.
• Designers get overloaded in waves. Submitting forty packages in one week guarantees a slow month; smooth the flow deliberately.
• Substitutions need a commercial case, not just a technical one. Equal-and-approved claims fail when the submitter cannot show performance parity clause by clause.
• The register is a live document. A submittal log updated monthly is a historical record; updated weekly it is a controls tool.

Expert Tips

• Colour the register by "days until submission deadline", not by status. Status tells you where things are; the countdown tells you what to chase.
• Hold a fifteen-minute weekly submittal stand-up with procurement, the designer's lead and the subcontractor coordinators. It removes more delay per hour than any other meeting on a fit-out.
• Pre-agree the review duration and the definition of a complete package in the subcontract, and repeat it on the cover sheet of every submission.
• For critical long-lead items, ask for a pre-submittal review — an informal look at the draft before the formal clock starts.
• Keep a one-page compliance matrix at the front of every package mapping specification clause to data-sheet page. Reviewers approve what they can verify quickly.

Common Mistakes

• Building a submittal register from the drawings rather than the specification, so half the required packages are never identified.
• Scheduling installation dates without modelling approval and fabrication as predecessor activities.
• Letting subcontractors submit directly to the designer, so the main contractor loses both visibility and the review-duration record.
• Ordering "at risk" before approval to save time, then rebuilding at your own cost when the notes come back.
• Treating samples as a formality and shipping them late, holding up an otherwise complete package.

Key Takeaways

• The submittal register is the earliest reliable predictor of procurement-driven delay.
• Drive submission deadlines backwards from required-on-site dates, not forwards from convenience.
• Right-first-time packages beat fast packages, because resubmission restarts the queue.
• Long-lead submittals belong in the programme with real logic.
• Record submission and return dates; they are the backbone of any later delay narrative.

Related Concepts

Pairs with Baseline Schedule, Change Order Management, Float Management, and Handover Pack.