A technical report is most useful when the assembly it describes can be compared with the assembly proposed for the project. Start with identity and scope before quoting a result. This checklist helps organize the review; it does not verify a particular Dseal product or replace the project reviewer's decision.
Establish the document identity
Record the issuing organisation, report number, date, revision and the named applicant or product. Obtain the complete document with referenced drawings and appendices where they are part of the report. If only a cover page or extract is available, state that limitation. Ask the issuer or supplier to resolve uncertain authenticity or missing information before relying on the result.
Find the assembly description
Identify the exact model, components and configuration described in the report. Compare the dimensions, orientation, supporting construction and installation details with the proposed assembly using the report's own terminology. Record differences rather than treating a shared product-family name as a match. An isolated material certificate cannot by itself describe every component in an installed system.
Read the test scope before the result
Note the test method and edition actually cited and the conditions covered by the report. A movement result should not be relabelled as proof of unrelated performance. For example, ASTM's public E1399/E1399M scope describes cyclic movement assessment and expressly limits what that method establishes. Follow the source link for its scope; the complete standard was not used to approve any product here.
Keep project differences explicit
Prepare a comparison with separate fields for the tested arrangement and the proposed arrangement. Ask the responsible reviewer what further evidence is required when substrates, transitions, sizes or other conditions differ. Mark an unanswered field unknown. Do not invent an allowable variation or transfer a result between assemblies simply because a supplier describes them as similar.
Retain the decision and evidence
Link each claimed requirement to its supporting report section and record the reviewer's decision, date and qualifications. Keep outstanding evidence separate from accepted information. A report citation is an input to review, not automatic project acceptance. Preserve the complete document and the actual proposed drawing revision so later changes can be evaluated against the same evidence.
Working checklist
Example fields illustrate a review record; they are not a documented project, a technical approval or an installation instruction.
| Check | Tested assembly | Project proposal |
|---|---|---|
| Identity | Report model and drawing | Exact proposed model and revision |
| Configuration | Components, dimensions and supports | Matches, differences and unknowns |
| Scope | Method, conditions and reported result | Required claim and reviewer decision |
Leave a Reply