How to organize a security film submittal package
A register, a deviations list and revision control make a submittal reviewable. This is about organizing the record, not pricing bids or writing a new specification.
By Shore Tint & More editorial team · · 7 min read
Official sources checked . Procurement pages change; confirm with the agency.
Key takeaways
- Organize the submittal around the project's requirements, not a folder of brochures.
- A product name is not a technical description; use the current specification for the selected product only.
- Start with a register: number, title, revision, issue date, purpose and review status.
- Put deviations on their own list and change the revision identifier every time.
- The format here is a suggestion; the contract, owner or architect may require another.
Make the package easy to review
A submittal should help the team find the proposed products, see where they will be used and resolve deviations before installation. A large folder of unrelated brochures makes that harder. Organize around the project's requirements and the requested approval process. What the submittal should contain for attachment is covered in attachment in the project scope.
A product list is not a complete submission
3M's Safety S140 specifications (Rev. D, January 2025) address product requirements, authorized-dealer documentation, examination and installation — and state the film is not approved for windstorm or blast mitigation applications. That shows why a product name alone is not a technical description. Use the current specification for the selected system; do not paste S140 requirements into a submittal for another product.
Start with an index
| No. | Group | Title and revision | Issue date | Purpose | Review status |
|---|---|---|---|---|---|
| 01 | Product information | Manufacturer specification, revision as printed | As printed | Identify product | Submitted / reviewed / revise |
| 02 | Performance evidence | Test report number and date | As printed | Support stated use | Submitted / reviewed / revise |
| 03 | Installation details | Attachment detail per opening group | Project date | Define assembly | Submitted / reviewed / revise |
| 04 | Opening schedule | Internal labels only | Project date | Locate work | Submitted / reviewed / revise |
| 05 | Requested deviations | Deviation list | Project date | Decisions needed | Submitted / reviewed / revise |
| 06 | Warranty and maintenance | Warranty and care documents | As printed | Closeout | Submitted / reviewed / revise |
These groups are suggestions. The owner, architect or contract may require a different format, portal or sequence; follow it. Keep the opening schedule in restricted project files.
Need a reviewable submittal?
Shore can prepare product, attachment and opening documents organized for your review process.
Request an assessment →Make deviations visible
List each departure from the requested scope and each unresolved condition: the item, the proposed change, the reason and the decision required. Do not bury an alternate product or a missing attachment detail inside a manufacturer PDF. A reviewer should understand what they are approving without comparing every page to an earlier email.
Control revisions
Each resubmission gets a new revision identifier and a note of what changed. Keep superseded documents out of the installer's active package while retaining the history. Record the reviewer, response date and next action, and avoid naming a file "final" while comments remain open.
Connect approval to the installed record
Before work, confirm the installer has the accepted documents and that field changes have an approval route. At closeout, reconcile installed products and locations with the approved submittal and keep approvals and later changes together — the records guide shows how. This supports, but does not replace, contract administration or technical review. Evidence review is covered in how to read a test report.
Sources
These guides began as AI-assisted drafts from the Shore Tint & More editorial team. Our guides explain product documentation and practical project planning. Manufacturer test claims are linked, and site-specific recommendations require an assessment. Spotted an error? Contact us for corrections.