The Cost & Time Case

Start with the real gains, because they are real. The biggest and most reliable is speed through parallel working. On a conventional site, you cannot build the superstructure until the foundations are done - the work is sequential. With volumetric modular, the factory builds the modules at the same time as the site builds the foundations and groundworks; two long activities overlap instead of queueing. When the modules arrive, erection is fast - a floor of a building can go up in days rather than weeks. The result is a programme that can be dramatically shorter end-to-end, and on many projects that time is the dominant source of value: earlier completion means earlier rental or sales income, earlier occupation of a school or hospital, less time paying interest on the construction loan, and a shorter exposure to everything that goes wrong on a long site.

That shorter, more controlled programme creates a cluster of secondary savings. Prelims - the cost of simply running a site (site management, temporary works, welfare, security, scaffolding, plant hire, cranage time) - scale with how long the site is open, so compressing the on-site period cuts them directly. Quality and rework: factory conditions, jigs and bench inspection tend to reduce defects, and defects caught at the bench are far cheaper to fix than defects found on site or after handover, so the cost of rework and snagging can fall. Waste: measured, controlled cutting reduces material waste compared with open-site work. Weather and disruption: factory work does not stop for monsoon, so programme certainty improves, and a shorter, tidier site causes less disruption in sensitive or congested locations. Safety: less work at height and in the weather can reduce the human and cost burden of incidents.

Notice the shape of these savings: most of them are about time, certainty and quality, not about a lower unit rate for the physical building. This matters in the Indian context especially, because much of the Western prefab case rests on saving expensive site labour - and India's abundant, comparatively inexpensive construction labour weakens that particular argument. The Indian case for off-site leans much more on the savings listed here: speed, programme certainty, quality and the ability to deliver repeatable buildings at scale. Read honestly, prefab's economic promise is less I can build the same building cheaper and more I can build it faster, more predictably and more consistently, and those things have real monetary value - if the project is shaped to collect them.

Now the other side of the ledger, which brochures tend to skip. First, the factory: a production facility is a large fixed cost - tooling, jigs, the line, skilled staff, rent, overhead - and it has to be paid for. If it is underutilised (not enough volume to keep it busy), that fixed cost is spread thin and each module carries a heavy share, which is why factory set-up and utilisation dominate prefab economics. Second, transport: finished modules are large, heavy and fragile, and moving them from factory to site costs real money that a site-built project never incurs - and it rises sharply with distance, with the number of loads, and when modules are big enough to need oversize-load permits, escorts or route surveys. A factory far from the site can erase the saving entirely.

Third, craneage and erection: lifting heavy modules into place needs cranes, sometimes very large ones, plus the logistics of delivery sequencing, laydown space and a lift plan - costs concentrated into an intense, expensive few days. Fourth, and easily underestimated, design effort front-loaded: DfMA demands far more design and coordination done earlier and in more detail than a traditional project, because the factory needs complete, frozen information before it cuts anything. That is more design hours, more coordination, more up-front fee, spent before a brick is laid. Fifth, the cost of getting it wrong is higher: an error baked into a production run repeats across every module and is dreadful to correct once modules are built, so the risk premium and contingency can be higher.

Add these up and the picture is clear: prefab front-loads and concentrates cost into the factory, the design and the logistics, in exchange for a shorter, cheaper-to-run site. Whether that trade comes out ahead depends entirely on the project. A one-off bespoke building with little repetition, a distant or hard-to-reach site, a design likely to change, and no programme pressure is close to a worst case - the factory and logistics costs land with none of the volume savings to offset them, and such a project can cost materially more built off-site than on. This is why the honest answer to is prefab cheaper is always it depends, and why the next thing to understand is exactly what it depends on: volume and repetition.

