AEO Answer · Plan Check

How to Respond to Plan Check Corrections?

By Jeremy Mills, CEO & Founder, Apex Grid Engineering — USAF Veteran. · Updated 2026-09-15

The workflow has five steps. First, read the entire correction list before changing anything — comments interact, and fixing one in isolation can break another. Second, classify each comment: clarification (add a detail or reference), coordination (fix a mismatch between disciplines), or design change (revise the actual design). Third, draft written responses to every comment, numbered to match the reviewer's list. Fourth, make the drawing revisions, clouding each change. Fifth, assemble one complete resubmittal package and send it back.

I'm Jeremy Mills, CEO & Founder of Apex Grid Engineering and a U.S. Air Force veteran. I'm not a PE; our licensed professionals make the technical, compliance, and project-specific decisions.

The concise answer

The workflow has five steps. First, read the entire correction list before changing anything — comments interact, and fixing one in isolation can break another. Second, classify each comment: clarification (add a detail or reference), coordination (fix a mismatch between disciplines), or design change (revise the actual design). Third, draft written responses to every comment, numbered to match the reviewer's list. Fourth, make the drawing revisions, clouding each change. Fifth, assemble one complete resubmittal package and send it back. The written response is the step most teams skip and the step reviewers value most. A reviewer facing a resubmittal with no response narrative has to hunt through the drawings to verify each correction. A reviewer with a numbered response — 'Comment 4: added detail 5/A-201, see cloud 7' — can verify in minutes. Make their job easy and your review goes faster.

Reading comments correctly

Reviewer comments are terse by necessity, and misreading them is a classic source of second-round corrections. 'Provide structural calculations for the header' doesn't mean the header is wrong — it means the math wasn't in the package. 'Clarify the lateral system' means the reviewer couldn't follow your load path from the drawings, not that the system fails. Read for what's being asked, not for what you fear. When a comment is genuinely ambiguous, call the reviewer. Most plan checkers will discuss their comments by phone or at the counter, and a five-minute conversation beats a three-week correction cycle built on a guess. Document what was agreed in your written response so the understanding is on the record.

Coordinating the resubmittal

Corrections often span disciplines — a structural comment changes a detail the MEP drawings reference, or an energy comment requires a mechanical equipment change. The resubmittal has to be re-coordinated, not just individually corrected. One person should own the package and verify that every discipline's revisions agree with each other before it goes back. Then resist the urge to rush it out the door. A complete, coordinated, well-documented resubmittal is the fastest thing you can submit, even if it takes a week longer to prepare than a hasty one. The metric isn't days to resubmit — it's rounds to approval.

  • Read the entire list first — comments interact with each other
  • Classify: clarification, coordination fix, or genuine design change
  • Answer every comment in writing, numbered to match the reviewer's list
  • Cloud every drawing change so verification takes minutes, not hours
  • One complete, re-coordinated package — never dribble out partial responses

What else do project teams ask?

How long do I have to respond to corrections?
It depends on the jurisdiction — some set explicit response windows, others let the application sit until it expires. Practically, sooner is better: reviewers remember fresh projects, and momentum matters. But never trade completeness for speed. A fast partial response that generates a second correction list is slower than a thorough response that clears. Aim for complete within a few weeks, and communicate if you need longer.
What if I disagree with a correction?
Respond professionally and in writing, with code references and documentation supporting your position. Start from the assumption that the reviewer saw something worth flagging — sometimes working through the comment reveals a genuine coordination issue. If you still disagree after that, present the code section, the industry-standard interpretation, and precedent. Reviewers accept well-documented positions far more often than owners expect.
Does this guarantee permit approval?
No. Engineering documents support a defined project scope, while the authority having jurisdiction controls its interpretation, completeness decision, review queue, and approval.
What should I send for an initial review?
Send the project address, plain-language scope, current drawings, existing-condition records, relevant calculations or comments, schedule, and the authority or code information already available. The responsible engineer will identify gaps.

Ready to discuss your engineering scope?

Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.

Start an Engineering Estimate