I saw a recent proposal from a town looking to increase the use of native plants in site plan approvals. The intent is straightforward and reasonable: improve habitat, reduce invasive species, and promote a healthier ecosystem.

The proposed approach, however, follows a pattern I’ve seen before. A good environmental idea gets translated into a set of precise-sounding requirements that may not hold up particularly well once they leave the page and enter the real world.

In this case, the proposal sets percentage-based requirements for plantings:

* 100% of trees
* 85% of shrubs
* 75% of perennials
* and so on

At first glance, that sounds like a clear and enforceable standard. But once you start thinking through how these rules would actually function over time, some cracks begin to show.

The problem with precision

Percentages create the appearance of control, but landscapes are not static systems.  Plants die, others spread aggressively, maintenance changes over time, and eventually the property changes hands.

If a site is approved with 85% native shrubs, what happens five years later?

* If some native shrubs fail and non-natives persist or spread, is the site now out of compliance?
* Is someone responsible for counting shrubs over time?
* If so, who—and how often?

In many cases, requirements like these end up being checked once during the approval process and then gradually drift away from reality.

Scale matters more than site plans

There’s also a question of scale.

In an established town, most of the landscape already exists. A single development project, even a well-designed one, is only a small piece of that overall system.

Meanwhile, plant selection decisions made every day by homeowners, landscapers, and local nurseries likely shape the landscape far more over time than individual site plans ever will.

That doesn’t mean site plan standards are pointless. But it does raise a question: are they being asked to carry more weight than they realistically can?

The practical enforcement problem

It’s easy to write a requirement like “85% native shrubs.” It’s much harder to:

* verify consistently,
* maintain over time, and
* enforce fairly and predictably years later.

If a regulation can’t be meaningfully enforced, it often turns into either:

* a box-checking exercise during approvals, or
* a source of selective or inconsistent enforcement later on.

Neither outcome is particularly useful.

An alternative approach

If increasing native plant use is a real priority, it may make sense to pair site plan standards with approaches that operate where most planting decisions are actually being made.

For example:

* working with local nurseries to improve the availability of native species,
* creating incentives for homeowners to replace invasive or problematic plants, or
* offering voluntary programs and guidance that make better choices easier to make.

These approaches don’t replace regulation, but they may produce more meaningful results at the scale where change actually happens.

A better way to get to better rules

I saw a very different approach while working on a “general permit” for public works projects in a small town.

Instead of jumping directly into drafting language, I spent time gathering examples of how other towns handled similar situations. We reviewed different approaches, discussed the tradeoffs, and worked through the implications as a group.

The commission didn’t just react to a completed draft. They helped shape the framework before the writing even started.

By the time we sat down to actually draft the permit, the structure was already mostly understood. The final document ended up being more straightforward, easier to apply, and better understood by the people responsible for using it.

Just as importantly, everyone had a hand in building it.

Timing matters

One thing I’ve learned is that feedback is most useful before a proposal fully takes shape.

Once a commission has already invested significant time developing a draft, the conversation often shifts from:

* “What’s the best approach?”

to:

* “How do we refine what we already created?”

At that point, even thoughtful feedback can start to feel more like criticism than collaboration.

Better outcomes usually come from:

* introducing ideas early,
* presenting options instead of conclusions, and
* allowing the people responsible for the regulation to help shape and take ownership of the final approach.

Closing thought

Increasing the use of native plants is a worthwhile goal.  The difficult part isn’t identifying the goal. It’s translating that goal into something that:

* reflects how landscapes actually behave,
* can be applied consistently, and
* leads to meaningful change over time.

That translation step is where good ideas either become useful tools—or well-intentioned rules that look clear on paper but don’t quite work in practice.