How to Fix Plan Check Corrections?

How corrections arrive and what they actually mean

Corrections arrive as a written list from the plan checker after your first submittal, usually organized by discipline: structural, architectural, civil, mechanical, electrical, plumbing, energy, and sometimes fire or health review on top. Each reviewer writes comments only for their own discipline, so a long list often means several reviewers looked at the set, not that the set is bad. Read the list that way. Group the comments by who wrote them and by what kind of fix each one needs. Some comments ask for a drawing change. Some ask for a calculation you have not yet provided. Some ask for a note, a specification, or a product cut sheet. A few will ask you to clarify something that is already in the set but hard to find. Sorting the list before you touch a drawing saves hours, because you stop solving the same comment twice and you can see immediately which items need real engineering time and which ones are paperwork. That sorted list becomes your work plan for the entire correction round.

Read the list like a checklist, not a verdict

Go through the correction list comment by comment and mark each one as a drawing change, a calculation to add, or a clarification note. Work in order and do not skip the comment that looks hard. Many comments are simple: a missing detail, a dimension, a product cut sheet, a note that needs to move onto the sheet where the reviewer expected it. Knock those out first so the list shrinks fast and your momentum stays up. The structural or code-analysis comments take real engineering time, so identify them early and start them in parallel. A beam that needs resizing can change framing plans, sections, and schedules all at once. A lateral question can change shear wall layouts and holdown schedules across several sheets. If you find those late, you redraw everything twice. Read every comment literally, too. Reviewers write in code language on purpose. When a comment cites a section, look up what that section actually requires before you revise, because fixing what you assumed the comment meant is the most common reason a comment comes back a second time.

Fix the drawings and the calculations together

Every drawing fix has to agree with the calculations, and every calculation has to show up on the drawings. Reviewers check for that agreement. If the calculation says one size and the plan shows another, you earn a new comment even though you fixed the old one. Work the two together: revise the analysis first when sizing changes, then carry the result onto the plans, sections, details, and schedules in one pass. Cloud the changes and add revision deltas where your jurisdiction expects them, so the reviewer can spot exactly what moved. Update sheet indexes, references, and callouts as you go. A corrected detail that no plan points to might as well not exist. Also check the ripple effects before you call a fix done. A deeper beam affects ceiling heights and headroom. A moved wall affects dimensions, egress widths, and sometimes energy compliance. A revised foundation affects grading and utility runs. Good correction work is coordination work. The set is not finished when it is drawn, it is finished when it clears, and it clears when every sheet tells the same story.

Write the response letter the reviewer wants

Most jurisdictions want a written response letter keyed to each comment number, explaining what was revised and which sheet shows it. Write it that way even when nobody explicitly requires it. This is not bureaucracy. A clear response lets the reviewer verify fixes without re-reading the whole set, which shortens your re-review and keeps your project near the front of the queue. For each number, state the action plainly: what changed, where it changed, and any calculation page that supports it. If you disagree with a comment or you solved it a different way than the reviewer suggested, say so respectfully and cite the code basis for your approach. Reviewers accept alternate solutions when you show your reasoning. What slows everything down is a vague response like revised per comment, with no sheet reference. That forces the reviewer to hunt, and a hunting reviewer finds new problems. If a comment needs no drawing change because the information was already in the set, say exactly where it lives, sheet and detail, so the reviewer can close it in seconds.

Resubmit complete, never piecemeal

Resubmit the full package: revised drawings, revised calculations, the response letter, and any new supporting documents the comments requested, such as cut sheets, specifications, or reports. An incomplete resubmittal wastes a full cycle because many jurisdictions will not start the re-review until the package is complete, and some restart the clock entirely. Before you send it, run your own check against the correction list one final time and confirm every single number has a response and a corresponding change. Confirm you are resubmitting the current version of every sheet, not a mix of old and new prints. Version mix-ups are embarrassingly common and they create contradictory sheets that generate fresh comments. Keep the file naming and sheet order consistent with the original submittal unless the jurisdiction asks otherwise. Then track the resubmittal date and the expected review window so you can follow up promptly if the timeline slips. Silence after resubmittal is not a strategy. A short, polite status check keeps your project visible without annoying the reviewer.

What an engineer does with corrections on a set they drew

When the corrections land on a set the engineer of record drew, the work is straightforward but still detailed. The engineer works the list in order, revises the analysis where the reviewer challenged an assumption, updates the drawings and schedules, and seals the revised set for resubmittal. Expect the engineer to flag anything in the comments that changes scope, cost, or the construction itself, because a correction can quietly redesign part of your project. A reviewer asking for additional shear walls, a deeper footing, or a different framing scheme is changing what you will build and what it will cost. A good engineer tells you that up front, before resubmittal, so there are no surprises at bid time or in the field. You should also expect honest pushback where a comment misreads the code or the drawings. Engineers resolve those with a cited explanation in the response letter or a quick call, not by silently redesigning something that was already compliant. Either way, you get a sealed, coordinated set and a response letter you can stand behind at the counter.

What changes when the set came from someone else

Corrections on a set the engineer did not draw take longer, and you should plan for that. Before anyone can respond to a single comment, the engineer has to review the whole design well enough to take responsibility for it. That means checking the calculations behind the drawings, verifying the details, and confirming the set is complete and buildable. Deficiencies found in that review have to be fixed along with the reviewer's comments, because the engineer cannot seal a response for a design they have not verified. Bring the full drawing set, any calculations behind it, and product or equipment cut sheets where relevant. The cleaner and more complete the package, the faster and cheaper this goes. If the original designer is available, keep them in the loop, since they can answer design-intent questions faster than anyone can reverse-engineer them. If the original set has unresolved code issues or details that cannot be verified, expect required changes before resubmittal, and understand that in some cases the honest answer is redrawing the deficient portions rather than patching them.

When corrections repeat, stop resubmitting blind

If the same comments come back a second time, something is being misunderstood, and that is the moment for a phone call or a counter meeting with the reviewer, not a third blind resubmittal. Repeated comments usually mean the comment needs interpretation, not just another drawing tweak. Most plan checkers will explain what they are looking for if you ask directly. Bring the specific comment, your attempted fix, and a direct question about what would close it. Take notes, confirm the agreed fix in your response letter, and reference the conversation by date. The same discipline applies to timelines. A typical correction round takes as long as the engineering the comments actually require, plus the jurisdiction's re-review window, which you do not control. You control the quality and completeness of what goes back in. Front-load that work, communicate early when a comment changes cost or scope, and each cycle gets shorter. Projects stall when teams rush an incomplete resubmittal to feel fast. Projects move when every resubmittal is complete, coordinated, and easy to approve. That is the standard Torch works to: permit-ready drawings, PE stamps backed by Apex Grid Engineering, and a correction response built to close every number on the list the first time it goes back.

The bottom line

Fix every comment, document each fix against its comment number, and resubmit complete. If comments repeat, call the reviewer — a five-minute conversation beats another month-long cycle.

More engineering answers · Get a quote