Conformity Assessment Bodies (CABs) are increasingly receiving requests—often driven by regulatory expectations or market pressure—to apply test results to products beyond those physically tested. These requests most commonly arise from model number proliferation, regional part number variations, and post-issuance report revisions.
While CABs aim to support customers efficiently, ISO/IEC 17025 places clear limits on an accredited organization’s authority to make determinations related to conformity, applicability, or similarity for products that were not tested. When those limits are exceeded, testing organizations risk assuming responsibilities that properly belong to manufacturers, increasing exposure and weakening confidence in accredited testing.
The Practical Problem
Across regulatory discussions and routine testing activities, several recurring scenarios continue to surface.
Customers may request post-issuance revisions to test reports to add new or different model or part numbers—sometimes years after testing—asserting similarity to the originally tested product. Others seek to include multiple model numbers for a single tested sample, describing the products as identical hardware differentiated only by regional designation, labeling, or firmware. In addition, regulators—particularly outside the United States—may require the exact imported part number to appear on the test report and decline manufacturer justifications provided through a Supplier’s Declaration of Conformity (SDoC).
In each case, pressure is placed on the CAB to apply test results beyond the original tested configuration, often based on the assumption that accreditation confers both the authority and responsibility to do so. In practice, accreditation demonstrates that an organization is competent to perform specific tests and report objective results for the items submitted. It does not authorize the organization to determine whether those results apply to other products, configurations, or model numbers, nor does it create an obligation to make such determinations at the request of a customer or regulator.
This misunderstanding frequently arises because test reports are relied upon in downstream regulatory and market-access decisions. As a result, stakeholders may look to the testing organization to confirm product equivalence or extend test coverage. Those determinations, however, fall outside the scope of ISO/IEC 17025 testing and remain the responsibility of the manufacturer or of a conformity assessment body operating under a certification scheme.
This paper clarifies:
- What ISO/IEC 17025 permits organizations to report
- Where responsibility appropriately remains with the manufacturer
- Why informative annexes identified as customer-provided information represent a limited accommodation rather than an endorsement
- Why expectations for organizations to “extend” reports are misaligned with international conformity assessment principles
What ISO/IEC 17025 Allows — and What It Prohibits
In the testing industry, an organization’s primary product is the credibility of its reported results. That credibility depends not only on what is stated, but on how clearly and concisely those statements are made. ISO/IEC 17025 provides the framework that allows testing organizations to report results with confidence, supported by defined methods, controlled conditions, and objective evidence.
Traceability is central to this framework. Each item tested must be uniquely identified and described such that the original test configuration, conditions, and results can be reconstructed and verified. This requirement necessarily limits reporting to the specific item or configuration tested. Reported results therefore apply only to the tested item under the documented conditions and do not extend to other products or configurations without additional testing or a formally defined conformity assessment activity under an accredited scheme.
Clause 7.8 of ISO/IEC 17025 establishes the requirements governing the content and structure of test reports. These requirements set expectations for how results are presented, how test items are identified, and how traceability is maintained, providing the basis for understanding both what may be reported and where reporting boundaries exist.
Within this structure, Clause 7.8.2.2 allows additional information to be included in a test report, provided it is clearly identified and does not affect the validity of the results. This provision is often cited when organizations include supplemental content—such as customer-provided model numbers—outside the core reporting of test results. However, the inclusion of such information does not permit opinions, interpretations, or applicability determinations for products that were not tested, nor does it expand the scope of the report.
In practice, this allowance is sometimes addressed through informative annexes containing customer-provided information. When model numbers are known prior to report issuance, an annex may reflect that information, provided it is clearly labeled as customer-supplied and separated from the organization’s statements of test results. The presence of such information does not constitute an assessment of product similarity, an endorsement of those model numbers, or a statement of conformity or applicability for products other than the item tested.
Product Similarity and the Limits of Organizational Authority
In test reporting, product similarity generally refers to assertions that multiple products may be considered equivalent for regulatory or compliance purposes. These assertions often involve products sharing common hardware but marketed under different part numbers, products with regional variations, or products differing only in labeling, software, or firmware configuration. While these distinctions may appear administrative, they can carry technical and regulatory implications.
Determining whether products are sufficiently similar for test results to be considered applicable requires evaluation of design, configuration, components, and operating conditions. This process involves technical judgment rather than objective reporting and requires consideration of whether differences—however minor they may appear—could affect compliance.
ISO/IEC 17025 distinguishes clearly between reporting objective test results and making opinions, interpretations, or conformity determinations. Clause 7.8.6 addresses opinions and interpretations, while Clause 7.8.7 governs statements of conformity and requires documented decision rules. Extending test results to products that were not tested therefore constitutes an opinion, interpretation, or conformity judgment.
Accreditation confirms an organization’s competence to perform specified tests and report the resulting data. It does not authorize the organization to determine product equivalence or to declare that results apply to configurations that were not tested. Such determinations remain the responsibility of the manufacturer or of a conformity assessment body operating under an appropriate certification scheme.
Use of Informative Annexes and Post-Issuance Model Number Requests
Testing organizations are often asked to include information in test reports that is not generated through testing but is needed for administrative or regulatory purposes. One common accommodation is the use of informative annexes identified as containing customer-provided information, separated from the body of the test report to distinguish customer assertions from objective test results.
When model numbers are known prior to report issuance, such annexes may be used to reflect customer-supplied identifiers without implying that the organization has evaluated product similarity or extended the applicability of test results. Clear labeling, appropriate disclaimers, and separation from reported results are key to maintaining this distinction.
Additional challenges arise when this approach is applied after report issuance. Requests to add new or different model numbers months or years later introduce increased risk. Over time, products may undergo design changes, component substitutions, firmware updates, or manufacturing relocations, and traceability to the originally tested configuration may be reduced or lost. In these circumstances, annex updates can be perceived as a means of reusing an existing report for a different product, regardless of customer intent.
Similar issues arise when customers seek to list multiple model numbers based on claims of identical hardware with minor variations. While annexes may record customer assertions, they cannot replace an assessment of similarity or a determination of applicability. Informative annexes also cannot serve as evidence that the testing organization has approved or declared conformity for products that were not tested. Justification for applying test results to non-tested products remains the responsibility of the manufacturer, typically through documentation such as an SDoC.
Manufacturer and Testing Organization Responsibilities
A clear separation of responsibilities between manufacturers and testing organizations underpins the conformity assessment system. Manufacturers are responsible for product configuration control, managing changes, justifying claims of similarity, determining regulatory applicability, and issuing declarations of conformity.
Testing organizations accredited to ISO/IEC 17025 serve a complementary role by conducting testing on specified samples, reporting objective and traceable results, and maintaining impartiality. Accreditation demonstrates competence within a defined testing scope; it does not transfer manufacturer responsibilities or authorize applicability determinations for non-tested products.
Requests for testing organizations to justify similarity or apply results beyond the tested item represent a shift in responsibility that is not supported by ISO/IEC 17025 and risks undermining confidence in accredited testing.
Regulatory Expectations and International Misalignment
In some jurisdictions, regulators expect test reports to list the exact part number being imported or to state that results apply to that part number even when it was not tested. These expectations are often driven by legitimate enforcement needs but can conflict with ISO/IEC 17025, which limits organizations to reporting objective results for tested items.
When regulators expect applicability or conformity statements for non-tested products, testing organizations may be asked to perform activities that fall outside accredited testing. Alternatives exist, including manufacturer-issued SDoCs and supporting technical justification provided outside the test report.
Where expectations are misaligned, inconsistent practices may develop, organizations may feel pressure to exceed scope, and confusion can arise regarding the meaning and authority of test reports. Addressing this misalignment through clear communication and shared understanding supports confidence in accredited testing.
Navigating Product Similarity Challenges in Practice
Within these boundaries, both CABs and manufacturers have practical options for navigating challenges related to product similarity, model number proliferation, and regulatory expectations.
Testing organizations can support clarity by maintaining consistent internal practices for report content, use of informative annexes, and post-issuance revisions, and by communicating clearly about the limits of accredited reporting. Early engagement with customers—particularly when model number strategies or regulatory pathways are known in advance—can reduce downstream pressure to modify reports.
Manufacturers are best positioned to address similarity and applicability through configuration control and supporting documentation. Clearly defining product variants, maintaining traceability across design changes, and providing technical justification through SDoCs can reduce reliance on test report modifications.
Conclusion
The challenges surrounding product similarity, model number inclusion, and post-issuance report revisions reflect broader misalignment in expectations regarding the role and authority of ISO/IEC 17025 accredited testing.
Accredited testing organizations report objective results for the specific items tested under documented conditions. While ISO/IEC 17025 permits clearly identified additional information, it does not authorize extension of test coverage, applicability determinations for non-tested products, or transfer of manufacturer responsibilities. Informative annexes may support administrative clarity but cannot substitute for conformity assessment or regulatory justification.
Preserving a clear separation of roles is essential to accreditation integrity. Manufacturers remain responsible for product control, similarity justification, and conformity declarations, while testing organizations remain responsible for impartial testing and accurate reporting. Consistent application of ISO/IEC 17025 supports confidence in test reports and preserves the credibility of accredited testing in an increasingly complex regulatory environment.