Expansion joint equivalence should be assessed against a project’s requirements, not inferred from a cross-reference name. A finder can identify a possible alternative for review, but the proposed assembly still needs supporting documents. This checklist helps architects, engineers and procurement teams organise that review without treating different products as automatically interchangeable.
Write the requirement before comparing products
Record the application, nominal opening, movement directions and required movement range. Add the installation geometry, adjoining finishes and service conditions. The selected criteria should come from the project’s approved design and specification. If a requirement is unclear, flag it for the responsible designer. Comparing two brochures before defining the requirement can lead to a persuasive-looking table that answers the wrong question.
Compare the complete assembly
Check the actual profiles, seals, fixings, accessories and transitions proposed. A similar cover width or material name does not show that two assemblies function alike. Ask how the system interfaces with waterproofing and other required components. If the proposal depends on a separate barrier or accessory, include that component in both the technical and commercial comparison rather than leaving it outside the schedule.
Trace performance claims to evidence
Request the current technical data sheet and applicable test or assessment documents for the exact assembly. Check the issuer, date, tested configuration and stated limits. Distinguish a cited standard from demonstrated compliance, and distinguish a planned certification from an issued certificate. For fire or other safety-critical requirements, have the appropriate project professional review the evidence and the installation conditions before approval.
Record differences and the approval decision
Use a comparison sheet with columns for the project requirement, original proposal, alternative proposal, document reference and unresolved question. Keep price and delivery information separate from technical acceptance. If a condition is not supported, record it as unresolved rather than filling the cell with an assumption. The reviewer should be able to see precisely which differences were accepted and who approved them.
Next step
Use the Dseal cross-reference finder to begin a document review, then work through the project’s requirements with the responsible team. The knowledge bank and standards guide can help explain the terms appearing in submissions. Third-party brand names identify products for comparison and do not imply endorsement or affiliation. An alternative should be accepted only through the project’s documented approval process, with the relevant conditions and supporting evidence retained.
Leave a Reply