How to Read a Submittal Package

Why this matters

A submittal package is the only document in commercial work that records what was actually agreed to, as opposed to what was drawn, sold, or remembered. When a shop reads it properly before installing, the deviations get caught while they are still free to fix. When nobody reads it, the deviations get discovered at closeout by a reviewer holding the same package, and the shop pays for the difference. Years later, on a service call, the same package is often the only surviving evidence of what was supposed to be there, which makes it worth finding even when you had nothing to do with the install.

Step 1: Read the transmittal before anything behind it

The cover page tells you four things that change how you read everything else: who submitted it, which specification section it answers, whether this is a first submission or a resubmittal, and what review action came back. Techs skip the cover because it looks administrative. It is the index and the verdict.

A resubmittal matters more than a first submission, because the first one came back with comments and the second one is supposed to have resolved them. If you have the resubmittal but not the comments it answers, you are missing half the record.

Step 2: Establish the approval state and treat it as binding

Review stamps come in a small family, and the wording is not decorative.

"Approved as noted" is the one that causes trouble. The stamp is on the cover, the notes are scattered through the interior pages, and a crew that reads only the cover installs an unapproved configuration while believing it is approved. Find every note before you order.

Step 3: Reconcile the schedule against the product data, line by line

A submittal has two halves that people read as one. The schedule states what was required. The product data states what is proposed. The reason the package exists is the difference between them, and reading either half alone tells you nothing.

Work one required line at a time and find its match. Where you cannot find a match, that is a finding, not a gap in your attention.

Step 4: Separate declared deviations from silent ones

A properly prepared submittal lists its deviations on a page of their own. Those are the easy ones, and they have already been considered. The expensive ones are silent: the proposed product simply does not carry a feature the specification called out, and nothing on the page says so. Silent deviations are found only by reconciling line by line, which is why Step 3 cannot be skimmed.

Skipping this step is the single most common way a shop ends up buying a change at its own cost. Once the equipment is set, the argument about who should have caught it is one you lose on paper.

Step 5: Chase the tags

Equipment tags tie a submitted product to a location on a drawing. Six identical units with six different tags are usually not identical, because at least one of them serves a different zone and carries a different selection. Confirm every tag on the schedule appears in the product data with its own selection, rather than one selection covering the group.

Step 6: Flag every "by others" and "field verify"

These two phrases transfer work or risk to somebody, and the somebody is frequently you. "Disconnect by others" means the disconnect is not in the equipment package and someone has to buy it. "Field verify" means the dimension shown is not guaranteed and the consequence of it being wrong lands on whoever set the equipment. Both are legitimate. Both need to land on a list with a name attached before install day.

Step 7: Note the underlying document dates, not just the approval date

The approval date tells you when a reviewer signed. The revision dates on the product data tell you which version of the manufacturer's literature was reviewed. When those are far apart, or when the literature has been revised since, the approval attached to a document that no longer describes what will ship. That is worth a question rather than an assumption.

The artifact: a filled-in reconciliation record

The output of Steps 3 through 6 is one table per equipment tag. Here is a completed one for a single air-moving unit, with illustrative values, exactly as it would go into the job record.

Tag: AHU-3. Spec section: air handling units. Submission: 2nd (resubmittal). Stamp: Approved as noted.

Five lines, three open. Work each one.

Line 1 is the one that decides the job. The schedule's 0.8 in w.c. external static is the duct designer's number for the duct that was drawn. The submitted unit delivers 0.6 in w.c. at the same 1200 cfm, which is 25% below the requirement. This is not a rounding difference; it means the unit was selected against a lighter duct system than the one on the drawings. If it installs as submitted, airflow lands below design and the balancer is the one who discovers it, at the end of the job, when the duct is in the ceiling. The disposition is to send it back before ordering, not to note it and hope.

Line 2 is the one your service side cares about most. A 1 inch rack in place of a 2 inch rack roughly halves the media depth and therefore the dust holding capacity, which shows up as a shorter filter interval. Illustratively, a site changing filters twice a year on 2 inch media moves to four times a year on 1 inch. That is 2 extra visits per unit per year, and across the 6 units on this schedule it is 12 extra visits a year that nobody priced. If your shop is holding the maintenance agreement, catching this at submittal is the difference between a priced scope and an argument.

Line 3 is a purchase nobody made. "By others" is not a problem in itself, it is a problem when the list of others has no name on it. The disposition is one email naming who is buying the disconnect and confirming it matches the unit's maximum overcurrent protection.

Lines 4 and 5 close on sight. They are the reason the table has five rows instead of three: a reconciliation you cannot see the closed lines in is one you cannot tell was actually completed.

The stamp on this package said "approved as noted." Somebody reviewed it and let 0.6 in w.c. through, most likely by reading the capacity column and not the static column. An approval stamp is somebody else's reading, not a substitute for yours.

Finding the deviation after the equipment is already on site

The reconciliation is worth most before ordering and still worth doing after delivery, because the cost of correcting a deviation climbs in steps rather than smoothly. Uninstalled in the crate is one step. Set and connected is another. Concealed behind finished construction is the last, and after that the conversation stops being about the equipment.

Four moves, in order, and the order is what protects you.

1. Stop before you install it, if it is not installed. Every hour of installation labor you add to a deviation is labor you may be asked to reverse, and the reversal is not usually paid.
2. Write it up the same day, in neutral language. Three facts: what the schedule required, what arrived, and what the physical consequence is. Leave out who should have caught it. A write-up that assigns blame gets argued with; one that states a fact gets answered.
3. Route it to whoever holds the contract, not to whoever is standing closest on site. A superintendent's verbal "just put it in" does not change the approved submittal, and it moves the risk from the party that made the error onto you.
4. Get the direction in writing and treat silence as unresolved. An unanswered notice is not approval. Follow it up on a stated interval, and keep installing everything else.

The one exception to stopping is a deviation that has no physical consequence, which does exist. A finish color, a nameplate style, or an accessory that was never going to be used are worth a note in the record and nothing more. Reconciliation is meant to surface what matters, and treating every difference as an event trains everyone around you to ignore your notices.

The closeout submittal, and why it arrives when it is least useful

Operation and maintenance manuals are assembled at closeout, which means they land after every decision they could have informed. Nobody selects, orders, or installs anything from an O&M set. Its value is entirely retrospective, and that is exactly why it is the document your service side should chase.

One thing is worth checking on receipt. O&M sets are usually assembled from the approved submittal rather than from the building, so a late substitution shows up as a manual that faithfully documents equipment that is not there. On the first maintenance visit, spot-check three tags against the field: model designation, serial, and the option that most affects service, such as filter size or access side. If all three match, the set is probably trustworthy. If one does not, treat the whole set as approximate and rebuild the equipment record from nameplates.

What the package is worth to you five years later

Long after the job closes, this same stack is the highest-quality record of the building that exists. On a service call to a unit whose nameplate has weathered off, the submittal gives you the model, the selected options, the coil arrangement, and the electrical characteristics, which is more than the nameplate carried even when it was legible. It also tells you what the equipment was selected to do, which lets you separate "this unit is failing" from "this unit never met the design."

Ask for it on the first visit to any commercial account, store it against the equipment record, and note the approval stamp and submission number when you file it. A package filed without its stamp loses the one piece of information that says whether anyone agreed to it.

References

• Trade-standard practice for construction submittal review, shop drawings, and product data
• Manufacturer product literature conventions for equipment schedules and selection data
• See related: What a Cut Sheet Is For and What It Leaves Out
• See related: The Revision Block and Why It Decides Everything