Build a document-match record
Record issuer, report identifier, revision, named product, profile, application and conditions. Match that identity against the quotation. Keep evaluation reports, installation instructions, warranties and maintenance guidance in separate records: they answer different questions. A report can be useful without covering every consumer attribute.
Resolve conflicts explicitly
Do not select the more favorable statement when two documents disagree. Preserve both document identities and ask the manufacturer or responsible reviewer which applies. Until then, keep the relevant requirement unresolved. The next reviewer should see the conflict, not just a completed checkbox.
Read beyond the cover and report number
An evaluation report concerns an identified product under stated conditions. Start by matching the report holder and product description to the proposed material. Check the version and current status at the issuing body's source. A downloaded copy in an old sales folder may no longer be the appropriate reference.
ICC-ES describes the sections of its evaluation reports, including uses, installation and conditions of use. Those sections explain the boundaries of the evaluation. The existence of a report does not mean every product variant or every proposed application is covered.
Turn conditions into project questions
Read the document alongside the project brief and installation instructions. Mark where the proposal matches, where it differs and where information is missing. Do not silently resolve a difference in favor of the product because the report appears authoritative.
| Review item | Question to answer |
|---|---|
| Product identity | Is the exact proposed board or system included? |
| Intended use | Does the report address the application being proposed? |
| Installation | Are the specified supports, connections and details being used? |
| Conditions and limitations | Which restrictions affect this project? |
| Supporting documents | Are referenced instructions and drawings available? |
For example, evidence for a decking surface should not automatically be used to support a guard, a stair component or a different assembly. Identify the use actually evaluated and the use actually proposed. If they differ, obtain the appropriate evidence rather than stretching the original document's meaning.
Distinguish a report from other useful documents
A warranty, marketing sheet, test report and installation manual answer different questions. A warranty describes stated commercial terms and exclusions. A test report describes a test and its specimen. An installation manual describes the manufacturer's required method. Keep each document's role visible in the comparison.
If two candidates provide different kinds of evidence, do not pretend the columns are equivalent. Write “evaluation report supplied” or “test data supplied” and identify the scope. Missing evidence should remain missing until the relevant document is obtained.
Retain the reviewed version and the unresolved questions with the comparison record. If the selected product changes, repeat the affected review. The test-limits guide helps interpret evidence without turning a narrow result into a broad claim about durability, comfort or suitability.
A change in decking priorities
A deck-board report is supplied for a stair application. The reviewer checks the stair-tread scope before accepting it as evidence for that location.
Hypothetical planning example.
Technical context
ASTM D7032’s public scope includes multiple performance considerations for WPC/plastic products. Citing the number alone does not prove a product complies.
ASTM D7032-21: Public scope