Test evidence, approvals and certifications
What counts as evidence that a flashing or edge-metal product performs: test standards, reports, listings, approvals and evaluation reports, how to match them to a project, and how to catch a bad evidence package.
4 lessons · about 45 min · 13 diagrams · 1 video
Version 1.0.0
Builds on these modules
Lessons
0 of 4 complete
Lesson 1 · 10 min · 9 slides · 8 questions
Test evidence, approvals and certifications: principles and terminology
What counts as evidence that a flashing or edge-metal product performs: the chain from test standard to inspection, who issues which document, why a test proves only one assembly, and what AFS can show today.
You will be able to: Tell a test standard, a test report, a listing, an evaluation report, an approval and a manufacturer claim apart; say who issues each; and state what AFS can and cannot show as evidence today.
Not startedStart →Lesson 2 · 14 min · 12 slides · 11 questions
Test evidence, approvals and certifications: materials, standards and design constraints
Which evidence fits which product: the RE-1, RE-2 and RE-3 tests, how results are written, installing as tested, extension by similarity, code editions, other routes to acceptance, and material and finish evidence.
You will be able to: Pick the ES-1 test a product needs, read how a result is expressed, explain why an assembly must be installed as tested, apply the five-condition similarity rule, and name the code, programme, approval and material evidence that applies.
Not startedStart →Lesson 3 · 11 min · 10 slides · 8 questions
Test evidence, approvals and certifications: methods and worked application
A documented method for matching evidence to a project, with an illustrative demand worked through AFS's wind function, Drexel's published ratings read against it, a range check, a coping caution and a submittal evidence matrix.
You will be able to: Apply a seven-step method to match evidence to a project: state the demand and its basis, read a published rating against it, run the range check, flag the coping caution, and build an evidence matrix with a verdict per row.
Not startedStart →Lesson 4 · 10 min · 10 slides · 7 questions
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.
Not startedStart →
Practical task
Build an evidence packet for one roof-edge detail: name the ES-1 test it needs, mark up the assembly, line the evidence up against the requirement in a matrix, compare an illustrative demand with a published rating, and list what is missing and who must supply it.
Hand in
- A decision rationale naming the ES-1 test (RE-2 or RE-3) the detail needs and why, with the ES-1 section it rests on
- A marked-up section showing the cover, cleat, fasteners and their spacing, the splice and the nailer, with the parts the test does and does not cover labelled
- An evidence matrix with one row per requirement: the evidence offered, whether it matches the exact assembly, size, date and scope, and a verdict of accept, request or reject
- A demand-versus-published table for stated, illustrative wind inputs, with the factor and the basis stated, and the published values labelled as the manufacturer's
- A gap list naming each missing document and who must supply it, plus a one-page "what to ask the supplier" list
Rubric
| Criterion | Meets the standard when |
|---|---|
| Test choice | The packet picks RE-2 or RE-3 correctly from the exposed horizontal part and cites ES-1. |
| Assembly match | Every attribute of the assembly is compared with the record: product, metal, gauge, cleat, fasteners, spacing, splice and size. |
| Basis | Demand and published value are on the same stated basis, with the factor named and attributed to the engineer of record. |
| No pass or fail from one coping number | A coping with one published number is marked "request the test report", not passed or failed. |
| Gaps named | Each missing document is named with who must supply it; nothing is guessed or assumed. |
| Verdicts | Each matrix row ends in accept, request or reject with a reason that cites a document. |
| Safety | The packet states that evidence review is desk work and that anyone on a roof edge follows 29 CFR 1926.501. |