Why MEP Sets Bounce at Plan Check
Three common reasons MEP sets get sent back by the building department or AHJ, and the coordination habits that improve your odds of a clean first review.
- A common cause of review comments is missing information rather than an incorrect answer.
- Each unresolved conflict can draw a comment, and collectively they can tell the reviewer the disciplines weren't talking to each other.
- Run the set through a reviewer's checklist before the AHJ does.
Three common causes of MEP plan-check comments are incomplete information, coordination conflicts, and an undocumented code-compliance path. A pre-submission review that checks all three — before the building department or AHJ ever sees the set — can reduce avoidable first-review comments.
A resubmittal never costs just a resubmittal. It can add review time while the set waits in the queue again. It may incur an additional fee, depending on the jurisdiction. It can cost the schedule you promised your client, and a little of the confidence they had in you.
A “bounce” at plan check — the building department (or authority having jurisdiction) returning an MEP set with correction comments — can result from gaps in completeness, coordination, and documentation, as well as technical noncompliance.
Having read a lot of sets from the review side, the reasons cluster into three failure modes. Fix these three and fewer correction comments come as surprises.
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 usually cheaper to fix before submission than once it's a formal correction comment — those unresolved gaps can delay a permit.
Failure Mode 1: The Set Is Incomplete
A common cause of review comments is missing information rather than an incorrect answer. 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 can go 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 a big one. Mechanical shows equipment electrical doesn't feed. Plumbing routes through structure. A rooftop unit the structural set doesn't know about. Each unresolved conflict can draw a comment — and collectively they can tell the reviewer the disciplines weren't talking to each other, so now they may read everything harder.
Building departments or authorities having jurisdiction (AHJs) may flag these coordination issues during review — or send the set back for clarification before approving it — but permit review is not a comprehensive coordination check. The aim is to find them before submission rather than leave discovery to the reviewer or field crews.
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, structured coordination reviews across disciplines can catch many conflicts — 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 usually 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 the applicable adopted codes and referenced standards, such as ASHRAE 62.1, ASHRAE 62.2 for nontransient residential dwelling units, or ASHRAE/ASHE 170 for covered healthcare spaces. 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 a high-value habit — run the set through a reviewer's checklist before the AHJ does. Completeness. Coordination. Code path. Discipline-to-discipline consistency. It's the kind of scrutiny a plan examiner applies, done by your own team while you can still fix things quietly.
A thorough pre-submission review can reduce avoidable first-review comments — it addresses common causes of review comments before the set is ever submitted. Approval is the reviewing authority's call, but a set that's complete, coordinated, and documented gives the reviewer less to comment on.
The specific comments these three failure modes produce — and the correction each one wants — are catalogued in the 7 MEP plan-check comments I wrote on almost every set.
Before a set goes to the AHJ, the checks that help catch common 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 (the DOE state energy code portal is a quick check for the energy code) · cross-discipline review complete · internal QA/QC sign-off done. Some of these checks are administrative; others need calculations, coordination, and engineering review — which is exactly why a structured review beats hoping.
Why “Clears Plan Check” and “Builds Clean” Are the Same Habits
There's a bonus that's easy to miss: the habits that help a set clear plan check are largely the same ones that help it build cleanly. Coordinated disciplines are less likely to clash in the field, although installation conditions, substitutions, and changes still need review. Complete documentation can answer the crew's questions much as it answers the reviewer's. A genuinely coordinated set can reduce coordination-related plan-check comments, construction RFIs, and change orders — which is also, not coincidentally, what teams often get wrong before a project even breaks ground; see what clients get wrong before MEP design starts.
Our design-support reviews address completeness, coordination, and code documentation to help teams reduce avoidable resubmittals, RFIs, and coordination surprises. The client's engineer of record reviews, seals, and issues the drawings. 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
MEP plans can receive correction comments for missing schedules or compliance documents, conflicts between disciplines, or an undocumented code-compliance path. Substantive code violations and unmet jurisdictional submission requirements can also require correction.
BIM coordination merges each discipline's 3D model and runs automated clash detection before the set is issued, so many conflicts can be 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 a checklist like the one a plan examiner would use — completeness, discipline coordination, and code documentation — before it ever reaches the building department or AHJ, so problems can be fixed quietly instead of triggering a resubmittal cycle.
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; ask the AHJ about current correction-review queues, procedures, and any expedited options — and resolve the common comment causes before the first submission to reduce the chance of needing one.
No. BIM clash detection helps catch many physical conflicts so they can be resolved in design, but approval also depends on completeness and documented code compliance, and the final call rests with the reviewing authority.
Senior electrical designer with 6+ years in U.S. MEP design, contributor to 900+ projects, and an experienced third-party peer and plan reviewer.
Connect on LinkedIn →