1. What Is ICC-ES Acceptance Criteria and Evaluation Reports?
ICC-ES Acceptance Criteria and Evaluation Reports form a technical code-qualification system for building products, materials, components, and construction methods. They are not a conventional management framework. Acceptance Criteria establish an evaluation basis where code provisions or referenced standards do not adequately address a product; Evaluation Reports document product-specific findings, permitted applications, and limitations. ICC-ES means ICC Evaluation Service; ICC stands for International Code Council.
For executives and consultants, the central question is: What evidence and operating controls are needed to substantiate the uses we intend to sell? For manufacturers of insulation and roofing products, that question should shape product configurations, testing investment, factory readiness, and launch claims.
2. Origin and Background
ICC-ES was established in 2003 through the consolidation of four legacy building-product evaluation services. Acceptance criteria and evaluation reports existed within those predecessor organizations, so the approach predates the consolidated institution. Its origin is institutional rather than attributable to an individual management thinker.
The underlying problem was—and remains—how to evaluate alternative products that codes do not explicitly describe. ICC-ES technical staff develop criteria with applicant and stakeholder input. Product-related criteria generally proceed through public review and an Evaluation Committee composed of code officials. The system provides a repeatable technical basis for assessing innovation without treating a manufacturer’s claims as sufficient evidence.
3. How ICC-ES Acceptance Criteria and Evaluation Reports Works
Acceptance Criteria: the evaluation requirements
Acceptance Criteria, abbreviated AC, establish requirements for evaluating defined product categories or applications. They can address testing, engineering analysis, performance requirements, and supporting documentation. For example, AC04 addresses sandwich panels, while AC10 addresses quality documentation. Selecting a criterion requires examining its applicability, not merely matching a product name to a directory entry.
Evidence: connecting performance to production
The evaluation combines relevant test results, calculations, product descriptions, installation instructions, and manufacturing quality documentation. A qualifying factory inspection verifies consistency between manufactured products and those presented for recognition, together with implementation of the documented quality system. Laboratory performance and production control are therefore connected, not separate workstreams.
Evaluation Reports: a bounded conclusion
An Evaluation Service Report, abbreviated ESR, identifies the report holder, evaluated products, applicable codes, properties evaluated, uses, installation requirements, conditions of use, evidence submitted, and product identification. Its conclusion is bounded by that scope. Executives should analyze a product–configuration–application combination, not assume that one report qualifies every variant sold under a brand.
Structural and fire claims require different evidence
Structural qualification does not automatically establish fire performance. ASTM International’s E84 test addresses surface-burning characteristics; E119 evaluates fire resistance of building elements and assemblies under specified exposure conditions. A favorable flame-spread result is not an hourly fire-resistance rating. For siding and cladding, scrutinize the evaluated wall configuration rather than treating a material test as qualification of every possible assembly.
4. When to Use ICC-ES Acceptance Criteria and Evaluation Reports
This approach is particularly useful when launching an alternative structural product, expanding an existing report’s scope, entering jurisdictions with different requirements, or assessing an acquisition’s product claims. It helps structure questions such as:
- Which panel thicknesses, connections, substrates, and applications should the initial qualification cover?
- Which commercial claims lack adequate evidence?
- Can another manufacturing facility consistently produce the evaluated product?
- Does the proposed market require additional jurisdiction-specific documentation?
An ESR supports code-compliance review; it does not replace the building official’s project-approval responsibilities. Model-code coverage also needs to be distinguished from state or local requirements, which may require supplementary evaluation.
Bring together engineering, quality, manufacturing, technical sales, and qualified testing specialists. Useful inputs include drawings, material specifications, existing reports, proposed installation details, and target applications. A preliminary scope assessment is different from completing qualification: specimens, laboratory availability, review iterations, inspections, and possible criteria development determine the schedule.
The approach is misleading when production differs from evaluated specimens or intended installations fall outside the evidence. It is also not a substitute for market research, profitability analysis, or determining whether a direct code-compliance or listing route would be more appropriate.
5. How to Apply ICC-ES Acceptance Criteria and Evaluation Reports: Step-by-Step
Clarify the decision and scope. Define the applications to qualify, target jurisdictions, launch horizon, and commercial claims. Separate roof from wall uses, load-bearing from nonload-bearing applications, and structural claims from fire-performance claims.
Agree on the evaluation route. Review applicable codes, standards, and existing criteria with ICC-ES before commissioning tests. Confirm the proposed scope, laboratory eligibility, specimen selection, and documentation expectations. Avoid spending against an assumed qualification pathway.
Define configuration-level units. Identify material formulations, dimensions, facings, connections, substrates, manufacturing locations, and installation arrangements. Establish which combinations need separate evidence and which may be grouped only with technical justification.
Build a requirements-to-evidence matrix. For each intended claim, record the applicable requirement, supporting test or analysis, specimen configuration, evidence status, gap, owner, and dependency. This is a management artifact supporting the evaluation—not a replacement for ICC-ES documentation.
Interpret gaps and limitations. Have qualified specialists assess whether evidence supports the intended application. Examine connections and complete load paths, not just component strength. For fire claims, match the property claimed to the relevant test and assembly configuration.
Translate findings into release decisions. Fund missing evidence, narrow unsupported claims, or redesign configurations. Submit the evaluation package and complete required review and inspection activities. ICC-ES—not the consulting team—issues the report. Align sales literature and installation documents with its final scope.
Test alternative assumptions. Examine how supplier substitutions, wider spans, different supports, another plant, or revised target applications affect the qualification plan. Sensitivity analysis can reveal additional work; it cannot waive technical requirements or authorize extrapolation.
Align stakeholders and maintain control. Assign ownership for report maintenance, manufacturing conformity, installation guidance, and change review. Establish escalation before changes affect evaluated products. Include continuing inspections and report-maintenance obligations in the operating plan.
For a multi-plant manufacturer, qualification program management should coordinate specimen production, testing dependencies, technical submissions, factory readiness, and launch decisions. The deliverable is an executable qualification plan with clear accountability—not simply a collection of test reports.
6. Example: ICC-ES Acceptance Criteria and Evaluation Reports in Action
Fictional example: Northline Panel Systems develops insulated metal roof and wall panels for industrial buildings. Its sales team proposes three thicknesses, production at two plants, and an hourly fire-resistance claim.
The technical director uses the ICC-ES pathway to distinguish desired applications from substantiated ones. Following scope discussions, the team plans the applicable sandwich-panel evaluation and maps each thickness, facing, support arrangement, and manufacturing location to its evidence.
The matrix exposes three gaps: incomplete support for certain wall connections, no assembly evidence supporting the proposed hourly rating, and inconsistent production records at the second plant. Surface-burning results do not resolve the fire-resistance gap.
Northline prioritizes configurations for which it can complete the necessary evidence. Following evaluation, it launches only the roof and nonload-bearing wall uses covered by the issued report, subject to its conditions, and defers the rated-wall opportunity.
The operations team commissions quality system design to establish material controls, traceability, release checks, and change escalation. Technical sales receives a claims checklist, while installers receive configuration-specific guidance. The commercial benefit is a defensible initial offering, not an assumption of unrestricted market access.
7. Strengths and Limitations
Strengths
- Explicit boundaries: The approach makes evaluated applications and restrictions visible to engineering and commercial teams.
- Reusable technical evidence: A published report provides a common reference for designers, specifiers, and code officials.
- Production discipline: Linking qualifying evidence to manufacturing controls helps keep the commercial product aligned with the evaluated product.
Limitations
An ESR addresses specified properties and applications; it is not a blanket endorsement, warranty, or assessment of every product attribute. Project-specific design and approval work can remain necessary.
Assembly variations are especially important for fire performance: changes in materials, dimensions, construction, or openings can affect applicability of test results. Management should therefore resist turning a qualified configuration into a broad claim about an entire product family.
8. Common Pitfalls and How to Avoid Them
- Testing before defining scope. Results may not support the intended application. Agree on the evaluation basis and specimen configurations before authorizing laboratory expenditure.
- Treating the report number as a badge. Commercial teams overlook restrictions. Translate conditions of use into quotation, specification, and installation checks.
- Conflating fire properties. Keep surface-burning, fire-resistance, and other fire-related claims distinct, with evidence assigned to each claim.
- Grouping variants without justification. Document differences in materials, geometry, connections, and production locations; obtain technical confirmation before extending conclusions.
- Using stale documents. Check the report’s current status, covered code editions, applicable criteria, and supplements rather than relying on an archived sales attachment.
- Stopping at issuance. Assign ongoing owners for conformity, changes, inspections, and report maintenance. Treat qualification as a controlled product lifecycle, not a one-time launch task.
9. How ICC-ES Acceptance Criteria and Evaluation Reports Relates to Other Frameworks
Stage-Gate: controlling development investment
Stage-Gate organizes product development into stages separated by management decisions. Use it before and alongside qualification to decide whether to fund testing, redesign, or tooling. The distinction is straightforward: Stage-Gate governs investment progression; the ICC-ES pathway substantiates defined code-compliance claims. For a new panel system, establish the intended qualification scope before committing major production capital.
Failure Mode and Effects Analysis: anticipating failure
Failure Mode and Effects Analysis, or FMEA, identifies potential failures and prioritizes preventive action. Apply it alongside qualification to examine manufacturing and installation risks such as inconsistent bonding, incorrect fasteners, or omitted protection. It can guide process controls and training, but risk rankings cannot replace required evidence. Prefer FMEA when the immediate question is how a process might fail; use the ICC-ES pathway when the question is whether an application has an adequate evaluation basis.
10. Key Takeaways
- Acceptance Criteria establish an evaluation basis; ESRs document product-specific conclusions.
- Qualify configurations and applications—not brands or unrestricted product families.
- Separate structural and fire claims, and substantiate each appropriately.
- Connect testing to factory controls, installation guidance, and commercial claims.
- Use qualification findings to prioritize investment and narrow initial launch scope.
- A report supports approval decisions; it does not eliminate project-specific requirements.
11. FAQs About ICC-ES Acceptance Criteria and Evaluation Reports
Does every building product need new Acceptance Criteria?
No. Existing code provisions, referenced standards, or established criteria may provide the evaluation basis. New criteria address gaps or unresolved issues. Confirm the route with ICC-ES before assuming that criteria development—or a particular testing program—is necessary.
Does an ESR guarantee local project approval?
No. The building official assesses the proposed use under the applicable requirements. Submit the relevant report together with project-specific documentation, and demonstrate that the actual product, configuration, and installation fall within its scope.
How long does an ICC-ES evaluation take?
Build the schedule around the agreed scope rather than a generic benchmark. Existing evidence, specimen readiness, laboratory capacity, review iterations, factory inspections, and possible criteria development all influence completion. Distinguish the internal planning deadline from the date when a report is actually issued.
