If you've worked in stormwater management anywhere else in the country and then taken on a project along Colorado's Front Range, you've probably had at least one moment where you realized the rules you learned somewhere else don't fully apply here. Colorado's combination of climate, soils, topography, and regulatory structure creates stormwater challenges that are genuinely unique, and understanding them is the difference between a project that runs smoothly and one that generates surprises.

I've spent over a decade working stormwater projects from Fort Collins to Colorado Springs, and these are the issues that come up repeatedly. Some of them are obvious if you've lived here for a while. Others catch even experienced engineers off guard.

The Weather Doesn't Follow the Rules

Colorado's Front Range has a precipitation pattern that defies simple characterization. Annual rainfall along the urban corridor averages roughly 15 to 17 inches, which puts us firmly in semi-arid territory. But that average masks a reality that anyone who's been through a July afternoon on the Front Range understands: when it does rain here, it can rain with extraordinary intensity.

Summer convective thunderstorms routinely produce rainfall rates that exceed design assumptions based on annual totals alone. Half an inch of rain in 20 minutes is not unusual. An inch in an hour is well within the range of a normal summer storm. These high-intensity, short-duration events generate runoff volumes and peak flow rates that can overwhelm control measures designed for gentler rainfall patterns.

This is why the MHFD drainage criteria are calibrated specifically for the Denver metropolitan region rather than relying on national standards. The WQCV, the EURV, and the design storm frequencies in the USDCM reflect local rainfall data, not national averages. If your stormwater design is based on criteria developed for a different climate, it's probably undersized for Colorado conditions.

The flip side of intense summer storms is the long dry stretches between them. Your construction site might go three or four weeks without meaningful rainfall, creating a false sense of security. Then a single afternoon storm drops enough rain to mobilize every bit of loose sediment on the site. Control measures that haven't been maintained during the dry period fail when they're needed most. The lesson: maintain your control measures during dry weather, not just after storms.

Expansive Soils Complicate Everything

If there's one geotechnical condition that defines Front Range development, it's expansive clay soils. The bentonite-rich claystone formations that underlie much of the corridor from Castle Rock to Longmont create soils that swell when wet and shrink when dry. This affects stormwater management in ways that aren't always obvious.

Infiltration-based practices are often not feasible. Bioretention, permeable pavement, and infiltration trenches rely on water being absorbed into the underlying soil. When that soil is clay with an infiltration rate of 0.1 inches per hour or less, water sits on the surface instead of percolating through it. Any infiltration-based practice on expansive clay needs to be designed with an underdrain system that collects and conveys filtered water to an outlet point. Without the underdrain, you're building a pond, not a filter.

Detention facilities can experience structural issues. Extended detention basins built in expansive soils can develop cracking in outlet structures, slope instability on embankments, and differential settlement that affects grading and flow paths. The geotechnical recommendations for your site should address these risks, and your stormwater engineer should design the facility with appropriate over-excavation, moisture conditioning, and structural details to account for soil movement.

Pipe systems are vulnerable. Storm sewer pipes bedded in expansive clay can shift, separate at joints, and lose grade over time. This doesn't just affect the pipe's hydraulic function; it can create preferential flow paths that erode surrounding soils and undermine adjacent improvements. Proper bedding and backfill in accordance with the project's geotechnical recommendations is critical.

If your project's geotechnical report identifies expansive soils (and on the Front Range, the odds are good that it will), your stormwater design needs to account for that from the beginning, not as an afterthought when things start moving.

Altitude, Evaporation, and the Water Balance Problem

The Front Range sits at roughly 5,000 to 6,500 feet of elevation, and the combination of altitude, low humidity, and abundant sunshine produces evaporation rates that would surprise most people from wetter climates. Annual pan evaporation can exceed 50 inches along parts of the corridor, which is roughly three times the annual precipitation.

This creates a significant challenge for any stormwater facility that relies on a permanent water level. Constructed wetland ponds and retention ponds need a reliable water source to offset evaporation losses. If the water budget doesn't pencil out, the pond draws down during the summer, vegetation dies back, and the facility loses both its treatment function and its aesthetic value.

The MHFD criteria address this by generally favoring EDBs (which are dry between events) for most applications, with retention facilities reserved for situations where a sustainable water source can be demonstrated. If a client wants a permanent water feature as an amenity, the conversation needs to start with the water balance, not the landscape plan.

This same evaporation dynamic also affects seed establishment for final stabilization. A site seeded in late fall may not germinate until the following spring, and even then, supplemental irrigation may be needed through the first growing season to achieve the vegetative cover required for permit termination. Colorado's growing season is short and the available moisture window is narrow. Plan stabilization timing carefully, or budget for carrying your CDPS permit through the winter and into the next growing season.

Floodplain Complexity

The Front Range has a well-documented history of catastrophic flooding, and the regulatory response to that history shapes how every development project deals with drainage. MHFD maintains detailed floodplain mapping and master plans for major drainageways across the metro region, and local jurisdictions enforce floodplain development standards that can significantly constrain what you can build and where.

If your project is located near a mapped floodplain, on or adjacent to a major drainageway, or within a mapped flood hazard area, your stormwater design will need to account for floodplain regulations in addition to the standard water quality and detention requirements. This can include no-rise certifications, floodplain fill mitigation, and channel setback requirements that affect your buildable area.

The September 2013 floods along the Front Range led to significant updates in how Colorado approaches flood risk, and MHFD has incorporated lessons from that event into their criteria and master planning. If you're working with floodplain data that predates 2013, make sure you're using the most current effective mapping and any Letters of Map Change (LOMCs) that may have been issued for your area.

The Regulatory Layer Cake

I've touched on this in other articles, but it's worth emphasizing here because the layered regulatory structure is itself one of Colorado's unique stormwater challenges.

A single construction project on the Front Range might be subject to the CDPS state permit (COR400000), a local MS4 construction stormwater ordinance, MHFD drainage criteria, a Cherry Creek Basin Regulation 72 overlay, local floodplain regulations, and potentially FEMA requirements if the project affects mapped flood hazard areas. Each layer has its own standards, terminology, submittal requirements, and review process.

The projects that navigate this successfully are the ones that identify all applicable requirements at the very beginning of design, not halfway through plan review when a reviewer flags something the team didn't know about. A pre-application meeting with your local jurisdiction, an early conversation with MHFD if your project involves a major drainageway, and a thorough review of all applicable overlay regulations should happen before you draw the first line on your grading plan.

Why Local Experience Matters

Every point in this article comes back to the same theme: Colorado's Front Range has conditions that require local knowledge. A stormwater engineer who's worked in Denver for ten years will intuitively account for afternoon thunderstorms, expansive clay, evaporation rates, and the MHFD criteria because they've designed through those conditions dozens of times. An engineer who's technically skilled but has always worked in a different climate will need to learn those lessons on your project.

That's not a knock on talent from elsewhere. It's an acknowledgment that stormwater management is inherently local, and the Front Range has enough unique characteristics that local experience is worth prioritizing when you're selecting your project team.