How to Respond to Plan Check Comments and Avoid a Third Resubmittal

What is plan check?

Plan check is the building department's review of construction documents against the adopted building, fire, energy, and zoning codes before it issues a permit. IBC Section 107.2.1 requires the documents to show the work conforms to code "as determined by the building official," and the plans examiner is the person making that call. When something is missing or noncompliant, the examiner sends back a correction list.

The applicant revises the set and resubmits, and the cycle repeats until every reviewer approves. California jurisdictions usually call this plan check; elsewhere it is often plan review. Requirements vary by city, and Helonic's plan check by city pages cover the adopted codes and local amendments in each one.

Three or more plan check rounds is common

Honolulu's Department of Planning and Permitting reported an average of 3.4 plan review cycles across 17 residential permits that did not use its AI pre-screen. Seattle's 2026 CivCheck evaluation report puts the historical median for middle housing at 3.72 correction cycles and 161 calendar days to pass plan review.

Each cycle in Seattle takes about a month of calendar time, by the same report. Getting out in two rounds instead of three or four is mostly a matter of how the first response is written and checked.

How should a plan check comment-response letter be structured?

The response letter is a checklist for the examiner. A good one lets them find every change in seconds. Build it this way:

1. Wait for every review to finish. Seattle will not accept correction responses until all reviews in the cycle are complete, per SDCI's response instructions. Answering one discipline early invites a second round from another.
2. Header: project address, permit number, resubmittal round and delta number, and date. Hawaii County defines the correction response letter as dated and signed by the licensed architect or engineer of record.
3. One section per reviewing discipline, in the order the city listed them. Milpitas asks for a response to each comment for each review discipline.
4. For each comment: the city's comment number, the comment quoted as written, what you changed, and where it is. Milpitas requires the letter to say which details, specifications, or calculations show the correction.
5. Where you did not make the change, give a code citation or documentation that explains why. Seattle asks for exactly that.
6. List voluntary changes separately, so the examiner knows which clouds were not asked for.
7. Consolidate every consultant's responses into one letter. Seattle asks applicants to put all responses from designers, engineers, and owners on one consolidated plan set.

Here is what three entries look like when they are written to be checked:

Compare that with "Revised per comment." That response gives the examiner nothing to check, so they recheck the whole sheet and anything nearby.

How do clouds and deltas work on a resubmittal?

Clouds show the examiner where the set changed, and deltas show which round each change belongs to. Hawaii County's cloud and delta memo is a clear version of the rule most cities follow:

• Draw a cloud around every change, anywhere in the set.
• Label each cloud with a delta symbol carrying that resubmittal's number. The first resubmittal is delta 1 on every sheet, even for unrelated changes.
• Add a revision block on each sheet that summarizes the change and the reason for it.
• Resubmit the full set, replacing superseded sheets and keeping the original sheet numbering.

Hawaii County rejects resubmittals at intake that skip the cloud and delta format or the response letter. Milpitas keeps earlier clouds on the sheets and gives each round its own delta, and only clouded changes carrying that delta count as part of an approved revision. An unclouded change is an unreviewed change.

Format matters as much as content at intake. Seattle reviews only complete plan sets, not loose sheets, and rejects uploads that are missing sheets or correction responses. Danville treats a resubmittal without a response letter as incomplete.

Why do permit sets go to a third round?

A third round usually traces back to how round two was answered. These are the patterns that cause it:

• The letter says fixed and the drawing does not. The response describes a change that never made it onto the sheet, or made it onto one sheet and not the plan that matches it.
• The fix stopped at one sheet. A wall type changes on the floor plan while the door schedule, the code sheet, and the detail still show the old condition.
• The fix created a new conflict. A corridor widened for egress takes the turning space out of the toilet room next to it, and the accessibility reviewer comments on round two.
• Changes went in without clouds. The examiner finds an unclouded change and comments on it, or the change is not treated as part of the approved revision.
• One consultant did not answer. The structural or MEP responses never reached the consolidated letter, so the open items roll into the next round.
• The disagreement had no code citation. Pushback without a section number reads as a refusal and comes back as the same comment.
• The package was incomplete. Loose revised sheets, a missing letter, or the wrong file format can send the resubmittal back at intake.

The second item on that list has a long tail. A comment can be closed with the city while the condition is still wrong somewhere else in the set, which then reaches the field. That problem, and how to reconcile it before construction, is covered in code comments become field problems.

Check the resubmittal against the prior set before it goes back

Before upload, check the revised drawings and ignore the letter. Read each comment, open the sheet you cited, and confirm the change is there and clouded. Then search the set for every other place the changed element appears: the door number, the wall type, the occupant load, the equipment tag.

Helonic does the comparison step on the PDFs. Revision comparison tracks what changed between the prior set and the revised one and flags modifications that were not clouded. A fresh review of the revised set with code compliance checking catches fixes that created a new conflict, with a page location for each finding.

The fewer comments you get in round one, the less of this there is. The pre-submittal plan review checklist covers that pass. For the AI tools some cities now run before intake, see city AI plan review vs applicant AI plan check and what the Honolulu and Seattle AI permit pilots measured. For the broader category, read what AI plan review is and AI plan check on the building department side.