Plan Corrections from City Hall

Plan corrections are the changes a building department asks for after reviewing a submitted set. The reviewer issues written comments, the design team revises the drawings to address each one, and the revised set goes back for another review. That cycle repeats until the comments are cleared. Each jurisdiction runs it differently, with its own comment format, response requirements, and review timeline. What is consistent is that the response has to be traceable: every comment answered, with a note saying where the change is. A remote architect or drafter can carry the revision work and build the comment response document alongside it. Keeping both with one person is what stops a comment from being answered twice or not at all. Your architect of record reviews, signs, and resubmits, and keeps the relationship with the department. We produce, you file.

Your firm does, and that line does not move. The architect of record is the one who submits, corresponds with the plan checker, attends any review meeting, and signs the resubmittal. The professionals we place are not licensed in the United States and do not represent your firm to a jurisdiction. What they do is the work behind the response: interpreting the comments, revising the drawings, assembling the response document, and tracking every item to closure. Where a comment is ambiguous, they draft the question for your team to ask rather than calling the department themselves. That division exists for a reason. A permit conversation carries commitments, and commitments belong to the licensed professional who is responsible for the project. Anyone offering to handle that conversation for you is describing a service they cannot lawfully provide.

That depends on how many comments there are and how deep they cut, so no honest answer is a fixed number. What can be said is when the work starts. Because the professional works your hours, corrections received in the morning are being worked on that afternoon, not on the following day. Simple comments about notes, dimensions, or missing information move fast. Comments that force a design change, a consultant revision, or a code reinterpretation take as long as the decision does, and that decision is yours. What kills a resubmittal schedule is usually not drawing time, it is the days a comment spends waiting for someone to decide something. Ask us what the first cycle looks like on a set like yours. Be suspicious of anyone who quotes a turnaround before reading the comments.

Missing information, inconsistency between sheets, and accessibility. Reviewers regularly ask for code analysis data that is not on the drawings, occupancy and construction type information, egress calculations, or energy compliance documentation. The second category is internal contradiction. A schedule that disagrees with a plan. A detail that does not match the wall type. A dimension that changed on one sheet and not on the others. The third is accessibility, where the requirements are dimensional and a reviewer can check them directly against the ADA standards and the state accessibility code. None of those are design failures. They are documentation failures, which is why a coordinated set and a second reader before submittal removes a large share of them. That second read is worth more than the revision work it prevents, and it costs a fraction of a review cycle.

Yes, and it is a common request, usually when a project changes hands or a consultant leaves mid-permit. The first step is reading the set rather than editing it, because inherited drawings carry conventions and assumptions that are not obvious. We need the current submitted set in its native files and the correction comments. Send the previous responses if there were any, plus whatever background the earlier team left behind. Where files are only available as PDFs, the set has to be converted before it can be revised, which is its own scope. What we do not do is take responsibility for the work already submitted. Your architect of record decides what to adopt and what to redraw. Reading an inherited set before touching it is the step that separates a revision from a redraw.