Category: Uncategorized

Readers need to know whose perspective a product comparison represents. Dseal.org is an owned-brand portal, so comparison content should make that relationship clear and support individual claims with relevant evidence. A disclosure helps readers interpret the context, but it does not make an unsupported performance claim reliable. Use the checklist below when preparing or reviewing a comparison.

State the relationship in plain language

Identify the authoring or publishing brand and any relevant commercial relationship. Place that information where a reader can find it alongside the comparison. Avoid describing an owned-brand article as an independent test or neutral certification. If a document comes from another organisation, identify its source without implying that the organisation endorses the article or its preferred product.

Compare identifiable products and circumstances

Give the exact product references and the purpose of the comparison. Distinguish information about a proposed assembly from information about a brand in general. For example, a document for one system configuration does not establish the performance of every product sold under the same name. Mark unavailable information as unavailable rather than assigning a low score to a competitor whose evidence has not been obtained.

Keep claims connected to their sources

Retain the document title, revision and relevant scope behind a factual statement. Separate a supplied specification, a test result and a project suitability decision. Do not extend a source beyond what it covers or suggest that an older document proves a current product claim. If the evidence cannot support a comparison, narrow the statement or leave the point open for clarification.

Make the reader decision practical

Explain which project inputs still need review and where further product-specific information should be requested. Avoid a universal winner based on selective criteria. Keep the comparison date and revision trail so later changes can be checked. Clear affiliation, consistent criteria and visible limitations help a reader prepare a better enquiry while preserving the difference between a brand explanation and an independent assessment.

Related information

• Review a tested assembly
• Request supporting documents

Before using a test report in a technical submission, identify who issued it and which document is being supplied. A familiar logo or an extracted result is not a complete report review. This checklist helps organise questions about the source and status of the document without declaring a product compliant, equivalent or suitable for a particular project.

Identify the issuing organisation and report

Record the issuer name, report identifier, date and revision shown on the document. Check whether the pages appear to form the stated complete report and note missing attachments. If the document is an extract, identify who supplied it and request the relevant complete source before treating the extract as the entire evidence set.

Clarify the roles named in the report

Distinguish the issuer, the party requesting the test and the product or specimen identified in the document. Ask about any unclear relationship rather than inferring it from branding. An organisation named in correspondence may not be the report issuer. Retain the information needed to connect the document to the proposed product and arrangement.

Check questions through an appropriate contact

Where authenticity, revision status or scope needs clarification, use a contact route established independently for the issuing organisation. State the report identifier and the specific question. Do not circulate confidential project or report material more widely than permitted. A request for clarification is not a finding that the document is false or that the product failed a test.

Keep the response within its scope

Retain the issuer response with the document version reviewed. Separate confirmation of a report reference from conclusions about the project requirement or proposed installation. Mark unanswered questions and identify who will evaluate their significance. A clear evidence trail supports the project review without extending an answer beyond what the issuer actually confirmed.

Related information

• Review a tested assembly
• Request supporting documents

Two joint-system submissions may show similar finished appearances while describing different arrangements for later access or replacement. Compare the issued details and maintenance documents before summarising that aspect of a proposal. This is a document-review framework, not a statement that any system is maintenance-free or that one detail will suit every building. Ask the relevant source to clarify information that is missing.

Identify the component and proposed task

State what the review concerns: access for inspection, removal of a cover, replacement of a seal or another defined task. Use the component names in the submitted documents. A general statement that a system is replaceable is not enough to explain which part is meant. Keep the proposed task linked to a location and detail reference.

Read the arrangement alongside adjacent construction

Compare the submitted section with the finishes and surrounding work shown for the project. Ask whether the stated access assumes parts of that work are removable or unaffected. Do not infer a removal sequence from a finished photograph alone. If a maintenance instruction addresses a different arrangement, record the mismatch and request the applicable document rather than extending the instruction by analogy.

Ask what must be confirmed by the project team

Record questions about access permissions, work-area restrictions and the parties responsible for associated work. Request current component identification and sourcing information where relevant. Do not invent replacement lead times or availability promises. A proposal can identify a part without guaranteeing that it will be held in stock for the lifetime of the building.

Preserve the limits of the comparison

Summarise the evidence supporting each access statement and label unresolved points. Keep the source document, revision and response with the comparison. If the project detail changes, review whether the earlier access statement still applies. A useful comparison explains what the documents establish and what needs confirmation, leaving the actual replacement method and safety arrangements to the responsible project process.

