What integrated delivery looks like on the ground at Atitlán

This series has covered five disciplines: preconstruction, the Schedule of Values, the construction schedule, material logistics, and the natural and vernacular materials that work at the lake. We have written about each one as if it were a discipline of its own, because at most builders that is how they are treated as separate teams, separate documents, separate handoffs, separate failure modes.

This post is the argument that they are not separate. They are one discipline expressed in five documents. And when they are treated as one, when the same team is responsible for all five, working from the same set of facts, updating the same baseline, and reporting to the owner in the same rhythm — the result is a project that behaves differently from one built by handoff.

That is what we mean when we say Atitlán Build is an integrated project delivery firm. This post is about what that actually looks like when the work is happening.

The five disciplines, viewed as one

Preconstruction is where the project is pressure-tested on paper. It produces a budget, a schedule, a procurement plan, a logistics plan, and a documentation set. Each of those is the starting point for one of the other four disciplines.

The Schedule of Values is preconstruction’s budget, expressed as a working document. Every line in the SOV came from the preconstruction estimate. Every assumption in the SOV traces back to a decision in the preconstruction design coordination. The SOV is not a separate document. It is the budget, alive.

The construction schedule is preconstruction’s schedule, also expressed as a working document. Every activity on the schedule corresponds to one or more SOV line items. Every long-lead procurement item flagged in preconstruction has a position on the schedule with the appropriate logistics buffer. The schedule is not a separate document either. It is the time dimension of the budget.

Material logistics is the supply chain that connects the schedule to the actual work. Every procurement document from buyout schedule to verified material commitments log to lead-time log to deposit tracking schedule is built against the construction schedule and the SOV. When a long-lead item slips, the schedule shows the delay, the SOV shows the financial implication, and the procurement log shows why. All three documents update together.

Natural and vernacular materials is the design dimension that ties everything else to place. Every material decision affects logistics, schedule, budget, and the integrated review during preconstruction. When local materials win, they win because the integrated review made the case visible early enough to change the design. When imported materials are chosen, it is because the project genuinely required them not because nobody asked the question.

These five disciplines are not a service menu. They are five views of the same project. The integrated delivery firm is the firm that can hold all five views at once.

What this looks like in monthly reporting

The clearest place to see integrated delivery is in the monthly owner report. A typical Atitlán Build owner report includes the following, all updated against the same set of facts on site:

The schedule, with planned versus actual progress and any variances flagged with named causes.

The SOV, with this month’s draw request, the line-item verification, and the cumulative cost-to-date against budget.

The procurement log, with every long-lead item’s current status, including any deposits paid this month and any deliveries received.

The site logistics summary, with any incoming deliveries scheduled for the next two weeks and any constraints on access or staging.

A narrative section that ties the four documents together: what happened this month, what slipped, what was recovered, what is at risk, and what decisions the owner needs to make.

This is the reporting rhythm that integrated delivery produces. The owner sees the project in four dimensions at once. Cost, time, materials, and logistics are not separate questions answered by separate people. They are one situation, described from four angles, in one document, every month.

For an owner who is not physically at the site and most of our owners are not, this rhythm is what makes the project knowable. The owner does not need to ask “how is it going.” The owner already knows, in specific detail, against specific baselines, with specific variances flagged. The owner’s job becomes reviewing decisions and authorizing actions, not chasing information.

What it looks like when a problem appears

The real test of integrated delivery is what happens when something goes wrong. Projects always have problems. The question is whether the problem stays small or grows.

In a non-integrated delivery model, a problem in one discipline tends to surface as a problem in another. A late material arrives, and the schedule slips. The owner is informed about the schedule slip. The cost implications surface later, in a change order. The procurement breakdown that caused the late material may never be identified, which means the same kind of problem recurs.

In an integrated model, the same problem surfaces differently. The procurement log shows the material delay the day it happens. The schedule shows the downstream impact within the same reporting cycle. The SOV shows the financial implication in the same draw period. The owner gets a single coordinated message: this material slipped by 11 days, here is the activity that is affected, here is the cost implication if we do nothing, here are the recovery options. The problem still happened. But the problem stays measured, not multiplied.

The integration is not magic. It is the consequence of one team being responsible for all five disciplines and all five documents, reporting to the owner on the same rhythm against the same baseline. When the documents update together, problems stay visible. When the documents are owned by different teams updating on different rhythms, problems hide in the gaps.

Why this matters at the lake specifically

Integrated delivery is good practice anywhere. At Lake Atitlán it is closer to necessity than good practice.

The lake adds layers from language to customs to permit complexity to material sourcing geography to seismic considerations to the regional craft economy. Each layer multiplies the cost of decisions made in isolation. A non-integrated project at Atitlán is not a project with a few more problems than a non-integrated project in the Bay Area. It is a project with cascading problems, because the decisions in each discipline ripple into the others in ways that builders working at a distance from the lake do not anticipate.

A foundation system specified without checking material logistics may turn out to require components that cannot physically reach the site. A finish material specified without checking customs lead times may delay the project by three months. A structural system specified without checking local craft capacity may require importing a crew the project budget never accounted for. A schedule built without acknowledging the rainy season will slip. An SOV built without alignment to the drawings will produce change orders.

Each of those failure modes is preventable. None of them is prevented by being talented in one discipline. All of them are prevented by holding the five disciplines together.

That is the work Atitlán Build is built to do. The firm exists because the lake demanded it. The integration is not a marketing claim. It is the operating model.