The waterproofing pre-installation meeting: who comes and what gets decided
The installer arrives to start a foundation area, but the substrate lead has not agreed who repairs the remaining defects. The mechanical trade expects to add a penetration later. Both issues could have been raised before mobilization, but the meeting discussed only the planned start date.
Use the waterproofing pre-installation meeting to agree the work boundaries, readiness checks, interface decisions and protection handovers before installation starts. Bring the people who can supply the substrate, resolve details, arrange required reviews and control following work. Ask for concrete outputs with owners and dates. A useful meeting exposes an unready condition; it should not be recorded as technical approval merely because everyone attended.
Leave the meeting with usable handovers
- Bring one current package. Circulate the specified assembly, approved submittals, current details and known open questions. Ask participants to identify missing information before the meeting so the crew does not discover conflicting revisions at the wall.
- Agree substrate responsibility. Name who prepares the surface, who addresses defects and who checks it against the applicable system requirements. Record the evidence and release route without inventing a generic cure or moisture limit.
- Review difficult interfaces. Walk the joints, transitions, penetrations and terminations on the project’s current drawings. Invite the affected trades to confirm scope boundaries and raise unresolved technical details to the responsible designer and manufacturer contact.
- Confirm inspection and testing arrangements. Identify the required parties, supporting records, booking actions and stage at which work stays exposed. Give each preparation item a name and date rather than assuming the reviewer appears on request.
- Agree the protection handover. Identify following trades, access routes, storage and covering work under the approved arrangements. Name who confirms protection readiness and who reports damage before an area is concealed.
- Read back decisions and open items. Issue an action record with owners, due dates and release status. Separate agreed coordination from technical questions awaiting an authorized answer, and transfer those actions into the look-ahead.
Common mistakes
- Inviting only the installer when another trade controls an interface.
- Listing unresolved technical questions as agreed decisions.
- Leaving following-trade protection outside the agenda.
Action list
The meeting’s working outputs
- Current package and open-detail list.
- Substrate preparation and acceptance owners.
- Interface responsibilities and decision dates.
- Inspection and testing preparation actions.
- Protection handover and damage-reporting route.
Check your understanding
Everyone attended the meeting, but nobody accepted responsibility for a substrate defect. Is the start condition resolved?
.jpg){kind=link}