Related information

• Review a tested assembly
• Request supporting documents

A product brochure, quotation and issued warranty document may describe different things. Before repeating a warranty statement in a comparison or proposal, identify its exact source and intended scope. This is a document-reading checklist for technical submissions, not an interpretation of legal rights or a promise that a particular project will receive cover. Refer unanswered questions to the issuer and the responsible project adviser.

Locate the actual source of the statement

Retain the document title, issuer, date and exact product or system reference. Note whether the source is a promotional summary, an offer of a possible warranty or a document issued for a named project. If only an email mentions a duration, request the relevant written terms before using that duration as a comparison value. Keep the original wording accessible to the reviewer.

Identify what the document says it covers

Read the stated subject and record whether it refers to supplied material, an installed arrangement or another defined scope. Identify the named parties and location where stated. Do not extend the wording to accessories, application work or adjacent construction that the source does not identify. If the document is unclear, turn the uncertainty into a specific question rather than a confident summary.

Retain conditions alongside the headline

When summarising a statement, retain its relevant conditions, exclusions and document references. Ask the issuer which records or project steps it requires, where that information is missing. Do not silently discard qualifications because a comparison table has a small cell. A separate note linked to the full source can preserve detail without pretending that the headline duration describes every condition.

Keep a reviewable quotation trail

Date the review and identify which source version supported the statement. Mark unresolved questions and obtain clarification through the agreed project route. When a revised document arrives, update the comparison and retain the earlier version as superseded. Avoid describing a warranty as a test result, certification or evidence of equivalence: those are separate claims that need their own appropriate supporting documents.

Related information

• Review a tested assembly
• Request supporting documents

An acoustic statement is more useful when the reader can trace it to a defined report, tested arrangement and measurement. A product description or a single headline value leaves those questions open. When reviewing a proposed expansion joint or surrounding construction, ask for the source behind the claim and record what that source actually covers. This guide is a document-review framework. It does not assign an acoustic rating to a Dseal product, establish equivalence between systems or replace the project acoustic reviewer’s assessment.

Identify the claim and the complete source

Write down the exact statement being evaluated and the project question it is intended to answer. Request the complete report, with its issuer, identifier, date and referenced test method. Keep a brochure statement separate from the report it cites. If only an extract is available, identify which pages and contextual information are missing. Do not fill a gap with an assumed rating or describe an absent report as either proof of performance or evidence of a failed test.

Check what was measured and how it was arranged

Read the report’s description of the specimen, mounting and test conditions. ISO’s public description of ISO 10140-1 explains that the laboratory framework includes preparation, mounting and operating conditions; its description of ISO 10140-2 concerns airborne sound-insulation measurement. Those source summaries illustrate why a method number and specimen arrangement matter. They do not establish that a particular joint system was tested under that method or that the method answers every acoustic question in a project.

Compare the reported arrangement with the proposal

List the proposed system and surrounding detail beside the arrangement identified in the report. Record differences and missing information for the acoustic reviewer to consider. Retain the reported quantity, unit and any stated limitations when transcribing a result. Do not rank offers by a number alone when their methods, quantities or configurations have not been reconciled. Where applicability is uncertain, ask a defined question instead of labelling the proposal equivalent because one material or brand name matches.

Retain the project conclusion and its limits

Ask the responsible reviewer to record the document version considered, the scope of any acceptance and the outstanding conditions. Separate receipt of a report from acceptance for the proposed use. If the configuration or requirement changes, flag the acoustic review entry for reconsideration. Keep the original report available alongside the summary so later readers can check the context. Any project decision should remain limited to its actual basis rather than becoming a general product endorsement.

Working record

The following example fields are a planning format, not a completed project record.

Related information

• ISO 10140-1: public scope and application rules
• ISO 10140-2: public scope of airborne measurement
• Review a tested assembly
• Request supporting documents

A product assessment is useful only within the scope and conditions it actually states. Record those limits beside the conclusion when reviewing a proposed joint system. This helps a project team distinguish the document’s own statements from assumptions added during a comparison, without broadening the assessment into an unrestricted approval.

Identify the document and its role

Retain the issuer, title, identifier, revision and issue date where supplied. State whether the copy is complete or an extract and identify the question it is being used to address. Avoid relabelling a brochure, test report or supplier letter as a product assessment merely because it contains a favourable statement. Use the document type actually established by its source.

Locate the limits in the source

