"One project, built twice" sounds, at first, like it's describing a modeling exercise — build it in software, then build it for real. That's true as far as it goes, but it undersells what the first build is actually for. The digital build isn't a rehearsal. It's where the project gets resolved while its decisions are still cheap to change.
Two kinds of building material
Every project is made of two different things: information and physical work. A dimension on a drawing, a material selection, a structural approach, a mechanical layout — these are all information, and information can be tested, compared, argued about and revised at very little cost. The moment that same decision becomes a poured foundation, an ordered material, or a wall that's already closed up, it becomes physical — and changing it now costs real time and real money.
A decision can be modeled, priced, checked against code, tested for constructability, and changed — repeatedly, cheaply — before anything has been purchased or built.
The same decision, once built, can usually still be changed — but now it means demolition, waste, delay and cost that didn't need to happen.
The economic principle underneath "built twice" is simple: resolve as much as possible while it's still information, because that's the version of the decision that's actually inexpensive to get right.
What gets resolved in the digital build
This goes well beyond a 3D model. The digital build isn't a single model or piece of software. It's the progressively developed body of information that describes the project before it becomes physical — drawings, models, engineering, cost, schedule, procurement, approvals, logistics and construction knowledge working together. Before anything happens in the field, that body of information is where the following converge and get tested against each other:
None of these are being considered in isolation, and none of them are waiting for their turn after design is "done." A structural approach gets checked against cost. A material selection gets checked against lead time. A detail gets checked against how it will actually be built in the field, by the people who will actually build it — while it's still a drawing, not a change order.
Resolve decisions while they are still information.
Why this isn't just preconstruction
The word describes work that happens before building starts. Building the project digitally means bringing that same knowledge forward so it can influence decisions while they are still design decisions. Why that matters, and what preconstruction is left to do, is the subject of When Should Construction Knowledge Enter an Architectural Project?
What the second build actually is
Because so much has already been resolved, the physical build shouldn't be where the project first figures itself out. It's where an increasingly understood and coordinated project becomes physical.
Field conditions still arise — they always do — but they're conditions being managed against a developed body of information, rather than the primary mechanism by which unresolved design decisions finally get made.
That's a meaningfully different experience of construction: it can mean fewer surprises and fewer change orders driven by decisions that were never really settled, and a physical build that's carrying out intent rather than discovering it.