How to Organize a Response to Building Plan-Check Comments

Turn the comment letter into a work register

Number each reviewer item and preserve its wording in your internal register. Add the person responsible, required action, affected sheet and status. Avoid reducing several specific comments to a task labeled fix plans. That label makes it hard to know whether every point was addressed.

Distinguish an information request from a design change and a disagreement requiring clarification. The next action differs. If a comment is unclear, have the appropriate professional ask a focused question using the relevant drawing reference rather than guessing at a change that could create another issue.

Use the authority’s required response format

San Mateo's San Mateo: Revision and Resubmittal Form requests an itemized response and identifies resubmittal documentation. The San Mateo: Online Permit Center explains its submission workflow. These instructions make the expected deliverable more specific than a collection of revised pages. Follow the current requirements for the authority reviewing your project.

Write a response that tells the reviewer where to find the answer. A statement such as addressed is less useful than a concise explanation and sheet reference. Keep the response factual and professional; a disagreement should identify the question and supporting basis rather than attack the reviewer.

Coordinate changes that cross disciplines

A layout revision may affect structural, mechanical, plumbing or electrical information. Assign a lead to verify that the current package reflects the same decision throughout. If one consultant is waiting on another, show that dependency in the register rather than submitting inconsistent sheets to appear responsive.

San José's San José: Preapproved ADU and Site-Specific Application describes further cycles when comments require responses. The practical way to reduce avoidable cycles is a coherent submission, not a promise that every project can pass on the next try. Ask the team which remaining comments depend on an owner selection so those decisions do not arrive after coordination is complete.

Separate added scope from correction work

If an owner uses the review cycle to change finishes, layout or size, document that change separately. Ask how it affects professional scope, construction price and review. Otherwise, an invoice or delay can become difficult to interpret because the team treats all work as simply responding to the city.

A hypothetical owner moves a window while the designer is answering an unrelated structural comment. The revised package should explain both changes and their consequences. This avoids a reviewer discovering an unexplained alteration and a contractor pricing from an earlier version without realizing it has changed.

Check the package before sending

Confirm every comment has a response or an explicit pending question. Check the drawing index, revision dates, clouding or other requested change markings, associated calculations and response references. Submit through the official process, retain the receipt and archive the exact package.

After submission, update the schedule with the actual milestone. Do not label the project approved because all applicant tasks are finished. Track the next reviewer response and carry unresolved items forward. A good response register becomes the project's technical memory, making later revisions, inspection questions and professional handovers easier to understand.

A response entry that a reviewer can follow

A strong entry includes the original comment identifier, a concise explanation of the response and the exact sheet or document location. If the team seeks clarification rather than proposing a change, say that openly and identify the question. Do not write resolved when the decision is still pending.

For an issue touching several disciplines, identify the coordinated change in each affected document. Ask the lead professional to check that the response letter and drawings agree. A reviewer should not have to infer that an unlabeled change on another sheet is part of the answer.

Keep owner changes in a separate change list even when submitted with the same package. This makes later invoices and schedule discussions easier to interpret. It also prevents a reviewer from seeing unexplained alterations that were not requested in the original comments. At the next response, compare the new letter with the previous register and carry forward unresolved items deliberately. The register should evolve with the application, preserving the reason for decisions rather than becoming a disconnected checklist recreated from scratch at every cycle.

At the coordination meeting, ask each responsible professional to identify one remaining dependency, even if the answer is none. This prompts a direct check for missing owner decisions, calculations or outside information. Record the result before submission so the owner can distinguish a genuinely complete response package from one that is merely waiting for a last undocumented contribution.