Common Reviewer Flags on Drainage Report Submittals

Drainage report submittals draw predictable reviewer flags, including incomplete sections, conflicting documents, missing floodplain records, and unreadable sheets. The way to reduce those flags is to check the package as a reviewer would before submitting it. A complete report is a coordinated record of finished documents that meets the agency’s requirements and supports the same design throughout.

Why drainage report submittals keep coming back from review

Reports fail review in the same ways because agencies check them against clear requirements. A gap in those requirements generates a comment whether it concerns the engineering analysis or a missing cover sheet entry. The checklists are public documents, so the grounds for a return are generally knowable before submission. Packages repeatedly fail review because they are assembled without a systematic check against familiar standards.

That distinction makes the problem manageable. Completeness, consistency, regulatory documentation, readability, and comment resolution are separate checks, and passing one does not establish that the others are satisfied. A technically developed report can still fail at the administrative threshold. Before submitting, engineers need to check that all required material is there and that the parts fit together.

Missing or incomplete required sections

The first threshold is whether the package contains what the agency requires. The City of Phoenix G&D checklist states that plans may be returned without formal review if the engineer fails to address all applicable checklist items. A report that omits a required component can be returned before its technical conclusions receive consideration.

The City of Durham checklist requires report covers to carry the project name as it appears on the construction drawing cover sheet, REID numbers, and the signing professional’s seal. Each element has to appear where the checklist requires it. A project name elsewhere in the package does not complete a deficient report cover. Likewise, an otherwise finished report does not satisfy the cover requirements if the identification numbers or seal are missing. These are mechanical checks with explicit answers.

Applicability also needs an explicit answer. The Durham and Phoenix checklists require engineers to mark items N/A. A blank entry does not distinguish an omitted requirement from one that does not apply. The Town of Elizabeth criteria also call for three copies, a state-licensed PE’s signature, and a statement of whether the report is preliminary or final. Missing those requirements can trigger resubmittal before content review.

The required contents also depend on the project classification. Seattle’s January 2026 Stormwater Manual draft distinguishes appendix requirements for subdivisions and short plats from those for unit lot subdivisions. A report assembled against the wrong project category can therefore appear complete while still omitting required material. The applicable section list is the baseline. Without that baseline, checking that every heading has text is not a completeness review.

Cross-document inconsistencies between narrative, calculations, and plan sheets

Nomic’s drainage review documentation describes reviewers cross-referencing the written methodology against drainage area maps, plan sheets, calculation appendices, and profile sheets. That comparison reaches beyond arithmetic to drainage areas, storm events, pipe sizes, elevations, assumptions, and references. A calculation may be internally consistent yet describe something different from the plan. The package then fails to give the reviewer a single, supported account of the design.

The conflicts can be small in appearance but substantial in meaning. A drainage area may carry one label in the narrative and another on the exhibit. A pipe size used in the hydraulic calculations may differ from the size shown on the plan sheet. An assumption stated in the methodology may contradict the value used in the calculation appendix. Similarly, an elevation in the profile may conflict with the grading plan.

These discrepancies recur because cross-document review is difficult to compress into a final deadline check. The documents are large, and they are produced at different times. A late change in one document rarely propagates to every other place where the same information appears. Reviewing each file separately can therefore miss the very conflicts that become visible when the files are compared. Local completeness is not package consistency.

Some agency requirements expose those conflicts immediately. The City of Phoenix checklist requires retention calculations and storm event type on the cover sheet, where they can be checked against the report body. The City of Durham checklist requires the same project name on report covers and submitted file names as on the construction drawing cover sheet. Even the project identifier must remain consistent across the submission. These checks illustrate why a final QA pass needs to follow information between documents rather than stop at the end of each file.

Floodplain documentation and offsite drainage that reviewers expect but engineers often omit

Floodplain and offsite drainage omissions sit at a different boundary. The report may describe the on-site design while leaving out the records or review routing required by conditions beyond that design. Treating those obligations as someone else’s scope does not remove them from the agency’s requirements. The resulting flag may be a missing approval, an unaddressed review channel, or an incomplete account of offsite drainage.

The City of Phoenix G&D checklist requires an approved Floodplain Clearance Form for a project within floodplain boundaries. Submitting without that form halts review. Moving the package forward requires the approved clearance in addition to any discussion of floodplain conditions in the report. The presence of one does not substitute for the other.

The City of Durham checklist identifies a separate route for projects that did not require a site plan but have stream buffers and/or floodplain on the property. It sends those projects to DSCFloodPlain@durhamnc.gov and says they may need more permits. Failure to identify and address that route before submission can produce rejection on procedural grounds. A package prepared for the main review channel can still be incomplete for the property’s regulatory conditions.

