Plan corrections, explained

Two kinds of comment letters

Corrections arrive from two desks, and confusing them wastes cycles. A reviewer's comments come from the engineer examining your documents before sealing; they concern whether the engineering supports the drawings and the standard of care. An authority's comments come from the permitting office after submittal; they concern compliance with that jurisdiction's adopted codes, ordinances, and submittal rules. The two often overlap in substance — a good engineering review anticipates the authority's likely comments — but they are answered to different readers, and a sealed set can still draw authority comments, because the permitting decision belongs to the jurisdiction.

The categories comments fall into

• Calculation support. A detail is drawn that the calculations do not justify, a load path is asserted but not traced, or the calculations in the package describe an earlier revision of the design.
• Code compliance. A system, material, or configuration conflicts with the adopted code or a local amendment — occupancy-specific requirements are a frequent source.
• Coordination. The disciplines disagree with each other: the mechanical schedule exceeds the electrical service, the structural framing collides with the plumbing runs, the architectural plan shows a different building than the engineering sheets do.
• Completeness. Missing sheets, missing specifications, missing schedules — the documents cannot be approved because part of the design exists only in the designer's head.
• Documentation and form. Title blocks, revision clouds, jurisdiction-specific submittal items: unglamorous, and a real share of every comment letter.

How a clean response works

The response that restarts a review fastest has a recognizable shape. Each comment is answered individually and in writing, in the comment's own numbering. Each answer says what changed, and where — sheet, detail, calculation page. Revised documents are clouded or otherwise marked so the reviewer can find the change without re-reading the set. Where the design team disagrees with a comment, the answer says so and shows the code basis for the disagreement; reviewers accept argued positions far more often than silent non-responses, which read as oversights and return as the same comment in the next round.

What does not work: resubmitting the set unchanged with a cover letter, answering nine of eleven comments, or revising drawings without updating the calculations that support them. Each produces the same artifact — another round.

Corrections are information, priced in

Because correction rounds are normal, they belong in the plan rather than the list of surprises. Scoping accounts for them: the written scope describes how review rounds are handled for the engagement, and the design team's own schedule should hold time for at least one full cycle. A project that treats its first submittal as its final one has not been planned — it has been hoped. The cost guide discusses how correction rounds figure into what drives review cost; the short version is that complete documents and complete responses are the only reliable discount.