Why MEP Sets Bounce at Plan Check
The three reasons MEP sets get sent back by the building department or AHJ, and the coordination habits that get you first-pass approval and a cleaner build.
Most MEP sets bounce for one of three reasons: the set is incomplete (a missing schedule or compliance document), the disciplines aren’t coordinated (mechanical, electrical, and plumbing conflict with each other), or the code-compliance path isn’t documented. A pre-submission review that checks all three — before the building department or AHJ ever sees the set — is the single highest-leverage habit for first-pass approval.
A resubmittal never costs just a resubmittal. It costs the weeks the set sits in the queue again. It costs the fee to refile. It costs the schedule you promised your client, and a little of the confidence they had in you. And the frustrating part is that most bounced sets don't come back for hard engineering problems. They come back for preventable ones.
A “bounce” at plan check — the building department (or authority having jurisdiction) returning an MEP set with correction comments — rarely comes from one big error. It comes from a few avoidable gaps in completeness, coordination, and documentation.
Having read a lot of sets from the review side, the reasons cluster into three failure modes. Fix these three and first-pass approval stops being luck.
The pattern repeats across projects: a mechanical schedule referencing equipment that doesn't match the electrical load calculations, or rooftop units shown on the mechanical plans that never made it onto the structural sheets. Each is cheap to fix before submission and expensive once it's a formal correction comment — that gap, not the engineering, is what actually delays permits.
Failure Mode 1: The Set Is Incomplete
The most common rejection isn't a wrong answer — it's a missing one. A schedule that isn't there. An energy-compliance document that never made it into the set. Details referenced but not drawn. Occupant loads the reviewer can't find.
A reviewer can't approve what isn't in front of them. Gaps don't read as "we'll add that later" — they read as "this set isn't ready," and the whole thing goes back.
The habit that fixes it: a completeness pass before submission. Every referenced detail drawn, every schedule present, energy compliance documentation included, occupant loads and code data on the sheet.
Failure Mode 2: The Disciplines Aren’t Coordinated
This is the big one, and it's the reason multifamily and TI sets get bounced again and again. Mechanical shows equipment electrical doesn't feed. Plumbing routes through structure. A rooftop unit the structural set doesn't know about. Each conflict is a comment — and collectively they tell the reviewer the disciplines weren't talking to each other, so now they read everything harder.
Most building departments or authorities having jurisdiction (AHJs) will catch these coordination issues during review — or send the set back for clarification before approving it. The only question is whether you find them first, on your schedule, or the reviewer finds them for you, on theirs.
The habit that fixes it: coordinate before you submit. On BIM-enabled projects, federated models and automated clash detection catch many conflicts before submission. On smaller or 2D projects, the same result comes from structured coordination reviews across disciplines — the tool varies; the discipline of checking every system against every other one doesn't. Either way, conflicts get resolved in a working session, not left for the field: catching them before submission is dramatically cheaper than catching them at plan check or, worse, in the field.
Failure Mode 3: The Code Path Isn’t Documented
The systems can be right and the set still bounces because the *compliance story* isn't told. Energy compliance documentation is missing or mismatched. Ventilation rates that don't trace to ASHRAE 62.1. A load calc that doesn't agree with the panel schedule. National details in a jurisdiction with its own amendments.
A reviewer's job is to confirm compliance. If you don't hand them the compliance — the right forms, matching the drawings, at the correct code edition — they can't confirm it, so they comment.
The habit that fixes it: treat code documentation as part of the design, not a final-day scramble. Confirm the jurisdiction and edition at kickoff, pick the compliance path early, and cross-check every code document against the drawings before issue.
The Pre-Submission Review
Here's the single highest-leverage habit — run the set through a reviewer's checklist before the AHJ does. Completeness. Coordination. Code path. Discipline-to-discipline consistency. It's the same scrutiny a plan examiner applies, done by your own team while you can still fix things quietly.
A thorough pre-submission review significantly improves the odds of first-pass approval — it addresses the most common causes of review comments before the set is ever submitted. Approval is always the reviewing authority's call, but a set that's complete, coordinated, and documented gives the reviewer far less to comment on.
The Comments That Actually Come Back
Most MEP correction comments trace to one of three root causes — an incomplete set, a coordination gap, or unproven compliance. The specific comments that come back most often tend to look like this:
| Typical reviewer comment | Root cause |
|---|---|
| Equipment schedule missing or incomplete | Incomplete set |
| Load calculations don't match the schedules | Documentation mismatch |
| Rooftop/mechanical equipment not shown on structural | Coordination gap |
| Fire-damper detail missing (fire protection by others, but MEP references it) | Missing reference/detail |
| Ventilation basis / code path unclear | Code documentation |
The Pre-Submission Review That Prevents Them
Before a set goes to the AHJ, the checks that catch the most comments: all referenced details actually included · equipment and panel schedules complete · load calculations coordinated with the schedules · structural openings and equipment support confirmed · equipment power verified across mechanical and electrical · energy compliance documentation attached · adopted code edition confirmed for the jurisdiction · cross-discipline review complete · internal QA/QC sign-off done. None of these is engineering-hard — they're discipline-hard, which is exactly why a structured review beats hoping.
Why “Clears Plan Check” and “Builds Clean” Are the Same Habits
There's a bonus most teams miss: the habits that get you first-pass approval are the same ones that make a set build cleanly. Coordinated disciplines don't collide in the field any more than they do on the reviewer's screen. Complete documentation answers the crew's questions the same way it answers the reviewer's. A set that's genuinely coordinated produces fewer plan-check comments and fewer construction RFIs and change orders — which is also, not coincidentally, what most teams get wrong before a project even breaks ground; see what clients get wrong before MEP design starts.
Our three-phase process — pre-design, design, and post-design — applies the same review discipline a plan examiner uses, so teams reduce resubmittals, minimize RFIs, and move from permitting to construction with fewer surprises. It's the same discipline behind every white-label engagement we run: read about our coordination approach, or schedule a scope call.
Related: MEP Coordination Best Practices · MEP Design Phases (SD/DD/CD) · COMcheck vs. Title 24
Common Questions
Most rejections cluster into three failure modes: the set is incomplete (missing schedules or compliance documents), the disciplines are not coordinated (conflicts between mechanical, electrical, and plumbing), or the code compliance path is not documented (energy forms, ventilation basis, or load calcs that do not trace to the code).
BIM coordination merges each discipline’s 3D model and runs automated clash detection before the set is issued, so conflicts get caught and resolved on paper during design instead of surfacing as field RFIs and change orders during construction.
A pre-submission review runs the completed set through the same checklist a plan examiner would use — completeness, discipline coordination, and code documentation — before it ever reaches the building department or AHJ, so problems get fixed quietly instead of triggering a resubmittal cycle.
The Authority Having Jurisdiction — the building department, agency, or official responsible for enforcing the adopted codes and approving the permit set for a given project location.
A coordinated set with plans, equipment and panel schedules, load calculations, details, applicable code/energy-compliance documentation, and specifications — exact requirements vary by jurisdiction.
It varies widely by jurisdiction and workload; the reliable way to shorten it is to avoid it — resolve the common comment causes before the first submission.
No. BIM clash detection removes many physical conflicts, but approval also depends on completeness and documented code compliance, and the final call is always the reviewing authority’s.
Senior electrical design engineer and experienced third-party peer and city plan reviewer, having reviewed and produced sets across 900+ U.S. projects.
Connect on LinkedIn →Need This Level of Rigor on Your Next Set?
Send us your project basics — occupancy, square footage, jurisdiction, and timeline. We’ll come back with scope, deliverables, and a schedule you can hold us to, usually within 24 hours.
Schedule a Scope CallSend Your Project