The comment was submitted two days before the deadline. I saved the confirmation email beside the old permit documents. The dispute over the pond had taught us how to respond to a threat. Now we were learning how to prevent a bad rule from creating the next one.
The county held its hearing in a room that was smaller than the high school auditorium but just as crowded. Developers sat along one wall. Residents and watershed volunteers filled the chairs opposite them. The county's consultant presented a series of charts showing projected reductions in runoff costs.
When our turn came, Mara explained the double-counting concern. I displayed the watershed diagram. Then the consultant asked whether our interpretation would make it impossible for private owners to receive any credit for preserving natural features.
“No,” I said. “It would make the credit depend on what the feature actually does beyond the baseline condition. If a wetland already provides storage, that existing service should not be sold twice under two different labels. If an owner restores or improves its function, the added benefit can be measured and considered.”
The consultant looked at the diagram again. “That is a more complicated calculation.”
“It is,” I said. “The water is complicated.”
A few people laughed, but the chair asked us to continue. We proposed a separate category for natural features, baseline documentation before credits were issued, and a requirement that watershed-scale impacts be considered where facilities were connected.
A developer representative argued that the added review would increase costs and discourage conservation. The district hydrologist responded that a clear baseline would protect responsible owners as well as the public. Without it, disputes would be inevitable.
The hearing ended without a decision. As we packed our papers, a county commissioner approached me.
“Your group has become difficult to surprise,” she said.
I thought about that. “We've had practice.”
The revised fee policy arrived six weeks later. It did not adopt every recommendation, but it separated constructed detention facilities from natural wetlands and required baseline documentation before a credit could be awarded for restoration. It also required the county to consider downstream effects when a facility was part of a connected drainage system.
The county described the changes as technical clarifications. We knew they were more than that. They meant a natural feature could no longer be treated as a convenient number detached from its place in the watershed.
At the next committee meeting, we reviewed the policy and agreed that it was workable. Then Denise asked whether we should send a thank-you note to the county staff who had helped.
Paul raised an eyebrow. “Are we thanking them for fixing something they almost got wrong?”
“We can do both,” Denise said.
We sent the note. It acknowledged the changes and asked that the county publish an annual summary of credits issued under the new policy. The request was accepted. It was a small example of a habit we had developed: when an institution corrected a mistake, we recorded that too.
The old version of me might have considered that generosity unnecessary. The person I had become understood that public trust required an accurate account of failures and improvements alike.
In early spring, I received a letter from a woman named Evelyn Price. She lived in a town two counties away and had found the Blue Heron story through the state training presentation. Her neighborhood association had ordered the removal of a line of trees beside a drainage channel. The association claimed the trees blocked maintenance access. Residents believed the channel was a seasonal stream, but nobody had a current map.
Evelyn asked whether I could tell her what to do.
I read the letter twice before answering. I could not give legal advice, and I did not know the facts of her property. I wrote back with a short list of practical first steps: obtain the recorded plat and easements, request the relevant drainage and environmental records, photograph existing conditions from places where she had permission to stand, and ask the appropriate agency whether a formal review was needed before work began.
I also sent her the public field-day guide and the sample observation log. I warned her not to trespass or confront contractors, and to keep every communication factual.
A week later, she wrote again. The tree work had been paused while the county checked its records. She thanked me for helping her slow the situation down.
I printed her note and placed it in the folder. Blue Heron had not become a universal answer. It had become a reason someone else knew which questions to ask.
Evelyn's case stayed with me because it revealed a danger in the way our story was being told. People liked the dramatic version: an association issued an order, a resident fought back, and the pond survived. That version was easy to repeat, but it made the outcome seem like a matter of courage alone.