BuildBudgeter

Waterproofing and wet zones

Critical-stage waterproofing for bathrooms, terraces and penetrations. Work focuses on continuous membranes, junction details, falls to drains and reliable pipe seals to prevent leaks and structural damage in operation.

Priority Critical control stage
Inspection window Before waterproofing, facade, or finish layers lock defects in
Evidence level Photos, tests, approvals, and measured acceptance records
Late-fix multiplier 4-8x
Delay exposure 14-45 days

Stage control summary

Overview

Waterproofing defects are among the most expensive because they are often discovered after finishes, joinery, ceilings, and occupancy expectations are already in place. The correct control mindset is not 'did we apply waterproofing?' but 'did we protect every joint, transition, drain, and penetration that can later move or leak?'

Stage-level control gates

Work-package checklist

Bathroom and shower waterproofing #ST5-WP-BATH-001

This package protects the most repetitive wet-area risk in the project. Repetition is dangerous here: teams stop seeing mistakes because every bathroom looks similar.

What to verify

  • Check membrane upturn height, corner treatment, and pipe penetration details in every wet room, not only in the first sample.
  • Verify waterproofing continuity at thresholds, niches, and wall-to-floor junctions.
  • Confirm substrate slope is formed toward drains before tile layers hide the build-up.

What usually goes wrong

  • Bathrooms are assumed identical, but drain height and threshold detail vary from room to room.
  • Pipe penetrations are sealed with generic products instead of a repeatable detail.
  • Tile workmanship hides slope defects until water starts to sit in corners.
Terrace and balcony waterproofing #ST5-WP-TERRACE-002

Terraces fail where rain, movement, facade edges, and drainage all meet. They must be controlled as exposed envelope zones, not as simple horizontal surfaces.

What to verify

  • Confirm falls are directed to drains or edges without trapping water at doors, parapets, or facade transitions.
  • Check waterproofing turn-ups and threshold transitions before finish layers cover them.
  • Verify terrace edge, drip, and facade interface details as a single water-shedding assembly.

What usually goes wrong

  • Thresholds are prioritized visually and become the weakest waterproofing point.
  • Facade finishes bridge over movement-sensitive terrace details.
  • Drain placement is correct on plan but wrong in actual finished geometry.
Waterproofing joints and movement bands #ST5-WP-JOINTS-005

Joints are where a waterproofing system proves whether it is buildable under movement, shrinkage, and temperature change.

What to verify

  • Inspect all internal corners, change-of-plane conditions, and movement-sensitive joints before the finish layer starts.
  • Verify bandage, tape, or joint reinforcement is installed continuously and not cut back at awkward geometry.
  • Check joint detailing where waterproofing meets drains, penetrations, and threshold assemblies.

What usually goes wrong

  • Joint reinforcement is omitted where crews think the area is too small to matter.
  • Bands are interrupted by penetrations and never reconnected correctly.
  • Joint logic changes between bathrooms, terraces, and service areas without design intent.

Evidence to collect before sign-off

Related glossary

Waterproofing /waterproofing

Barrier systems preventing water penetration.

Wet-area drain slope /wet-area-drain

Floor fall geometry directing water to drains.

Floor trap /trap

Drain element with seal preventing sewer odors.

Movement joint /movement-joint

Joint detail allowing controlled movement between building elements or finishes.

Roof slope /roof-slope

Planned roof gradient for reliable water runoff.

Climate exposure /climate-exposure

Environmental stress conditions such as rain and salt.

Pool type /pool-type

Selected technical pool concept (skimmer or overflow).

Use this with the rest of the product

Switch between stage guidance, checklist control, and cost-of-error analysis. The same work packages should tell one consistent story across all three views.