Quick Answer
A submittal is not a product brochure with a cover sheet. It is a package that lets a reviewer who has never spoken to you reach a defensible conclusion.
Six documents make it reviewable:
| Document | Answers |
|---|---|
| Specification response | Which clause each property satisfies |
| Model-level data sheet | What this exact product is and is not for |
| Test evidence | Which tests, on which configuration, at which revision |
| Compatibility statement | Which substrates were assessed, and how |
| Installation requirements | What the site must provide for the product to perform |
| Traceability link | How the approval ties to what will be delivered |
A package missing any one of the six generates a question, and a question during submittal review costs a week. Most returned packages are not weak on product; they are incomplete on the fifth and sixth.
1. Start From the Specification, Not the Catalogue
The reviewer’s first action is to compare your submission against the specification clause. If your package is organised by product feature, that comparison is their work, not yours — and they will do it badly, or return it.
Structure the submittal as a response document:
- Quote the requirement.
- State the proposed product’s value or position.
- Point to the document and page that evidences it.
A three-column table covering every performance clause does more for a submission than thirty pages of data sheets. Where a clause is not addressed by the product, say so explicitly — an acknowledged gap is reviewable, an omission is not.
This is also where structural and weather-sealing scopes must be kept apart. A package that offers a weather sealant as evidence for a structural bond fails on the first read, and the reviewer’s confidence in the rest of the document drops with it. The functional difference is set out in structural silicone versus weatherproofing sealant.
2. The Data Sheet Must Be Model-Level
Family-level documents are the most common source of submittal queries, and the reason is structural: a façade consultant is being asked to accept a specific bead on a specific building, and a family document does not identify which bead.
What the reviewer looks for on the data sheet:
- Exact model designation, matching the submittal cover and the purchase documents.
- Stated intended use, including any exclusion.
- Movement capability or mechanical properties, with the test method named.
- Application limits: temperature, joint geometry, substrate preparation.
- Revision or issue date.
Where the manufacturer publishes a family document plus model-level supplements, submit both and say which is which. Mixing them without labelling invites a request for clarification that could have been avoided by one sentence.
3. Test Evidence: Scope Beats Quantity
A thick test file is not a strong test file. Reviewers assess four things, in this order:
- Product identity — does the report name this model?
- Configuration — does the tested build-up match the proposed one (substrate, thickness, joint dimensions, cure)?
- Method — is the test method the one the specification names?
- Currency — is it the current revision, and does it correspond to the formulation being supplied?
A single report that passes all four is stronger than a folder that passes one. Where the test was performed on a representative assembly rather than the actual project’s, state that clearly and let the reviewer decide whether it is sufficient.
A report is only as useful as the checking done before it is submitted. The four scope checks that separate a genuine document from a well-formatted one are set out in verifying TDS, SDS and test reports.
For structural applications, compatibility and adhesion evidence is normally project-specific: the substrates, the spacer, the gasket and the coating all take part. A general statement that a product bonds to glass does not address that, and reviewers in this field know it.
4. Compatibility Is a System Question
Structural glazing assemblies involve more materials than the two faces of the bead. Sealant, spacer tape, setting blocks, gaskets, coatings and the glass itself form a system, and compatibility has to be assessed across it.
The submittal should state:
- Which materials were included in the compatibility assessment.
- Which were not, and why.
- Whether any component is a proprietary item requiring the manufacturer’s own confirmation.
- Whether project-specific testing is recommended.
Leaving a material out and hoping nobody notices is a poor strategy in a field where the reviewer’s entire job is to notice. Declaring the boundary — “assessed for these four materials; the gasket is a proprietary system component and requires the system supplier’s confirmation” — reads as competence.
5. Installation Requirements Belong in the Submittal
The fifth document is the one most often missing, and its absence is what turns an approval into a site argument.
State what the installation depends on:
- Surface preparation method and the interval before sealing.
- Primer requirement, or explicit statement that none is specified.
- Joint geometry limits — minimum and maximum width and depth.
- Backer rod and bond breaker requirements.
- Ambient and surface temperature limits during application and cure.
- Cure time before movement, water or load.
These are not caveats. They are the conditions under which the approved product performs, and a reviewer who signs off without them has approved a product while leaving the outcome undefined. Including them protects both parties.
Where the geometry cannot be met as drawn, that is a design conversation to have before approval, not a site variation afterwards. The checklist for that conversation is in the building envelope sealant specification checklist.
6. Traceability: From Approval to Delivered Batch
The sixth document connects the decision to the material.
At minimum, the submittal should identify how the delivered product will be shown to be the approved product: model marking, batch or lot identification, and the documents that will accompany the shipment.
This is not bureaucracy. It is the only mechanism that catches the three failure modes that appear after approval: a substitution made for availability, a batch released against a superseded specification, and a model that looks identical but is not.
Where the project requires it, agree the goods-in check at submittal stage. Adding it later means negotiating while a container is waiting.
7. Why Packages Get Returned
| Return reason | What it usually means |
|---|---|
| Model mismatch across documents | Cover, data sheet and test report name different designations |
| Report covers a different substrate | Evidence exists but not for this build-up |
| Superseded revision | The file was assembled from an old folder |
| Performance clause unaddressed | The submission is organised by product, not by requirement |
| Installation conditions omitted | The package describes a product, not a system |
| No approval route stated | Nobody knows who signs, or in what form |
Six reasons, all of them procedural. None of them is fixed by a better product, and all of them are fixed before the package is sent.
8. Assemble It Once, Reuse It
A submittal package that works is an asset. The core — model-level data, test evidence, compatibility boundary, installation conditions — changes slowly. What changes per project is the specification response and the traceability section.
Builders who keep a maintained core package submit in days instead of weeks, and they answer queries with a page reference instead of a fresh email chain.
Keep the revision dates visible on every document. A package assembled from a current core and an outdated appendix is worse than an incomplete one, because it looks complete.
Conclusion
A structural glazing submittal succeeds when a reviewer can reach a conclusion without contacting you. That requires six documents, organised by requirement rather than by feature, with the boundaries stated as clearly as the capabilities.
The product is rarely the problem. The package usually is.