The Phoenix checklist requires separate offsite plans showing drainage facilities unless those details appear on the grading plan. The Town of Elizabeth criteria require the preliminary report to address both existing on-site problems and offsite impacts of the proposed development. A report that covers only post-construction on-site conditions leaves out part of what is required. The requirement is not merely to describe the proposed work, but to document the drainage context the agency has asked to review.

Illegible reproductions and formatting problems that trigger resubmittal before review begins

Problems with how a report is presented can delay a project even when there is no disagreement over engineering judgment. The Town of Elizabeth criteria require reports to be cleanly and clearly reproduced and legible throughout. Blurred or unreadable portions are unacceptable and require resubmittal. A complete appendix therefore does not satisfy the requirement if its contents cannot be read. Legibility is part of whether the information has actually been submitted in a reviewable form.

The City of Phoenix checklist sets a minimum lettering and symbol size and requires original plan sheets clear enough to produce legible prints from a scanned copy. Reduction, scanning, or printing at a non-standard scale can make the reproduced sheet unreadable. The relevant threshold is the clarity of the material the reviewer receives.

Common problem areas include photostatic copies of nomographs, charts, and reference tables that become unreadable after reduction or re-scanning. CAD exports or PDF conversions can compress line weights or drop small text, while scanned handwritten calculations can enter an appendix without a scan-quality check. The City of Durham checklist also requires all sheets to be signed and sealed by a registered professional licensed in the State of North Carolina before final submittal. Missing or illegible seals remain a flag even at that stage. These are mechanical defects, but their effect on readiness for review is direct.

Failure to fully address prior review comments before resubmitting

After a review return, closing the outstanding comments takes priority over checking initial completeness. A response that addresses only part of a comment leaves the underlying issue open. Resubmitting the package does not itself resolve that issue or advance it toward approval. The Town of Elizabeth criteria state that the Town cannot approve reports or plans by default. A non-response or incomplete response therefore does not become acceptable with time.

A recurring failure is to resolve the straightforward comments while leaving the technically complex or ambiguous ones with a brief note. The response may note the concern but leave it unsettled. Reviewers then flag the item as unresolved, extending or restarting the review cycle. The useful distinction is between recording a response and closing a requirement. Only the latter clears the outstanding issue.

Tracking the review round supports that distinction. The City of Durham checklist requires engineers to track the submittal number on resubmittals and includes the instruction “do not pay again” for additional fees. Losing track of which comments belong to which round makes omissions more likely. A comment-response matrix keyed to the reviewer’s original comment numbers reduces that risk compared with a narrative response letter. Each line item has to be explicitly closed rather than absorbed into a general account of revisions.

That discipline also points back to the initial submission. The matrix makes the review requirements visible and keeps unresolved items from disappearing into the package. The same principle applies before any agency comments exist, when the checklist provides the requirements to be closed. Engineers who clear review on the first pass check the package before submission as thoroughly as reviewers check it during review.

Using a pre-submittal QA pass to catch these flags before the reviewer does

Every category of flag described here is detectable before the package leaves the firm. The agency checklist provides the requirements, while the assembled documents provide the evidence that those requirements have been met. The City of Phoenix checklist requires the engineer of record to certify that all applicable requirements have been satisfied before submission. Treated seriously, that certification calls for a substantive pre-submittal pass. It is the conclusion of the check.

A structured internal review mirrors the reviewer’s workflow. It compares the documents with one another, then checks the package against the agency checklist line by line. This includes checking that the narrative assumptions match the calculations and that all required supporting documents are there. It also gives reproduction quality and outstanding comments a defined place in the review.

AI-assisted QA can make that cross-document work more systematic. Nomic’s drainage review documentation describes tools that read multiple documents together and surface inconsistencies between narrative assumptions, drainage area maps, plan sheets, tables, and calculation appendices. The tool serves as a first-pass QA layer that organizes findings for professional review. The licensed civil engineer still verifies assumptions, applies engineering judgment, and makes the final submittal decision.

For AEC firms already using Civil 3D, Revit, or Bluebeam, pre-submittal QA can extend the existing workflow. An AI partner that fits those tools and learns the firm’s standards can help flag inconsistencies before submission. The value is faster systematic checking and fewer avoidable review rounds. A drainage report is ready when its required parts are present, readable, coordinated, and resolved. The pre-submittal QA pass is where the firm establishes that readiness before asking the reviewer to assess it.