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.
| Evidence question | Reference to retain | Limit to preserve |
|---|---|---|
| What is claimed? | Actual wording and requirement | Component, assembly or project detail |
| What was reviewed? | Document and configuration | Conditions and missing context |
| What remains open? | Interface and decision reference | Unresolved project coordination |
Leave a Reply