Transport & the Module Envelope

A volumetric module is, for one crucial journey, not architecture at all — it is a load on a vehicle on a public road, and public roads impose limits that have nothing to do with your brief. There are four that matter, and they are not equally forgiving.

Width is almost always the tightest. Roads, lanes, bridge parapets and oncoming traffic leave only so much room, so there is a width beyond which a load can no longer travel freely in normal traffic. Cross it and you enter the world of permits and escorts. Because width is so constrained, it tends to set the *short* dimension of a module — and therefore the depth of the rooms inside it. This single limit is why so many modules are long and relatively narrow: you can add length far more easily than width.

Height is the next constraint, and it is brutal because it is set by things you cannot negotiate with: bridges, railway arches, gantries, cables and tree canopies along the route. The limit is the clear height of the *lowest* thing on the whole journey, measured from the road to the top of the module *including the trailer deck it sits on*. A deep floor cassette or a pitched roof carried upright eats into the allowance fast. Height failures are unforgiving — a load that is too wide can sometimes crawl through with escorts; a load that is too tall simply does not fit under the bridge.

Length is usually the most generous of the four, which is why designers lean on it, but long loads still struggle on roundabouts, tight junctions and switchback site access, and beyond a point they too become 'abnormal'. Weight is the fourth, and it governs the axles and the bridges: total mass, and how it is spread across the trailer's axles, decides which routes and structures can carry the load. A heavy precast module may be within width and height yet barred from a weak rural bridge.

Hold the order in your head — width tightest, then height, then length, then weight — because it explains the typical shape of a module before you have drawn a single room. You are not designing a room that happens to travel; you are designing a legal load that happens to contain a room.

Put the four limits together and you get the transport envelope: the three-dimensional box, plus a weight ceiling, within which a load moves along a given route without extraordinary permits. It is not a single national number — it depends on the country, the specific roads between factory and site, and the trailer used — which is exactly why it must be established *early*, by transport specialists, for the actual journey, not assumed.

The envelope matters to you because it sets a ceiling on the module, and the module sets a ceiling on the room. Work the chain inward. Start from the route's free-travel width and subtract the wall build-up on both sides (structure, insulation, linings, the module's own frame); what remains is the clear internal width of the room. Do the same for height: route clearance, minus trailer deck, minus floor cassette, minus ceiling and services zone, leaves the clear internal ceiling height. The room you can offer is whatever survives after transport and construction have taken their share.

This is why module planning is a negotiation between the plan you want and the load you can move. A generous hotel room might need to be two modules joined on site, with the join detailed to disappear. A wide living space might be impossible as a single volumetric module and better done as panels assembled on site, or as a hybrid. The choice of *how far along the prefab spectrum to go* — which you met in Module 0 — is often decided right here, by a tape measure against a bridge.

There is a liberating side to the constraint. Because the envelope is fixed, it rewards a disciplined module size repeated many times: design one module that uses the envelope well, prove it travels, and repeat it. The envelope becomes a design module in the truest sense — a fixed unit you compose with. Crucially, none of these numbers is a specification you should carry from this lesson. The real envelope for a real project is set by the governing road rules and a transport assessment of the actual route, and it can change if a single bridge on the way is downgraded. Treat the envelope as a principle that disciplines the plan, and get the numbers from the people who move loads for a living.

What happens when the room you need genuinely will not fit the free-travel envelope? You do not simply stop — you escalate, and the escalation is a ladder where each step adds cost, time, coordination and risk. Understanding the ladder is part of judging a module size honestly.

At the bottom sits the normal load: within all limits, travels any time on any suitable road, no special permission. One step up, a load that exceeds a threshold becomes notifiable — the mover must give notice to the relevant authorities before travelling. Higher still, a genuinely oversize or abnormal load needs a permit for a *specific route at a specific time*, often with one or more escort vehicles, a prior route survey to confirm every bridge, bend and overhead clears, and restrictions on when it can move (frequently nights or weekends to avoid traffic). At the top, the largest special loads may need police escort, temporary removal of street furniture or signs, traffic management, and movement in convoy at walking pace. Each rung multiplies the cost per delivery and the lead time, and adds failure points — a permit refused, a road closed, an escort unavailable.

The design lesson is blunt: the envelope is not a wall but a cost gradient. You *can* move a bigger module, but every centimetre past the free-travel line is bought with money and schedule, paid on *every single delivery*. A scheme with three hundred modules that each need an escort is a very different proposition from one whose modules travel freely. Good module sizing keeps as many deliveries as possible in the cheap, unpermitted band, and spends the permit budget only where the architecture genuinely demands a larger volume.

There is also a risk dimension. Oversize moves are slower, more visible and more exposed to the weather, traffic incidents and delay; a damaged module arriving late can stall an entire crane-and-assembly operation waiting on site. This is precisely the kind of binding, consequence-heavy decision the course keeps handing to specialists: the permit thresholds, the escort rules, the route survey and the legal responsibility for an abnormal move belong to transport and logistics specialists and the governing road authorities, and they vary sharply by country and state. Your job is to design so that you need them as little as possible, and to bring them in early when you do.

There is one transport envelope so standardised, so globally agreed, that it has become a design primitive in its own right: the intermodal (ISO shipping) container. Its fixed external dimensions were set so that a box could move seamlessly between ship, rail and truck anywhere in the world — and that same fixity makes it an attractive, and heavily used, starting point for prefab, especially for off-grid, remote or export projects.

The appeal is obvious. A container is a known, repeatable envelope that is *guaranteed* to travel, because the entire global freight system is built around it: cranes, trailers, ships and rail wagons already fit it. Its corner castings give ready-made lifting and stacking points. It is robust, weatherable and available. For a site at the end of a difficult supply chain — an island, a mine, a disaster-relief deployment — designing within the container envelope can turn an impossible logistics problem into a solved one.

But the container is a transport solution first and a room second, and its dimensions were chosen for freight efficiency, not for living. The internal width in particular is tight for habitable rooms once you add insulation and linings, and the proportions are long and narrow. Serious container architecture therefore rarely leaves the box untouched: modules are combined side by side, cut open and joined to make wider spaces, or used as one ingredient in a hybrid. The romantic image of simply stacking raw containers into comfortable homes usually collides with the reality of width, insulation, thermal performance, cutting-induced structural work and the cost of all that modification — often enough that a purpose-built module sized to the *road* envelope is the better answer, reserving true containers for where their global mobility is the actual point.

The broader principle is the one to keep. Whether you adopt the ISO container or design a bespoke module to a road's free-travel envelope, you are choosing a fixed transport unit and composing architecture from it. The container simply shows the idea in its purest, most disciplined form: a standard envelope that can go anywhere, at the price of living within dimensions the freight system chose. As always, the exact sizes, weights, stacking and structural modifications are engineering and manufacturer matters — verify them against the real system, never from a diagram.