AEO Answer · Plan Check

How Does Plan Check Resubmittal Work?

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

The resubmittal package has four components. Revised drawings, with every change clouded and numbered so the reviewer can find them. A response narrative addressing each correction comment by number — what was changed and where to find it. Updated supporting documents: recalculated sheets, revised energy compliance forms, new details. And the jurisdiction's resubmittal forms and fees, which vary by agency.

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 resubmittal package has four components. Revised drawings, with every change clouded and numbered so the reviewer can find them. A response narrative addressing each correction comment by number — what was changed and where to find it. Updated supporting documents: recalculated sheets, revised energy compliance forms, new details. And the jurisdiction's resubmittal forms and fees, which vary by agency. Once submitted, the package typically returns to the same reviewer, who verifies each correction against the response. This is why the response narrative matters so much: verification is fast when the reviewer can follow your trail, and slow — sometimes generating new comments — when they have to hunt. You're not just resubmitting drawings; you're making the reviewer's verification job effortless.

Clouding and the response matrix

Clouding is the industry's change-tracking language: a revision cloud around every modified area on the drawings, usually with a numbered triangle tag. The response matrix ties it together — a table listing each reviewer comment, the action taken, and the drawing or document where the reviewer can verify it. Together they turn a hundred-page set into a guided tour of exactly what changed. The discipline that pays off here is completeness of the clouding. Unclouded changes erode reviewer trust fast — the reviewer starts wondering what else changed that they can't see, and the review gets more skeptical, not less. Cloud everything, even the trivial fixes. Transparency is cheaper than suspicion.

Fees, queue position, and round two

Most jurisdictions charge a resubmittal or recheck fee, often scaled to the review time. And the resubmittal rejoins the review queue — it doesn't jump to the front. That's the hidden cost of correction rounds: not just the revision work, but the queue wait each time. Two extra rounds can add months even when the revisions themselves took days. On round two, reviewers check two things: that every prior comment was addressed, and a fresh-eyes pass that sometimes surfaces new comments on items that weren't flagged before. New comments on round two are normal and not a sign of failure — but they're another argument for making round one count.

  • Package anatomy: clouded revised drawings, numbered written responses, updated supporting docs, agency forms and fees
  • Response matrix: every comment mapped to an action and a verifiable location
  • Cloud everything: unclouded changes erode reviewer trust and invite scrutiny
  • Rejoins the queue: each round costs revision time plus queue wait
  • Round-two reviews can surface new comments — another reason to nail round one

What else do project teams ask?

Is there a fee to resubmit?
Usually, yes. Most jurisdictions charge a recheck or resubmittal fee tied to the review time the round requires. The fee schedule is published — check it when budgeting, because multiple rounds compound. Some agencies also have plan check expiration clocks, where an application dormant too long requires renewal fees. The fee is real but it's the queue time, not the money, that hurts most.
How many resubmittal rounds are normal?
One thorough round is the target and entirely achievable with a complete response. Two rounds total is common and unremarkable. Beyond that, diagnose: incomplete responses, scope changes mid-review, or a genuine technical disagreement with the reviewer. Each has a different fix, but all of them start with an honest look at why the previous round didn't close.
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