First off, let’s break down Low Impact Development. It’s like choosing a salad over fries—it’s good for you, but it can get complicated. This idea started in the 1990s in Prince George’s County, Maryland. It was a move away from old ways of handling rainwater.
This method of stormwater management wonders what if we made landscapes like forests again. The idea is to slow down water, soak it in, and clean it up. It’s like making a site do its own magic with water.
The aim is more than just following rules. It’s about making nature work for us. This means less runoff, cleaner water, and recharging our aquifers. The tools are simple yet effective, like bioretention cells and rain-drinking pavers. But these common LID codes turn simple ideas into strict rules.
Variations by jurisdiction
The basics of Low Impact Development are the same everywhere. But how they’re applied varies greatly from place to place. It’s like each area has its own language.
Local development codes are like living documents with their own quirks. They change slowly and often hold old ideas. The EPA says these codes can actually block new ideas.
Old rules, like big streets, hold back new ideas. It’s like trying to watch a high-definition movie on an old computer. The idea is good, but the old system gets in the way.
In Washington, the rules are complex. Each area follows its own guidebook. This means different rules for different places.
Every place has its own twist on the rules. Some are smart, others are strange. Bainbridge Island starts LID rules earlier than others. Edmonds has special rules for old sites.
Why does this matter? If you follow state rules, you’re only part way there. Local rules can change everything. What’s good in one place might be bad in another.
Knowing the local rules is key. It’s not just about following a manual. You need to know the local details. Some places are welcoming to LID, while others are not.
Some places have old rules that don’t fit with LID. Their municipal standards are outdated. Getting through these rules can be tough.
The rules for LID vary a lot. It’s like navigating a medieval kingdom. Each place has its own rules and officials. Success depends on knowing the local culture and rules.
Navigating conflicting requirements
Welcome to the world of bureaucratic battles. Your sustainable drainage plan must face off against old, outdated regulations. The LID design standards clash with stormwater codes and other rules. These include parking, landscaping, fire access, and street design rules from the past.
One project can deal with 15 to 20 code conflicts. That lovely rain garden might not meet parking island rules. Permeable pavers could run into sidewalk slope standards. This is the everyday challenge of water management facing old regulations.
The idea that staff can easily waive these conflicts is a dangerous myth. Variance processes are like quicksand. They’re expensive, slow, and full of uncertainty. Most developers will remove LID features to avoid these issues.
Passing a stormwater ordinance is like putting a new engine in a car with flat tires. If other codes block design compliance, you won’t get anywhere. The EPA’s Barrier Busters initiative shows how conflicts are everywhere in codes.
To escape this, you need to be a barrier buster. This means finding conflicts early, not just during review. It’s about seeing each conflict as a chance to update old rules.
The right approach is to review and update codes. Look at common issues like:
- Bufferyard rules that require hard surfaces
- Setback rules that block stormwater features
- Parking island specs that don’t allow infiltration
- Street standards that prioritize speed over absorption
Your goal is to get permission through new language. Offer code-friendly solutions that will help future projects too. This is true barrier busting.
| Conflict Type | Traditional Approach | Barrier Busting Strategy | Outcome |
|---|---|---|---|
| Parking Lot Islands | Request variance for curb cuts | Propose new language allowing “curb cuts or alternative drainage inlets” | Code change benefits all future projects |
| Landscaping Buffers | Accept turf grass requirement | Demonstrate native plants meet “vegetated cover” intent better | Expanded plant lists for stormwater features |
| Street Width Standards | Narrow lanes only with fire department approval | Show permeable shoulders reduce runoff without compromising access | Revised street typologies include LID options |
| Setback Requirements | Move rain garden to less optimal location | Argue stormwater features enhance “open space” intent of setbacks | Setbacks redefined to include green infrastructure |
This isn’t just about winning one battle. It’s about changing the game. When you find a conflict, document it well. Show how old codes prevent better outcomes. Offer clear, enforceable alternatives.
The best barrier busting comes from working together, not fighting. The Houston Land/Water Sustainability Forum shows how. Early collaboration can turn enemies into allies. Fire safety, public works, and planning all have valid concerns. Show how LID design standards can meet these needs while improving water quality.
Remember, every code conflict is a relic from the past. It’s a fossil of a solved problem that no longer fits today’s needs. Your challenge is part archaeology, part diplomacy, and part visioning. Don’t just navigate these conflicts. Help break them down.
Documentation strategies
Your permit package is more than just paperwork. It’s a story where rainwater is the hero and your design is the twist. It’s like your legal brief in a court of approval, where judges are busy and skeptical.
The WBDG process is like jazz, not a symphony. You start with goals, then evaluate the site and create plans. This process is dynamic, not just following steps. It’s about dancing with the data as it comes.
Your stormwater management plans should be like a detective story. Follow the water from rooftop to groundwater. Show the treatment steps and answer all possible questions.
Begin with a master plan that’s easy to understand. Use the language of the reviewers. Reference the codes you’re following and adapting, with your solutions. This shows you’re not just checking boxes, but engaging with the rules.
Technical manuals are your key to understanding. The Washington guidebook points to useful resources. Use standard detail sheets from cities like Seattle and Renton. This builds trust with the reviewers.
Here’s a table comparing traditional vs. narrative documentation:
| Element | Traditional Submission | Narrative Strategy |
|---|---|---|
| Master Plan | Technical drawings only | Story of water flow with visual overlays |
| Code References | List of complied sections | Dialogue with adapting sections highlighted |
| Standard Details | Generic manufacturer specs | Local municipal sheets integrated |
| Reviewer Experience | Checklist verification | Collaborative journey through site |
Good documentation makes you a collaborator, not just a supplicant. It turns the permit process into a shared problem-solving session. When you show you’ve done your homework and speak their language, you’re educating.
This approach is what forward-thinking municipalities want. For example, Nashville’s water department offers resources for low-impact development. They’re looking for partners, not just applicants.
Your permit strategies should include “the preemptive FAQ.” Anticipate every question and document every assumption. This isn’t defensive design—it’s confident, transparent engineering that tells a great story about water.
Reviewer expectations
Here’s the final challenge of your LID quest. The plan review isn’t just a faceless system. It’s a person, often buzzing with caffeine, ready to check your work against local codes. Your goal is to meet their reviewer expectations before they check you.
Many municipal staff are not fans of LID. They stick to the rules. Surprise them, and you might lose. The Houston LWS Forum notes show that a professional look boosts your credibility. Make sure your documents fill their knowledge gaps. It’s like a quiet lesson.
See your bioswale as the best way to meet code goals. Talk about local successes. Share maintenance guides early. This way, you’re not just applying. You’re working together.
The approval process relies on this teamwork. Guides like EPCOR’s LID Design Guide suggest talking to city departments early. Make your application so clear and strong that approval seems inevitable. You’re not just following LID design standards. You’re showing you get why they matter.
When you meet reviewers where they are, you get more than approval. You pave the way for future projects. That’s the real victory.