A clear stormwater plan-review comment log helps developers, engineers, and municipalities track each drainage issue from first review through response, revision, and final documentation.
Repeat comments are frustrating because they consume reviewer time, delay design decisions, and make it difficult for a project team to know whether a concern was actually resolved. A comment log cannot guarantee approval or eliminate every revision. It can, however, make the review process more transparent by connecting the original issue, the responsible person, the proposed response, and the evidence that supports the response.
Stormwater reviews often involve more than one discipline. A drainage model may affect grading, a detention design may affect maintenance access, and an erosion-control detail may need to coordinate with construction phasing. Local criteria, NPDES requirements, MS4 procedures, watershed constraints, and project-specific conditions also vary. The right log helps the team separate a technical question from a missing document, a policy choice, or a field condition that needs confirmation.
Who This Affects
Municipal plan reviewers, city and county engineers, developers, civil engineering firms, surveyors, landscape architects, and construction managers can all benefit from a consistent comment log. Public works departments may use one to coordinate drainage, transportation, utilities, and long-term maintenance. Developers may use one to organize responses before resubmitting civil plans. Owners and facility managers may use a smaller version when reviewing improvements that change drainage patterns or impervious area.
The log is especially valuable on infill and redevelopment projects. Existing pipes, inlets, easements, pavement, neighboring properties, and undocumented drainage paths create constraints that are not always visible on a new-site template. A comment that appears minor, such as a missing overflow route or unclear access to a control, may reveal a larger coordination issue.
It also matters when several agencies or departments review the same project. A watershed agency may focus on peak flow or water quality, a municipality may focus on public infrastructure, and a construction reviewer may focus on erosion and sediment controls. The project team needs to know which comment controls a design decision and which one asks for documentation or coordination.
The Stormwater Planning Issue
A plan-review comment is useful only when the team can understand what the reviewer needs. “Revise drainage” does not tell the designer whether the problem is a missing catchment, an inconsistent slope, a capacity issue, an incorrect receiving system, a maintenance concern, or a missing narrative. A better comment identifies the drawing or calculation, describes the concern, and states what information would allow the reviewer to close it.
The response should be equally specific. “Addressed” is not enough. A response can identify the revised sheet, calculation, model input, detail, easement, maintenance note, or field verification that answers the question. If the team disagrees, the log should record the technical basis for the alternative and the person responsible for confirming whether the alternative is acceptable.
Stormwater planning also extends beyond the initial design. A detention basin, infiltration feature, swale, outfall, or proprietary treatment device may work as designed but fail to provide its intended benefit if access, vegetation management, inspection, sediment removal, or ownership is unclear. Plan review is an opportunity to ask who will inspect the BMP, what condition triggers maintenance, and where those obligations are documented.
Regulatory context should be stated carefully. A construction project may need stormwater permit coverage and a stormwater pollution prevention plan, while an MS4 community may have local review procedures and post-construction requirements. The log should point the team to the applicable permit, ordinance, design manual, or agency requirement without implying that a generic checklist guarantees permit approval.
What to Review Before Moving Forward
Start with a controlled log rather than a collection of email threads. Each comment should have a unique identifier, date, reviewer, source, priority, related sheet or calculation, response owner, due date, status, and closure evidence. Useful status values include open, response drafted, revised, awaiting agency confirmation, closed, and superseded.
Before resubmittal, check the following:
- Every comment is copied accurately, with the source document and review date preserved.
- The team has identified whether the issue affects hydrology, hydraulics, grading, erosion control, water quality, maintenance, permitting, or documentation.
- The response names the exact plan sheet, detail, model, report page, or field record that changed.
- Revised sheets use consistent labels, elevations, flow arrows, drainage areas, and structure numbers across the plan set.
- Calculations and narratives reflect the same assumptions shown on the drawings.
- The design identifies ownership, access, inspection, and maintenance responsibilities for permanent BMPs.
- Construction-phase controls are coordinated with phasing, stabilization, stockpiles, entrances, dewatering, and receiving waters.
- Open questions that require agency confirmation are not marked closed prematurely.
- Superseded comments remain traceable, so the next reviewer can understand why the design changed.
The team should perform a cross-discipline review before sending the package back. One person can read the log for completeness, while another checks the plan set and calculations. If the revised basin footprint changes grading, that should be visible in the drainage analysis. If an outfall changes, the receiving system, erosion protection, access, and downstream conditions may need another look.
Use a short decision note for comments that involve judgment. Record the alternatives considered, the selected approach, the basis for selection, and any condition that must be verified later. This is helpful when a project changes hands or a public meeting raises questions months after the design decision.
For larger programs, managers can summarize open comments by project phase and risk. That view helps identify whether schedule pressure is coming from survey gaps, design coordination, missing ownership information, or agency questions that need a meeting instead of another markup.
Do not let the log become a private document that only one consultant understands. Give the owner, reviewer, contractor, and maintenance contact the information needed for their role. Sensitive internal notes may be kept separately, but the project-facing response should be clear, factual, and easy to audit.
Planning, Permitting, or Compliance Support That Fits
Some teams need a technical plan review, drainage study, SWPPP planning, BMP selection, or post-construction maintenance framework. Others need help organizing an MS4 program, mapping assets, preparing outfall screening, or prioritizing capital projects. A comment log can reveal which service is appropriate because it separates the immediate design correction from a broader program gap.
Stormwaterplanning.us can support planning and documentation workflows that help clarify responsibilities and prepare materials for review. The useful starting point is the unresolved issue: a grading conflict may need civil design coordination, a missing inspection procedure may need operations planning, and repeated submittal comments may indicate that the internal quality-control process needs a standard.
Training can help staff understand the review cycle, but training does not replace project-specific engineering or a jurisdiction's determination. Municipal and development teams should pair training with current local criteria, qualified technical review, and direct coordination with the authority having jurisdiction.
For organizations with recurring projects, create a reusable checklist from past comments. Separate universal quality checks from local requirements that must be confirmed for each jurisdiction. Review the checklist after closeout so it reflects the issues that actually caused rework, maintenance confusion, or construction changes.
Common Mistakes to Avoid
The first mistake is treating the log as a response letter instead of a control document. A polished narrative can still omit an owner, due date, or closure record. The second is copying old comments into a new project without confirming that the referenced criteria, receiving system, or site conditions still apply.
Another mistake is closing a comment because a drawing changed without checking the related calculations and maintenance notes. Stormwater systems are connected, and a small grading change can affect flow paths, storage, access, or downstream discharge. The log should prompt a coordinated check when one part of the design moves.
Teams should also avoid promising that a complete response will produce approval. The reviewer may identify a new issue, a different agency may have a separate requirement, or field conditions may change. Careful language supports compliance planning and reduces misunderstandings.
Finally, do not hide unresolved decisions in email. If the team is waiting on survey information, a utility owner, a property agreement, or agency direction, record that dependency and its effect on the schedule. Visibility helps managers make an informed decision about scope, timing, and communication.
A good log can also support future operations. At closeout, transfer the final BMP locations, ownership notes, access requirements, inspection frequency, and maintenance triggers into the owner's records. That handoff keeps the review conversation connected to the people who will inspect and maintain the system after construction, when undocumented assumptions are often discovered too late.
Next Step
Take the last stormwater review package that required more than one resubmittal and reconstruct the comment trail. Identify which questions were repeated, which responses lacked evidence, and which design changes were not carried through to related sheets. Turn those findings into a practical review log and a pre-submittal quality check for the next project.