Owner's representative drawing review is usually described as a single event: a set goes out, a reviewer checks it, findings come back before bid. That description holds for a single building on a single schedule. It stops holding the moment a program is broken into phases — a campus expansion delivered building by building, a hospital renovated wing by wing while parts stay occupied, a mixed-use development released in stages tied to financing. On a multi-phase program, the review question isn't just "is this set internally coordinated." It's whether this phase still agrees with the phase before it, and the one before that.
Why phasing creates a coordination problem a single review doesn't have
A one-building project has one set of interface points to check: where structural meets MEP, where the spec book meets the drawings, where civil meets the building envelope. A phased program has all of that, per phase, plus a second layer that doesn't exist on a single-building job — the interface between phases themselves. A shared utility riser sized in Phase 1 has to still work when Phase 3's loads get added to it. A structural grid established at the start of the program has to hold when a later phase's engineer, who may not be the same engineer, ties into it. A life-safety egress strategy designed around a fully built-out campus has to remain valid at every intermediate stage, when parts of the site are still under construction and other parts are already occupied.
None of these are things a reviewer catches by reading the current phase's set carefully. They're only visible by comparing the current phase against what was actually built, or approved, in the phases before it — which means the review has to carry information forward, not just check what's in front of it.
Where consistency actually breaks between phases
The failure pattern on multi-phase programs is rarely a single dramatic conflict. It's smaller and more structural than that:
Design team turnover. Multi-phase programs often run long enough that the architect, structural engineer, or MEP consultant on Phase 3 isn't the same firm — or the same individuals within the firm — who worked Phase 1. Standards that were never fully written down, just understood by the people who set them, don't transfer automatically to whoever picks up the next phase.
Code and standard changes mid-program. A program that spans several years can span a code cycle. A detail that was compliant when Phase 1 was permitted may not be the detail a later phase should replicate, even though matching what was already built is the instinct that keeps a campus looking and performing consistently.
Shared infrastructure sized for an assumption that shifts. Utility capacity, structural load paths, and site drainage are frequently sized against the full build-out program at the start, then re-verified loosely, if at all, as later phases actually get designed. A later phase that quietly exceeds what earlier infrastructure was sized for doesn't show up as an error in that phase's own set — it only shows up as a conflict against the earlier one.
Spec drift. Material and system specifications get revised phase to phase — sometimes deliberately (a product got discontinued, a better option came along), sometimes as an unexamined default from whichever spec template the current design team started from. Either way, an owner running a program expecting some consistency of finish, performance, or maintenance across buildings can end up with drift nobody flagged as a decision.
None of these four failure patterns show up in a standard single-set constructability check. Each one requires the reviewer to hold information about a prior phase — what was actually built, approved, or specified — and check the current phase against it, not just against itself.
What a phase-aware review actually checks
A drawing review scoped for a multi-phase program has to do everything a single-phase review does — full cross-discipline coordination, spec-to-drawing consistency, code compliance — plus a specific set of cross-phase checks a reviewer can only perform if the engagement is structured to carry information forward:
- Interface points with prior phases, checked against as-built or as-approved conditions from the earlier phase, not against the current phase's own assumptions about what's already there.
- Shared infrastructure capacity, re-verified against the cumulative load of every phase built or approved so far, not just the phase currently under review.
- Standards continuity, flagging where a current phase's detailing, material selection, or system approach diverges from what an earlier phase established — not to force uniformity where a deliberate change is justified, but so the divergence is a decision someone made on purpose, not an accident of design-team handoff.
- Code-cycle changes, noting where a detail that matched an earlier phase is no longer the code-compliant version, so the owner can decide between matching the existing campus and meeting current code, rather than a designer defaulting to one without flagging the tradeoff.
Why this needs a running record, not a fresh review each time
The practical obstacle to catching any of this is that it requires memory. A reviewer engaged fresh for each phase, with no visibility into what an earlier engagement — by the same firm or a different one — actually found and resolved, is starting from zero every time. That works fine for the internal coordination check. It doesn't work for the cross-phase check, because there's nothing to compare the current phase against except whatever the reviewer happens to remember or re-request from the owner.
The fix isn't a more careful reviewer — it's a findings record that persists across phases and gets checked against on every subsequent one. That's a structural feature of the engagement, not something a single review adds after the fact: a cumulative log of what each phase's review found, what got resolved, and what standards or dimensions were established, available to whoever reviews the next phase, whether that's the same firm or the owner's rep referencing it directly.
This is also where an owner's representative's continuity matters more on a phased program than almost anywhere else in the process. Design teams can and do change phase to phase. A GC on a phased program is frequently rebid or renegotiated per phase too. The owner's rep — and a review process the owner's rep maintains across the program — is often the only party with visibility across every phase from the first one to the last, which makes that role, and the review record it holds, the actual mechanism for consistency rather than an assumption that consistency will happen on its own.
Key takeaways
- Multi-phase programs add a coordination layer a single-building review doesn't have: whether the current phase agrees with what earlier phases actually built or approved.
- Design team turnover, code changes mid-program, shared infrastructure sized against shifting assumptions, and spec drift are the four places consistency most often breaks between phases.
- A phase-aware review checks interface points, cumulative infrastructure capacity, standards continuity, and code-cycle changes against prior phases — not just the current set against itself.
- Catching cross-phase drift requires a findings record that persists across the whole program, not a fresh review scoped independently each time a new phase goes out.
- An owner's representative with visibility across every phase, backed by a maintained review record, is usually the only party positioned to catch drift that no single phase's design team would see on its own.
Phasing a program is often the right call — it matches design and construction to financing, occupancy, or site constraints that a single mobilization couldn't accommodate. It just means the review has to be scoped for the program, not for the phase in front of it. Building an owner's representative drawing review into the project team from day one covers how to set that up before the first phase even goes to bid, and the same logic that separates constructability review consultants from in-house QA/QC applies here too — an in-house team reviewing its own current phase rarely has the independent, cross-phase record an outside reviewer can maintain for the life of the program.
Frequently Asked Questions
What's different about reviewing a multi-phase program versus a single building?
A single building only needs internal coordination checked — do the disciplines within this one set agree with each other. A multi-phase program adds a second layer: whether the current phase's set agrees with what earlier phases actually built or had approved, at shared interface points like structural grids, utility risers, and life-safety strategy.
Why does design team turnover matter for consistency across phases?
Standards set early in a program — material choices, detailing conventions, structural assumptions — are often never fully documented; they're understood informally by the people who set them. When a later phase brings in a different architect, engineer, or even a different team within the same firm, that informal knowledge doesn't transfer automatically, which is exactly where drift starts.
Can a code change mid-program actually cause a coordination problem?
Yes. A program that spans a code cycle can leave a later phase choosing between matching an earlier phase's now-outdated detail or meeting current code. Left unflagged, a designer defaults to one option without the owner ever making a deliberate call — which is the kind of decision a phase-aware review is meant to surface, not resolve unilaterally.
Does each phase need a completely new review, or should it build on the last one?
It should build on the last one. A review with no record of what earlier phases found or established can only check the current set against itself, missing everything that only shows up by comparing this phase to prior ones. A cumulative findings record, maintained across the program, is what makes the cross-phase check possible at all.
Who is best positioned to catch drift between phases on a long program?
Whoever has continuous visibility across the whole program — typically the owner's representative — combined with a review process that maintains its own record phase to phase. Design teams and GCs frequently change between phases; a review record that persists independently of those changes is what actually catches drift the current phase's team wouldn't otherwise see.