What's in a commercial flooring submittal

You already know a submittal is how you prove the products you are installing match what the project specified. The part that costs you is the detail: when a package is incomplete, mismatched, or out of date, it comes back — and a rejection costs you weeks. This is the document set a reviewer expects, and the few things they reject over.

The documents a complete package contains

A complete commercial flooring submittal carries the following per product line. This is the canonical checklist the other guides refer back to:

• Technical data sheet — the product's specifications, matched to the exact SKU.
• Installation guide — the manufacturer's current installation instructions.
• Maintenance instructions — care and cleaning guidance for the specified product.
• Warranty documentation — the warranty that applies to the specified line.
• Sustainability / LEED documentation — EPDs, HPDs, or LEED contribution summaries where the project pursues credits.

Why "matched to the SKU" matters

A data sheet for the wrong color, gauge, or backing is the most common reason a package is rejected. Each document has to correspond to the exact line item specified, not just the product family.

Start with the spec, not a template

There is no industry-standard flooring submittal form. Every architect writes their own spec and every GC has their own transmittal, so the package should bend to the spec, not the other way around. Open the flooring section for the job — for example 09 65 19 Resilient Tile Flooring, 09 68 13 Tile Carpeting, or 09 65 13 Resilient Base and Accessories — and read the Submittals articles in Part 1. Most specs written in the standard format split them up like this:

• Action submittals — product data for each product, shop drawings or layouts where required, samples, and a product schedule that uses the same designations as the drawings.
• Informational submittals — installer qualifications, product test reports, and a sample of the special warranty.
• Closeout submittals — maintenance data for the O&M manuals and the final warranty.
• Maintenance material submittals — extra stock (attic stock) from the same production run, labeled. The quantity varies by spec: one resilient tile spec may ask for 1 box per 50 installed, a carpet tile spec for 5 percent but not less than 10 square yards. Always use the number in your spec.

Also check Division 01. The submittal procedures section sets the format rules (numbering, stamps, number of copies, electronic or paper), and a sustainable design requirements section, if there is one, tells you which LEED or WELL documents the flooring package has to carry.

What goes on the cover sheet

The cover sheet is the first thing the reviewer reads. A clean one tells them exactly what you are submitting and where to find it:

• Project name and number — exactly as the GC and architect write it.
• Submittal number and revision — follow the GC's numbering. A common pattern is spec section plus sequence (09 65 19-001), with Rev 0 for the first issue.
• Spec section — number and title. One section per submittal unless the spec says otherwise.
• Date submitted, submitted to (the GC, and the architect it goes on to), and submitted by (your firm, contact, phone, and email).
• Submittal type — action, informational, or closeout.
• Product list — each product with its drawing tag (LVT-1, CPT-2, RB-1), manufacturer, line, style or color, and size.
• Deviations — list any deviation or substitution. If there are none, say "No deviations from the contract documents." A blank reads as an oversight.
• Sustainability summary — on LEED or WELL jobs, a short per-product table of emissions certification, recycled content, manufacture location, and EPD and HPD availability.
• Room for review stamps — the GC's review stamp and the architect's action stamp.

What order the documents go in

Reviewers move faster when every package is built the same way. This order works for most jobs:

• Cover sheet — the fields above.
• Product schedule — one line per product, using the drawing tags, so the reviewer can match each product to the finish plan.
• Product sections, in schedule order — for each product, the data sheet, installation instructions, then everything that goes with it: adhesive, underlayment, transitions, and base. Accessories are the most commonly forgotten item.
• Sustainability documents — behind each product or in their own section, whichever the spec or the LEED consultant asks for.
• Shop drawings or layouts, if the spec calls for them — seaming, pattern direction, transitions, and cutouts.
• Sample transmittal — physical samples usually travel separately, so add a page listing what you are sending.
• Informational items — installer qualifications, test reports, and the sample warranty.

Merge it all into one PDF with a bookmark for each product and continuous page numbers, so the reviewer can jump straight to LVT-2 instead of scrolling. Closeout items such as maintenance data and the final warranty usually go in later with the closeout package — note on the cover sheet if any are included now.

Why packages get rejected on first pass

Roughly one in three submittals is rejected on first review. The recurring causes are mundane: a missing document, a document that does not match the specified SKU, or an outdated revision the manufacturer has since superseded.

Each of those has a fix you control — the full breakdown of why submittals get rejected walks through them.

Get early access — opens a sign-up form

Assembling a package that passes

The reliable approach is to treat completeness and currency as things you prove, not assume: confirm every required document is present, matched to the SKU, and the latest known revision before the package leaves your hands.

Where SubmitPak fits

SubmitPak builds this exact document set for you: it pulls each required document across manufacturers, matches it to the specified SKU, flags anything it cannot verify as current, and outputs one bookmarked, branded PDF — so the package you send is complete and SKU-matched, with nothing unverified passed off as current.