Test evidence, approvals and certifications · Lesson 4 of 4

Test evidence, approvals and certifications: defects, verification and case study

How to catch a bad evidence package: ten defects, eight checks, verification at the issuer, an illustrative coping case study, who decides the fix, how to log it, and why no document is a guarantee.

You will be able to: Name ten ways an evidence package goes wrong, verify a document at its source, diagnose an illustrative coping submittal, say who decides the correction, and record the finding.

10 min · 10 slides · 7 questions

All lessons in this module

Slide 1 of 10

A claim versus a record

A data-sheet sentence, a print-approval line or a brochure is a claim, not a record; ES-1 testing is shown by the test report or an ES-1 certificate.

Claim without a report: the sheet says tested but names no laboratory, report number or date.

A claim points to evidence; the report is the evidence. The bracketed words show what to ask for and are not real entries.

Sources

SPRI, ES-1 Testing in the Industry (draft-labelled file dated 2023-06-15, version 1.2) - SPRI
DM-16277 Econo Coping Technical Data Sheet 10.29.25 (a Drexel Metals publication held in AFS's records) - Drexel Metals
DM-15493 Econo-Coping Print Approval 11.03.25 (a Drexel Metals publication held in AFS's records) - Drexel Metals

Glossary

Basis mismatch: Comparing a demand and a tested value that are on different bases, for example psf against a classification, strength level against allowable stress, or a factor applied on one side only.
Scope limit: A statement in an approval of what it does not cover, such as a Miami-Dade Notice of Acceptance that excludes fire classification.
Verification at the source: Checking a document with the body that issued it, for example searching Intertek's directory for NRCA's certification, rather than trusting a copy.
Issue log: The record of each finding in a review: the document, the requirement, what was found, the source, who must supply what is missing, and a status.