A set goes through an AHJ's plan review before a permit is issued, so it's a fair question: doesn't that already cover what a third-party plan review is checking for? The short answer is no — the two processes run on different tracks, checking different things, for different audiences, and the confusion usually costs owners a round of avoidable change orders once they assume permitting stood in for coordination review.
The confusion is understandable. Both processes involve someone outside the design team reading the set closely. Both produce comment sets the design team has to respond to before work proceeds. But an AHJ's plan review exists to protect the public interest under the adopted code; a third-party plan review exists to protect the owner's budget and schedule by catching cross-discipline conflicts the code was never written to address. They intersect at specific, identifiable points in the process — not everywhere.
What an AHJ's plan review is actually checking
A building department's plan review — run by the jurisdiction, or by an ICC-certified third-party reviewer contracted to act on the jurisdiction's behalf — checks a submitted set against the adopted building code: life safety, egress, structural code minimums, accessibility, zoning, and fire/life-safety systems. Many jurisdictions run formal expedited review programs built around exactly this scope; Fairfax County's Expedited Building Plan Review Program, for example, lets applicants route their set to a jurisdiction-approved list of certified peer reviewers specifically to compress code review turnaround, not to add a coordination check.
That's the key distinction: an AHJ reviewer's job is to confirm the set complies with code, not to confirm the mechanical, structural, and electrical drawings agree with each other on a routing decision that has nothing to do with a code section. A duct that clears every code-mandated clearance can still collide with a beam the structural set shows six inches over — code-compliant and uncoordinated at the same time. The AHJ's plan review has no mechanism to catch that, because catching it was never the assignment — the same scope boundary we've laid out in how a third-party plan review is scoped differently from an architect's own QC, applied here against the permitting process instead of the design team's own review.
Passing AHJ plan review confirms a set meets the adopted code. It does not confirm the set is internally coordinated across disciplines — those are two different questions, checked by two different processes, and a set can pass one cleanly while still carrying real cross-discipline exposure the other was built to catch.
Where the two processes actually intersect
The overlap isn't zero — there are a handful of specific points where a third-party plan review and the AHJ permitting process touch the same documents.
- The permit set itself. A third-party review run against the same issued-for-permit set the AHJ is reviewing is looking at identical drawings and specs, just asking a different question of them. Findings on one track don't automatically surface on the other.
- Deferred submittals. Items like fire alarm shop drawings, truss packages, and certain specialty equipment are frequently deferred — submitted after the permit is issued, subject to the building official's prior approval per code (California's model language, adopted in similar form elsewhere, requires deferred items to be listed on the construction documents and approved before they're deferred). A third-party review that flags a coordination gap involving a deferred item is flagging something the AHJ won't independently catch until that deferred package is actually submitted, often well after the general contractor has priced the work.
- Bulletins and addenda driven by either process. A code comment from the AHJ can trigger a revision that introduces a new cross-discipline conflict; a third-party finding can trigger a revision that needs a formal permit amendment. Each process can generate work the other has to react to, which is the main practical reason to sequence them deliberately rather than let them run on separate, uncoordinated timelines.
Sequencing: why timing the two processes matters
Because both processes can trigger revisions to the same set, running them without any sequencing invites duplicated redline cycles — a bulletin responding to an AHJ code comment lands after a third-party review has already checked that sheet, and now the coordination check has to be redone against a set that's already moved. The lower-cost sequence is to run the third-party review first, against the same set headed to permit, so cross-discipline fixes get folded in before the set goes out the door rather than layered on top of it afterward. That's consistent with what we've written about pre-bid vs. issued-for-construction review timing generally: the earlier a conflict is caught relative to when the set locks, the cheaper the fix is to make.
What a third-party plan review flags that never reaches the AHJ's desk
Most of what a third-party plan review exists to catch has no code angle at all, which is exactly why it never surfaces during permitting. A mechanical routing decision that contradicts a structural member's location isn't a code violation if both disciplines independently meet code minimums — it's a coordination failure between two sets that were never checked against each other. The same is true of a spec section calling for a product or assembly the drawings don't match, or a connection detail that one discipline assumed was the other's scope and neither drew. None of that trips a code plan reviewer's checklist, because none of it is a code question. It shows up in the field instead, as an RFI or a change order, unless something upstream of the field was scoped to catch it and write it up the way described in the anatomy of a real findings report — specific sheets, a stated contradiction, and a dollar exposure figure, not a general comment that the set "looks coordinated."
Key takeaways
- AHJ plan review checks code compliance; third-party plan review checks cross-discipline coordination. Passing one says nothing about the other.
- The two processes intersect at the permit set itself, at deferred submittals, and at bulletins/addenda triggered by either track.
- Sequencing a third-party review before the set goes to permit avoids duplicated redline cycles later.
- Most third-party findings — cross-discipline clashes, spec-vs-drawing conflicts — have no code angle and will never surface through the AHJ process on their own.
- A clean permit approval is not evidence of a coordinated set; it's evidence of a code-compliant one.
Frequently Asked Questions
Does passing AHJ plan review mean the set is coordinated across disciplines?
No. AHJ plan review confirms code compliance — life safety, egress, structural minimums, accessibility, and similar criteria. It doesn't check whether the mechanical, structural, and electrical sets agree with each other on routing, clearances, or assembly details, because that's not a code question. A set can pass permitting cleanly and still carry real cross-discipline exposure.
Can a third-party plan review affect the permitting timeline?
Indirectly, yes, in a positive direction when it's sequenced correctly. Findings caught and resolved before the set is submitted for permit mean fewer bulletins generated mid-permit-review, which keeps the AHJ's review moving against a more stable set. Run after permit issuance instead, findings that require formal changes may need a permit amendment, which does add time.
Are deferred submittals a gap between the two processes?
Yes, and it's one of the more common intersection points. A deferred item — fire alarm shop drawings, trusses, specialty equipment — isn't reviewed by the AHJ until it's formally submitted, often after the general contractor has already priced the work. A third-party review that reads the base set for how a deferred item is expected to coordinate with adjacent disciplines can catch a conflict before that later, harder-to-fix submission stage.
Is a third-party plan review required to get a permit?
No. It's not part of the regulatory approval process and isn't required by any AHJ. It's commissioned independently by the owner to catch coordination risk the permitting process isn't scoped to check, which is why the two can run on completely separate timelines if no one deliberately sequences them.
Who should commission the third-party review relative to the permit submission?
Typically the owner or the owner's representative, timed to run against the set before it's finalized for permit submission. That sequencing lets cross-discipline fixes get folded into the same set the AHJ will review, rather than generating a separate bulletin cycle after permit comments are already in hand.