In most projects, a design decision and its construction consequence are separated by a handoff: documents are issued, pricing follows, revisions are made, and questions arise in the field. Each step is reasonable. Together, they put distance between the people who make a decision and the people who find out what it means.
Integration changes that distance.
How a decision travels
- A design decision is made
- It is documented and handed over
- It is priced by a different party
- Revisions follow what the price reveals
- Questions arise as it is built
- A design decision is made
- It is tested for cost, constructability and procurement as it is made
- It is documented with that knowledge in it
- It is built by people connected to the decision
Continuity is the point
The advantage of integration isn't convenience, and it isn't simply having one name on a contract. It's continuity. The people who define, design, price, coordinate and eventually build the project remain connected to the same body of information and the same project objectives, from the first conversation through completion.
The point of integration isn't convenience. It's continuity.
What continuity changes
- Knowledge arrives earlier
- Construction experience takes part while decisions are still design decisions, as described in when construction knowledge should enter a project.
- Cost is feedback
- Cost is visible as the project develops. Where it's handled openly, the owner can see how a number is built up, which supports the ongoing alignment described in keeping a project budget meaningful.
- Constructability and procurement are inputs
- How something will be built, and whether it can be obtained, shape the design while they can still change it.
- The field informs the design
- What's learned in building returns to the people who made the decisions, so it improves the next one, not only the repair.
- Accountability is clearer
- When something doesn't work as intended, an integrated process makes it clearer who needs to resolve it, rather than allowing responsibility to disappear across a handoff.
What separation tends to lose
Every handoff asks information to cross a boundary, and some of what travels is the drawing while some of what stays behind is the reasoning: why a detail is the way it is, what a priority was, what was traded for what. That reasoning is what lets a decision be interpreted correctly later. When the people who hold it remain part of the project, less of that reasoning has to be reconstructed later. The documentation described in buildable information carries much of it, and continuity carries the rest.
What this means for an owner
It means a project that is worked through as one process instead of as separate phases, with decisions that can be traced from the first priority to the finished building. What that looks like in day-to-day practice, and what it can't promise, is the subject of what to expect from a design-build team.