A standard citation names a reference; evidence of compliance shows what was assessed, how it was assessed and what the result covers. When reviewing an expansion joint submission, keep those two ideas separate. A brochure can help identify a proposed system, but a standard number printed beside it is not enough to establish that your project’s requirement has been met.
Start with the exact requirement
Record the standard designation, edition and the particular requirement stated in the project specification. Ask the responsible reviewer to clarify incomplete references. A hypothetical note such as ‘movement test required; report pending’ makes the gap visible without asserting a result. Different references can concern different properties, so avoid treating every standard citation as interchangeable evidence of movement, fire, water or loading performance.
Identify the type of evidence supplied
List each document as a technical data sheet, test report, declaration, certificate or design calculation, using the issuer’s own description. These documents have different purposes. ISO explains that it develops standards and does not provide certification or conformity assessment. When a submission refers to ISO certification, identify the actual issuing body and the certificate’s scope. Do not imply that ISO issued a product approval merely because an ISO standard is named.
Match the assessed item to the proposed system
Compare the exact product identity and configuration in the evidence with the proposal. Record any differences and ask for an explanation from the supplier and appropriate review by the project professional. For example, a report for one assembly should not silently be applied to another assembly. A document review can reveal a mismatch, but it does not itself establish the technical significance of that mismatch or approve the proposed alternative.
Record scope, conditions and unresolved points
Create a brief evidence register: claimed property, document reference, assessed item, stated conditions, reviewer and outcome. Mark ‘not supplied’ or ‘clarification required’ where needed. Keep report dates and revisions alongside the proposal revision. If an assessment covers only one property, do not broaden its conclusion into a claim about every project requirement. Refer acceptance questions to the responsible reviewer rather than filling a missing result with marketing language.
Use reference portals as starting points
The Dseal knowledge bank and standards page can help organise terminology and identify questions. They are owned-brand resources, not independent certification bodies. The earlier equivalence checklist helps compare an alternative against the actual project requirement and available documents. Request the complete supporting evidence for the exact proposed system and keep the review decision traceable. The useful output is a clear list of supported points and open questions, not an unsupported blanket statement of compliance.
Leave a Reply