Understanding ICC-ES evaluation reports and product approval processes.
2
hours
0.2
CEUs
Building Products
1.7.2
Understanding ICC-ES evaluation reports and product approval processes.
Format
On-Demand Online
Delivery
Self-Paced
Access
24/7 After Enrollment
Certification
Certificate of Completion
Have questions about this course or our platform?
Contact our support teamUnderstand ICC-ES evaluation and approval criteria
Start with the problem that evaluation reports exist to solve. The model codes are largely prescriptive: they name the materials, assemblies, and installation methods that experience and testing have shown to work. But manufacturers continually bring products to market that the code never anticipated — proprietary anchors and fasteners, engineered connectors, foam plastic assemblies, coatings, cladding systems, entire alternative methods of construction. Every I-Code therefore contains an administrative provision allowing the building official to accept alternative materials, designs, and methods that are not specifically prescribed, provided the alternative meets the intent of the code and is at least equivalent to what it prescribes. That channel is discretionary, and it runs on evidence: per the Building Department Administration text, the official may use whatever credible means are available — evaluation reports, engineering analysis, laboratory test results, or documented acceptance by other respected building departments — and must be able to demonstrate the basis for acceptance.
This is where ICC Evaluation Service (ICC-ES) fits. ICC-ES is a nonprofit subsidiary of the International Code Council, formed when the three legacy evaluation services were consolidated at the birth of the ICC — an organization, as the administration literature puts it, created for code officials by code officials. Its lineage runs back to the 1930s, when regional groups of building departments first recognized that individual jurisdictions could not evaluate the flood of new products with uniformity or technical independence. ICC-ES employs a large staff of professional architects and engineers whose entire job is assessing code compliance. A manufacturer submits test reports, product data, and quality-control documentation; when compliance is demonstrated, ICC-ES publishes an evaluation report describing the product, its approved uses, and the conditions under which it complies.
For product categories the code does not adequately address, ICC-ES first develops acceptance criteria — documents defining the technical data, test standards, and manufacturing quality-control measures needed to justify recognition of that class of product. Acceptance criteria are considered at public hearings before an evaluation committee of practicing code officials, and hundreds have been developed and posted for free public access. Quality control is integral to the system: periodic factory inspections by accredited agencies provide ongoing assurance that the product being shipped is the product that was evaluated.
The essential concept for the practitioner: an evaluation report is packaged evidence for the alternative-materials decision, produced by an organization doing work no single building department could do on its own. It informs the building official's judgment; it does not replace it.
A plans examiner receives a submittal for a mid-rise project specifying a proprietary post-installed concrete anchor in place of the prescriptive cast-in-place anchorage. The manufacturer's catalog page is attached, but nothing else. The examiner's first question is not "does this product work?" — it is "what evidence of code compliance accompanies it?" A search of the ICC-ES online directory turns up a current evaluation report for the anchor. Now the review has traction: the report identifies the code editions evaluated against, the concrete conditions and load types covered, the installation parameters, and the special inspection expectations. The examiner checks that the proposed use falls inside that envelope and requires the report number on the approved construction documents so the field inspector can pull the same report.
Contrast the neighboring case: a second proprietary product on the same job has no evaluation report at all. That does not make it unapprovable — it makes it an ordinary alternative-materials request, with the applicant assembling the evidence: approved-agency test data, an engineering analysis demonstrating equivalency, or comparable documentation. In a genuinely difficult case, the department can ask ICC-ES itself for a Building Department Service — supplying what is known about the product and its proposed installation, and receiving a priority technical opinion — a slower, costlier path used when no report exists and the stakes justify it. The report does not create the approval channel; it just makes traveling it far faster and more reliable.
The most common error is treating a manufacturer's data sheet or marketing literature as equivalent to an evaluation report. Catalog claims are not independent verification; require either a current evaluation report or a properly documented alternative-materials submittal. A second error runs the opposite direction: treating the absence of a report as automatic grounds for rejection. The code's alternative-methods provision predates and outranks any private evaluation program — the official must still consider test data and engineering analysis on their merits, and when denying an alternative should state the reasons in writing. A third error is assuming that because ICC-ES is an ICC subsidiary, its reports carry regulatory force of their own. They do not; they are technical evidence offered to the authority having jurisdiction, and the adopted code and local amendments always govern. Finally, confirm the report was issued against a code edition relevant to the one the jurisdiction has adopted — the compliance basis matters, not just the report's existence.
Interpret evaluation reports and scope limitations
An evaluation report is a structured document, and reading it well is a learnable skill. The Building Department Administration text describes the report's contents in exactly the terms an inspector needs: it describes the product and its uses, provides installation instructions, points out how the product can be identified in the field, and lists the evidence relied on in determining compliance. Translate that into a reading order.
First, the scope. Every report opens by identifying the product evaluated and the specific uses and code provisions it was evaluated against. This is the report's outer boundary: a structural screw evaluated for wood-to-wood connections is not thereby evaluated for steel; a coating evaluated for interior use is not thereby evaluated for weather exposure. If the proposed application is not named in the scope, the report is silent on it — and silence is not approval.
Second, the conditions of use. This is the section practitioners skip at their peril, because it is where the report imposes its own limits: substrate types and thicknesses, fastener patterns and edge distances, load limits, exposure restrictions, required special inspections, and design provisions that must accompany the product. The blanket rule from the administration literature is worth memorizing: a department can rely on a reported product only if the product is as described in the report, is installed in accordance with the report, and meets all the conditions of the report. All three legs must hold.
Third, the compliance basis — which code editions and acceptance criteria the evaluation rests on. A report issued against an older edition may not align with provisions the jurisdiction has since adopted; the examiner must judge whether the differences matter for the use at hand.
Fourth, identification, labeling, and quality assurance. The report states how conforming product is marked — manufacturer name, model designation, report number, or listing mark — and describes the follow-up factory inspection program. Field identification ties the physical object on site back to the paper evaluation.
Fifth, currency. Reports carry issue and revision dates and defined validity periods; they are reexamined, revised, and sometimes withdrawn. Because they are published online for free access, the authoritative version is always the one posted now, not the PDF stapled into a two-year-old submittal. Checking currency online should be reflex.
A plans examiner reviews a submittal for a wood-framed multifamily building that uses a proprietary shear connector system in place of conventional detailing. The drawings cite an evaluation report by number. The examiner pulls the current report from the ICC-ES directory and works the reading order. Scope: the connector is evaluated for the seismic design categories and framing configuration proposed — good. Conditions of use: the report requires a minimum framing member size, a manufacturer-supplied fastener, and periodic special inspection of installation — and the statement of special inspections omits it. That becomes a plan-review comment: not a rejection of the product, but a required correction so the approved documents match the report's conditions. Compliance basis: the report was issued under the edition the jurisdiction has adopted — no gap to reconcile. Finally, the examiner confirms the report is active and requires the report number on the cover sheet of the approved plans, so the field inspector inherits the same reference. This is the plan-review discipline that makes field inspection possible: the report is reviewed at the desk to determine compliance of the design, then used again on site to verify the construction matches what was approved.
The classic interpretation error is reading only the scope and stopping — accepting a product because "it has a report" without verifying each condition of use against the actual design. The correction is a condition-by-condition check, documented in the plan-review record. A related error is accepting an outdated copy of a report from the submittal package rather than confirming the current posted version; a revision may have narrowed the scope or added conditions. Examiners also err by extrapolating between products from the same manufacturer — a report covers the specific models named, not the product line. Finally, some reviewers treat the report's installation instructions as advisory. They are not: installation in accordance with the report is one of the three legs on which reliance stands, and an installation that deviates from the report is outside the evaluation entirely.
Understand conditions of use and certification limitations
Understanding what an evaluation report is requires equal clarity about what it is not. It is not a blanket approval: the building official retains the judgment and responsibility the code assigns, and a report is evidence offered to that judgment. It is not valid outside its own conditions: the moment a product is installed on an unlisted substrate, with an unlisted fastener, beyond a stated limit, or without a required special inspection, it is no longer the evaluated installation — it is an unevaluated alternative needing its own justification. And it is not a substitute for the adopted code: where a report and the locally adopted code or amendments conflict, the code governs.
For the field inspector, this converts into a two-question verification. Question one: is the installed product actually the listed product? The report tells the inspector how conforming product is identified — labels, stamps, model designations, the report number on packaging or the product itself. An unmarked product, or one whose model number does not match, cannot be tied to the evaluation, and the paper trail collapses. Question two: are the report's conditions met on this site? That means physically checking what the conditions name: the substrate, the fastening size, pattern, spacing, and edge distances, embedment depths, required accessories, and whether required special inspections occurred. The administration literature is explicit that this is the inspector's role: the plans examiner reviews the report to determine compliance of the design, and the inspector then uses it on site to verify the construction complies with the approved report.
When either answer is no, the inspector has a mismatch call to make, and the discipline is to frame it correctly. The finding is not "this product is bad"; it is "this installation is outside the conditions of the evaluation, and therefore lacks demonstrated code compliance." The resolutions follow: bring the installation into conformance with the report, or route the as-built condition through the alternative-materials process with its own engineering justification. Quiet acceptance is not available — approval outside the evaluated conditions leaves the department with no defensible basis.
Awareness of acceptance criteria completes the picture. Behind every report for an innovative product class stands an acceptance-criteria document defining how that class is tested and what quality control it requires. An inspector need not master these documents, but knowing they exist explains why reports in the same category impose similar conditions — and why those conditions are not arbitrary fine print but the distilled terms under which the product class was found to comply.
A framing inspector on a light-commercial project encounters a proprietary powder-actuated fastening system attaching cold-formed steel track. The approved plans carry an evaluation report number, so the inspector pulls the current report on site. Identification checks out — the fasteners and tool match the models named in the report. The conditions of use do not. The report lists the fastener for attachment to structural steel of a stated minimum thickness and to normal-weight concrete of a stated minimum compressive strength; on this project, a section of track has been shot into a lightweight-concrete topping slab, a substrate the report never names. The installer's position is that the fasteners "hold fine." That may even be true — but it is exactly the argument the evaluation system exists to replace. The inspector writes the correction citing the mismatch between the installed substrate and the report's conditions of use, with the resolution paths laid out: refasten per the report on a conforming substrate, or have the design professional submit substantiating data for the unlisted substrate through the alternative-materials process. The report made the first ninety percent of this inspection fast; the inspector's judgment handled the last ten percent — precisely the division of labor the system intends.
The overarching mistake is treating a report as a talisman — "it has an ESR" — rather than a bounded technical document. Corrections follow the boundaries. Do not accept an unidentifiable product against a report; verify labels and model numbers. Do not accept installed conditions that deviate from the report's named substrates, fasteners, spacings, or limits; the evaluation does not travel outside them. Do not let a report override the locally adopted code or amendments. Do not skip special inspections named as conditions of the report — a condition unmet is an evaluation unfulfilled. And frame a mismatch not as a product defect but as an absence of demonstrated compliance, which the responsible parties can cure with conforming installation or independent justification.
This course examined ICC-ES evaluation reports as the working link between innovative building products and code compliance. Prescriptive codes cannot anticipate every proprietary product, so the codes provide an evidence-driven alternative materials and methods channel — and ICC-ES, the nonprofit ICC subsidiary, exists to produce that evidence at a technical depth no single building department could sustain. Participants learned to read a report in order — scope, conditions of use, compliance basis, identification and quality assurance, currency — and to apply the three-legged reliance rule: the product must be as described, installed in accordance with the report, and in compliance with all its conditions. Equally important is what a report is not: a blanket approval, a document valid outside its conditions, or a substitute for the adopted code. Plan reviewers anchor proprietary systems by requiring report numbers on approved documents; inspectors close the loop by verifying identification and conditions on site and framing mismatches as absent compliance to be cured.