Icc-Es Evaluation Report Lookup Data: Dataset Structure and Field Coverage

An ICC-ES evaluation report lookup starts at the ICC-ES Evaluation Reports Directory maintained at icc-es.org/reports-directory by ICC Evaluation Service, a subsidiary of the International Code Council. On Datadory's 21 August 2026 verification pass the directory's result table held about 2,461 rows — one record per issued report, each covering a single manufacturer's product line and each linking to a multi-page signed PDF.

Those rows span more than twenty report programs: Evaluation Service Reports (ESRs), Evaluation Service Listings (ESLs), Canadian Listings (ELC), Design Listings, IRC Equivalency Reports (EER), CodeMark Australia, Legacy Reports, Formaldehyde Emission reports, Environmental Product Declarations (EPDs), VAR Environmental Reports, DASMA thermal performance verifications, regional supplements for Los Angeles, California, Florida, DSA/OSHPD, APA joint reports and Oceania, and PMG plumbing/mechanical/gas listings including India, Canadian, WaterSense, WaterMark and cabinetry variants. The breadth is deliberate: a model-code evaluation for structural products, a listing for plumbing fittings, and an environmental declaration sit in one searchable table, so one query covers all three document families.

Two audiences drive the query. Building officials confirm a product carries a current report before accepting it, and manufacturers cite the report number in submittals. Within Datadory's building-products slice — 24 primary datasets, 17 of them free outright — this is the only record dedicated to code-compliance evaluation, and Datadory rates it quality score 8.

Four columns settle most lookups:

• Report Number — the citable identifier, and the formats vary by era and program: modern ESR numbering (ESR-1234), older legacy strings such as BOCA-95-47.02, and PMG-1020-style plumbing/mechanical/gas listings.
• Manufacturer — the report holder whose product line the report covers.
• Product Name — the evaluated product or system exactly as stated in the report.
• Codes — legend badges showing which editions the evaluation supports: I-Codes editions, LC (Legacy Code), OS (Other Standards), CBC, FBC.

Report Type and CSI Division Number round out the row; the division value mirrors the CSI MasterFormat division printed inside the PDF, such as "03 - Concrete" for concrete products.

Sample rows show how much the formats differ. BOCA-95-47.02 covers Watts Radiant, Inc.'s Onix Radiant Heating Hose in five inner diameters (3/8 through 3/4 inch I.D.). CM-90002 covers TMA Corporation Pty Ltd.'s Termimesh System TM2 under OS (Other Standards). Row 93-04.01 covers Dean Enterprises, Inc.'s DECO Penetrating Concrete Sealer 20 under LC (Legacy Code). If a submittal hands you any one of those identifiers, an evaluation report search by number is the decisive path; if it names only a product, work from manufacturer plus product type instead.

The directory's search form mirrors exactly the questions a plans examiner asks: report type, report number, SASC certificate number, design listing number, product name, product type, code edition, referenced standard, manufacturer and country. Run it in this order:

1. Set Report Type if you know the program — ESR for model-code evaluations, PMG for plumbing and mechanical listings, EPD for environmental declarations, ELC for Canadian listings.
2. Enter the report number when the submittal names one; this confirms the number is real and currently listed.
3. Filter by Manufacturer or Product Name when you hold a product but no number.
4. Narrow by code edition — I-Codes editions from 2000 through 2024, IGCC, CALGreen, CBC, FBC among others — and by referenced standard (ASTM, ANSI, UL, CSA and more) to match what your jurisdiction enforces.
5. Browse by CSI MasterFormat division instead when scoping a category rather than a product: divisions run from 01 General Requirements through 40 Process Integration.
6. Open the hit's /report-listing/<report-number>/ page, which embeds the full signed PDF, and read the Codes badges against your adopted code cycle.
7. Record the number, holder and code editions in the permit file, then recheck before each new submittal — the directory refreshes weekly, so status can change between jobs.

Every ICC-ES report follows a fixed eleven-part structure, which makes the documents skimmable under deadline: QR code, CSI division number, report holder, evaluation subject, evaluation scope, properties evaluated, uses, description, installation, conditions of use, evidence submitted, and identification.

Three of those parts carry the decision weight. Properties Evaluated states what was assessed — structural, fire, durability. Conditions of Use states the limitations, and it is where an approval quietly narrows: a product cleared for one substrate or exposure may fail another. Evidence Submitted lists the test reports and data the evaluation relied on, which tells a reviewer whether the basis is a current standard edition or a superseded one. The QR code ties the printed sheet back to the live directory entry, so a paper copy can be checked against the 2,461-row register rather than trusted on its face.

ICC-ES answers whether a product cleared code; the rest of the building-products stack verifies everything around it. The building products data guide maps all 38 datasets Datadory catalogs for the industry — 24 primary and 14 related — from the Sweets Building Product Catalog and Specification Data — tens of thousands of listings across 35 MasterFormat divisions — to the Census and Eurostat series behind demand cycles.

Two sibling guides extend this one directly: the window u-factor SHGC ratings database walkthrough covers the thermal-performance side of fenestration submittals, and the building products MasterFormat directory guide covers spec organization by CSI division. For the wider landscape, start at the building-products data hub.