Record the sections that describe the assessed product, application and stated conditions. Connect a summary entry to its exact source reference so another reviewer can locate it. If a condition is unclear or the relevant section is missing, record a question. Do not replace an unavailable statement with an assumption that the document has no restrictions.

Compare the named arrangement

Identify the proposed assembly and drawing revision alongside the configuration described in the assessment. Record differences in the information actually supplied rather than inventing a universal tolerance for equivalence. A limit concerning one component or arrangement should not be ignored because the proposal carries the same brand. Refer uncertainty about the effect of a difference to the responsible reviewer.

Keep applicability separate from receipt

Show whether the document has been received, checked against the proposed reference or accepted for a defined project requirement. For example, complete copy received can be a closed document request while configuration clarification remains open. Do not combine those states into one compliant cell that conceals the unresolved applicability question.

Retain the conclusion with its conditions

Ask the responsible project team to record the decision, document version considered and any remaining conditions. Preserve limitations when quoting or summarising the assessment in later correspondence. Review the relevant entry if the proposed product or detail changes. A recorded project decision should not be presented as a broader certificate, warranty or endorsement than the source and review establish.

Working checklist

Example fields illustrate a record format; they are not a documented project, an approval or an installation instruction.

Related information

• Read document dates and revisions
• Review the tested assembly
• Record review exceptions
• Ask for supporting documents

When a joint proposal includes a water-management statement, ask what the statement covers and which evidence supports it. Keep the proposed assembly, the surrounding interfaces and the conditions described in the evidence connected. A general product phrase should not silently become a promise about every part of an installed building detail.

Clarify the actual statement

Record the wording used in the proposal and the requirement it is intended to address. Ask whether the statement concerns a component, an assembly or a particular project detail. Keep supplier terminology with its explanation rather than treating different phrases as interchangeable. Identify who must interpret the response against the project requirement.

Identify the configuration behind the evidence

Ask for the exact system and the drawing or specimen arrangement named in the supplied document. Note the components and interfaces it describes. Compare that scope with the proposed assembly before using the document in a review. A report for another configuration is a relevance question to resolve, not automatic proof of either acceptance or failure.

Read conditions and limits explicitly

Request the relevant document and retain the conditions, procedure and result it actually states. Ask which aspects of the project requirement remain outside that scope. Do not add a pressure, duration, service-life claim or universal field-performance conclusion that the source does not establish. Keep extracts identified as extracts if the complete context is unavailable.

Ask about adjoining water-management details

Show the project interfaces relevant to the enquiry, including ends, transitions and surrounding construction where applicable. Ask which details form part of the proposed response and which require coordination elsewhere. Record unresolved interfaces separately. Evidence about one assembly should not be used to erase an unanswered question about a different part of the project arrangement.

Retain an appropriately scoped conclusion

Ask the responsible reviewer to record the evidence considered, the proposed configuration and any conditions on the decision. Keep manufacturer guidance, supplied reports and project acceptance as distinguishable records. Reopen the relevant question if the detail changes. Avoid turning an incomplete comparison into a blanket watertightness or maintenance-free claim about the completed installation.

Working checklist

Example fields illustrate a record format; they are not a documented project, an approval or an installation instruction.

Related information

• Review the tested assembly
• Compare installation geometry
• Record review exceptions
• Request supporting documents

Two joint proposals can quote the same nominal opening while showing different installation arrangements. Compare their drawings against a common set of project references before treating the proposals as interchangeable. A geometry comparison records fit and interface questions; it does not certify equivalent movement, loading, fire or waterproofing performance.

Use the same project reference

Identify the project section, revision and location used for both proposals. State the units and relevant level or datum references. If one supplier used an earlier section or a different application, record that difference before comparing dimensions. Do not describe a mismatch caused by different inputs as a confirmed product defect.

Separate the dimensions being compared

Label the opening, overall assembly extent, available recess and adjacent finished levels separately using the supplied drawing terminology. Record the value and source for each proposal. A dimension called width on one drawing may describe a different feature on another. Ask for clarification rather than aligning unlike measurements in a single comparison cell.

Check the arrangement at interfaces

Compare the details supplied for edges, supporting construction, changes in plane and adjacent finishes relevant to the actual location. Mark missing sections or unresolved transitions. A straight-run illustration may not explain an end condition or a wall connection. Keep those gaps visible instead of assuming that the same nominal system designation covers every detail.

Distinguish fit from performance evidence

