"Doesn't the architect already review the set?" is the first question most owners ask when a third-party plan review comes up. The honest answer is yes — and that review is real, thorough, and staffed by people who know the design cold. It's also scoped to a different question than the one a third-party plan review is built to answer, which is why hiring one isn't redundant with a process that already exists on every project.
The confusion is understandable. Both reviews look at the same sheets. Both produce comments the design team has to respond to. From the outside, "someone checked the drawings" looks like one activity. In practice, it's two reviews with different reporting lines, different questions, and different definitions of what counts as a problem worth flagging — the same gap we've written about from the owner's side in architect QC vs. owner-side review, looked at here from the scope-of-work angle: exactly where the line is drawn between what each review is contracted to check.
What the architect's own QC is actually scoped to check
An architect's quality control process — typically run under the terms of an AIA B101-style owner-architect agreement — checks the issued set against the architect's own design intent. The core question their QC is built to answer is: does what got drawn match what the design team meant to draw? That includes internal consistency within the architectural set, code compliance as the architect understands it, and coordination of the architect's own sheets with each other.
That's a legitimate and necessary check. It's also, by definition, a single-discipline read run by the party who authored the documents being reviewed. The architect's QC isn't structured to ask whether a duct routed on the mechanical engineer's sheet clears a beam on the structural engineer's sheet, because that's a cross-discipline question sitting between two different consultants' scopes of work — not an internal consistency question within the architect's own drawings.
An architect checking their own set for internal consistency is not the same activity as an independent party checking whether the architectural, structural, and MEP sets agree with each other. Both are real. They answer different questions, and a set can pass the first cleanly while still carrying serious conflicts the first was never built to catch.
What a third-party plan review is scoped to check instead
A third-party plan review starts from a different premise: no single discipline's QC process, run by the party that produced those drawings, is positioned to catch a conflict between disciplines. So the review is structured around the boundary lines where sets from different consultants meet — and where the drawings meet the specs.
In practice, that means checking:
- Cross-discipline conflicts — a mechanical routing decision that contradicts a structural member's location, an electrical panel clearance that a wall assembly doesn't allow for, a fire-rated assembly one sheet calls out and another sheet's detail doesn't support.
- Drawing-versus-spec conflicts — a spec section that specifies a product or assembly the drawings don't match, or a detail that assumes a condition the specs don't call out.
- Omissions between disciplines — places where a connection or transition should have been drawn or specified by someone, and wasn't, because each discipline assumed it was the other's scope.
None of that is a code-compliance check, and none of it duplicates what the architect's own QC already does within their own set. It's scoped specifically to the seams between disciplines' work — which is also exactly where coordination conflicts tend to hide, because no single consultant's own QC process has visibility across another consultant's sheets.
The independence question, not just the checklist
The scope difference isn't only about which conflicts get checked — it's about who the review reports to. An architect's QC, however rigorous, is run by a member of the design team, checking work that team produced, under a contract scoped to design services. Independent plan review firms are structurally separate from the design team and the contractor precisely so the review isn't checking the reviewer's own work — the same logic behind conflict-of-interest rules that bar a project's own designers from serving as third-party reviewers on code-compliance plan review, applied here to constructability review instead.
That separation changes what the review is incentivized to surface. A finding that reflects poorly on the design team's own coordination is easier to write plainly when the party writing it didn't produce the documents being checked and isn't the one who has to fix them.
Where this matters most: the handoff points between consultants
The scope boundary shows up most clearly at the interface points between disciplines — the places where one consultant's sheet ends and another's begins. A structural grid line, a mechanical routing decision, an electrical clearance requirement, and a fire-rated assembly detail can all touch the same six square feet of a building and be drawn by four different people who never directly coordinated that specific intersection. As we've covered in where coordination conflicts actually originate on a set, those interface points are disproportionately where conflicts live — and they're structurally outside the scope of any single discipline's own QC, architect's included, because no one discipline's review is positioned to see both sides of the seam.
That's also why a clean architect's QC review and a findings-heavy third-party plan review aren't contradictory results on the same set. They're checking different things. A set can be internally consistent within the architectural drawings — passing the architect's own QC cleanly — while still carrying real cross-discipline exposure that only shows up when someone reads the mechanical, structural, and electrical sets against each other and against the specs. What that reads like once it's written up is covered in the anatomy of a real findings report: specific sheets, a stated contradiction, a severity rating, and a dollar exposure figure where one is defensible — not a general comment that the set "looks coordinated."
Frequently Asked Questions
Does a third-party plan review replace the architect's QC process?
No. It runs alongside it, not instead of it. The architect's QC checks the architect's own set against design intent — a necessary step no third-party review is scoped to replace. A third-party plan review checks the interface points between disciplines and between drawings and specs, which the architect's QC was never structured to cover in the first place.
Is a third-party plan review the same as the plan review an AHJ or building department does?
No, and the naming overlap causes real confusion. A building department's plan review checks a set against applicable code before issuing a permit — life safety, egress, zoning, and similar code criteria, done by or for the jurisdiction. An owner-commissioned third-party plan review of the kind covered here checks constructability and cross-discipline coordination on the owner's behalf, independent of the permitting process. Both are legitimate; they answer different questions for different parties.
If the architect's QC already found no issues, is a third-party review still worth doing?
A clean result from the architect's QC confirms the architectural set is internally consistent with the architect's own design intent — it doesn't confirm the mechanical, structural, and electrical sets agree with each other or with the specs, because that was never what the architect's QC was checking. The two results aren't in conflict; they're answering different questions about the same set.
Who typically commissions a third-party plan review?
It's usually commissioned directly by the owner or the owner's representative, independent of the architect's design contract, specifically so the review's findings report to the party paying for the review rather than to the design team whose work is being checked.
At what point in the process should a third-party plan review happen?
Before bid, when possible — findings can still be resolved as redlines before pricing locks in. A review run against an issued-for-construction set can still catch the same conflicts, but the fix typically comes with a bulletin or change order discussion attached instead of a free correction.