What a commercial roof submittal should tell the owner

A proposal tells you a price. A submittal tells you what you’re actually buying. It’s where a line item like “60-mil single-ply membrane” turns into named products, named details, and a named guarantee. It usually lands on your desk right before material gets ordered.

TL;DR: A commercial roof submittal package can include cover sheets, product data, flashing details, specifications, safety data sheets, contractor certification and approval placeholders, and a guarantee specimen. It is the last easy moment to catch a gap between what you agreed to buy and what is about to ship. Read it before materials arrive.

Most owners read the bid harder than the submittal

Most owners put their energy into the bid comparison. Three numbers on one spreadsheet. Wrong place to spend all of it.

A bid is a promise about cost and scope, written in general language. The submittal is the document set that turns that language into specific manufactured products with specific part numbers, thicknesses, and installation details. Two contractors can bid the same specification, land within a few percent of each other, and submit two roof systems that aren’t the same roof at all. The insulation can differ. The fastening pattern can differ. The edge metal can differ. So can the warranty term and its exclusions.

You find that out in the submittal, which is why the step exists at all.

Timing matters too. The submittal comes before fabrication and delivery, so it’s the cheapest moment in the project to change your mind. Once tapered insulation is cut to a shop drawing and sitting on a truck, the conversation about whether it matches the drainage plan gets expensive. Once a crew is on the roof and the old system is open, it gets expensive and urgent at once. Review is cheap in the office. It’s never cheap on the deck.

I treat submittal review as an owner’s job, not a technical formality. You don’t have to know how to install a roof to know what you’re approving.

What a submittal package can include

Manufacturers publish tools that assemble these packages, which tells you how standardized the contents have become. Johns Manville’s commercial roofing submittal wizard describes a package that can include cover sheets, contractor certification and approval placeholders, product data, flashing details, specifications, SDS documents, and a guarantee specimen.

Read that list again as an owner rather than as a roofer. Each item answers a different question you should already be asking.

Cover sheets and approval placeholders tell you who signed off and when. Product data tells you what’s going on the building. Flashing details cover how the system handles the places roofs actually fail. Specifications say how it’s supposed to go together, and SDS documents list what chemicals are coming to your property. Contractor certification shows whether the installer is recognized by the manufacturer whose warranty you’re counting on. Last, the guarantee specimen: what you’re promised after the crew leaves.

If a package shows up missing several of those categories, that’s not automatically a problem with the contractor. It may reflect a smaller project, a different manufacturer’s format, or a spec that didn’t call for the full set. It is a reason to ask, though. Simple question, and not a fight: what’s in this package, what isn’t, and why.

Start with product data, then slow down on the details

First-time submittal readers tend to stop at the product data sheets. Glossy pages, the logo, a physical properties table, the code listings. They matter. They’re also the easiest part of the package to approve without learning anything.

The product data answers a narrow question. What material, what thickness, what color, what listed properties. Compare it line by line against the specification you agreed to buy. If the spec said one thing and the data sheet says another, you’ve found a substitution, and substitutions are worth a conversation whether or not they’re downgrades. Sometimes it’s the contractor solving a lead time problem in your favor. Sometimes it’s a margin decision. You can’t tell which without asking.

The flashing details are the part I’d slow down on. Field membrane is the easy part of a roof. The failures cluster where the roof stops being flat and starts being a transition: perimeter edges, parapets, curbs, drains, scuppers, pipe penetrations, expansion joints, equipment supports. Details are the drawings that show how each of those transitions gets built.

Nobody expects you to critique the drafting. What you can do is confirm the details in the package match the conditions on your building. If your roof has forty rooftop units, six skylights, and a screen wall, and the detail sheets cover none of that, the package is describing a simpler roof than the one you own. Ask what governs the conditions that aren’t drawn.

The specifications sit between the two. They describe sequence, substrate preparation, attachment, and the conditions the manufacturer expects for the system to perform as intended. Dry reading. Also where a lot of the accountability lives when something goes wrong later, because a claim conversation tends to start with whether the system was installed to specification.

Assembly listings, safety data, and certification

Three items get skipped more than the rest. Each is worth your attention, for a different reason.

Assembly listings are not always part of the package. Ask for them. They are the listings and assembly numbers that tie your specific build-up to a tested performance claim. Wind uplift, fire, code compliance. The important word is assembly. Ask what the listing covers: the specific combination of deck, insulation, attachment, and membrane, or a single product. A component swap that looks small on a spreadsheet can move you off the assembly you thought you were buying. If your building carries insurance requirements or a local code trigger tied to a listing, confirm the assembly in the submittal is the assembly your requirement names.

Safety data sheets are the item owners most often wave through, and I understand why. They read like regulatory paperwork. They’re still telling you what’s arriving at your property and what handling it requires. If you run an occupied building, that matters to more people than the roofing crew. Adhesives, primers, and sealants have odor and ventilation implications, and tenants notice. Read the SDS package early so any conversation with tenants about odors or access happens before application, not during it.

Contractor certification is the one I’d put in front of anyone signing a large reroof. Ask the manufacturer directly whether its guarantee requires installation by a contractor it has approved for that system, and get the answer in writing. The certification page is where that relationship gets documented in your project file. A small piece of paper attached to a large financial promise.

None of these three make the roof better on their own. They make the roof legible while you can still act on what you read.

The guarantee specimen is the document owners skip

A guarantee specimen is a sample of the warranty document your project is expected to receive, not the executed one. It’s the form, with the terms, the exclusions, and the obligations spelled out before you’re locked in.

The timing here is the best an owner gets, and most let it pass. Read the specimen while you still have decisions in front of you. Start with the exclusions, because that’s where the document tells you what it doesn’t cover. Check the maintenance obligations, and whether coverage depends on the owner performing and documenting maintenance. Then find out what happens when other trades work on the roof, because in a few years somebody will mount something up there and nobody will call you first.

Last, read the difference between what the manufacturer guarantees and what the contractor warrants. The manufacturer and the contractor are making two different promises, for two different durations. Owners who mix them up tend to learn the difference on the day they need it.

A guarantee you’ve read is worth more than a longer one you haven’t.

How to review a submittal without being a roofing expert

None of this requires technical training.

Set the deadline in the contract, not in the moment. Decide up front how many business days you get for review and who has to sign. A review window agreed to during negotiation is a schedule item. A review window requested after the package lands is a delay.

Compare against the specification you bought. Put the spec and the submittal side by side. Mark every line where they differ. Judging whether a difference is acceptable comes later. Right now you’re building the question list.

Count your conditions. Walk the roof, or walk a current roof plan, and list every penetration, transition, and piece of equipment. Then confirm the detail sheets address them. Gaps between that list and the details are the most useful finding an owner can produce.

Ask about substitutions in writing. Any product in the package that doesn’t match what you agreed to buy gets one email: what changed, why, and what it affects. Keep the answer with the project file.

Read the guarantee specimen before you approve anything else. Exclusions first, maintenance obligations second, term third.

Confirm certification for the specific system. A contractor may be recognized for one manufacturer’s system and not another. Match the certification to the system in the package.

Write your approval down. Approved, approved as noted, or revise and resubmit, with your name and the date. Verbal approval of a document set is not a record. In a dispute two years out, the marked-up submittal is one of the few artifacts that shows what both sides understood at the time.

Keep the package. File it with the executed warranty and the closeout documents. The next person who owns this building, or the next person who manages it, will need it. The submittal is the only place the roof is described in full before it’s buried under the finished surface.

The submittal describes the roof before anybody builds it. Approve it like the description matters, because when a leak shows up in year six, that stack of documents is what the argument gets built on.