Record whether the submitted geometry appears to address the stated project inputs, subject to responsible review. Keep movement and other performance claims in their own evidence fields. A system fitting an available space does not establish that its tested configuration or intended service requirements match the project. Refer any proposed alteration of the supporting construction through the project review arrangements.

Request a coordinated response

Send a marked comparison identifying the exact drawing differences and the question each creates. Ask the supplier and responsible project reviewer to resolve their respective items. Retain revised drawings with their dates and any conditions. Do not close the geometry review on a price comparison or accept an unrecorded site adjustment as the resolution of a drawing conflict.

Working checklist

Example fields illustrate a record format; they are not a documented project, an approval or an installation instruction.

Related information

• Build a comparison matrix
• Read document revisions
• Record review exceptions
• Request a drawing clarification

An alternative joint comparison is easier to act on when every unresolved difference has a named requirement and a clear next step. Keep an exception register beside the comparison matrix. Its purpose is to record what still needs review, not to turn missing information into a failed test or a technical acceptance.

Give each exception a specific reference

Identify the requirement, proposed assembly and document revision involved. Quote only the short reference needed to locate the issue in the project record. A note such as movement not confirmed is less actionable than a note identifying which direction, limit or report reference remains unavailable. Do not widen one exception into an unsupported conclusion about an entire product range.

Describe the type of gap

Distinguish missing documentation, an unclear statement, a proposed departure and a measured difference supported by the supplied evidence. Record the source for the observation. For example, no report received and report configuration differs from the proposed drawing are different states requiring different responses. Neither should silently become a claim that the proposed assembly failed testing.

State the clarification requested

Ask a question that the supplier or responsible reviewer can answer against the cited documents. Specify the exact system and revision when requesting additional evidence. If a departure is proposed, ask for its stated basis and refer it through the project review process. The person maintaining the register should not invent a tolerance or accept a departure simply to close the row.

Assign the response and decision separately

Record who is being asked to provide information and who is responsible for the technical decision under the project arrangements. Those roles may differ. Retain the received response, its date and any qualifications. A supplier reply can resolve a document request while leaving the project acceptance decision outstanding; show both states rather than marking the whole exception closed.

Close only the issue actually resolved

Link a closure entry to the decision or document that supports it and retain any remaining conditions. If the proposed assembly changes, check whether earlier closures still apply. Preserve superseded entries as review history instead of overwriting their basis. A closed register is evidence of a recorded process, not an independent certificate of equivalence or guaranteed performance.

Working checklist

Example fields illustrate a record format; they are not a documented project, an approval or an installation instruction.

Related information

• Build a comparison matrix
• Read document revisions
• Missing report versus failed test
• Request documents

A technical review can contain a current brochure, an older test report and a drawing revised last week. Their dates describe different events. Record what each date means before deciding whether the documents support the proposed assembly. A date alone neither establishes suitability nor proves that an older report is invalid.

Identify the document before interpreting its date

Record the issuer, title, document identifier and revision where supplied. Distinguish a test report from a product datasheet, drawing or certificate. Note whether the copy is complete or an extract. A download date records when you obtained a file; it should not be substituted for its issue date or the date of the activity described inside it.

Read the date labels as written

Separate a test date, report issue date, drawing revision date and any stated expiry or review date. Copy the labels into the document register rather than inventing one general valid-until field. If the document does not state an expiry, do not assign one from its age alone. Ask the issuer or responsible reviewer what currency requirements apply to the actual document and project.

Connect revisions to the named configuration

Compare the assembly designation and configuration in the evidence with the current proposed drawing and product documents. Ask what changed between revisions and whether the supporting evidence addresses the proposed arrangement. A more recent brochure cannot on its own extend a report to a different assembly. Equally, an older report should not be dismissed solely because the marketing literature was updated later.

Preserve superseded copies with their status

Keep earlier documents that explain a previous decision, but mark them clearly in the review record. Identify the current proposed revision and who supplied it. Avoid overwriting a file in a way that removes the version used for an approval or quotation. A register can show both the historical basis and the current unresolved review without presenting both as interchangeable current instructions.

Ask a precise currency question

When the relationship between documents is unclear, request confirmation for the exact system, drawing revision and project requirement. Cite the document identifiers and the difference that needs explanation. Record the response and any limitations rather than changing a comparison cell to compliant because a newer date appears. Keep receipt, relevance and technical acceptance as separate review states.

Working checklist

Example fields illustrate a record format; they are not a documented project, an approval or an installation instruction.

Related information

• Review the tested assembly
• Use a comparison matrix
• Ask for supporting documents