Put the two sides together and a simple, powerful picture emerges - the one idea that decides most prefab business cases. Think of total cost as a fixed part plus a per-unit part. Site-built has a relatively low fixed cost (no factory to set up) but a higher cost per unit (every unit is made slowly, in the open, by hand). Prefab has a high fixed cost (the factory, the tooling, the front-loaded design, the logistics set-up) but a lower cost per unit once the line is running and repetition kicks in. Plot total cost against the number of repeated units and you get two lines that cross. Below the crossover - few units, little repetition - site-built is cheaper, because the factory's fixed cost is spread over too little volume. Above the crossover - many identical units - prefab is cheaper, because the low per-unit cost overwhelms the fixed set-up. The crossover point is the repetition threshold: the volume at which going off-site starts to pay.

This is the single most useful mental model in prefab economics, and it explains almost everything. It explains why off-site suits large repetitive programmes - housing, hotels, student accommodation, wards, cells, classrooms - where the same module repeats hundreds of times, and why it struggles with bespoke one-offs. It explains the learning curve: each repeat of an identical module is made faster and with fewer errors than the last, pushing the per-unit cost down further with volume, so repetition helps twice over. And it explains why concentrating the bespoke effort - a special ground floor, entrance and roof - while keeping the repeated accommodation standardised is such a common and sensible strategy: it preserves architectural interest where it is seen and harvests the volume saving where it is not.

But treat the crossover as a shape, not a number. Where exactly it falls depends on the system, the degree of repetition, the transport distance, local labour cost, the design effort, and how busy the factory is - all of which vary by project and region. In a high-labour-cost market the site-built line is steeper, so prefab wins at lower volumes; in India, where site labour is comparatively inexpensive, the site-built line is shallower, pushing the crossover to higher volumes and meaning you generally need more repetition before off-site pays on cost alone (which is why the Indian case leans so heavily on speed, quality and scale rather than unit cost). Locating the crossover for a real project - actually modelling where the lines cross with current rates - is precisely the work of a quantity surveyor or cost consultant. Your job as a designer is to understand that the crossover exists, to recognise whether a project has the repetition to clear it, and to design for repetition so the project sits on the right side of the line.

Even when prefab wins on total cost and time, it changes when the money is spent, and this catches clients and lenders out more often than the headline price does. On a traditional site, spend follows visible progress: you pay for what has been built, roughly in step with value appearing on the ground, and the cash-flow S-curve is gentle and familiar. With off-site, a large share of the building is manufactured in a factory before it ever reaches the site - so the client is asked to pay the manufacturer for modules that are sitting on a factory floor many miles away, well before there is anything to see at the site. The spend is front-loaded and steeper, and it is spent on assets the client cannot yet stand in.

That shift has real consequences. It needs financing that accommodates earlier outflows, and it needs trust and protection, because paying for work not yet delivered or installed carries risk - if the manufacturer fails, what has the client paid for and can they get it? This is why off-site procurement leans on mechanisms such as stage payments tied to manufacturing milestones, vesting certificates (transferring ownership of modules to the client as they are built and paid for), bonds or parent-company guarantees, and sometimes escrow - devices that manage the gap between paying early and receiving late. A client used to traditional cash-flow can be genuinely alarmed by the prefab curve if it is not explained up front, and a financing structure that assumes the traditional S-curve can starve the project at exactly the wrong moment. (The deeper procurement and insolvency risks behind these mechanisms are the subject of the next lesson.)

And here is the firm boundary for this whole lesson. Everything above is the shape of prefab economics - the kinds of saving, the kinds of extra cost, the crossover, the cash-flow shift. None of it is a number you can apply to a project. Whether the business case actually stands for a specific building - the real capital cost, the true programme saving and its monetary value, where the crossover falls, whether the financing works - is a quantitative question for quantity surveyors and cost consultants, using current rates, the chosen manufacturer's actual prices, this site's logistics and this region's labour market, alongside the manufacturer's own quotation. Treat every figure in a course like this as illustrative of a principle. The designer's contribution is to understand the economic shape well enough to recognise when prefab is likely to pay and to design the project - repetition, early certainty, buildability - so that it can; the binding business case is the cost consultant's.