Your model runs without errors. But does it represent the site you are actually designing?
A successful simulation can still contain outdated drainage boundaries, unsupported runoff assumptions, or an outlet condition that understates flood risk. These gaps can surface during permit review—or after construction, when correcting them becomes far more disruptive. The stakes extend beyond a single storm. FEMA’s flood terminology guidance explains that a 100-year flood has a 1% chance of being equaled or exceeded in any year. The name does not mean a site gets 99 flood-free years between events.
This blog discusses seven hydrology model checks that help civil teams identify weak assumptions, coordinate drainage documentation, and prepare a more defensible design before final submission.
Why Hydrology Models Need More Than a Successful Run
Reviewers need to trace the analysis from rainfall and site conditions through runoff generation, routing, storage, and discharge. When assumptions are unexplained or calculations conflict with drawings, even plausible results become difficult to verify.
Hydrology establishes how much runoff is generated and when it arrives. Hydraulic analysis checks how that water moves through drainage infrastructure. Final review should connect both.
The Seven Checks Before Finalizing Your Drainage Design
1. Confirm Rainfall Data and Design Storms
Using rainfall copied from an earlier project can introduce the wrong location, duration, or storm distribution. A correct rainfall depth paired with an unsuitable distribution can also distort peak flows.
NOAA’s precipitation-frequency data include 90% confidence intervals, highlighting uncertainty around rainfall estimates.
Better practice: Confirm the rainfall source, coordinates, units, required storm frequencies, durations, and temporal distribution against jurisdictional criteria. Record the dataset version and retrieval date. Consider uncertainty where required or warranted by project risk; confidence bounds are not automatically mandatory design inputs.
2. Match Catchment Boundaries to Current Grading
A late grading change can redirect runoff while the model retains the original drainage areas. Roof connections, retaining walls, curb openings, and off-site contributions can create similar mismatches.
Better practice: Overlay catchment boundaries on the latest grading surface. Check that every area drains to its assigned receiving point and that overlapping or missing areas are resolved.
Use consistent catchment identifiers across:
- Drainage-area maps
- Model inputs
- Calculation tables
- Design reports
Clearly separate the existing and proposed conditions so reviewers can reproduce the comparison.
3. Verify Runoff and Infiltration Assumptions
A single default runoff parameter rarely describes an entire development. Soil conditions, land cover, compaction, and directly connected impervious surfaces influence the response.
The EPA’s SWMM 5.2 User’s Manual distinguishes four hydrologic soil groups—A, B, C, and D—with different runoff potential.
Better practice: Document the basis for curve numbers, runoff coefficients, or infiltration parameters, depending on the method used. Reconcile impervious percentages with the current layout. Check whether soil mapping adequately represents disturbed conditions and test influential assumptions where field information is limited.
4. Review Flow Paths and Runoff Timing
Peak discharge depends on when runoff reaches the outlet. An unrealistic time of concentration or lag time can change the peak and the apparent performance of storage facilities.
Better practice: Trace representative flow paths using current elevations, lengths, slopes, and surface conditions. Where applicable, distinguish sheet flow, shallow concentrated flow, and channel flow.
Confirm that the selected timing method is suitable for the model. Check rainfall, computational, and reporting intervals so that short peaks are resolved rather than hidden by coarse output.
5. Check Storage, Outlets, and Downstream Conditions
A detention facility may appear adequate because its storage curve is outdated or its outlet assumes unrestricted discharge. Downstream water levels can affect performance even when upstream runoff calculations are correct.
Better practice: Reconcile stage-storage relationships, outlet dimensions, invert elevations, and control structures with the drawings. Review tailwater assumptions, emergency overflow routes, maximum water levels, and applicable freeboard requirements.
Compare both peak discharge and runoff volume. Reducing the peak alone does not establish that every downstream impact has been addressed.
6. Investigate Continuity Errors and Unstable Results
A completed simulation is not proof of numerical reliability. Unexpected spikes, oscillations, or unexplained losses require investigation.
The EPA’s SWMM guidance on interpreting results states that continuity errors exceeding a reasonable level, such as 10%, call the validity of results into question. This is a warning example, not a universal acceptance threshold.
Better practice: Review model warnings, runoff and routing balances, and hydrograph shapes. Investigate instability and, where appropriate, test smaller computational time steps. Apply project-specific quality criteria; a low continuity error alone does not validate the underlying assumptions.
7. Reconcile the Model With the Submission Package
The model, drainage report, and plan set must describe the same design. Variations in catchment acreage, outlet sizes, or discharge values create avoidable review questions.
Better practice: Complete a final comparison of inputs, calculations, drawings, profiles, and schedules. Record the model version, software version, run date, and design revision.
Provide a concise results table identifying each required storm, discharge point, peak flow, storage level, and applicable criterion. Have another qualified team member review critical assumptions before the issue.
Hydrology Model Pre-Submission Checklist
Before issuing the drainage package, confirm that:
- Rainfall data and design storms match jurisdictional criteria.
- Catchment boundaries reflect the latest grading and site layout.
- Runoff and infiltration parameters have a documented basis.
- Flow paths, timing assumptions, and computational settings have been reviewed.
- Storage, outlet controls, and downstream conditions have been verified.
- Model warnings, continuity errors, and unstable results have been investigated.
- Model outputs agree with the drainage report, plans, profiles, and schedules.
- The model version and design revision are documented.
- Critical assumptions and results have received an independent review.
Where Model Gaps Create Avoidable Project Costs
An unsupported input can trigger more than a calculation revision. It may require updated drainage exhibits, resized infrastructure, revised grading, and another coordination cycle. A structured review helps teams catch these dependencies while changes are still manageable. It also makes comment responses easier because assumptions and revisions are traceable.
When Additional Hydrology Production Support Makes Sense
When overlapping deadlines limit internal capacity, additional production support can help maintain coordination while your engineering team retains design oversight. Intrivis, Inc. supports your team with hydrology modeling, drainage calculations, and supporting documentation, working within your standards and under your engineers’ direction so your project stays on schedule without compromising quality.
Need support with hydrology modeling or drainage documentation? Share your project scope with Intrivis, Inc. to discuss additional capacity for your next submission.