How to prepare a submittal package.
A submittal package that gets approved on the first pass is built in six steps: list every item your spec sections require, pull each item's current data sheet from the manufacturer, mark the exact model and options, check the sheet's values against the drawings before it leaves, assemble it per spec section with an index and a transmittal, and keep revision discipline when anything comes back.
1. Build the register from the spec
Read Division 01 for the package rules, then every section in your scope for its SUBMITTALS article. One row per product spec: the spec section, the item, what the article demands (product data, shop drawings, samples, warranty), and the basis of design named on the drawings. The register is the contract's own list of what you owe; an item missing from the package is an automatic return, no matter how good the rest is.
2. Get the sheet from the maker, current and unmarked
Pull each data sheet from the manufacturer's site, current revision, not from a years-old job folder. Subs tell each other that half the package time is hunting files and reformatting PDFs, and that hunt is also where the errors enter: an old revision shows options that no longer exist and misses the ones that do. The sheet that goes in the package is the maker's original; the markup goes on your copy.
3. Mark the exact model
Highlight the model number you're submitting and every option and accessory that applies, on every page where a choice exists. A reviewer who has to hunt your model across a six-option table is a reviewer reaching for Revise and resubmit, and the spec's package rules usually let them return unmarked pages unreviewed.
4. Check the values before it leaves
Put the schedule row and the sheet side by side: capacity, size, voltage, phase, full-load amps, warranty term. On our sample project, a fan-powered terminal unit was scheduled with a 1/6 HP motor at 1.5 FLA while the submitted sheet's smallest motor ran 1/2 HP at 4.1 FLA: caught at your desk, that's an afternoon and a different selection; caught in review, it's a resubmittal cycle; caught in the field, it's a change-order fight. Two looks before it leaves your desk beats three reviews after.
5. Assemble it the way reviewers require
Per spec section, with a cover and transmittal that lists every item and its submittal number, bookmarks to each item, and file names that carry the number and revision. This is not decoration: Division 01 usually makes it a requirement, and packages that skip it are the ones reviewers describe as thousand-page catalog dumps and send back whole.
6. Track what comes back
Approved as noted means make the noted correction and proceed. Revise and resubmit means a new cycle: revise only what differed, mark the new revision on the item and the file name, and resubmit under the same number. A resubmittal that changes things nobody asked about starts the argument over.
Or send us the scope
This six-step build is exactly what Beem does as a service. Send the drawings and spec for your scope: we build the register, pull every current sheet from the maker, mark the models, check every value against the drawings and spec, and hand back an indexed package with anything doubtful flagged for your call, in days. We never pick the product and never promise approval; we make the package the easiest thing the reviewer reads that week.
Questions subcontractors ask
What goes in a submittal package?
Whatever the spec sections in your scope demand in their SUBMITTALS articles: usually product data sheets, shop drawings where required, samples, and warranty documents, assembled per spec section with a transmittal, item numbers and an index.
Where do I get cut sheets?
From the manufacturer, in the current revision. A sheet from an old job folder is the fastest way to submit options that no longer exist. The sheet goes in unmarked except for your highlighting of the model and options.
Why was my package returned without review?
It failed the package rules in Division 01: items missing against the spec's own list, models unmarked on catalog pages, no index, or sections mixed together. Reviewers are entitled to return that unreviewed, and most now do.
What does Beem need to build my package?
The drawings and specification for your scope. We build the register from them, source every sheet from the maker, check the values, and return an indexed package with anything doubtful flagged. You stay the one who picks products and signs the transmittal.