Lesson 8.4Lesson 8.4 · Services, MEP & Finishes
Weathertightness & Module Joints
Each module leaves the factory watertight, but the gaps between modules, and between the factory-built and the site-built, are open until they are sealed — and the joint, poorly detailed, is exactly where a modular building lets the water in
Every module leaves the factory watertight. Put two of them together and you have just created a gap that is not — and water finds gaps.
A volumetric module is, on its own, a well-sealed box: built in the dry, its envelope completed and often tested in the factory. The problem begins the moment you assemble modules into a building, because between every pair of modules — side to side, and stacked one on another — there is a joint: a gap where two separately-built envelopes meet, closed not in the controlled factory but out on site, in the weather, after the lift. And water, relentlessly, finds the gap.
This is why the joint is the single most important detail in the weathertightness of a modular building, and why modular buildings, when they leak, most often leak at the joints. It is also a place where the honest discipline of this course matters most: weathertightness is binding building-envelope engineering, and the detailed waterproofing design, the tested details and the warranties belong to the manufacturer and the facade and waterproofing specialists, not to a course. What this lesson teaches is the *logic* every designer should understand — where the vulnerable interfaces are, why a good joint works in layers rather than on a single line of sealant, how the building is kept dry during the exposed window of assembly, and why getting the joint right is the difference between a dry building and a callback. The binding detail, always, is the specialist's.
Box = watertight. Joints = the leak. Drain, seal, back up — never one bead. Keep it dry during assembly. Warranted detail from the specialist, always.
Why the joint is the weak point
To see the problem clearly, separate two things that are easy to conflate: the module envelope and the joints between modules. The module envelope — the walls, floor and roof of a single box — is built in the factory under good conditions and can be made and checked watertight there; it is rarely where trouble starts. Trouble starts at the interfaces, the gaps that only exist once modules are assembled, because those are closed on site, in the weather, and they are where two independently-built, slightly-imperfectly-positioned envelopes have to become one continuous barrier.
There are several such interfaces, and a designer should be able to name them. The inter-module joints run between adjacent modules (vertical joints where boxes sit side by side) and between stacked modules (horizontal joints where one box sits on another); on a typical stacked building these joints form a grid of lines across every face and through the building. The module-to-podium or module-to-foundation joint is where the modular superstructure meets the in-situ base. The module-to-core joint is where modules meet a site-built stair or lift core. And the module-to-facade interface is where the modular structure meets the external cladding or curtain wall. Every one of these is a place where the continuous waterproof barrier has to be *made*, on site, across a gap — and every one is a candidate for a leak if it is detailed or built poorly.
What makes these joints genuinely hard is the combination of three things. First, tolerance: modules are large and are not placed to the millimetre, so the joint has to close a gap that is never exactly the drawing dimension and varies along its length. Second, movement: the building moves — thermally, structurally, under wind and load — and the joint has to stay sealed while the gap opens and closes slightly over time, which is why a rigid, brittle seal fails. Third, exposure and access: the joint is sealed on site, often at height, sometimes in poor weather, and once the building is finished the joint is usually concealed and hard to reach, so a defect is both likely to occur and hard to find and fix. Understanding that the joint — not the module — is the weak point is the first principle of modular weathertightness, and it reframes the designer's attention from the box to the lines between the boxes.
The box is watertight. The gaps between boxes aren't — yet. Inter-module joints, module-to-podium, module-to-core, module-to-facade. Water finds every one.
The logic of a good joint: drain, seal, back up
The single most important principle of a weathertight joint is this: never rely on one line of sealant. A joint that depends on a single bead of mastic to keep water out will, sooner or later, let water in — the sealant ages, the gap moves, the bead was imperfect along part of its length — and when it fails there is nothing behind it. Good joints work in layers, a defence in depth, so that water is resisted several times over and any that gets past the first line is caught, drained and sent back out before it reaches the inside.
The layered logic, from outside in, runs roughly as follows. An outer line sheds the bulk of the water — an overlap, a lap, a flashing, a cover, profiled so that gravity and geometry throw most of the water off before it ever reaches a seal. Behind it, many good joints use a drained and (often) ventilated cavity: a deliberate void that accepts that some water will get past the outer line, then *drains it away* and lets it evaporate, rather than pretending no water ever enters. This 'drained and back-ventilated' or pressure-equalised principle is the heart of modern weathertight jointing — it manages water rather than trying to achieve a perfect, permanent, single barrier. Then come the seals: typically a primary seal as the main barrier and a secondary or backup seal behind it as a last line of defence, so that failure of the first does not mean failure of the joint. Compression seals and gaskets are preferred where movement and tolerance must be accommodated, because they stay sealed as the gap changes.
The designer's takeaway is the principle, not the product: a good joint drains, seals and backs up, and it is designed to tolerate the real gap and the real movement rather than assuming perfection. The best joints are also designed for the sequence in which they are built — they can be formed and, crucially, *inspected* as the modules go up, because a seal you cannot inspect is a seal you cannot trust. But the specific detail — which seals, which cavity, which flashing, what dimensions, what materials, how it performs against wind-driven rain and over what life — is binding building-envelope engineering that belongs to the manufacturer's tested system and the facade and waterproofing specialists. The designer's job is to understand the layered logic, to give the joint the room, access and tolerance it needs, and to insist that the detail is a proven, warranted one — not to invent the waterproofing.
Never one bead of sealant. Layers: outer overlap sheds > drained cavity drains > primary seal > secondary backup. Drain and manage water, don't pretend it never enters.
Temporary weather protection during assembly
There is a dangerous window in every modular build that has nothing to do with the permanent joint detail: the period during assembly, when modules have been lifted into place but their joints are not yet sealed, and the building — including all those finished interiors from the last lesson — is open to the weather. A module that was watertight in the factory can take in water through an unsealed joint during assembly, and because the interiors are already finished, that water does real, expensive damage to floors, linings, joinery and services that were installed months ago. Managing this exposed window is as important as the permanent detail.
Several strategies reduce the risk, and they are planned before assembly starts. Sequencing is the first: the assembly and sealing are planned so that the exposed window is short — the sealing crew follows close behind the crane, closing joints as soon as modules are set, rather than stacking the whole building and sealing later. Temporary protection is the second: modules may be wrapped, tented or covered; open faces and the tops of partially-built stacks are closed with temporary covers or end panels; and temporary drainage may be provided to carry water away from vulnerable zones. Factory closure helps too — designing modules so they arrive with as much of their envelope closed and protected as possible, with openings temporarily sealed, reduces what the site has to protect. And the programme and weather are watched: lifts and the exposed window may be planned around the forecast and the season, which in the Indian context means taking the monsoon seriously as a hard constraint on when modules can be safely exposed.
The honest point is that temporary weather protection is a real cost and a real risk that the enthusiasm for factory finishing can obscure. The very thing that makes volumetric modular attractive — arriving with finished interiors — is also what makes the assembly window dangerous, because there is so much finished work to ruin if water gets in before the joints are sealed. A project that finishes interiors in the factory but fails to protect them during assembly can lose the quality it paid for. So protection during assembly is part of the design and the method statement, not an afterthought left to the site: it is planned, sequenced and costed. The binding design of both the temporary protection and the permanent weathertightness belongs to the manufacturer, the specialists and the contractor's method statement; the designer's role is to understand the exposed window exists and to insist it is managed.
Why the joint leaks — and what to defer
Pulling the threads together: modular buildings most often leak at the joints, and they leak there for reasons that are now clear. The joint is the place where two independently-built envelopes must become one continuous barrier, across a real and variable gap, that moves over time, closed on site in imperfect conditions, and then concealed where a defect is hard to find and fix. If the joint is detailed as a single line of sealant, if it cannot accommodate the real tolerance and movement, if it cannot drain the water that inevitably gets past the first line, if it was built in the wet or could not be inspected, or if the building was left exposed during assembly — any of these, and the building leaks. Almost every widely-reported failure of a modular building traces back to a joint or interface, not to a module.
That is precisely why weathertightness is one of the clearest 'defer to the specialist' subjects in the whole course. The designer should understand and insist on the principles — the joint is the weak point; it works in layers that drain, seal and back up; it must tolerate the real gap and movement; it must be buildable and inspectable; and the building must be protected during the exposed assembly window. But the binding design — the specific tested joint detail, its performance against wind-driven rain, its materials and dimensions, its expected life, and crucially the warranties and approvals that stand behind it — belongs to the manufacturer's proprietary tested system and to the facade and waterproofing specialists, governed by the relevant codes and standards. A designer who invents a bespoke, unwarranted waterproofing detail for a modular joint is taking on a risk they are not qualified to carry; the right move is to require a proven, warranted, tested detail and to design the building so that detail can be installed, inspected and maintained.
The constructive role the designer does own is real and important: reduce the number and length of exposed joints where the design allows; locate joints where they can be made and inspected well, and where they are protected (the classic move of expressing or protecting joints rather than hiding them in the worst-exposed positions); coordinate the interfaces between modular and site-built work so the barrier stays continuous; and plan, with the contractor and manufacturer, for the building to be kept dry during assembly. Weathertightness is won or lost at the joint — understand the logic, design for it, and leave the binding waterproofing and its warranty to the specialist who can stand behind it. That is the honest and competent position, and it closes the module's account of how a building made in a factory is kept dry once it is assembled in the rain.
Building-envelope & waterproofing design
The tested joint detail, wind-driven-rain performance, materials, life
Binding waterproofing and weathertightness design belongs to the manufacturer's proprietary tested system and the facade/waterproofing specialists, with warranties and approvals; the designer understands the logic and insists on a proven detail.
Temporary works & method statement
Keeping the building dry through the exposed assembly window
Temporary weather protection, sequencing and drainage during assembly are the contractor's and manufacturer's temporary-works design and method statement. Module 7; the designer insists the window is managed.
NBC India & local codes / standards
Regulatory and performance standards for weather resistance
The National Building Code of India and relevant standards govern weather resistance; off-site joints must meet them via the manufacturer's approvals and the specialists, taking the monsoon as a hard constraint.
Workshop — map the leak risk and reason a layered joint
Weathertightness starts with seeing where the gaps are. In this workshop you will map the vulnerable interfaces of a small stacked modular building, reason out a layered joint in principle, and plan how the building would be kept dry during assembly — all as design reasoning, with the binding detail deferred to the specialist.
Paper, a simple stacked modular building, and this lesson. No waterproofing design — the binding detail and warranty are the specialist's; this is about understanding the logic and the risk.
Goal: an interface leak-risk map and a layered-joint rationale Inputs: a simple stacked modular building (3-4 floors of repeated modules) + this lesson + paper Time: ~45 minutes
- 1Map the joints: draw the building and mark every weathertightness interface — inter-module vertical and horizontal joints, module-to-podium, module-to-core, module-to-facade. Highlight the most exposed (roof line, corners, wind-driven faces).
- 2Rank the risk: for each interface note why it is hard — tolerance (variable gap), movement (opens and closes over time), exposure and access (sealed on site, later concealed). Pick the two highest-risk joints.
- 3Reason the layers: for one high-risk joint, sketch the layered logic in principle — outer overlap that sheds water, a drained/ventilated cavity that manages what gets past, a primary seal, a secondary backup seal. Show that it tolerates the gap and can be inspected as built.
- 4Plan the exposed window: write how you would keep the building dry during assembly — sequencing the sealing crew behind the crane, temporary covers and end panels, watching the monsoon/forecast — noting what finished interiors are at risk.
- 5State the deferral: write one line naming what you would require from the manufacturer and waterproofing specialist — a proven, warranted, tested joint detail and approvals — and what you as designer own (fewer, accessible, inspectable, protected joints; continuous interface coordination).
You’ll walk away with
A one-page weathertightness read: an interface leak-risk map, a ranked risk note, a layered-joint rationale for one high-risk joint, an exposed-window protection plan, and an explicit deferral to the manufacturer/specialist — all as design reasoning, not a waterproofing specification.
Three altitudes on the same idea
Read the band that fits you — or all three.
Weathertightness is won or lost at the joints, and though the binding detail is the specialist's, the decisions that make a dry building are yours. Reduce the number and length of exposed inter-module joints where the design allows; locate joints where they can be made, inspected and maintained well, and in positions that are protected rather than worst-exposed; and coordinate the interfaces between modular and site-built work — podium, core, facade — so the waterproof barrier stays continuous. Understand the layered logic (drain, seal, back up; tolerate the gap and the movement; never a single bead) well enough to insist on a proven, warranted, tested detail rather than a bespoke invention. Plan, with the contractor and manufacturer, to keep the building dry through the exposed assembly window. Own the joint strategy, the interface coordination and the insistence on warranted details; defer the binding waterproofing design, performance and warranties to the manufacturer and the facade/waterproofing specialists and the governing codes.
The finished interiors you specified are exactly what a joint leak destroys — so weathertightness is your concern even though the detail is not your design. The floors, linings and joinery installed in the factory can be ruined by water entering an unsealed joint during assembly, or by a poorly-detailed joint over the building's life, so understand where the vulnerable interfaces are and insist that the exposed assembly window is properly managed and that warranted joint details are used. Where your interior crosses a marriage line or meets the facade or a wet zone, coordinate with the manufacturer and specialists so the waterproof barrier and your finishes are resolved together and the junction is both dry and clean. Design access so joints in or near your fit-out can be inspected and maintained without destroying finishes. Defer the binding waterproofing to the specialist; protect the quality of the interior by insisting the building is kept dry.
Learn the single most useful fact about modular weathertightness: the module is watertight, but the joints between modules are where buildings leak. Understand where the vulnerable interfaces are — inter-module joints, module-to-podium, module-to-core, module-to-facade — and why they are hard: they close a real, variable gap that moves over time, they are sealed on site in imperfect conditions, and they are then concealed. Learn the layered logic of a good joint — it drains, seals and backs up, and never relies on one bead of sealant — and the danger of the exposed window during assembly, when unsealed joints can let water ruin finished interiors. You are not designing waterproofing details — that is binding engineering for the manufacturer's tested system and the specialists, with warranties — but you are expected to understand the principles, why the joint is the weak point, and why this is a subject to defer to those who can stand behind the detail.
“Modules are built and sealed in the factory, so a modular building is actually more watertight than a site-built one — the weather is not really a concern once the boxes are up.”
Do it yourself
No tools needed — reason it through.
- 1Distinguish the module envelope from the joints between modules, and explain why the joint, not the module, is the weak point for weathertightness.
- 2Name the vulnerable interfaces in a stacked modular building, and the three things (tolerance, movement, exposure/access) that make joints hard.
- 3Explain the layered logic of a good joint — drain, seal, back up — and why relying on a single line of sealant fails.
- 4What is the exposed window during assembly, why is it dangerous in a building with finished interiors, and how is it managed (especially given the monsoon)?
- 5Which parts of modular weathertightness should the designer understand and own, and which binding parts must be deferred to the manufacturer's tested system and the specialists, with warranties?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Weatherization — Wikipedia — Weatherization, 2026.
- 02Curtain wall (architecture) — Wikipedia — Curtain wall (architecture), 2026.
- 03Modular building — Wikipedia — Modular building, 2026.
- 04National Building Code of India — Wikipedia — National Building Code of India, 2026.
That completes the module's account of how a factory-made building carries its services, its finishes and its weathertightness across the factory-site boundary. Next the course turns to performance, risk and economics — fire, acoustics and the honest cost-and-time case — where the same discipline of deferring binding engineering to the specialists applies with particular force.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →