What Happens After You Receive Civil Plan Review Comments?

What Plan Review Comments Mean

Review comments may identify code or standard compliance, missing information, a design concern, a coordination conflict, a documentation issue or a request for clarification. A comment does not always prescribe the final engineering answer. The design team remains responsible for understanding the concern and developing an appropriate response within the authorized scope.

Classify the Comments

• Compliance: a code, ordinance, standard detail or agency criterion is not shown or addressed.
• Missing information: a dimension, elevation, note, calculation, report or supporting document is absent.
• Coordination: civil information conflicts with architecture, landscape, utilities, traffic, survey or another discipline.
• Design concern: the reviewer questions the proposed technical approach.
• Formatting or documentation: sheet references, signatures, legends, linework or submittal conventions need correction.
• Clarification: the reviewer needs the design basis or intent explained.

First Step: Build a Comment Matrix

Create a log that preserves the agency comment verbatim, assigns responsibility, records the proposed response, identifies affected sheets or documents and tracks status. Numbering should remain aligned with the review letter. The matrix becomes the coordination record for the resubmittal and reduces the risk that a comment disappears inside email or marked-up PDFs.

Determine What Each Comment Requires

Some items are straightforward drafting revisions. Others require engineering judgment, updated calculations, agency clarification, an owner decision, architectural coordination, utility information, a survey update, geotechnical input or traffic analysis. Identify these dependencies before editing begins. A plan revision made without the necessary decision can create a second round of avoidable changes.

Update the Plans and Supporting Documents

Revise the drawings deliberately and use consistent revision conventions. If a change affects grades, drainage areas, utility profiles, accessible routes, pavement limits or quantities, check every related sheet. Update calculations, reports, details, specifications and estimates when the design basis or quantities change. A resubmittal should tell one consistent technical story.

Write Useful Responses

Respond to every comment. Identify the sheet, detail, note, calculation or report section that changed. Avoid a response that only says “corrected.” A useful response explains what was revised and, where appropriate, the design basis. If the team disagrees with a comment or needs clarification, document the issue professionally and coordinate with the reviewer through the accepted agency process.

Cross-Check the Entire Set

A local revision can have system-wide effects. A shifted driveway may affect grading, sight distance, striping, utilities and landscaping. A drainage change may affect basin geometry, walls, parking and earthwork. A revised accessible route can change spot grades and entrances. Before resubmittal, review grading, drainage, utilities, ADA, traffic, details, quantities, notes and permit documents for consistency.

Resubmittal and Later Rounds

Package the revised plans, response letter, calculations and supporting documents according to agency requirements. Confirm file names, seals or signatures where applicable, revision dates and required forms. Second-round comments may address incomplete responses, new conflicts introduced by revisions or issues not visible in the earlier set. They do not necessarily mean the first response failed; they do require another controlled review.

When Comments Reveal Larger Scope

A review comment can expose missing survey data, an unavailable utility connection, inadequate drainage space, a required offsite improvement or a conflict between disciplines. When the response exceeds the original scope, pause and define the added investigation, design responsibility, schedule and fee before proceeding. Treating a major design change as a quick redline creates risk for the entire team.

Common Causes of Delay

• Incomplete responses or skipped comments.
• Plans revised without updating calculations, reports or other sheets.
• Owner or design-team decisions made late.
• Unresolved utility, survey or geotechnical information.
• Responses that do not identify where the change was made.
• New inconsistencies introduced during rushed revisions.
• Resubmittal packages that do not follow agency file or documentation requirements.

Pre-Resubmittal Checklist

• Every comment appears in the response matrix.
• Responsibility and status are assigned.
• Plans, details, notes, quantities and supporting documents agree.
• Calculations and reports reflect design changes.
• Cross-discipline impacts were reviewed.
• Revisions are clearly identified.
• Written responses state what changed and where.
• Required signatures, seals, dates and file conventions are complete.
• The complete package received an independent final check appropriate to the scope.

When to Involve a Civil Engineer

Civil engineering involvement is appropriate when comments require design judgment, calculations, changes to grading, drainage, utilities, access, ADA or traffic elements, or coordination across the plan set. A defined review can also help an owner or contractor understand whether a comment is a documentation issue, a design change or a larger project constraint.

Related Services

• Permitting & Construction Support
• Engineering Production, CAD & QA/QC
• Rapid Response
• Start a Project

Related Insights

• When Independent Civil QA/QC Adds Value
• Traffic Control Plan vs. MOT Plan

Professional Note

Requirements vary by jurisdiction and project. This article provides general engineering guidance and is not a substitute for project-specific review of applicable codes, standards, records, surveys, geotechnical information, utility information or agency requirements.

Sawan Dhaliwal, PE
Licensed Civil Engineer — AZ | CA | MO