What a Third-Party Architectural Review Actually Is (And What It Isn't)

A third-party architectural review is not an audit of the architect. It is not a redesign, a code certification, or a second opinion on the aesthetic decisions. It is something more specific and more useful: an independent read of your construction documents before they go to the field, looking for what will cause problems once they do.

Most developers who commission this work have already learned why it matters. They have been through a project where coordination gaps between disciplines turned into field conflicts, where details that looked resolved on paper fell apart during construction, where the drawing set said one thing and the contractor's interpretation said another. The review is how they avoid paying for that lesson twice.

Here is what that review actually involves, and what it is looking for.

Cross-discipline coordination

A construction document set is produced by multiple consultants: architect, structural engineer, MEP/FP engineers, civil engineer and other consultants. Each working in their own drawing set, referencing each other's work, and hoping the references hold. Often they mostly do. The places where they don't are the places that generate RFIs, field conflicts, and change orders.

A thorough review reads across all disciplines simultaneously, looking for inconsistencies: structural details that don't match architectural details, civil information that conflicts with what's shown on the foundation plan, MEP routing that works on paper until it hits a beam that was moved in a later structural revision. These are not hypothetical problems. They appear in nearly every set reviewed at the 90% CD stage, because that is when the pressure to finish tends to outpace the bandwidth to coordinate.

Finding them before construction starts costs a fraction of resolving them in the field.

Constructability

A drawing set can be technically correct and still be difficult to build. Dimensions that require cross-referencing three sheets to understand. Details that are clear in isolation but don't resolve at the intersection of two systems. Sequencing that works as drawn but creates a problem in the field when the actual construction order becomes clear.

Reading a set for constructability means reading it the way a contractor will.  Looking for what is ambiguous, what is underspecified, what will generate a question during construction that should have been answered during design. Every one of those questions is a potential RFI. Every RFI is schedule or cost exposure. Some become change orders.

Building performance and long-term risk

Some issues in a drawing set are not coordination problems. They are design decisions that will create performance problems after the building is occupied.  For example, thermal bridging at structural penetrations, envelope details that are vulnerable to water infiltration under freeze-thaw conditions, air and vapor barrier continuity gaps that will affect energy performance and may draw inspection comments.

These items are worth identifying before construction not because they are always easy to fix, but because they are significantly harder to fix after the fact. A wall assembly that is built wrong is a warranty claim or a litigation risk. Caught at 90% CDs, it is a drawing revision.

Code and regulatory coordination

A third-party review is not a code compliance certification, that is the design team of record’s responsibility. But a review will surface the places where the documents appear internally inconsistent on regulatory matters: life safety notes that don't match the plans, code summaries that reference systems not reflected in the drawing set, specification sections that conflict with the details they're meant to govern. These are the items that create friction with building officials and inspectors, and that slow projects down at the worst possible moment.

What the deliverable looks like

A useful review produces a structured written report organized by discipline and system, with specific drawing references for each observation. It distinguishes between items that represent significant risk and items that are minor clarifications. It is written to be actionable, specific enough that the design team can respond to each item directly, and clear enough that the owner can understand what is at stake without translating from technical language.

The report is not a punch list and it is not a redesign. It is a set of observations and recommendations that the owner can take back to the design team, who remain responsible for the resolution. The value is in having an independent set of eyes, which are not under time pressure to finish the set, not managing a consultant relationship, and not looking at the drawings for the first time when the contractor calls with a question.

When to commission one

The most useful moment is at the 90% CD stage.  This is late enough that the set is substantially complete and early enough that findings can be addressed before the documents are issued for permit or bid. A review at 50% SD is too early; too much will change. A review after construction starts is better than nothing, but the window for clean resolution has closed.

For developers running projects with outside design teams, the review is one of the lowest-cost risk management tools available relative to what it protects. A drawing set that goes to a GC with unresolved coordination issues will generate those costs one way or another. The question is whether you find them or the contractor does.

The contractor's version is more expensive.