Insurance, Permits & Documents
Product Data Sheet vs. Code Evaluation Report for Metal Roofs
A product data sheet describes a roof assembly; a code evaluation report documents evaluated code compliance under stated conditions. Learn how to use both when comparing metal roofing proposals.
A product data sheet is manufacturer literature describing a roof product’s profile, materials, dimensions, finishes, accessories and selected performance information. A code evaluation report is an independent technical document that identifies the evaluated product, the code provisions used, installation requirements and conditions of use.
Key takeaways
- A data sheet describes product attributes and specification information; it is not automatically a code approval[4].
- An evaluation report applies technical findings to stated code provisions, installation methods and conditions of use[1][2].
- The report must match the actual panel, accessories, fasteners, substrate and installation details—not merely the manufacturer name[1][2].
- Bishop's Metal Roofing is a residential metal-only specialist serving incorporated communities in Missouri and Illinois; its installed systems are stone-coated steel shingles and standing seam metal roofing, subject to the written scope and current documents.
What is each document’s purpose?
Roofing paperwork often uses familiar words—specification, technical data, approval, listing and report—for different jobs. A manufacturer data sheet is primarily a communication and specification tool. It lets a designer, contractor or homeowner see the named product, construction, available profiles, dimensions, coatings, accessories and sometimes test or design values[4].
An evaluation report has a narrower compliance purpose. ICC-ES describes an ESR as presenting the findings, conclusions and recommendations of a technical evaluation, including the applicable code provisions or acceptance criteria, product identification, installation guidance and conditions of use[1]. That is why a report is not simply a more detailed brochure: it connects a specific product to a defined evaluation basis and defined limitations.
| Question | Product data sheet | Code evaluation report |
|---|---|---|
| Primary purpose | Describe product attributes and specification information[4]. | Document technical findings against stated code provisions or acceptance criteria[1][2]. |
| Typical author | Manufacturer or supplier[4]. | An evaluation agency or code-evaluation program[1][2]. |
| What to verify | Profile, material, accessories, dimensions and referenced manuals[4]. | Product identity, code basis, installation conditions and limitations[1][2]. |
| What it does not prove | It is not automatically approval for every assembly. | It does not authorize installation outside its conditions of use or replace local review[1][3]. |
What does a manufacturer product data sheet tell you?
A useful data sheet answers, “What is this product?” Depending on the manufacturer and roof type, it may identify panel profile, metal type and thickness, seam or interlock geometry, finish, available lengths, minimum slope, trim, clips, fasteners and compatible accessories. A specification data sheet can also provide language that helps a contractor or specifier write a project specification[4]. Treat those details as product information, not a blanket promise for every assembly.
Read the revision date and product name carefully. A data sheet may cover a family of profiles while an actual proposal names only one. It may also refer you to an installation manual, structural tables, fire or wind test documentation, warranty terms or an evaluation report. The missing documents matter: a panel description does not establish that a particular roof deck, underlayment, clip spacing, flashing package or fastening pattern meets the requirements for your project[4].
What does a code evaluation report add?
An evaluation report answers, “Under what documented conditions may this product be used for the evaluated code provisions?” ICC-ES reports identify the evaluated product and explain the code requirements or acceptance criteria used; they also describe how the product should be installed to meet those requirements[1][2]. A report can therefore be valuable when a product is innovative, when a code official needs a formal compliance path, or when the manufacturer’s literature points to a tested assembly.
Reports commonly specify eligible substrates, roof slopes, fasteners, underlayment, spans, exposure conditions, limitations and installation details. Some programs publish supplements for additional state or local requirements[1]. A public report is evidence to review, not permission to change the assembly. If the proposed installation falls outside the report, the contractor or design professional must identify another accepted compliance path rather than stretching the report’s language.
How do I check the complete roofing system matches the documents?
Metal roofing performance belongs to the complete assembly. Compare the report’s product identification with the proposal’s profile and material. Then compare the listed clips or fasteners, spacing, substrate, underlayment, flashings, penetrations, valleys, edges and slope with the installation plan. A report that covers one panel profile does not automatically cover a visually similar profile, a different fastener, or a different attachment pattern[1][2].
This is also where a data sheet and report work together. The data sheet helps you recognize the product and its components; the report supplies the evaluated conditions. Manufacturer installation manuals and project-specific drawings may fill in practical details. NRCA notes that its technical manuals address roofing standards, building-code requirements and installation guidance, reinforcing that compliance is not just a product-label question[6].
How should I read the paperwork in a proposal?
Request a document set before signing: the current product data sheet, installation manual, report or approval number if one is cited, and the exact scope of work. Check the manufacturer and product family, report status and revision, evaluated code editions, allowable uses, required accessories and conditions of use. Look for exclusions, not just ratings. A report directory or agency page can help you locate the source document; ICC-ES identifies its directory as a resource used by code officials[1].
Then ask the contractor to show where the proposal matches the documents. Useful questions include: Which profile is being installed? What attachment method and spacing are specified? Does the report cover the existing deck and planned underlayment? Which flashings and penetrations are included? Who will address conditions that are outside the report? These questions are about document control and scope, not about diagnosing your roof from a distance.
Why does local review still matter in Missouri and Illinois?
Model-code documentation does not replace the authority having jurisdiction’s review. ICC-ES explains that supplements may address additional state and local requirements, while Texas Department of Insurance describes product evaluations as tools used by inspectors, engineers, contractors, builders and consumers to check adopted specifications and proper installation[1][3].
Do not infer an insurance result from a report. TDI expressly cautions that linking a third-party report does not mean the report provides evidence that an improvement complies with the applicable windstorm building code[3]. For a Missouri or Illinois home, the contractor and local building department can explain which documents are relevant. Keep the final approved scope, permit records and product documents with your home records.
How does Bishop's Metal Roofing fit the document process?
When comparing a Bishop's proposal with another metal-roofing proposal, ask for the same document set and compare the same system-level fields. Confirm the named product, accessories, installation method and written scope. Bishop's states a 50-year warranty, but the current written warranty controls its terms; a warranty is separate from a code evaluation report and should not be treated as proof of code compliance.
This educational article is general information, not a code determination, engineering opinion, legal advice, financial advice, insurance advice or a diagnosis of an unseen roof. Requirements vary by product, project and local authority. Verify the current documents, written scope and local requirements with the roofing professional and authority having jurisdiction. Bishop's business facts are stated only as provided in its manifest; current written contract and warranty documents control.